Paging system for multi-network terminals
Abstract
Terminals which can communicate with more than one network in a time-shared manner must, on being called from such a network, be paged by said network. It can occur, however, that a terminal does not receive a paging message which was destined for it because it was engaged with another network at just the same time. By letting each terminal pass to the network with which it maintains a communication session the points in time at which the terminal can successfully receive and process paging messages, the problem is solved. The terminal thus functions as master' and the networks function as slave'.

Term
Term ended
Projected expiry passed 29 October 2016, 9.9 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
6 claims: 1 independent, 5 dependent
- 1Communication system, comprising networks and terminals, provided with means for initiating and maintaining communication sessions with each other, in which one terminal can simultaneously initiate and maintain time-shared communication sessions with several networks, and in which a network can transmit to a terminal, with which a communication session is maintained, system messages relating to said communication session, characterised in that the terminal transfers parameters to the network, relating to the points in time at which the said system messages can be received by said terminal.
36 paragraphs, as filed
A.
Background of the invention
The invention relates to a communication system, comprising networks and terminals, provided with means for initiating and maintaining communication sessions with each other, in which one terminal can simultaneously initiate and maintain time-shared communication sessions with several networks, and in which a network can transmit system messages, related to that communication session, to a terminal with which it maintains a communication session. In particular, the future Universal Mobile Telecommunications System (UMTS) is borne in mind.
A terminal as mentioned above can be available to several users simultaneously and also simultaneously form the connection between said users and several networks, for example a mobile enterprise network and the public mobile network. The users can choose domicile at a certain terminal and register themselves for certain services, for example voice, data or facsimile transmission, at one or more networks with which the terminal has a connection. Not only human users, but services (servers) also can be accommodated at a terminal.
As soon as a call for a registered user occurs in a network, the terminal where said user has chosen domicile must be called. It is suggested that paging be used for that purpose, the network transmitting the identification code for the terminal being sought, the user and the service chosen by the user, in the assumption that the terminal will react thereupon.
Problematic is that, since the terminal is connected to several networks on a time-sharing basis, the probability exists that a paging message is not received by the terminal due to it being engaged with "reading out" another network, or with exchanging information with another network, at the time the paging message is transmitted.
A possible solution is to provide terminals with several receivers operating in parallel, one for each network, which continuously read out the paging channels of all networks. That implies an unacceptable extension of the hardware of the (mobile) terminals, however. Another possibility is to provide for the synchronisation of the paging signals of the various networks, and to agree on which networks transmit their paging messages in which time slots. This solution is unattractive because that would encroach upon the independence of the networks. Another solution, the repetitive transmission of paging messages, is unacceptable because of the relatively heavy burden which the paging function would place on the transmission capacity, while it would neither then be completely guaranteed that the paging messages are always received by the terminal being sought. Another option still, transmitting all paging messages via one separate paging network, demands rather heavy additional means, while the mutual independence of the networks, an important issue in UMTS, would be encroached upon.
B.
Summary of the invention
The invention provides a solution of the paging problem without the objections mentioned. Briefly stated, the invention involves that each terminal itself passes on to the networks to which it is connected the points in time when the terminal can be successfully paged. The invention is based on the insight that only the terminals themselves have an overview of the networks with which they are connected. The networks lack said overview. As far as the paging points in time are concerned, therefore, the terminals should function as <img file="EP0785692A2_D0001.tif" />master<i>'</i> and the networks as <img file="EP0785692A2_D0002.tif" />slaves<i>'</i>.
In order to obtain a workable situation for the networks as well as for the terminals, the paging messages are transmitted per network during transmission blocks which have a fixed period and a fixed block time. It is assumed that the block periods and block times of the networks with which the terminal is connected are known at the terminal. On the basis of said network parameters, the terminal transfers the paging points in time it requires at the beginning of a session, for example, "transmit paging messages every 12 paging blocks, starting with paging block 3 as of now". The network stores said parameters with the other parameters of said terminal (terminal identifier, terminal channel and identifiers and such of the users domiciled at said terminal). These aspects are further elaborated below.
C.
Examples of embodiment
Fig. 1 shows a diagrammatic view of a communication system in which the invention is applicable. The figure shows a terminal T at which various users, A, B and C, choose domicile. They do this by reporting themselves at said terminal and entering their data. That can be done, for example, with a smart card and/or by manual data entry. In this connection it is also made known which network or which networks the user wishes to use, and for which service (telephone, data, facsimile, EDI, etc.). Said data are stored in a buffer ("users&netw.") in the terminal. User A, for example, will wish to use data network I simultaneously for receiving or transmitting EDI messages, while he/she wishes to use enterprise network II for telephony. User B wishes to use only the public telephone network III, while user C wishes to use data network I and the public telephone network. In order to successfully establish communication sessions with the selected networks, the terminal will need to know the necessary parameters, such as entry address and protocol, of said networks. Said parameters are buffered in the terminal ("Network parameters").
If said terminal is connected to a fixed physical network port, calls from within the network to the terminal can be simply routed to said network port (for example in a conventional fixed telephone network). This becomes different if the terminal can not be accessed via a fixed network port, as is the case in networks for mobile communication (although not only in mobile networks, but also in advanced, non-wireless "UPT" networks). In said cases, the terminal for which the message is destined must be called by a general paging message to contact the network. It was discussed above that in the case of a simultaneous connection with several networks, that is, the situation in which a terminal is registered as an accessible terminal in said networks, the terminal, however, is not able to pay continuous attention to any paging calls from within a network. Calls to a terminal should therefore only be transmitted if said terminal is prepared for receiving and processing them.
After the users have registered themselves at the terminal, the terminal establishes a connection with the various networks selected by the users and has itself (that is to say, an identifier) registered in said networks as an accessible terminal, including the data (identifiers and such) of the users who wish to be able to use said networks for certain services (user/service identifiers). In the present example, the terminal passes to network I (data network) the identifiers of users A and C, to the network II (enterprise telephone network) those of user B, and to network III (public telephone network) those of users B and C. In this way, calls from within the networks I, II and III for the users A, B and C can be transferred to terminal T. On a call, for example, from within network III for user B, network III will consult its registered data and find that user B is registered at terminal T. Thereupon a paging message for terminal T is transmitted. As soon as the terminal detects that a paging message with its identifier has been transmitted (or the user/service identifier of a user who has chosen domicile at said terminal for using, via said terminal, a service offered by the network), the terminal transmits a response code to the network III and the call can be routed to the terminal. User B is notified by the terminal T and can subsequently answer the call.
On registering itself in a network, the terminal should also transfer parameters which indicate at which points in time, or within which periods, the terminal can be successfully paged by the network. Said <img file="EP0785692A2_D0003.tif" />paging time<i>'</i> parameters are calculated within the terminal by a control unit (<img file="EP0785692A2_D0004.tif" />Control<i>'</i>) on the basis of the networks where the terminal has already registered itself and the paging time parameters already used in that regard, and of the optional paging time parameters which are known from the <img file="EP0785692A2_D0005.tif" />new<i>'</i> network. As far as the latter is concerned, it is possible to make use of a file of optional paging time parameters of all networks, which is already present in the terminal, with which the terminal could establish a connection. In order to be able to make use of the most current information, however, said optional parameters are preferably downloaded from the network upon the initialisation of the session or periodically, during the session. Besides said parameters always being correct, a redundant buffering in said (each) terminal of optional paging time parameters of all networks falling under consideration is also prevented.
The calculation of the paging time parameters which are to transferred to the <img file="EP0785692A2_D0006.tif" />new<i>'</i> network is performed as follows:
It is assumed that the network transmits the paging messages for the various terminals in a block, and that the mutual distance between said blocks is fixed. The mutual block distance is represented by a, and the block length by l. The terminal should indicate in which block it wishes to be paged. The problem is to determine the paging period for each network such that paging collision does not occur.
It is observed that the paging parameters constantly require revision upon changes in terminal/network combinations.
In the algorithm elaborated hereafter, N represents the number of networks, a<sub>i</sub> (a<sub>i</sub> ≥ a<sub>i+1</sub>) represents the distance between the paging blocks ("block distance"), and l<sub>i</sub> represents the length of the paging block ("block length") for network i. The time to the beginning of the next block is represented by d<sub>i</sub>, and the time the terminal requires to switch from one network to the other ("change-over switching time") is represented by s.
First of all, the number of blocks after which network i can periodically page the terminal ("paging period"), represented by p<sub>i</sub>, and the first block n<sub>i</sub> falling under consideration, must be calculated. (If n<sub>i</sub> = 0, the period starts at the next block; if n<sub>i</sub> = 1, the period starts at the second block, etc.)
The calculation of n<sub>i</sub> is performed as follows: Assume that n<sub>1</sub> = 0 and T = d<sub>1</sub> + l<sub>1</sub> + s. Then for i = 1, 2, 3, 4, ..., N determine n<sub>i</sub> such that: <ul id="ul0001" list-style="none" compact="compact"><li>1. d<sub>i</sub> + (n<sub>i</sub> - 1) * a<sub>i</sub> < T ≤ d<sub>i</sub> + n<sub>i</sub>*a<sub>i</sub></li><li>2. T = d<sub>i</sub> + n<sub>i</sub>*a<sub>i</sub> + l<sub>i</sub> + s ("shifting up of the time").</li></ul>
Hereafter p<sub>i</sub> must be calculated: Determine P as first multiple of the least common multiple of (a<sub>i</sub>, ......, a<sub>n</sub>) such that P ≥ T - d<sub>1</sub>. For each network, p<sub>i</sub> is now determined from p<sub>i</sub> = P / a<sub>i</sub>.
The foregoing algorithm ensures that the paging blocks are distributed such that they do not overlap each other and that the terminal has enough time to switch over from one network to the other. By choosing the period such that it is a multiple of the greatest common divisor of the distances, it is achieved that network blocks do not shift with respect to each other. If this is nevertheless the case because, for example, the network clocks are not completely synchronised, the terminal will notice that and carry out the algorithm again if the paging blocks start overlapping each other.
On transferring the n<sub>i</sub> values to the networks, the fact should be taken into account that the actual time has progressed somewhat since the moment the algorithm started. If a network has already transmitted one or more paging blocks in this period of time, these must be subtracted from the n<sub>i</sub> value (modulo p<sub>i</sub>).
For the determination by the network of the block in which a terminal can be paged, the networks must count their own paging blocks. Thus, upon the transmission of a paging block, a counter C is incremented by one. If a terminal t indicates that it can be successfully paged with a period of p<sub>t</sub>, starting with block n<sub>t</sub>, the following is carried out in the network: Determine C<sub>t</sub> = C + n<sub>t</sub> and store C<sub>t</sub> and p<sub>t</sub> with the data relating to terminal t. If a paging message must now be transmitted to terminal t, the network determines the next suitable paging block as follows: <i>(div((C - C</i><sub><i>i</i></sub><i>), p</i><sub><i>t</i></sub><i>) + 1)* p</i><sub><i>t</i></sub><i> + C</i><sub><i>t</i></sub><i> (div</i> meaning integer division, that is, rounded off to the first lower integer number.
It is observed that if the distance a between the blocks can be freely determined by the networks, the value of P can become very large, so that the period p<sub>t</sub> also becomes very large. This results in a fairly large delay in paging - and thus in the building up of the connection. This can be prevented by forcing a fixed blocking distance a on all networks.
Below, finally, another example is elaborated in which a terminal determines at which moments it wishes to be paged by three different networks. In the terminal, the above algorithm is used.
The terminal has a few users who are registered in total in three networks: N1, N2 and N3. The values for the distance a and the length l of the paging blocks of the respective networks are listed in the table below. Therein is also listed after how many time units d the next paging block starts. <tables id="tabl0001" num="0001"><table frame="all"><tgroup cols="4" colsep="1" rowsep="0"><colspec colnum="1" colname="col1" colwidth="39.37mm" /><colspec colnum="2" colname="col2" colwidth="39.37mm" /><colspec colnum="3" colname="col3" colwidth="39.37mm" /><colspec colnum="4" colname="col4" colwidth="39.37mm" /><thead valign="top"><row rowsep="1"><entry namest="col1" nameend="col1" align="center">Network</entry><entry namest="col2" nameend="col2" align="left">a</entry><entry namest="col3" nameend="col3" align="center">l</entry><entry namest="col4" nameend="col4" align="center">d</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">N1</entry><entry namest="col2" nameend="col2" align="right">20</entry><entry namest="col3" nameend="col3" align="right">3</entry><entry namest="col4" nameend="col4" align="right">5</entry></row><row><entry namest="col1" nameend="col1" align="left">N2</entry><entry namest="col2" nameend="col2" align="right">12</entry><entry namest="col3" nameend="col3" align="right">8</entry><entry namest="col4" nameend="col4" align="right">3</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">N3</entry><entry namest="col2" nameend="col2" align="right">10</entry><entry namest="col3" nameend="col3" align="right">2</entry><entry namest="col4" nameend="col4" align="right">2</entry></row></tbody></tgroup></table></tables> The change-over switching time of the terminal 1 time unit: s = 1.
The calculation starts by determining the n<sub>i</sub> values. Assume first that n<sub>i</sub> = 0 and determine the following time T = d<sub>1</sub> + l<sub>1</sub> + s = 5 + 3 + 1 = 9. Network 1 may now page in the time indicated in Fig. 2A, namely from point in time 5 (d<sub>1</sub>) to point in time 8 (d<sub>i</sub> + 1).
Hereafter an iterative process follows for i = 2 and i = 3: _i = 2: determine n<sub>2</sub> such that 3 + (n<sub>2</sub> - 1)*12 < 9 ≤ 3 + n<sub>2</sub>*12; the result is n<sub>2</sub> = 1. The time subsequently shifts up to after this paging block: T = 3 + 1*12 + 8 + 1 = 24. Network 2 may thus page from point in time 15 up to, but not including, point in time 23. _i = 3: determine n<sub>3</sub> such that 2 + (n<sub>3</sub> - 1)*10 < 24 ≤ 2 + n<sub>3</sub>*10; the result is n<sub>3</sub> = 3. The time subsequently shifts up to after this paging block: T = 2 + 3*10 + 2 + 1 = 35. Network 3 may thus page from point in time 32 up to, but not including, point in time 34.
Now the value for p<sub>i</sub> must still be determined: - first determine P = l.c.m. (20, 12, 10) = 60, since 60 ≥ T - d = 35 - 5 = 30. The values for p<sub>i</sub> are now: p<sub>1</sub> = 60/20 = 3, p<sub>2</sub> = 60/12 = 5, and p<sub>3</sub> = 60/10 = 6.
D.
References
Leih, G.; Lensink, A.; Levelt, W.G. "The impact of multi-user terminals" RACE MOBILE Workshop, Amsterdam, May 1994
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO2013191925A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9148837B2 | Cited by | United States of America | Applicant |
| EP1527622B1 | Cited by | European Patent Office (EPO) | Examiner |
| EP1527622A2 | Cited by | European Patent Office (EPO) | Examiner |
| GB2283154A | Cites | United Kingdom | Search report |
| US4642758A | Cites | United States of America | Search report |
| WO9101615A1 | Cites | World Intellectual Property Organization (WIPO) | Search report |
15 members in 7 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 1001561 | Netherlands (Kingdom of the) | A | |
| 1001561 | Netherlands (Kingdom of the) | A | |
| 1001561 | Netherlands (Kingdom of the) | – | |
| 1001561 | – | – | – |
| NL19951001561 | – | – | – |
Members15
| Document | Office | Kind | |
|---|---|---|---|
| NL1001561C2 | Netherlands (Kingdom of the) | C2 | |
| EP0785692A2This record | European Patent Office (EPO) | A2 | |
| EP0785692A3 | European Patent Office (EPO) | A3 | |
| EP0785692B1 | European Patent Office (EPO) | B1 | |
| AT393511T | Austria | T | |
| ATE393511T1 | Austria | T1 | |
| DE69637508D1 | Germany | D1 | |
| EP1940121A2 | European Patent Office (EPO) | A2 | |
| EP1940122A2 | European Patent Office (EPO) | A2 | |
| PT785692E | Portugal | E | |
| DK0785692T3 | Denmark | T3 | |
| ES2306449T3 | Spain | T3 | |
| DE69637508T2 | Germany | T2 | |
| EP1940121A3 | European Patent Office (EPO) | A3 | |
| EP1940122A3 | European Patent Office (EPO) | A3 |
69 legal events, as 12 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Change of representativeR082 | R082 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Announcement of lapse in spainLapsedFD2A | FD2A | ES | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent expired after termination of 20 yearsExpiredPE20 | PE20 | GB | |
| Expiry of rightR071 | R071 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Ep patent has lapsedLapsedEUG | EUG | SE | |
| Lapsed because of non-payment of the annual feeLapsedV1 | V1 | NL | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Be: lapsedLapsedBERE | BERE | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Ep patent lapsedLapsedEBP | EBP | DK | |
| Annulment/lapse due to non-payment of fees, searched and examined patentLapsedLAPSE DUE TO NON-PAYMENT OF FEESMM4A | MM4A | PT | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Fr: translation filedET | ET | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Definitive protectionFG2A | FG2A | ES | |
| Ep patent validated in greeceEP | EP | GR | |
| Ep patent with danish claimsT3 | T3 | DK | |
| Translation of granted ep patentGrantedTRGR | TRGR | SE | |
| New agentNV | NV | CH | |
| Translation is availableAVAILABILITY OF NATIONAL TRANSLATIONSC4A | SC4A | PT | |
| European patents granted designating irelandGrantedLANGUAGE OF EP DOCUMENT: FRENCHFG4D | FG4D | IE | |
| Corresponds to:REF | REF | EP | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP3 | RAP3 | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 0785692
- Publication, DOCDB
- 0785692
- Publication, EPODOC
- EP0785692
- Application
- 96203014
- Application, DOCDB
- 96203014
- Application, EPODOC
- EP19960203014
Titles3
- German
- Rufsystem für Mehrnetz-Endgeräte
- English
- Paging system for multi-network terminals
- French
- Système de messagerie pour terminaux de réseaux multiples
Classification
- CPC, 8
- H04W8/245
- H04L12/5692
- H04W28/18
- H04W68/00
- H04W68/025
- H04W88/06
- H04W76/20
- H04W76/10
- IPC, 9
- H04L12 28
- H04L29 06
- H04W8 24
- H04W28 18
- H04W68 00
- H04W68 02
- H04W76 02
- H04W76 04
- H04W88 06
Designated states1
- Contracting states, 1
- Sweden