The present invention relates to a communications system supporting communication of data, which comprises a number of core networks with a plurality of core network functional server nodes, also called core nodes, and a number of radio access networks, each with a number of radio access network control nodes, also called control nodes, wherein at least some of the core nodes are arranged in a pool to, in common, control at least a number of control nodes supporting pooling of core nodes. The invention also relates to a core network functional server node, or a core node, used in a communication system supporting communication of data, for mobility (and session) management, and which forms part of a pool of core network functional server nodes which, in common, are able to serve at least one radio access network, or part of a radio access network, to which mobile stations can connect over radio access network control nodes. Still further the invention relates to a method for handling connection of a mobile station moving in a communication system supporting communication of data, and comprising a number of core networks with a plurality of core network functional server nodes, and a number of radio access networks, each with a number of radio access network control nodes, wherein at least some of the core nodes are arranged in a pool to, in common, control at least a number of radio access network control nodes supporting pooling of core nodes.
Communication systems, particularly wireless communication systems, supporting communication of data or packet data, provide access over a number of radio networks and comprise one or more core networks. Each radio network generally comprises radio network control means comprising a number of radio network control nodes controlling base stations to which user stations or mobile stations can be connected or attached. Generally a radio network control node is controlled by a core network functional server node, in the case of packet data a packet data support node, of a core network. For GPRS GSM/UMTS such a packet data support node is denoted an SGSN (Serving GPRS Support Node). Generally each core node, particularly SGSN, controls one or more radio network control nodes, i.e. it is responsible for such radio network control means, for example RNCs (Radio Network Controller) or BSCs (Base Station Controller). Generally it is fixed which SGSN controls which RNCs. This is often disadvantageous among others since an SGSN has to be dimensioned for the worst case, i.e. a number of subscribers may be roaming within the network in a similar manner at the same time, meaning that an SGSN has to be configured to have a lot of spare capacity, which only is used in such cases. During other circumstances it is a waste of resources. When a subscriber or a mobile station is roaming within the network such that the closest base station will be controlled by another radio network control node than the one he attached to, and the SGSN which is responsible for a particular radio network control node is statically configured, the responsibility for the connection will have to be taken over by another SGSN. This involves a lot of signalling, for example with the home location node of the subscriber or for updating purposes, which means a substantial load on the home location nodes. Furthermore it has been realized that it is very expensive and requires a lot of complicated configurational work to make reconfigurations and/or to add equipment in such systems. High costs are also involved when such a system needs to be built out or when servers are to be replaced by other servers or SGSNs e.g. in the case of malfunctioning. Moreover it is disadvantageous as far as load sharing and redundancy issues are concerned. For a subscriber who is roaming within the network or changes routing area, responsibility for such a subscriber by a core node will have to be transferred to other core nodes as the subscriber moves throughout the network. This leads to a lot of signalling between the core nodes and home location nodes of the subscriber in order to update involve nodes, for example HLR (Home Location Register) nodes, between concerned core nodes, e.g. SGSNs, and between concerned SGSN and GGSN (Gateway GPRS Support Node), which severely loads the nodes and requires a lot of signalling in general. Therefore the so called pooling concept has been introduced. The pooling concept relates to pooling of core network nodes. As referred to above, a subscriber or a mobile station moving from one routing area handled by for example one SGSN to another routing area handled by another SGSN, will trigger a so called Inter SGSN Routing Area Update (ISRAU). This is described in 3GPP TS 23.060, version 5.6.0, Release 5, section 6.9.1.2.2, Inter SGSN Routing Area Update, the content of which herewith is incorporated herein by reference.
In a pool an SGSN handles a much larger number of routing areas (shared by other SGSNs), and a mobile station or a roaming subscriber, can remain connected to one and the same SGSN as long as it is within the area covered by the pool. This means that a number of SGSNs are responsible for a number of routing areas, or a number of radio network control means, which they control in common and wherein particularly each SGSN is able to control any radio network control means within the pool. The pool concept for pooling of SGSNs and MSCs (Mobile Switching Centers) has been standardized in 3GPP TS 23.236, Release 5, which herewith also is incorporated herein by reference. Thus, when the pooling concept is implemented, a mobile station will remain connected or attached to one and the same SGSN as long as it is in the geographical area covered by the pool (unless the SGSN is to be taken down or malfunctioning or similar). The allocation of a mobile station to a particular SGSN in a pool can be done in different ways, it may for example be done arbitrarily or randomly, it may be done taking load sharing and/or redundancy into consideration, or consecutive attaching mobile stations may be allocated consecutive SGSNs etc. In principle any algorithm or method for allocating an SGSN (or an MSC) in a pool to a mobile station can be used.
However, not all radio access networks are, or will be, pool enabled, i.e. support pooling of core nodes, and the current development indicates that the GSM RANs will be pool enabled before the UMTS RANs. The situation may also occur that not all radio network control means, e.g. RNCs or BSCs, support the pooling concept even if belonging to one and the same radio access network, i.e. part(s) of a radio access network may support pooling, whereas other part(s) of the same radio access network do not.
Dual mode core nodes, for example dual mode SGSNs, which support for example both GSM and UMTS, are known. This means for example that a dual mode SGSN supporting both GSM and UMTS potentially could be connected to a GSM RAN that supports pooling i.e. the control nodes of which are pool enabled and to an UMTS RAN that is not pool enabled. Similar situations might also occur in multi-vendor scenarios when for example radio network control means, e.g. RNCs or BSCs, of one vendor support pooling whereas those of another do not. Moreover, in most cases UMTS coverage will be introduced as so called “hot spots” on top of existing GSM coverage. This is illustrated in
What is needed is therefore a system through which advantage can be taken under varying conditions of the pooling concept, i.e. the arrangement of a number of core nodes, such as SGSNs or MSCs, in a pool. Particularly a system is needed through which advantage of pooling can be taken when part of a radio access network, or radio network control nodes in a part of a radio access network is/are not pool enabled, i.e. do not support pooling of core nodes. A system is also needed through which advantage of pooling can be taken when different radio access networks are provided of which for example one does not support the pooling concept whereas another does. Particularly a system is needed through which the benefits of the pooling concept can be enjoyed in a mixed pool-enabled/non-pool-enabled radio access network environment. A system is also needed through which it gets possible to maintain a mobile station roaming in a network implementing the pooling concept connected to a core node at least under particular circumstances even if there are parts of the radio network or different radio access technologies which do not support pooling. Still further a system is needed through which signalling can be reduced in a network supporting or implementing the pooling concept. Particularly a system is needed through which signalling between core nodes and signalling between core nodes and home location nodes etc. can be reduced as compared to through known solutions. A system is also needed through which the costs can be lowered and bandwidth can be saved for example on links between a pool and home location nodes. Particularly a system is needed through which the benefits of the pooling concept can be increased and more flexibly be taken advantage of under different circumstances.
A core network functional server node (core node), e.g. in this case SGSN and MSC etc. or a packet data support node, is needed through which one or more of the above mentioned objects can be achieved. Still further a method as initially referred to is needed through which one or more of the above mentioned objects can be fulfilled.
Therefore a communication system as initially referred to is provided wherein, for a transition of a connection of a mobile station from a first core network functional server node, in the following denoted first control node not supporting pooling of core nodes, but served by a first core node belonging to a pool, to a second control node supporting pooling of core nodes, the mobile station is able to remain connected to said first core node forming part of the pool.
Particularly the core node comprises means for generating and allocating, to a mobile station connecting/attaching to a first core node, a temporary mobile station identity (temporary MS id) ((P)-TMSI), which temporary mobile station identity further is provided with a pool identification for identifying the core node in the pool to which the core node belongs, and said pool identification is included in a modified mobile station routing/location area update message. The temporary mobile station identity and pool identity is allocated to the mobile station irrespectively of whether the mobile station connects to a (radio network) control node which is pool enabled or not (as long as the core node controlling the control node forms part of the pool). When the mobile station moves from the coverage of the first control node controlled by a first core node to that of the second control node, said modified routing/location area update message including the pool identification is relayed to said first core node. Particularly said transition comprises an intra core node intersystem change. In a particular implementation at least one of the core nodes of the pool comprises a dual-/multimode core node supporting access over more than one radio access network implementing different radio access technologies.
According to one aspect of the present invention said first and second control nodes belong to the same radio access network, wherein a first part of said network does not support pooling and contains said first control node, whereas a second part of said radio access network supports pooling and contains said second control node. In particular implementations said core nodes comprise Serving GPRS Support Nodes (SGSNs) and the control nodes comprise Base Station Controllers (BSCs) for GSM communication and/or Radio Network Controllers (RNCs) for UMTS communication using WCDMA radio access technology.
In other implementations at least some of the core nodes comprise Mobile Switching Centers (MSC) for circuit switched communication, at least some of the control nodes comprising Base Station Controllers (BSCs).
In one implementation said first and second control nodes belong to the same radio access network comprising an UMTS access network or a GSM access network, and part of said UMTS or GSM radio access network does not support pooling of core nodes. In another implementation the first and second control nodes support different radio access technologies and belong to different radio access networks, the first core node comprising a dual access node. In one implementation the first control node is an UMTS RNC not supporting pooling and the second control node is a GSM BSC supporting pooling. In another implementation the first control node is a GSM BSC not supporting pooling whereas the second control node is a UMTS RNC supporting pooling. Advantageously the first core node of a pool allocates a temporary mobile station identity to a connecting/attaching mobile station irrespectively of whether the mobile station connects over a control node supporting pooling of core nodes or to a control node not supporting pooling of core nodes. Particularly the temporary mobile station identity comprises a ((P)-TMSI) modified in that a pool identification e.g. comprising a Network Resource Identification (NRI, Network Resource Identifier) is included. Particularly said pool identification, e.g. NRI, is included in a mobile station routing/location area update message provided to the second control node as the mobile station moves from the area covered by the first control node to that covered by the second control node. Particularly the first core node uses the Gb-flex/Iu-flex mechanism (cf. 3GPP TS 23.228, v.5.2.0., Release 5) for allocating a temporary mobile station identity comprising pool unique identity irrespectively of whether the radio access networks or part of networks are not Iu-flex/Gb-flex enabled.
Therefore the invention also provides a core network functional server node (core node) as initially referred to, which comprises means for, at the transition of a connection/attachment of a mobile station from a first control node not supporting pooling of core nodes to another, second, control node supporting pooling of core nodes, keeping the mobile station connected/attached to said first core node. Particularly said means comprises means for generating and allocating and using a received temporary mobile station identity further comprising a pool identification for identifying the core node in the pool to which a core node belongs. Particularly the temporary mobile station identity is generated and allocated irrespectively of whether the mobile station is connected/attached to a control node supporting pooling of core nodes or not. Particularly said temporary mobile station identity is contained in a routing/location area update message received/relayed from a second control node enabling keeping the mobile station connected to the (first) core node. Particularly a mobile station transition from a first to a second control node comprises an intra core-intersystem change. Particularly the first core node comprises a dual/multi-mode core node supporting access over more than one radio access network, wherein the at least two radio access networks implement different radio access technologies. Particularly the node comprises a Service GPRS Support Node (SGSN). Alternatively it comprises a Mobile Switching Center (MSC). Particularly the node uses the Gb-flex mechanism or the Iu-flex mechanism for allocating a modified temporary mobile identity (with pool identity) to a mobile station and the transition comprises an intra SGSN intersystem change.
The invention therefore also suggests a method as initially referred to, which comprises the step of; for a mobile station moving from a first routing/location area in which it is connected to a radio access network control node not supporting pooling of core nodes but served by a first core node forming part of the pool, to a second routing/location area controlled by a radio access network control node supporting pooling of core nodes, keeping the mobile station connected to said first core node at least until the mobile station enters a routing/location area controlled by a radio network control node not supporting pooling of core nodes. Particularly the method comprises the steps of; allocating a temporary mobile station identity provided with a pool identification to a mobile station connecting to a first radio network access control node served by a core node of the pool, irrespectively of whether the first radio access network control node supports pooling of server nodes or not; including the pool identification in the message relating to change/updating of routing/location area when the mobile station moves to a routing/location area covered by a second radio access network control node supporting pooling of core nodes; relaying the routing/location area change/updating message to the first core node.
Particularly the first and second radio access network control nodes belong to the same radio access network and implement the same radio access technology. Particularly the first core node comprises a dual/multimode access node supporting at least two radio access technologies. In one implementation the first control node is an UMTS RNC and the second control node is a GSM BSC. In an alternative implementation the first control node is a GSM BSC whereas the second control node is an UMTS RNC. Particularly the first and second core nodes are SGSNs. In an alternative implementation said first and second core nodes comprise mobile switching centers (MSC).
The invention will in the following be more thoroughly described, in a non-limiting manner, and with reference to the accompanying drawings, in which:
However, in this particular embodiment RAN-2, or the control node 211, does not support pooling of core nodes, i.e. it is not pool enabled. RAN-2 control node 211 can in this embodiment only be controlled by dual mode core node 21. RAN-1 control node 111 here controls location/routing (LA/RA) areas 311, LA/RA 321, whereas RAN-1 control node 121 controls routing area LA/RA 341 and LA/RA 33. RAN-2 control node 211 controls LA/RA 411. It is here supposed that a mobile station MS is moving through the network. Upon entering the common pool area served by core nodes included in the core node pool 10, it is here supposed that it enters LA/RA 311 handled by RAN-1111. Since RAN-1 control node 111 is a pool enabled control node, any one of core nodes 11-51 is able to control RAN-1 control node 111, or the mobile station MS. Which core node that is selected depends on the used algorithm, e.g. taking load sharing into consideration or an arbitrary core node can be selected. Here it is supposed that core node 31 has been selected. MS then remains connected to CN 31 when it moves through LA/RA 311 and LA/RA 321. However the mobile station leaves LA/RA 321, and at II it enters routing area LA/RA 411 controlled by RAN-2 control node 211, which is not pool enabled. This transition will trigger an ISRAU as standardized in 3GPP TS 23.060, Section 6.9.1.2.2 describing the ISRAU procedure and the MS will be transferred to dual mode core node CN 21 instead, which always handles RAN-2 control node 211. This is here the only node that can control RAN-2 control node. However, the MS proceeds through the network and at III leaves LA/RA 411 to enter LA/RA 341 handled by RAN-1 control node 121. RAN-1 control node 121 however is pool enabled. This means that the MS can stay connected to the preceding core node which was dual mode core node 21 and instead of an ISRAU the transition III comprises an intra core node inter-system change. This is possible since, when the mobile station connects/attaches at I, wherein a connect/attach request is received from MS in RAN-1 control node 111, and when core node 31 has been selected, core node 31 allocates a temporary mobile station identity, e.g. ((P)-TMSI) to the mobile station which includes a unique identity of the core node within the core node pool 10 which is unique for that pool. This identity may for example comprise a network resource identity, NRI, which is included as a part of the, here by core node 31, generated and allocated mobile station temporary identity. This makes it possible when the MS moves from the coverage of RAN-1 to the coverage of RAN-2, and from the coverage of RAN-2 to the coverage of RAN-1, for RAN-1 control node 121 to find the unique pool core node identity, e.g. NRI, in the MS routing area update message, and to relay this message to the core node to which the mobile station previously was connected, in this case the dual mode core node 21. Thus, when the mobile station returns to a control node that is pool enabled, the MS can remain connected to the same core node as it was connected to when it was under control of a non-pool enabled control node. Although, in this particular embodiment the MS first attached/connected to a control node (111) that was pool enabled, in which case it always would be allocated a temporary MS identity with information about the pool identity, also in case a mobile station first connected/attached to a control node which was not pool enabled, also the unique core node identity within the pool would have been added, enabling the MS to remain with the preceding core node when moving from a control node which is not pool enabled, to a pool enabled control node, according to the inventive concept. This means that for a considerable number of the transitions between a non-core enabled radio access network and a core enabled radio access network, no ISRAUs will be due, which means that the signalling between the core nodes within the pool will be considerably reduced as well as the signalling between the pooled nodes and other network nodes such as switching nodes, gateway nodes and home location nodes will be considerably reduced.
Subsequently, it is supposed that, in this case, an ISRAU was required and that there was a change of SGSNs from SGSN to the dual access SGSN. Below the dashed line, it is supposed that the mobile station leaves the hot spot. The MS sends a routing area update request (including the P-TMSI with NRI received from RNC) to the relevant BSC, 1′. The BSC then sends a routing area update request to the dual access SGSN, since information to that effect was given by NRI, 2′. The dual access SGSN then sends a routing area update accept (with P-TMSI with NRI) to the BSC, 3′, which subsequently sends a routing area update accept with P-TMSI with NRI to the mobile station, 4′. Thus, when leaving the hot spot, no SGSN change is required.
At a later stage it is supposed that the MS changes routing area RA, as indicated through the dashed line in the Figure. Thus, the MS changes routing area and sends a routing area update request with P-TMSI with NRI to, here, RNC 2 belonging to the same radio access network RAN 1 as RNC 1. It is then examined if RNC 2 is pool enabled, 105. If not, the routing area update request is sent to the SGSN controlling RNC 2, e.g. SGSN X3, 105A. If, however, RNC 2 is pool enabled, RNC 2 uses NRI to send the routing area update request to SGSN X1 (or X2), 106. SGSN X1/X2 then sends a routing area update accept (on condition that it accepts), with P-TMSI with NRI to RNC 2, 107. RNC 2 forwards the routing area update accept to the MS, 108. It should be clear that this flow shows one particular plausible scenario, the important thing being that the unique pool identity is generated together with P-TMSI and provided irrespectively of whether an MS connects to, here, an RNC which is pool enabled or not, and that this information subsequently can be used when a mobile station leaves an, here, RNC which is not pool enabled. It thus relates to an implementation in which a part of one and the same radio access network does not support pooling of core nodes, here particularly SGSNs.
Subsequently it is supposed that the mobile station changes routing areas from RA 1 to RA 3 controlled by RNC 4 of the other radio access network RAN 2. A routing area update request with P-TMSI with NRI is then sent to (here) RNC 4, 204. It is then established if RNC 4 is pool enabled, 205. If not, it is established if SGSN Y1/Y3 is a dual access mode SGSN, 205A. If not, a dual mode SGSN is selected, e.g. SGSN Y2, 205C. If yes, the MS remains connected to SGSN Y1. If however RNC 4 was pool enabled, a routing area update request is sent to SGSN Y2 controlling RNC 4, (here SGSN Y2 is supposed be a dual mode SGSN), 206. (If, in step 201A, another SGSN (Y3) had to be selected since BSC 1 was not pool enabled, the routing area update request was sent to SGSN Y3 instead.) The MS is then connected to SGSN Y2 (c.f. step 201A), 207 following the ISRAU procedure.
Subsequently it is supposed that the MS once more changes routing area from RA 3 controlled by RNC 4 to RA 2 controlled by BSC 2 (which is pool enabled), of RAN 1. Routing area update request with P-TMSI and NRI is then sent to BSC 2, 208. BSC 2 uses NRI to send a routing area update request to SGSN Y2 (dual mode SGSN), 209. SGSN Y2 sends an accept with P-TMSI and NRI, to BSC 2, 210, and BSC 2 forwards the accept to the MS, 211.
It should be clear that this merely is one particular scenario intended to illustrate the inventive concept.
When referring to routing areas in
The invention is of course not limited to the particular illustrated embodiments and scenarios, but it can be varied in a number of ways, and it can be implemented in different systems etc. and further that the pools may be constituted in various different ways and that there may also be more than just two radio access networks involved, the inventive concept still is applicable.
Number | Date | Country | Kind |
---|---|---|---|
10359644.5 | Dec 2003 | DE | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/EP03/14209 | 12/13/2003 | WO | 9/18/2006 |