Patent Publication Number: US-2003228872-A1

Title: Method for location management in a radio access network and network elements therefor

Description:
[0001] The invention is based on a priority application EP 02 360 168.5 which is hereby incorporated by reference.  
       FIEL OF THE INVENTION  
       [0002] The present invention relates to a method for location management in a radio access network and network elements therefor.  
       BACKGROUND OF THE INVENTION  
       [0003] The architecture and the design of modern radio access networks, such as UTRAN (UMTS terrestrial radio access networks; UMTS: Universal Mobile Telecommunications System) are becoming more and more complex. The overall mobile radio systems have a lot of different entities, devices and components, namely user terminals, radio base stations, at least one radio network controller for controlling a cluster of radio base stations, and switching devices, such as a mobile switching center for establishing circuit-switched connections to public switched telephone networks (PSTN) or the like. Also routers for establishing packet-switched connections to IP based networks, esp. to the world wide web, may be installed as well.  
       [0004] Basically the base stations and the radio network controller are constituting the radio access network which is also referred to as RAN. The switching devices are constituting the so-called core network. The interface between the RAN and the core network is quite complex, in the case of UTRAN a so-called lu interface is used as being defined by the document 3GPP TS 25.410 having the title “UTRAN lu Interface: general aspects and principles”. There a so-called RANAP protocol (Radio Access Network Application Protocol) is used as defined in 3GPPTS 25.413 “UTRAN lu interface RANAP signaling”.  
       [0005] The RAN is providing mobile radio services to a wide geographical area which is divided into a multiplicity of radio cells. Every cell is controlled by a base station, and each base station controls at least one radio cell. In the UTRAN which is operating in accordance with the UMTS standard the base stations are referred to as node B. The base stations support the connection establishment to the terminals and establish the connections to a plurality of terminals in a radio cell. The connection has the form either of a permanent connection for the transmission of circuit switched data or a non-permanent connection for the transmission of packet switched data. The data signals transmitted via the connection are representing all kind of communication data, such as voice, audio, text, video data or other kinds of user data.  
       [0006] The network elements for controlling the radio cell clusters are the radio network controllers, also referred to as RNC. Each RNC is assigned to a plurality of base stations, typically up to few hundred base stations. The RNC performs for example the radio resource management and the terrestrial resource management of a radio cell cluster. In particular, the RNC controls transmission power on radio bearers, handovers (transfer of a terminal from one radio cell into another) as well as the macro diversity mode.  
       [0007] The RNC is connected via interfaces to the other network elements. In UMTS this means that a RNC comprises at least one lu-interface to a core network, possibly one or several lur-interface to other RNCs, at least one lub interface to a base station (e.g. to a Node B), and at least one logical interface to a terminal UE which runs physically across the lub-interface or the lub and lur interfaces.  
       [0008] In the existing radio access networks, such as the conventional UTRAN, all control and user plane information relative to a particular user terminal or to a certain area is exchanged via the lu interface between the core network and the radio network controller, which is the serving controller for this user terminal. In an evolved UTRAN, it is foreseen that the radio network controller is split into its control and user planes, which are located in different network elements, herein also called radio network controlling elements.  
       [0009] The principle of this clear separation between the control and user planes is shown in the FIGS. 1 a  and  1   b.  The user plane functions which basically contain all the channel processing, e.g. header compression, radio frame delivery acknowledgement, channel multiplexing and macro-diversity combining, are performed by user plane servers UPS. The control plane functions which mainly encompasses all signaling related processing for the application protocols, such as NBAP (Node B Application Part), RNSAP (Radio Network System Application Part) and RANAP (Radio Access Network Application Part) on the RAN-CN interface, and also signaling for the radio resource control RRC of the air interface (RAN-UE interface, i.e. Uu), are performed by at least one control plane server. Both types of servers are parts of the Radio Network Controller—the so-called RNC. Thus the servers CPS and UPS are also here named as radio network controlling elements RNCE.  
       [0010] The separation of user plane and control plane allows to separately scale both planes, what results in turn in a better scalability for the whole system. However, this separation also implies a higher number of hardware elements resulting in a higher number of external interfaces; some of them are new and must be defined. The split of control and user planes has also a certain impact on QoS (Quality of Service) provisioning, a problem which must be analyzed and solved in detail.  
       [0011] The RNCE as shown in FIG. 1 b  is a complex assembly of at least one control plane server CPS and at least one user plane server UPS for carrying out control or user plane functions respectively. These different types of servers perform many different and sometimes unrelated functions. This introduces extra complexity in the design of the RAN and even more of the whole mobile radio system.  
       [0012] If both planes are split, the lu, lur and lub interfaces are also split into their control and user plane components as can be seen from FIG. 1 a.  However, this does not require relevant changes in the RNC architecture, since different protocols for the control and the user plane are already used for these interfaces. The control parts of the interfaces would include the different application parts (so-called RANAP, RNSAP and NBAP), whereas the bearer parts would contain the different frame protocols.  
       [0013] Signaling between the RAN and the UE is also considered as belonging to the control plane. Therefore, the RRC (Radio Resource Control) protocol is terminated in the control plane, whereas layer  2  protocols (PDCP, RLC, MAC) and macrodiversity combining and splitting are located in the user plane.  
       SUMMARY OF THE INVENTION  
       [0014] In an evolved RAN architecture as shown in FIG. 1, the user and the control planes are separated into different network elements. If a further split will be introduced in the control plane in order to separate mobile control functions from the rest of the control functions, e.g. cell and multi-cell related control functions, then the functional entities responsible for the mobile control and for paging and broadcasting would not be located in the same network element. However, these entities for Mobile Control, Paging and Broadcasting shall work very efficiently, in particular they shall support well location management functions within the radio access network.  
       [0015] Therefore the object of the invention is to overcome the drawbacks as mentioned above and to present a new and advantageous method for location management and also new network elements for performing that method.  
       [0016] The object is solved by a method for location management in a radio access network wherein the user functions are split from the control functions by introducing a user plane and a control plane into the radio network controlling elements of the radio access network, the control plane being further split in mobile specific control functions and area specific (cell and multi-cell) control functions, the method comprising the steps of:  
       [0017] processing paging and broadcast functional tasks on the control plane of at least one of the radio network controlling elements resulting from this split,  
       [0018] processing mobile control functional tasks on the control plane of at least one other radio network controlling element resulting from the split,  
       [0019] processing the paging and broadcast functional tasks in a first and a second logical block, the first logical block performing paging tasks which are related to core network defined areas and the second logical block performing paging tasks for radio access network defined areas.  
       [0020] There is also proposed a set of network elements being part of radio network controlling elements of a radio access network, wherein the user functions are split from the control functions by introducing a user plane and a control plane into the radio network controlling elements, the set of network elements operating on the control plane and comprising a mobile control server having mobile control functions and an area control server having paging and broadcast functions for supporting location management procedures, the paging and broadcast functions being split in a first and a second logical block, the first logical block performing paging tasks which are related to core network defined areas and the second logical block performing paging tasks for radio access network defined areas.  
       [0021] There is further proposed a radio access network wherein the user functions are split from the control functions by introducing a user plane and a control plane into a radio network controlling elements comprising a set of network elements operating on the control plane and comprising a mobile control server having mobile control functions and an area control server having paging and broadcast functions for supporting location management procedures, the paging and broadcast functions being split in a first and a second logical block, the first logical block performing paging tasks which are related to core network defined areas and the second logical block performing paging tasks for radio access network defined areas.  
       [0022] The invention presents a new solution of radio access network design, in particular a split of the control plane entities with respect to paging and broadcasting tasks. Basically for location management purposes a first and a second functional block are introduced. The first block, called RAN related paging and broadcasting function, is managing paging tasks which are related to core network defined areas. The second block, called CN related paging and broadcasting function, is managing paging tasks for radio access network defined areas of at least one radio cell, i.e. cell, cells or so-called URA. 
     
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
     [0023] The invention and the advantages resulting therefrom will become apparent from the following more detailed description of preferred embodiments. For explanation purposes some schematic drawings are added and are shown in the enclosed figures:  
     [0024]FIG. 2 showing the status of entities in the core network and the terminal involved in paging procedures;  
     [0025]FIG. 3 showing a functional block diagram of the radio access network according to a preferred embodiment;  
     [0026]FIG. 4 showing a block diagram of tasks to be performed in the different network elements of the radio access network according to the invention;  
     [0027]FIG. 5 showing a block diagram of the radio access network according to a further embodiment;  
     [0028]FIG. 6 showing a flow chart of a subroutine for paging according to the method of the invention;  
     [0029]FIG. 7 showing a flow chart of a subroutine for location and routing area updating according to the method of the invention;  
     [0030]FIG. 8 showing a flow chart of a subroutine for paging of an user terminal when in idle mode according to the method of the invention;  
     [0031]FIG. 9 showing a flow chart of a subroutine for dedicated paging in a distributed radio access network;  
     [0032]FIG. 10 showing a flow chart of a subroutine for UTRAN registration area -URA- paging in a distributed radio access network. 
    
    
     DETAILED DESCRIPTION OF THE INVENTION  
     [0033] In FIG. 2 there is shown from a logical point of view, the concept of core network initiated paging by illustrating two state machines in parallel, both being assigned to the service domains of the network, one of them being a circuit switched service domain CSSD (also named PSTN/ISDN domain), the other one being a packet switched service domain PSSD (also named IP domain). Thus each service domain has its own service state machine. A mobile terminal UE, that is supporting both services, has a circuit switched service state machine CSST and a packet switched service state machine PSST. The two peers of the service state machines are working independently to each other, although associated to the same terminal UE (also named user equipment). The signaling between the terminal and the core network aims to keep the peer entities synchronized.  
     [0034] For both core network domains CSSD or PSSD, the terminal UE may either be in a DETACHED, IDLE or CONNECTED mode. If the terminal UE is IDLE in one of the domains, it is tracked based on Location Areas (LA) in the CSSD or Routing Areas (RA) in the PSSD. Therefore LA/RA update procedures are used which are known from UMTS as such. The location information is stored in the Home Location Register (HLR) database.  
     [0035] For terminals which are either in CS CONNECTED mode, PS CONNECTED mode or in both, a Radio Resource Control RRC connection exists between the terminal UE and its Serving Radio Network Controller (see SRNC in FIG. 3). Then a signaling connection is established on the lu interface (see lu-c, the control part of the lu interface, in FIG. 3) between the Serving Radio Network Controller and the corresponding core network node or nodes (see CN in FIG. 3). These nodes can either be Mobile Switching Centers MSC, Serving General Packet Radio Service Support Nodes SGSN, or both.  
     [0036] The RRC CONNECTED terminals, i.e. terminal being either connected to CSSD or PSSD or both are tracked inside the network UTRAN based on cell or UTRAN registration areas. Therefore the terminal UE informs its Serving Radio Network Controller about its new location.  
     [0037] If a terminal should be found by a core network domain in which it is idle, the corresponding domain sends a special message (RANAP PAGING message) to all Radio Network Controllers responsible for the Location Area or Routing Area. Depending on the Radio Resource Control status of the terminal UE in the other domain two main cases can be distinguished:  
     [0038] CS IDLE/PS IDLE: In this case the terminal UE is RRC IDLE, i.e. no Serving Radio Network Controller (SRNC) exits for this terminal. In this case all Radio Network Controllers which receive the RANAP PAGING message try to find the terminal UE using regular paging procedure such as known from UMTS. Therefore, no Mobile Control functional entity exists for the paged user, and no context is stored in the PBCN logical block.  
     [0039] CS IDLE/PS CONNECTED or CS CONNECTED/PS IDLE (IDLE/CONNECTED case): In this case the mobile terminal is RRC CONNECTED, i.e. one of the Radio Network Controllers which received the RANAP PAGING message is the Serving Radio Network Controller SRNC of this mobile terminal UE. Depending on the RRC status of the terminal UE it may not monitor the paging channel and could therefore not be reached by regular paging. Therefore the SRNC has to do some paging co-ordination which is discussed later in detail. In this case, there is a Mobile Control functional entity MC responsible for control of the terminal, and a context exists in the PBCN logical block pointing at the MC. The MC stores some context information required to provide paging coordination according to the state of the terminal UE.  
     [0040] If the terminal UE receives an RRC PAGING message it has to respond and as a consequence the RRC status of the terminal UE may change and further signaling follows. But this is not the main subject of the invention and therefore not described in more detail.  
     [0041] In addition to the described core network (see CN in FIG. 3) originated paging, the UTRAN itself may trigger the paging procedure by sending an RRC PAGING message which is handled in the same way as the second case above. In this case, paging is initiated by the SRNC in the original UTRAN architecture, and hence by the Mobile Control functional entity associated to the terminal UE.  
     [0042] However a specific problem arises due to the described hierarchical concept. It is that in the mixed IDLE/CONNECTED case the terminal UE may move over LA/RA area borders while it is tracked by its Mobile Control functional entity). If a new PBCN logical block is responsible for this new LA/RA a RANAP PAGING message sent by the IDLE CN domain to all RNCs (i.e. to all PBCN logical blocks) responsible for the new LA/RA would not reach the Mobile Control MC associated to the terminal, since none of the PBCNs has a stored context pointing at the MC. As a consequence of this the Mobile Control cannot do the described paging co-ordination and an terminal UE may not be reached. Therefore, an RRC CONNECTED UE can not do an LA/RA update while its Mobile Control does not change, i.e. the LA/RA stored in the HLR doesn&#39;t change even if the mobile crosses LA/RA borders. The key for this solution is that RRC CONNECTED UEs receive mobility management system information (LA/RA-Ids) on the established RRC connection from their MC while RRC IDLE UEs read this information from the system information broadcast (BCCH) of the current cell, i.e. even if the UE crosses LA/RA borders it will not be informed by its MC about the change. Hence, in the IDLE/CONNECTED case one of the PBCNs belonging to the current LA/RA has always context information pointing at the Mobile Control MC responsible for terminal control of the UE which can do the necessary paging co-ordination.  
     [0043] If an SRNS relocation is carried out (i.e. a new MC in a different network element becomes responsible for the terminal due to terminal movement) the new MC is responsible for sending the mobility management system information which may in turn cause a LA/RA update. In this case, one of the PBCNs in the LA/RA must be set up with a context pointing at the new MC (note that this PBCN could still be the old PBCN). This ensures again, that the IDLE CN domain contacts the correct RNC.  
     [0044] In order to reach a mobile user the current location of the terminal UE is stored in the mobile network. In the mobile radio access network proposed here a hierarchical concept is applied which splits the whole mobility management between the core network and the Radio Access Network UTRAN. In case of a mobile terminated call the core network locates the mobile user by querying the location databases DB which can be the Home Location Register HLR or the Visited Location Register VLR and by paging the mobile terminal UE inside its current registration/location area. In particular a new IP based architecture is proposed which splits the Radio Network Controlling Elements in several different parts. Preferably the support of several different air interface technologies is provided by a Multistandard RAN (MxRAN) architecture which is also described here, esp. in view of the impact of the proposed distributed architecture on the mobility management.  
     [0045]FIGS. 3 and 4 are showing the main architectural principles for the split of the control and user planes and the separation of cell, multi-cell and user related functions. According to these principles, the RNC functionality in RAN is distributed across several functional entities:  
     [0046] Mobile Control MC, responsible for user related functions belonging to the control plane, i.e. SRNC functions belonging to the control plane.  
     [0047] User Radio Gateway USRG, responsible for user related functions belonging to the user plane, i.e. SRNC functions belonging to the user plane.  
     [0048] Cell Control (CC), responsible for cell related functions belonging to the control plane, i.e. CRNC/DRNC functions related to a single cell and to the control plane  
     [0049] Cell Bearer Gateway (CBG), responsible for cell related functions belonging to the user plane, i.e. CRNC/DRNC functions related to a single cell and to the user plane  
     [0050] Paging and Broadcast (PB), responsible for paging coordination and for distribution of paging information and CBS messages across several cells. These functions are located in the SRNC and the CRNC.  
     [0051] Radio Resource Management RRM, or even Multi-Cell Radio Resource Management responsible for radio resource management with a multi-cell view. This functional entity is part of the CRNC.  
     [0052] The functional split and the interconnection between the functional entities as shown in FIG. 3 is one possible solution wherein several functional entities can be bundled together in a single network element and existing UTRAN interfaces can be reused for the interconnection of the different network elements such that only a few additional interfaces are necessary. For instance, several functional entities may be co-located in one network element in the final network reference architecture, e.g. a CC, a CBG and a Node-B may be co-located, or a PB, a RRM and several CCs may be located in a single Area Control Server (ACS).  
     [0053] For the mobility management especially the Mobile Control MC, the Paging and Broadcast PB functions, and the Cell Control CC functions as well as the related interfaces are important. Therefore the impact of these interfaces and the separation will be discussed here. In more detail the following problems are addressed and solved:  
     [0054] One aspect is a paging co-ordination to be realized between the Mobile Control MC and the Paging and Broadcast PB. Another aspect is a solution so that a Cell Control CC can find the Mobile Control MC using the available information. This solution is needed e.g. in the case of cell or URA update procedures, where the CC receives a cell or URA update RRC message on the CCCH which eventually should reach the Mobile Control MC of the corresponding terminal UE.  
     [0055] As the Cell Control CC does not store any terminal specific information and the Mobile Control MC is dynamically instantiated, at least during RRC establishment, the Cell Control CC needs a method to discover the correct Mobile Control MC. This is done by forwarding this message to the appropriate PBCN (which is identified by reusing the SRNC-ID included in the RRC message as the PBCN identifier) of the terminal UE which stores the terminal context pointing at the appropriate MC. There are further aspects, such as when must a LA/RA area update be performed in the new architecture? 
     [0056] This and other questions are addressed in the following section, which gives an overview on how the different mobility management related procedures may be handled in MxRAN. Moreover, alternative approaches are discussed.  
     [0057] In RRC and RNSAP messages of the current UTRAN architecture the identifiers of the SRNC and of the CRNC are used to identify the corresponding network elements, the terminal identifier is used to uniquely identify a certain terminal UE inside the SRNC. The identifier of the radio cell is used to uniquely identify a certain cell inside the CRNC. Thus it is very efficient to reuse the existing RNC-ID to identify a certain Paging and Broadcasting function PB. Moreover, as the UE-ID is just unique inside a certain SRNC, the combination of the RNC-ID and the UE-ID can be used to find a certain Mobile Control function MC. Similarly, the Cell-ID together with the CRNC-ID are used to uniquely identify a Cell Control function CC.  
     [0058] Although a Paging and Broadcasting function PB is a single functional element it has two different logical roles. This functional split is shown in FIG. 3:  
     [0059] The core network CN related Paging and Broadcasting part, as shown in the block PBCN, is responsible for the CN defined areas (i.e. LA, RA) and is contacted by the CN when the CN initiates paging. Therefore the PBCN together with the Mobile Control MC are responsible for doing the paging co-ordination.  
     [0060] The RAN related Paging and Broadcasting part, as shown in block PBRAN, which is responsible for the RAN related areas (i.e. URA, Cell) is contacted by the Mobile Control MC if paging related to Radio Registration Area tasks (URA paging) or Radio Cell tasks (Cell paging) should be carried out.  
     [0061] Furthermore, each part of the PB is responsible for a certain number of Cell Control CC and each CC belongs to one LA, to one RA, and to one or more URAs. Therefore a P&amp;B is at least responsible (among others) for the LA/RA/URA(s) a CC belongs to.  
     [0062] In order to understand in more detail the different roles of the Radio Network Control Elements SRNC, CRNC and DRNC in view of the split of the PB function into a first block PBCN and a second block PBRAN, these functions shall be described in even more detail as follows:  
     [0063] The first block PBCN is part of the radio network controller RNC as such whereas the mobile control MC function and the user radio gateway USRG are part of the serving radio network controller SRNC. The PBCN can not properly be considered as a part of the SRNC or the CRNC because its first task when it receives a paging request from the core network is to determine whether a context exists for the paged terminal. In this case, it would be part of the serving radio network controller SRNC responsible for the connected user. Otherwise, it would be part of a controlling radio network controller CRNC responsible for cells in the LA/RA. The second block PBRAN is part of the controlling radio network controller CRNC, which is also either the serving radio network controller SRNC responsible for the connected terminal or a so-called drift radio network controller DRNC, in this controller mainly the area specific (cell and multi-cell) related functions such as common radio resource management CCRM, cell control CC and cell bearer gateway CBG functions are processed.  
     [0064]FIG. 4 is showing a functional split of these and other functions to be performed either on the control plane or on the user plane.  
     [0065] A network design oriented split is shown in FIG. 5 in which two different network elements, namely a mobile control server MCS and an area control server ACS are shown. Both entities are belonging to the control plane and are representing a functional assembly comparable to the single control plane server CPS as shown in FIG. 2.  
     [0066] In the mobile control server MCS as shown in FIG. 4 the mobile control MC functions for a number of mobile terminals are gathered together. The cell control CC functions for several radio cells, the overall paging and broadcast PB function and the common radio resource management RRM are integrated into the area control server ACS.  
     [0067] User plane related functions are integrated into user plane servers UPS which are closely located to the respective base stations (Node Bs). The user plane functions perform all radio processing associated with layer 2  (L 2 ) protocols, i.e. they perform the PDCP (packet data convergence protocol), the RLC (radio link control) and MAC (medium access control) protocols. The BMC layer, responsible for the transmission of cell broadcast service messages in a particular cell is also located in the UPS, as well as the macrodiversity combining and splitting unit used for soft handover, which is considered as an upper sublayer of the physical layer.  
     [0068] But the main aspect of here is the split of the control plane functions and their implementation into separate servers MCS or ACS, both representing distributed parts of a control plane server assembly CPS. This is responsible for all control related procedures, i.e. it contains the termination of the different Application Parts, such as the so-called RANAP (radio access network application part), the RNSAP (radio network system application part), and the NBAP (node B application part) used for the exchange of control information between the different network elements in the radio access network (RAN) and with the core network (CN). The control plane CP contains also the termination of the SABP (Service Area Broadcast Protocol), which is used for the reception of cell broadcast service (CBS) messages. Therefore, the CP is responsible for distributing CBS messages to the appropriate elements in the user plane UP, which in turn distribute internally CBS messages to the BMC (Broadcast/Multicast Control) layer entities responsible for the broadcast in each particular cell. Moreover, the CPS contains as well the RNC part of the RRC (radio resource control) protocol, used for the exchange of control information between the RAN and the mobile terminals (UEs).  
     [0069] In the control plane, the RANAP protocol is used for the exchange of both generic and user specific control information between the CN and the CPS. Before any user plane data can be exchanged between a CN node, e.g. a mobile switching center (MSC) or a serving GPRS support node (SGSN) and a particular UE, a dedicated lu signaling connection is established between the MCS associated to the UE and the CN node. After this connection is established, all control information related to this particular UE is exchanged between the CN node and the MC associated to the UE (located in the MCS) by means of this lu signaling connection. However, for generic control information, connectionless mode is used. Paging notifications, whose purpose is to locate a particular UE, are also considered a part of the generic control information, since no lu signaling connection exists for the paged UE towards the CN node initiating the paging procedure.  
     [0070] A consequence of the division of the PB functional entity in two different logical blocks, namely PBCN and PBRAN, is that in a particular paging procedure (depending on the state of the UE), a PBCN and one or several PBRANs may be involved, and each of them can be located in different ACSs.  
     [0071] The method of paging according to the invention is shown in more detail in the FIG. 6 wherein basically two types of paging subroutines may occur:  
     [0072] First a so-called “CN initiated paging”, i.e. a paging which is triggered by the mobile switching center or serving GPRS support node of the core network, when the terminal is idle in the CN domain initiating paging. The core network related paging and broadcast block PBCN (also see FIG. 3) is contacted to send paging signals via a paging channel to the location area LA or routing area RA of that mobile terminal. However, if the terminal is in a RRC connected state (i.e. it has an RRC connection towards its associated MC), one of the PBCNs contacted by the CN has a context for the paged terminal pointing at the associated MC, and it must forward paging information to the MC.  
     [0073] If the terminal is in a RRC connected mode and the terminal is in an active status (i.e. in RRC Cell_DCH or Cell-FACH states) the paging is performed by mobile control MC via the dedicated channel, e.g. the DCCH.  
     [0074] If the terminal is RRC connected but not active (i.e. in RRC Cell_PCH or URA_PCH states) the paging is performed via a paging channel, e.g. the PCCH. In this case the MC forwards the paging information, together with the identification of the cell or URA onto which paging should be carried out, to the radio access network related paging and broadcast block PBRAN(also see FIG. 3), which then distributes that information to corresponding CC(s) which finally send paging signals via the paging channel PCCH.  
     [0075] The second type of paging can be the a so-called “RAN initiated paging”, i.e. a paging which is triggered by the MC associated to the terminal (which is necessarily in RRC connected state). Again the MC checks the RRC state of that terminal and goes on according to the steps explained above, i.e. DCCH paging of active terminals or PCCH paging of non-active terminals.  
     [0076] In FIG. 7 there is shown the chart of a LA/RA update procedures in MxRAN which work exactly the same as in the UTRAN architecture beside the fact that the MC functional entity carries out tasks performed by the SRNC in the original UTRAN architecture. Hence, no special adaptation is necessary for these procedures.  
     [0077] The FIG. 8 shows the subroutine for paging in a location area or routing area. If a terminal UE is in RRC IDLE mode and one of the CN domains wants to find the UE, the CN sends a RANAP paging message to all PBCN entities responsible for the corresponding LA/RA. In this case none of these entities has stored a terminal context. Hence, they proceed with the distribution of paging information to all CCs under their responsibility which belong to the requested LA/RA. This distribution is internal if the PBCN and the associated CC entities are located in the same network element i.e. the Area Control Server (ACS). In case they are not co-located, for instance because each CC functional entity is co-located with its associated Node B and not in the ACS, the distribution must be carried out externally by means of some protocol. A possible solution in this case would be to reuse the already existing RNSAP PAGING REQUEST message used on the lur interface in today&#39;s UTRAN architecture, or even a simplified version of this message. Once the CC has received paging information, it sends a PAGING TYPE 1 RRC message on the PCCH to the UE.  
     [0078] The procedure as shown in FIG. 8 is not more complex than that procedure defined in UMTS. The only difference is that the PBs have to contact a potentially high number of CCs (each CC is responsible for just one cell), what is handled inside the CRNC in the original UTRAN architecture. Hence, if the PBCN and the CC are separated in different network elements, this introduces additional signaling overhead and delay (one additional hop). However, if the CC (and the CBG) is co-located with the Node B, this effect is compensated or even over-compensated.  
     [0079] Further subroutines performed in a evolved RAN which can be a MxRAN for the paging of mobile terminals in RRC connected mode are shown in FIGS. 9 and 10:  
     [0080] If an UE in RRC connected mode is paged by the idle CN domain, the CN sends a RANAP paging request to all PBCNs which are responsible for the corresponding LA/RA and one of these knows the MC of the UE (this relation is generated during RRC establishment). This PBCN and the MC of the mobile have to co-ordinate the paging as previously. This can be done in different ways:  
     [0081] The PBCN is always updated when the RRC status of the UE changes and can therefore decide independently how to proceed.  
     [0082] The PBCN just knows the mapping between the MC-ID and the corresponding network element and forwards the RANAP PAGING message to the MC which then can decide how to proceed based on the already available information.  
     [0083] As the overhead introduced by permanently updating the PB seems to be very high, the second approach is favored and described in the following. Two cases must be distinguished depending on the RRC status of the UE.  
     [0084] The first one is shown in FIG. 9. There is shown the flow chart for a dedicated Paging for UEs in Cell_FACH or Cell_DCH:  
     [0085] For UEs in Cell_FACH or Cell_DCH RRC state dedicated paging is used, i.e. the MC sends an RRC PAGING TYPE 2 message on the already established DCCH to the UE.  
     [0086] The second subroutine is shown in FIG. 10. There is shown an URA/Cell Paging for UEs in URA_PCH or Cell_PCH:  
     [0087] If an UE is in URA_PCH or Cell_PCH RRC state, a PAGING TYPE 1 RRC message must be sent on the PCCH of the given cell or of all cell(s) of the given URA. As the URA paging is the more complicated case it will be described in the following. Cell paging is similar, but a single cell is involved (and hence also a single PBRAN and a single CC).  
     [0088] The PBCN forwards the paging message to the MC of the UE. The MC knows the current URA of the UE and all responsible PBRANs for this URA and sends a RNSAP PAGING REQUEST message to all of these PBRANs which in turn forward it to all the CCs under their responsibility which belong to the URA. All the CCs then send a PAGING TYPE 1 message on the PCCH of their cells which will finally reach the UE. As in the PBCN case explained before, the distribution between a certain PB (in this case PBRAN) and the associated CCs can be internal or external depending on the location of the CCs.  
     [0089] This scenario assumes that the MC knows all the PBRANs responsible for the URA. Alternatively the MC could just know the ID of one PBRAN, i.e. the ID of the PB which is responsible for the CC from which the last URA update was carried out. In this case the MC would send the RNSAP PAGING message to this PB which would then be responsible for distributing the message to all other PBs responsible for the URA.  
     [0090] Summarizing, some context information is required in the different functional entities in the preferred embodiment of the invention.  
     [0091] The CN associated paging and broadcast functional entity must have a context for RRC connected users consisting of the identification of the MC associated to the terminal (including the transport address of the network element MCS where this MC is located). This context is created during the initial RRC establishment procedure and deleted when the RRC connection is released. In case of a relocation, this context could be deleted in a PBCN functional entity and setup in a new one.  
     [0092] The Mobile Control (MC) functional entity associated to a particular terminal (which must necessarily be in RRC connected state) must contain (among other information) at least the following context for the terminal:  
     [0093] →The RRC status of the terminal (CELL_DCH, CELL_FACH, CELL_PCH or URA_PCH).  
     [0094] →If the terminal is in CELL_PCH state: the Cell-ID of the cell were the last cell update procedure was executed, and the PBRAN-ID of the PBRAN associated with the CC responsible for the cell (this PBRAN-ID corresponding to the CRNC-id used on air interface messages and lur RNSAP messages in today&#39;s architecture)  
     [0095] →If the terminal is in URA_PCH state: the URA-ID of the URA for which the last URA update procedure was carried out for the terminal and additionally either the PBRAN-ID of the PBRAN associated to the CC of the cell where the URA procedure was last executed or a complete list of the PBRAN-IDs of all PBRANs associated to CCs belonging to the URA.  
     [0096] No context information is required in the PBRAN for the terminal.  
     [0097] Context information required in MC for the RRC CELL_PCH or URA_PCH states is updated whenever a cell or URA update procedure is carried out by the mobile terminal. In this case, the terminal sends an RRC CELL UPDATE or URA UPDATE message on the CCCH of the cell where it is located. By reusing RNC-ids for the different PBs and the SRNC-id and UE-id to identify the MC associated to the UE, the cell-ID or URA-ID and the identification of the PBRAN associated to the cell where the procedure was triggered (or all the PBRANs associated to cells in the selected URA) can be forwarded to the appropriate MC, and the confirmation of the cell or URA update is sent back from the MC to the CC and from the CC to the UE.