Abstract:
The present invention describes a novel method, radio access node and system for specifying and interpreting identifiers in a telecommunications system. In the method of the present invention, an RNC identifier extension element extending the RNC identifier is created and one or more radio access network nodes are specified with the RNC identifier and RNC identifier extension element extending the RNC identifier in the first and/or second interface instance. In a preferred embodiment, the RNC identifier and RNC identifier extension element extending the RNC identifier specify a radio network access server and an IP base station in the second interface.

Description:
FIELD OF THE INVENTION  
         [0001]    The present invention relates to the telecommunication systems. In particular, the present invention relates to a novel and improved method and system for using and interpreting interface identifiers in a correct way in a telecommunication system.  
         BACKGROUND OF THE INVENTION  
         [0002]    In the current specifications of the third generation mobile networks (referred to as UMTS), the system utilizes the same well-known architecture that has been used by all main second-generation systems. A block diagram of the system architecture of current UMTS network is presented in FIG. 1. The UMTS network architecture includes the core network (CN), the UMTS terrestrial radio access network (UTRAN), and the user equipment (UE). The core network is further connected to the external networks, i.e. Internet, PLMN, PSTN and/or ISDN.  
           [0003]    The GSM Phase 1/2 Core Network consists of network switching subsystem (NSS). The NSS further consists of the following functional units: Mobile Switching Center (MSC), Visitor Location Register (VLR), Home Location Register (HLR), Authentication Center (AC) and equipment identity register (EIR). The GSM Phase 2+ enhancements to the GSM phase 1/2 CN are serving GPRS (General Packet Radio Service) support node (SGSN), gateway GPRS support node (GGSN) and CAMEL service environment. The most important new feature that is introduced with the GPRS is the packet switching (PS), which improves the capacity of the network.  
           [0004]    The UTRAN architecture consists of several radio network subsystems (RNS). The RNS is further divided into the Radio Network Controller (RNC) and several base stations (BTS, referred to as B nodes in the 3 rd  Generation Partnership Project (3GPP) specifications).  
           [0005]    In this architecture there are several different connections between the network elements. The Iu interface connects the CN to the UTRAN. The Iur interface enables the exchange of signaling information, as well as the establishment of user plane connections, between two RNCs. The signaling protocol across the Iur interface is called the Radio Network Subsystem Application Part (RNSAP). The RNSAP is terminated at both ends of the Iur interface by an RNC. The Iub interface connects an RNC and a node B. The Iub interface allows the RNC and node B to negotiate about radio resources, for example, to add and delete cells controlled by node B to support communication of dedicated connection between UE and S-RNC, information used to control the broadcast and paging channels, and information to be transported on the broadcast and paging channels. One node B can serve one or multiple cells. The UE is connected to node B through the Uu radio interface. The UE further consists of a subscriber identity module (USIM) and mobile equipment (ME). They are connected by the Cu interface. Connections to external networks are made through a gateway MSC (towards circuit switched networks) or GGSN (towards packet switched networks).  
           [0006]    In order to obtain the most efficient RAN architecture, which is based on using the good characteristics of IP, some functionality has to be relocated between network elements. In the most revolutionary architecture we no longer have a network element commonly known as a BSC (Base Station Controller) or RNC (Radio Network Controller), although this functionality must remain in the RAN. In one embodiment of the IP RAN, there has been chosen to locate some RNC functionality in the BTSs to enable e.g. soft handover and associated signaling to happen along the shortest path, producing minimum delay and signaling load to those parts of networks where this is not necessary. Referring to the above state of art description it can be said that IP RAN is realized by implementing most of the RNC (or BSC) functionality in the BTS (IP BTS). Only Paging, basic O&amp;M (Operation and Maintenance) and configurations, location calculation functions and common radio resource management may be implemented in separate servers outside the BTS site.  
           [0007]    In the distributed architecture of IP RAN, the distributed functionalities of RNC/BSC from the CN&#39;s or neighboring radio network&#39;s point of view are hidden. In an IP RAN architecture, the introduction of the Radio Network Access Server (RNAS, a signaling GW) and Radio Access Network Gateway (RNGW)/Circuit Switched Gateway (CSGW) (user plane GWs) creates two instances of the Iu interface from the core network towards the IP BTS. The same happens with the Iur interface from a conventional RNC to an IP BTS. The presence of two instances of the Iu and Iur interfaces for interworking reasons is one of the main characteristic of the IP RAN Distributed architecture.  
           [0008]    The IP RAN is a distributed architecture, where the RNAS and GWs are hiding the mobility to the core network. The current RAN architecture is not a distributed architecture. For a correct interworking of the two instances of Iu and Iur interfaces, the e.g. RNSAP and RANAP protocols in the inner instance of the interface (Iu′, Iur″) are not directly applicable. One problem is that the current RNC ID address space (12 bits) is not enough to specify the source IP BTS and target IP BTS in Iu′ interface during the relocation procedure. Additional problem is the addressing of connectionless messages in case of Iur″ interface (for example, Uplink Signaling Transfer, Paging Request). In this case, as far as the RNAS acts as interworking signaling unit, the identity of the receiving entity (RNC) has to be included into those messages so that RNAS can address properly this receiving entity.  
           [0009]    Therefore, the RNSAP and RANAP protocols in the inner instance of the interface (Iu′, Iur″) need to be modified in the handling of the instance identifiers. Without the solution described in the present invention it is not possible to implement the IP radio access network.  
         SUMMARY OF THE INVENTION  
         [0010]    The present invention describes a novel and improved method, network node and system for managing signaling bearer connection parameters in an interface instance between one or more radio network access servers of a distributed radio access network and at least one of the networks selected from a group of networks comprising a core network and a neighboring radio access network and also in the distributed radio access network.  
           [0011]    One objective of the present invention is to provide an addressing method in a telecommunication system comprising a first interface instance between one or more radio network access servers and at least one of the networks selected from a group of networks comprising a core network and a neighboring radio access network and a second interface instance between one or more radio network access servers and a set of IP base stations. An RNC identifier is used to specify a radio access network node in the first interface instance.  
           [0012]    The problem of the current systems is that the current RNC ID address space is only 12 bits. This is not enough to specify a unique identification for a source or target IP base station. Therefore, in the method of the present invention, an RNC identifier extension element extending the RNC identifier is created and one or more radio access network nodes are specified with the RNC identifier and RNC identifier extension element extending the RNC identifier in the first and/or second interface instance. In a preferred embodiment, the RNC identifier and RNC identifier extension element extending the RNC identifier specify a radio network access server and an IP base station in the second interface.  
           [0013]    In an embodiment of the present invention, the method further comprises the step of creating a target serving IP BTS identifier element with which an IP base station and the gateway radio network access server are specified in the first interface instance. The target serving IP BTS identifier element is preferably incorporated in the Source RNC to Target RNC transparent or Old BSS to New BSS container used in the first interface instance.  
           [0014]    In an embodiment of the present invention, the method further comprises the steps of reading the content of the Target RNC ID information element and the Target RNC ID information element extension element and copying the read information into the target serving IP BTS identifier information element used in the first interface instance.  
           [0015]    In an embodiment of the present invention, the RNC identifier extension element is used to extend the Source RND ID, Target RNC ID and/or Drift RNC ID information element in the first and/or second interface.  
           [0016]    In an embodiment of the present invention, with connectionless messages interworking with a conventional radio access network a destination RNC identifier is sent within one or more of the following messages: an uplink signaling transfer indication, a paging request, a downlink signaling transfer indication, a reset request or a reset response.  
           [0017]    In an embodiment of the present invention, the 3GPP RANAP and/or RNSAP specifications are changed to include the RNC identifier extension element the RNC identifier.  
           [0018]    In an embodiment of the present invention, the method further comprises the step of specifying a radio network access server, an IP base station, and user equipment in the second interface instance with a three-part form identifier wherein the first part identifies a radio network access server, the second part identifies an IP base station, and the third part identifies user equipment.  
           [0019]    According to another aspect, the invention relates to a system comprising a first interface instance between one or more radio network access servers and at least one of the networks selected from a group of networks comprising a core network and a neighboring radio access network and a second interface instance between the one or more radio network access servers and a set of IP base stations. An RNC identifier is used to specify a radio access network node in the first interface instance.  
           [0020]    According to the invention, the system further comprises an RNC identifier extension element used to extend the RNC identifier, wherein one or more radio access network nodes are specified with the RNC identifier and the RNC identifier extension element extending the RNC identifier in the first and/or second interface instance. In a preferred embodiment, the RNC identifier and RNC identifier extension element extending the RNC identifier specify a radio network access server and an IP base station in the second interface.  
           [0021]    In an embodiment of the present invention, the system further comprises a target serving IP BTS identifier element specifying an IP base station and the gateway radio network access server in the first interface instance. The target serving IP BTS identifier element is preferably incorporated in the Source RNC to Target RNC transparent or Old BSS to New BSS container used in the first interface instance.  
           [0022]    In an embodiment of the present invention, the system further comprises means for reading the content of the Target RNC ID information element and the Target RNC ID information element extension element and means for copying read information into the target serving IP BTS identifier information element used in the first interface instance.  
           [0023]    In an embodiment of the system of the present invention, the RNC identifier extension element is used to extend the Source RND ID, Target RNC ID and/or Drift RNC ID information element in the first and/or second interface. The RNC identifier extension element can, however, be used with any other present or future RNC identifier element other than mentioned above.  
           [0024]    In an embodiment of the system of the present invention, with connectionless messages interworking with a conventional radio access network a destination RNC identifier is sent within one or more of the following messages: an uplink signaling transfer indication, a paging request, a downlink signaling transfer indication, a reset request or a reset response.  
           [0025]    In an embodiment of the system of the present invention, the 3GPP RANAP and/or RNSAP specifications are changed to include the RNC identifier extension element the RNC identifier and/or the target serving IP BTS identifier element.  
           [0026]    In an embodiment of the system of the present invention, a radio network access server, an IP base station, and user equipment are specified in the second interface instance with a three-part form identifier wherein the first part identifies a radio network access server, the second part identifies an IP base station, and the third part identifies user equipment.  
           [0027]    According to another aspect, the invention relates to a method for interpreting signaling bearer connection parameters in a telecommunication system comprising a first interface instance between one or more radio network access servers and at least one of the networks selected from a group of networks comprising a core network and a neighboring radio access network and a second interface instance between the radio network access server and a set of IP base stations. An RNC identifier is used to identify a radio access network node in the first interface instance. In the method of the present invention, an RNC identifier extension element is used to extend the RNC identifier. Furthermore, a radio network access server and an IP base station are identified based on the RNC identifier and RNC identifier extension element extending the RNC identifier in the second interface instance.  
           [0028]    In an embodiment of the present invention, the method further comprises the step of using a target serving IP BTS identifier element with which an IP base station and the gateway radio network access server are identified in the first interface instance The target serving IP BTS identifier element is preferably incorporated in the Source RNC to Target RNC transparent or Old BSS to New BSS container used in the first interface instance.  
           [0029]    In an embodiment of the present invention, the method further comprises the steps of reading the content of the Target RNC ID information element and the Target RNC ID information element extension element and copying read information into the target serving IP BTS identifier information element used in the first interface instance.  
           [0030]    In an embodiment of the present invention, aforementioned identifying, reading and/or copying capabilities are arranged in radio network access servers and/or IP base stations of an IP radio access network.  
           [0031]    In an embodiment of the present invention, the method further comprises the step of specifying a radio network access server, an IP base station, and user equipment in the second interface instance with a three-part form identifier wherein the first part identifies a radio network access server, the second part identifies an IP base station, and the third part identifies user equipment.  
           [0032]    According to another aspect, the invention relates to a radio access network node interpreting signaling bearer connection parameters in a telecommunication system comprising a first interface instance to at least one of the networks selected from a group of networks comprising a core network and a neighboring radio access network and/or a second interface instance to radio network access servers or IP base stations. The system comprises means for identifying a radio network access server and an IP base station based on an RNC identifier and RNC identifier extension element extending the RNC identifier.  
           [0033]    In an embodiment of the radio access network element of the present invention, the means for identifying are arranged to identify an IP base station and the gateway radio network access server in the first interface instance based on a target serving IP BTS identification element used in the first interface instance. In an embodiment of the radio access network element of the present invention, the target serving IP BTS identification element is incorporated in the Source RNC to Target RNC transparent or Old BSS to New BSS container used in the first interface instance.  
           [0034]    In an embodiment of the radio access network element of the present invention, the radio network access node further comprises means for reading the content of the Target RNC ID information element and the Target RNC ID information element extension element and means for copying read information into the target serving IP BTS identifier information element used in the first interface instance.  
           [0035]    In an embodiment of the radio access network element of the present invention, the means for identifying are arranged to identify an RNC identifier in one or more of the following messages: an uplink signaling transfer indication, a paging request, a downlink signaling transfer indication, a reset request or a reset response.  
           [0036]    In an embodiment of the radio access network element of the present invention, the means for identifying, reading and copying are arranged in radio network access servers and/or IP base stations of an IP radio access network.  
           [0037]    In an embodiment of the radio access network element of the present invention, means for identifying are arranged to identify a radio network access server, an IP base station, and user equipment in the second interface instance based on a three-part form identifier wherein the first part identifies a radio network access server, the second part identifies an IP base station, and the third part identifies user equipment.  
           [0038]    The IP RAN is a distributed architecture, wherein the RNAS and GWs are hiding the mobility to the CN. So, for a correct interworking of the two instances of Iu and Iur interfaces, the RNSAP and RANAP protocols in the inner instance of the interface (Iu′, Iur″) need to be modified in the handling of the identifiers. The present invention describes the handling of the identifiers in the instances of the interface and the changes required to existing Iu and Iur application parts (RANAP and RNSAP) to support the two instances of the interface. Without the present invention it is not possible to implement an IP RAN.  
           [0039]    The present invention provides a solution for e.g. the problems related to the mobility and relocation issues. Furthermore, the extension of the RNC identifier allows the future removal of the interworking units (RNAS, RNGW, CSGW) and the direct connections of the core network and the IP BTSs, by solving the limitation of the addressing space of the identifiers. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0040]    The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this specification, illustrate embodiments of the invention and together with the description help to explain the principles of the invention. In the drawings:  
         [0041]    [0041]FIG. 1 is a block diagram illustrating a prior art telecommunication network,  
         [0042]    [0042]FIG. 2 is a block diagram illustrating an example of the overall system architecture of a distributed radio access network in which the present invention can be applied,  
         [0043]    [0043]FIG. 3 is a block diagram of identity definitions inside and outside an IP RAN, and  
         [0044]    [0044]FIG. 4 is a block diagram of an exemplary radio access network node in accordance with the present invention. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0045]    Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings.  
         [0046]    [0046]FIG. 2 illustrates an embodiment of a system in which the present invention can be used. The system comprises a core network CN connected to the IP radio access network IP RAN via the Iu interface. The Iu interface is described in more detail e.g. in the 3GPP specifications TS 25.410-25.415. In FIG. 2, the IP radio access network IP RAN comprises radio network access servers RNAS 1 , RNAS 2 , RNAS 3  and IP base stations IP BTS 1 , IB BTS 2 . The radio network access servers are connected to the IP base stations via the Iu′/A′ or Iur″ interfaces. The radio network access server RNAS 1  is connected to the RNC via the Iur interface. The Iur interface is described in more detail e.g. in the 3GPP specifications TS 25.420-25.427. The radio network access server RNAS 3  is connected to the BSC via the Iur-g interface. User equipment UE is connected to the IP base stations via the Uu interface.  
         [0047]    The radio network access server acts as a signaling gateway between RAN and CN. It has the following functions. It discriminates the control plane messages of the Iu and A interfaces and relays them further. It also can have paging server functions, i.e. the RNAS keeps track of the UE RRC (Radio Resource Control) status and location, processes the idle mode paging messages and other connectionless messages from the core network CN, and forwards them to the IP BTS controlling the cell the message is targeted to. In more detail, the RNAS has, for example, the following functions: RANAP connection termination, setup and release of the signaling connections, discrimination of connectionless messages processing of RANAP connectionless protocol messages, storing of information of the existing radio resource control (RRC) connection, relaying of idle mode paging message to the relevant entities, reset and overload control and management of reset and overload messages to/from the CN etc.  
         [0048]    Outside the IP RAN is the IP RAN external part comprising elements of other radio access networks. FIG. 2 comprises two Radio Network Controllers RNC of a UTRAN. Furthermore, FIG. 2 comprises a Base Station Controller BSC of e.g. a Global System for Mobile communications (GSM) system.  
         [0049]    In the IP RAN architecture, the introduction of the RNAS (signaling gateway) and RNGW/CSGW (user plane gateways) creates two instances of the Iu interface from the CN towards the IP BTS. The same happens with the Iur interface from conventional RNC to the IP BTS. The presence of two instances of the Iu and Iur interfaces for interworking reasons is one of the main characteristics of the IP RAN Distributed architecture. The present describes the handling of the identifiers in the IP RAN, and the changes required to existing Iu and Iur application parts (RANAP and RNSAP) to support the two instances of the interface.  
         [0050]    The IP RAN is interfaced to the external RANs and the CN via the 3GPP interfaces (Iu, Iur, A) and protocols. The same protocols are also used inside the IP RAN internal interfaces (Iur″, Iur′, Iu′, A′). As a consequence, the identifiers defined in the current GSM-RAN/UTRAN standard interfaces are also used within the IP RAN. In some cases, those identifiers need to be interpreted or used in a different way than they are used outside the IP RAN. Additionally, new identifiers and parameters need to be included in the IP RAN internal interfaces. The present invention provides a solution for this problem related the mobility and relocation issues.  
         [0051]    The problem in the Iu′ interface (RNAS-IP BTS) with relocations is that the current RNC ID address space (12 bits) is not enough to specify the source IP BTS and target IP BTS (and drift IP BTS in case of relocation with the drift) in the Iu′ interface during the relocation. For this reason, any occurrence of the RNC ID in the Iu′ interface (for example, the Source RNC ID, the Target RNC ID (and Drift RNC ID in the Source RNC to Target RNC Transparent Container IE)) are, as described in the present invention, extended in the Iu′ by adding a new proprietary information element (IE) called RNC id extension. The same extension is used in the Source RNC to Target RNC transparent container IE in the Iu interface.  
         [0052]    For the present invention to be fully usable, the same extension mechanism is necessary in the 3GPP Iu specifications in order to have an open interface to the IP BTS.  
         [0053]    In case of RNAS relocation, the Source IP BTS uses the target RNASid as the Target RNC ID IE on the Iu′ Relocation required message. But the target RNAS has no information about which is the target IP BTS. The solution is to include the Target Serving IP BTS ID IE in the Source RNC to Target RNC Transparent Container IE.  
         [0054]    The following table shows which are the modifications and different interpretations of the information elements in the relocation procedures.  
                                           Information   Modifica-               element   tion   Iu′ interface   Iu Interface                   Source RNC   Extension   RNCID + RNCID-   RNC ID = source       ID   added on   EXT =   RNC/RNAS ID.           Iu′ and A′   Complete IP BTS           by intro-   id           ducing a   (gateway RNASid +           new IE   IP BTSid)       Target RNC   Extension   RNCID + RNCID-   RNC ID = target       ID   added on   EXT =   RNC/RNAS ID.           the Iu′ and   Complete IP BTS           A′ (in case   id           of IS hand-   (geteway RNASid +           introducing   IP BTSid)           a new IE       Target   New IE in   This IE is not   Target IP BTS       Serving IP   the Source   needed in Iu′   ID = gateway       BTS ID (TS-   RNC to the   interface (in-   RNAS + IP       IPBTS)   target RNC   formation about   BTSid.           transparent   target IP BTS   Note: gateway           container   included in the   RNAS can be           on IU   Target RNCID IE)   different from                   the target RNAS                   included in the                   target RNCID IE       Drift RNC   Extension   Drift RNCID +   Drift RNCID +       ID   added on   RNCID-EXT =   RNCID-EXT =       (needed   the Iu′ and   Drift IP BTS:   Drift IP BTS:       only in   Iu by in-   Complete IP   Complete IP       case of en-   troducing a   BTSid gateway   BTSid (gateway       hanced Iu   new IE   RNASid + IP   RNASid + IP       relocation       BTSid)   BTSid)       keeping   Drift RNC:   Drift RNC:       drift RNC)       RNCID (exten-   RNCID (exten-               sion not used).   sion not used).                  
 
         [0055]    In the Iu′ interface the RNC identifier RNCID is extended by defining a new RNCID-EXT identifier field. In the Iu interface the extended RNC identifier specifies an RNC or RNAS depending on the radio access network in question. Actually, RNAS as an interworking signaling unit, is seen by the neighbor RNC and by the core network as another RNC.  
         [0056]    As mentioned before, two roles of the RNAS are defined:  
         [0057]    Gateway RNAS: The RNAS that is included in the complete IP BTS-ID identifier definition. The gateway RNAS is the one used for interworking with an RNC/BSC. There exists one gateway RNAS predefined for each IP BTS. The gateway RNAS identifier is included as serving RNC identifier in the air interface. For identification purposes, one IP BTS belongs to one gateway RNAS area. In FIG. 2, the Iur″ interface is the interface between the Gateway RNAS and the IP BTS.  
         [0058]    Serving RNAS: The RNAS that manage the Iu/A connection for the UE. Iu′/A′ are the interfaces between the serving RNAS and the serving IP BTS. The serving RNAS is not necessarily also the gateway RNAS for the IP BTS. One IP BTS may be connected to different serving RNASs.  
         [0059]    [0059]FIG. 2 and the associated description describes the present invention mainly using the Iu interface as an example. It is, however, obvious that in the case of the A interface it is the BSC (Base Station Controller) that uses the RNC ID.  
         [0060]    In one embodiment of FIG. 2, an RNC identifier is included in the Iur″ connectionless messages (e.g. an uplink signaling transfer message, a downlink signaling transfer message, a paging request message, a reset request or a reset response). The problem at the moment is that aforementioned Iur″ connectionless messages are not sent directly from the source IP BTS to the target RNC, but using the RNAS as a signaling gateway. In that case, there is a need to specifically specify which will be the target RNC (the one receiving the message), so that the RNAS can perform the correct routing. Therefore, the RNSAP protocol used in the Iur″ interface need to include the destination RNC identifier in the aforementioned messages.  
         [0061]    The RNC identifier extension element can also be used with any other present or future RNC identifier elements other than mentioned above.  
         [0062]    [0062]FIG. 3 illustrates the mapping between the U-RNTI protocol identifiers and the IP BTS identifier. The U-RNTI is allocated to all UEs having an RRC (Radio Resource Control) connection and it identifies the UE within the IP RAN, and identify univocally the user. It is defined as:  
         [0063]    Outside the IP RAN (SRNC id (12 bits)+S-RNTI (20 bits).  
         [0064]    Inside the IP RAN: gateway RNASid+(IP BTSid*+S-RNTI*).  
         [0065]    The n most significant bits of the S-RNTI are used as IP base station identifier BTSid* (identifies one IP BTS within one gateway RNAS area). The rest of the bits are used for the S-RNTI* (identify one UE connection uniquely within the IP BTS). An IP BTS is identified with the gateway RNAS ID and IP BTS id. This identifier can implicitly be presented in different formats: RNCID+SRNTI, RNCID+RNCID extension, or simply RNCID+IP BTS ID.  
         [0066]    The number of bits to be used for the IP BTSid* and for S-RNTI* is decided at the configuration stage, and different BTS may use different divisions between IP BTSid* and S-RNTI*, even if they are under the same RNAS. For example, an IP BTS at the center of a star point may have a large range reserved for the S-RNTI* while a small capacity indoor IP BTS need only a few bits for the S-RNTI*. In other words, several IP BTSids* could be assigned to one IP BTS for the support of a more number of users. Several RNC-ids may be assigned to an RNAS, so that the RNAS can support a higher number of users/IP base stations.  
         [0067]    [0067]FIG. 4 describes an exemplary radio access network node NODE in accordance with the present invention. The radio network element in FIG. 4 comprises two interface: a first interface IF 1  towards the core network and nodes in other radio access network(s) and a second interface IF 2  towards IP base stations. The radio access network node NODE comprises means for identifying IM a radio network access server and an IP base based on an RNC identifier and RNC identifier extension element extending the RNC identifier.  
         [0068]    In one embodiment of FIG. 4, means for identifying IM are arranged to identify an IP base station and the gateway radio network access server in the first interface IF 1  based on a target serving IP BTS identification element used in the first interface instance IF 1 .  
         [0069]    In one embodiment of FIG. 4, the radio network access node NODE further comprises means for reading RM the content of the Target RNC ID information element and the Target RNC ID information element extension element and means for copying CM read information into the target serving IP BTS identifier information element used in the first interface instance IF 1 . The target serving IP BTS identification element is incorporated in the Source RNC to Target RNC transparent container used in the first interface instance IF 1 .  
         [0070]    In one embodiment of FIG. 4, means for identifying IM are arranged to identify an RNC identifier in one or more of the following messages: an uplink signaling transfer indication, a paging request, a downlink signaling transfer indication, a reset request or a reset response.  
         [0071]    In one embodiment of FIG. 4, means for identifying IM are arranged to identify a radio network access server, an IP base station, and user equipment in the second interface instance IF 2  based on a three-part form identifier wherein the first part identifies a radio network access server, the second part identifies an IP base station, and the third part identifies user equipment.  
         [0072]    In one embodiment of FIG. 4, the radio access network node NODE is a radio network access server (RNAS). In another embodiment of FIG. 4, the radio access network node NODE is an IP base station (IP BTS). In this case, however, it may be possible that one or more of the aforementioned interfaces or means are not needed. The aforementioned means are preferably implemented with software and/or hardware, and therefore, they are not described in more detail.  
         [0073]    It is obvious to a person skilled in the art that with the advancement of technology, the basic idea of the invention may be implemented in various ways. The invention and its embodiments are thus not limited to the examples described above, instead they may vary within the scope of the claims.