EP2560423B1 - Method and system for allocating network temporary identities - Google Patents

Method and system for allocating network temporary identities Download PDF

Info

Publication number
EP2560423B1
EP2560423B1 EP11768405.0A EP11768405A EP2560423B1 EP 2560423 B1 EP2560423 B1 EP 2560423B1 EP 11768405 A EP11768405 A EP 11768405A EP 2560423 B1 EP2560423 B1 EP 2560423B1
Authority
EP
European Patent Office
Prior art keywords
information
home nodeb
hnb
identity allocation
prefix
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP11768405.0A
Other languages
German (de)
French (fr)
Other versions
EP2560423A4 (en
EP2560423A1 (en
Inventor
Min Xu
Dong Chen
Zheng Zhou
Bin Xu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CN201010155157.3A priority Critical patent/CN102223621B/en
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2011/072485 priority patent/WO2011127793A1/en
Publication of EP2560423A1 publication Critical patent/EP2560423A1/en
Publication of EP2560423A4 publication Critical patent/EP2560423A4/en
Application granted granted Critical
Publication of EP2560423B1 publication Critical patent/EP2560423B1/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/042Public Land Mobile systems, e.g. cellular systems
    • H04W84/045Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Description

    Field of Technology
  • The present invention relates communication technologies, and particularly, to a method and system of allocating Network Temporary Identities.
  • Background of the Invention
  • In some communication systems, such as Global System for Mobile Communications(GSM, Global System for Mobile Communications), Wideband Code Division Multiple Access Wireless(WCDMA, Wideband Code Division Multiple Access Wireless), Code Division Multiple Addressing(CDMA, Code Division Multiple Addressing), Worldwide Interoperability for Microwave Access (WiMAX, Worldwide Interoperability for Microwave Access), CDMA2000, TD-SCDMA, Long Term Evolution(LTE, Long Term Evolution), WLAN/WiFi and so on, in order to improve communication quality, a kind of home network technology is exploited.
  • As shown in Figure 1, a schematic diagram illustrating a structure of a UMTS in the prior art is illustrated. Universal Mobile Telecommunication System (UMTS, Universal Mobile Telecommunication System) adopting a similar structure as the second generation mobile telecommunication is a third generation mobile telecommunication system adopting WCDMA air interface technology. The UMTS is usually called WCDMA telecommunication system.
  • The UMTS system comprises a Radio Access Network (Radio Access Network, RAN) and a Core Network (Core Network, CN). Here, the Radio Access Network is used to process all functions related with Radio, while the CN processes all voice calling and data connection in the UMTS system, and realizes exchange and rout functions with External Network. The CN is logically divided into a Circuit Switched Domain (Circuit Switched Domain, CS) and a Packet Switched Domain (Packet Switched Domain, PS).
  • The Core Network (CN) comprises various network cells, such as a MSC/VLR, a Serving GPRS Support Node (SGSN, Serving GPRS Support Node), a HLR, a Gateway Mobile-services Switching Centre (GMSC, Gateway Mobile-services Switching Centre), a Gateway GPRS Support Node (GGSN, Gateway GPRS Support Node) and so on. The External Network can be connected through the GMSC or the GGSN. For example, a Public Land Mobile Network (PLMN, Public Land Mobile Network), a Public Switched Telephone Network (PSTN, Public Switched Telephone Network), an Integrated Services Digital Network (ISDN, Integrated Services Digital Network) and so on can be connected through the GMSC, and Internet can be connected through the GGSN.
  • The interface between a User Equipment (User Equipment, UE) and a UTRAN is Uu. A NodeB and a Radio Network Controller (RNC, Radio Network Controller) can be connected with each other through an Iub interface, and RNCs are connected with each other through an Iur interface. The interfaces between the UTRAN and the CN are all called Iu interface, which comprises an Iu-CS interface and an Iu-PS interface.
  • With the development of mobile communication technology, the demands of users present diversification. In order to satisfy the diversified demands of users, home coverage NodeB, corporation level inner coverage NodeB and other private networks emerge as the times require. For example, Home NodeB (Home NodeB, HNB for short) that is also called femtocell base station, femtocell, or AP (Action Point) turns into the most potential low-cost access technology.
  • As shown in Figure 2, a schematic diagram illustrating a structure of the Home NodeB system in the prior art is illustrated. The system comprises at least one Home NodeB, a HNB Management System (HMS, HNB Management System) and a Home NodeB Gateway (HNB-GW, Home NodeB Gateway). Here, the HNB provides the Uu interface to UEs, while the HNB and the HNB-GW are connected with each other through the Iuh interface, and the HNB-GW and the CN are connected with each other through the Iu interface (including the Iu-CS and the Iu-PS).
  • The HNB-GW is equivalent to the CN for the HNB, and is equivalent to the RNC for the CN. UEs are accessed to the network through the HNB and the HNB-GW In this case, the HNB realizes the functions of the NodeB and that of the RNC, the HNB-GW provides a HNB authentication and a control plane convergence and other functions, while the HMS mainly provides HNB related data configuration and other functions.
  • As a Home NodeB, the HNB, compared to traditional macro NodeBs, has the following characteristics: small coverage area, limited amount of carried users, large amount, dense deployment, multi-layer overlapping coverage, devices controlled by HNB users other than operators, HNB frequency band that may be different frequency deployed with Legacy network, low transmit power. The HNB may configure adjacent cells automatically through uplink detection, while it is hard to configure adjacent cell list in the prior art.
  • The application scenes of HNB are quite widely, such as home, corporation, public areas, etc. Different scenes have different demands on the HNB. For example, for the home usage, the coverage area of the HNB is small hence the number of users is small, while for the corporation usage, compared to the home usage, the coverage area of the HNB is relatively larger, and the number of user is obviously increased since users of the corporation are more concentrated.
  • In the macro network, UTRAN Radio Network Temporary Identity (U-RNTI, UTRAN Radio Network Temporary Identity) is used for identifying UE uniquely, and consists of two parts: U RNTI 32 bit = SRNC identity + S RNTI .
    Figure imgb0001
  • Here, the SRNC identity is an identity of RNC, identifying one RNC uniquely in one Public Land Mobile Network (PLMN, Public Land Mobile Network). While, the Serving-Radio Network Temporary Identifier (S-RNTI, Serving-Radio Network Temporary Identifier) is allocated by a Serving RNC (SRNC, Serving RNC) and identifies one UE uniquely under one RNC. Generally speaking, the length of U-RNTI is 32bits, the length of SRNC identity is 12bits, and the length of S-RNTI is 20bits. However, sometimes, an expansion is made to the SRNC identity whose length can reache to the maximum of 12bits, while in this case, the length of the S-RNTI is 16bits. In the UMTS macro network, the U-RNTI is allocated by a RNC entity to a UE with RRC connection. One new U-RNTI is allocated to the UE, when the UE sets up the RRC connection, or when the UE performes cell updating, or when the process of Serving Radio Network Subsystem (SRNS, Serving Radio Network Subsystem) relocation or other situation occurs.
  • However, for the HNB network, the RRC connection of UE terminates in the HNB. The HNB integrates functions of the NodeB and that of the RNC in the macro network, while the HNB-GW provides the function of control plane convergence. In the access network, the structure of the HNB network is evidently different from that of the macro network. In the HNB network, different methods of allocating U-RNTIs can be completed by any one or combination of the HNB and the HNB-GW. In this case, on the Iu interface of the HNB network, a RNC-ID is used for identifying HNB-GW uniquely in the Core Network, wherein the RNC-ID may be transfered to the HNB connected with the HNB-GW during a register process of the HNB. Therefore, when U-RNTI allocation is performed, the RNC-ID of HNB-GW may be used as the SRNC identity.
  • Therefore, in the HNB network, realizing of the U-RNTI may be as follows: U RNTI = RNC ID + S RNTI .
    Figure imgb0002
  • However, since multiple HNBs can be connected to one HNB-GW, uniqueness of S-RNTI needs to be guaranteed when U-RNTIs are allocated to these
  • In the prior art, the HNB and HNB-GW complete the allocation of U-RNTIs together, which mainly shows as follows:
    • After initialing a calling, a UE sets up Radio Resource Control (RRC, Radio Resource Control) connection with a HNB, and the HNB allocates randomly, in the Radio Resource Control Connection Setup (RRC Connection Setup) message, one U-RNTI to the UE. The UE initiates initial direct transfer, and the HNB transfers the U-RNTI allocated randomly by the HNB to the HNB-GW through RANAP User Adaption (RUA, RANAP User Adaption) CONNECT message, namely that the RUA CONNECT message transfered to the HNB-GW carries the randomly-allocated U-RNTI. The HNB-GW checks the allocated U-RNTI. If there is no conflict, the HNB-GW stores the U-RNTI and performs the normal process continuously. If a conflict is found, the HNB-GW reallocates one U-RNTI without conflict to the HNB. The HNB reallocates the U-RNTI to the UE, and notices the HNB-GW that the reallocation process has been completed.
  • In the prior art, the HNB-GW needs to manage allocation operation of each U-RNTI, and further needs to store each allocated U-RNTI. Simultaneously, the HNB-GW further needs to traverse each stored U-RNTI to check whether a conflict occurs after the HNB allocates one new U-RNTI each time, which increases the implementation complexity of the HNB-GW and brings some time delay. The document "Managing of U-RNTI over the Iuh interface", Kinteo Wireless Inc, 3GPP TSG-RAN WG3 Meeting #65, 24.-28.08.2009, discloses the U-RNTI coordination aspects within HNB network.
  • The document WO 2010/019970 A1 discloses the management of U-RNTI.
  • Summary of the Invention
  • The embodiments of the present invention provides a method of allocating Network Temporary Identities, Home NodeB Gateway, Home NodeB and system, which can reduce the implementation complexity of the Home NodeB Gateway and the time delay, as defined by the independent claims. The technical solutions disclosed by the embodiments of the present invention can reduce the implementation complexity of Home NodeB Gateway and the time delay.
  • Brief Description of the Drawings
  • To illustrate the technical solutions in the embodiments of the present invention or in the prior art more clearly, a brief introduction to the accompanying drawings which are needed in the description of the embodiments or the prior art is given below. Apparently, the accompanying drawings described below are some embodiments of the present invention, based on which other drawings can be obtained by the persons of ordinary skills in the art without any inventive efforts.
    • Fig.1 is a schematic diagram illustrating a structure of a UMTS in the prior art.
    • Fig.2 is a schematic diagram illustrating a structure of a Home NodeB in the prior art.
    • Fig.3 is a schematic diagram illustrating a structure of a Home NodeB provided in an embodiment of the present invention.
    • Fig.4 is a schematic flowchart illustrating a method of allocating UTRAN Network Temporary identities provided in another embodiment of the present invention.
    • Fig.5 is a schematic flowchart illustrating a method of allocating UTRAN Network Temporary identities provided in yet another embodiment of the present invention.
    • Fig.6 is a schematic diagram illustrating a tree strcuture of HNB-GW managing U-RNTIs provided in yet another embodiment of the present invention.
    • Fig.7 is a schematic flowchart illustrating a method of allocating UTRAN Radio Network Temporary Identities provided in yet another embodiment of the present invention.
    • Fig.8 is a schematic flowchart illustrating a method of allocating UTRAN Radio Network Temporary Identities provided in yet another embodiment of the present invention.
    • Fig.9 is a schematic flowchart illustrating a method of allocating UTRAN Radio Network Temporary Identities provided in yet another embodiment of the present invention.
    • Fig.10 is a schematic flowchart illustrating a method of obtaining U-RNTI during the process of cell updating provided in yet another embodiment of the present invention.
    • Fig.11 is schematic diagram illustrating a structure of the system of allocating UTRAN Radio Network Temporary Identities provided in yet another embodiment of the present invention.
    • Fig.12 is schematic diagram illustrating a structure of the system of allocating UTRAN Radio Network Temporary Identities provided in yet another embodiment of the present invention.
    • Fig.13 is a schematic diagram illustrating a structure of a Home NodeB provided in yet another embodiment of the present invention.
    Detailed Description of the Embodiments
  • In the following description, in order to illustrate other than to limit, specific details, such as specific system architecture, interface, technology and the like, are mentioned, so as to understand the present invention thoroughly. However, those skilled in the art should understand that the present invention can also be implemented in other embodiments without these details. In other cases, the detailed description of the well-known devices, circuits and methods are omitted to avoid unnecessary details to hinder the description of the present invention.
  • In the present application, "and/or", or "or/and" is a brief language expression manner, denoting three kinds of relationship. For example, "A and/or B"denotes that A is comprised alone, B is comprised alone, and A and B is comprised simultaneously.
  • The technical solutions of the present invention can be applied to various communication systems, for example, GSM, Code Division Multiple Access (CDMA, Code Division Multiple Access) system, TDS-CDMA, CDMA2000, WIMAX, Wideband Code Division Multiple Access (WirelessWCDMA, Wideband Code Division Multiple Access Wireless), General Packet Radio Service (GPRS, General Packet Radio Service), Long Term Evolution (LTE, Long Term Evolution), etc. The User Equipment (UE, User Equipment) may be Mobile Terminal or stationary terminal, etc.
  • As shown in Figure 3, a schematic diagram illustrating a structure of a Home NodeB system provided in an embodiment of the present invention is illustrated. For example, taking the WCMDA system as an example, the Home NodeB system may comprise at least one Home NodeB (HNB) 301, Home NodeB Gateway (HNB-GW) 303 and HNB management system (HMS) 305, wherein the HNB301 provides a Uu interface to at least one UE302, while the HNB301 and the HNB-GW303 connects with each other through an Iuh interface, and the HNB-GW303 and the CN307 connects with each other through an Iu interface (comprising an Iu-CS, an Iu-PS).
  • The Home NodeB system shown in Figure 3 only comprises one Home NodeB Gateway, three Home NodeBs (HNBs) and three User Equipments (UEs), but in practical, the present system may comprise any amount of Home NodeB Gateways, Home NodeBs and UEs, which is not limited by the present invention.
  • The HNB-GW303 or the HNB management system (HMS) 305 is used for obtaining capability information of the Home NodeB (HNB) 301, allocating information for performing identity allocation to the Home NodeB according to the capability information and sending the allocated information for performing identity allocation to the Home NodeB, wherein the different information for performing identity allocation corresponds to different Home NodeBs to implement network temporary identity allocation. The information for performing identity allocation is prefix information for performing identity allocation, and the lengths of the prefix information for performing identity allocation are different when the capability information of Home NodeBs is different.
  • In another embodiment of the present invention, the information for performing identity allocation is one or multiple prefix information for performing identity allocation with fixed length. The prefix information for performing identity allocation with fixed length is Cell ID information.
  • The HNB-GW303 or the HNB management system (HMS) 305 is used for obtaining the capability information of the Home NodeB (HNB) 301 and allocating prefix information for performing identity allocation with different lengths to the HNBs with different capabilities and sending the allocated prefix information for performing identity allocation to the HNB 301.
  • In another embodiment of the present invention, the HNB-GW303 or the HNB management system (HMS) 305 is further used for sending the length information of the prefix information for performing identity allocation to the HNB301.
  • For example, during a register process of the HNB, a configuration process of the HNB or a reconfiguration process of the HNB, the HNB 301 reports its capability information to the HNB-GW303 or the HNB management system (HMS).
  • In another embodiment of the present invention, the HNB-GW 303 obtains the capability information of the Home NodeB 301 through the HNB management system (HMS, HNB Management System) 305 or a configuration method of an Operation and Maintenance (OAM, Operation and Maintenance).
  • In another embodiment of the present invention, the capability information of the Home NodeB 301 may be HNB type information, HNB usage scene information, the number of UEs needed to be supported by the HNB, or specific identity length needed by the HNB.
  • The Home NodeB 301 is used for implementing the Network Temporary Identity allocation according to the information for performing identity allocation.
  • For example, the Home NodeB 301 is used for allocating corresponding amount of bits to identify Use Equipments under the Home NodeB according to the prefix information for performing identity allocation and the information for identifying the HNB-GW
  • For example, the Home NodeB301 allocates corresponding amount of bits for the information for identifying User Euipments under the Home NodeB according to the relationship that the sum of bits occupied by the length information of the prefix information for performing identity allocation, the length information of the information for identifying HNB-GW and the information for identifying User Equipment under the Home NodeB is a predetermined value.
  • The HNB-GW303 is further used for sending the information for identifying the HNB-GW to the HNB 301, for example, RNC-ID. The RNC-ID is used for identifying HNB-GWs in a same Core Network.
  • For the specific functions of the HNB 301 and that of the HNB-GW303, please refer to the description of embodiments provided in Figure 4.
  • The working process of the Home NodeB system may be illustrated by Figure 4, which is a schematic flowchart illustrating a method of allocating Network Temporary Identities provided in another embodiment of the present invention. In the present embodiment, the Network Temporary Identity may be a UTRAN Radio Network Temporary Identity.
  • 401, capability information of a Home NodeB is obtained.
  • For example, during a register process of the HNB, a configuration process of the HNB or a reconfiguration process of the HNB, the Home NodeB Gateway or the HNB management system (HMS) receives the capability information reported by the Home NodeB.
  • For example, during the register process of the HNB, the Home NodeB sends a register request to the Home NodeB Gateway or HNB management system (HMS), wherein the register request carries the capability information of the Home NodeB.
  • For example, during the configuration process of the HNB, the Home NodeB sends a configuration request to the Home NodeB Gateway or the HNB management system, wherein the configuration request carries the capability information of the Home NodeB.
  • For example, during the reconfiguration process of the HNB, the Home NodeB sends a reconfiguration request to the Home NodeB Gateway or the HNB management system (HMS), wherein the reconfiguration request carries the capability information of the Home NodeB.
  • In another embodiment of the present invention, the HNB-GW obtains the capability information of the Home NodeB by the HNB management system (HMS) or the configuration method of an Operation and Maintenance (OAM).
  • In another embodiment of the present invention, the capability information of the Home NodeB may be HNB type information, HNB usage scene information, the amount of UEs needed to be supported by the HNB, or specific identity length needed by the HNB.
  • 402, information for performing identity allocation is allocated to the Home NodeB according to the capability information, and the allocated information for performing identity allocation is sent to the Home NodeB.
  • For example, it is described based on the following situation as an example, that the information for performing identity allocation is the prefix information for performing identity allocation, and the lengths of the prefix information for performing identity allocation are different when the capability information of the Home NodeBs is different.
  • The Home NodeB Gateway or the HNB management system (HMS) allocates prefix information for performing identity allocation with different lengths to the HNBs with different capabilities, and sends the allocated prefix information for performing identity allocation to the HNBs.
  • In another embodiment of the present invention, the Home NodeB Gateway or the HNB management system (HMS) further sends the length information of the allocated prefix information for performing identity allocation to the Home NodeB.
  • For example, the HNB-GW allocates prefix information for performing identity allocation with different lengths to various HNBs according to different capability information of the various HNBs, and the Home NodeB allocates corresponding amount of bits for the information for identifying User Equipments under the Home NodeB according to the prefix information for performing identity allocation and the information for identifying the HNB-GW. For example, the HNB allocates corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationshipthat the sum of bits occupied by the length information of the prefix information for performing identity allocation, and the length information of the information for identifying HNB-GW and the information for identifying User Equipments under Home NodeB is a predetermined value.
  • For example, the UTRAN Radio Network Temporary Identity comprises RNC-ID and S-RNTI, namely U-RNTI=RNC-ID+S-RNTI. While, in order to identify HNBs under a same HNB-GW and UEs under a same HNB, S-RNTIs need to be allocated. For example, the S-RNTI further comprises the prefix information for performing identity allocation (S-RNTI prefix)and Home NodeB Radio Network Temporary Identity (HNB-RNTI), namely that the relationship between the information lengths is that U-RNTI=RNC-ID+S-RNTI prefix+HNB-RNTI.
  • Here, the RNCI-ID is used for identifying a HNB-GW under a same Core Network, and the S-RNTI prefix is used for a Home NodeB to implement the network temporary identity allocation.
  • In another embodiment of the present invention, the HNB-GW determines the information length of the prefix information that needs to perform identity allocation according to the capability information reported by various HNBs, and then allocates the prefix information for performing identity allocation with different lengths, for example, Home NodeB indications (S-RNTI prefixes), to the various HNBs with different capabilities.
  • The HNB-GW further sends the information for identifying HNB-GW to the HNB, for example, RNC-ID, wherein the RNC-ID is used for identifying a HNB-GW under a same Core Network.
  • 403, the Home NodeB implements the network temporary identity allocation according to the information for performing identity allocation, wherein the different information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  • For example, taking the information for performing identity allocation being the prefix information for performing identity allocation as an example, since the lengths of S-RNTI prefixes used by HNBs with different capabilities under a same HNB-GW may be different, the lengths of HNB-RNTIs reserved for the HNBs to allocate are different.
  • For example, assuming that the length of the U-RNTI is a certain predetermined value (N bits), when the length of the allocated RNC-ID is a first value (n1 bits) and the length of the S-RNTI prefix allocated to the HNB by the HNB-GW according to the capability of the HNB is a second value (n2 bits), the HNB allocates, according to the information length relationship, namely, U-RNTI=RNC-ID+S-RNTI prefix+HNB-RNTI, the remaining bits to UEs thereunder to identify various UEs.
  • For example, assuming that the length of the U-RNTI is 32 bits, if the length of the RNC-ID is 12 bits and the capability information reported by the HNB is that one HNB only needs to support 16 UEs, then the length of the S-RNTI prefix allocated by the HNB-GW is 16bits, namely that the maximum of 216=65536 HNBs may be supported under one HNB-GW, while the length of the HNB-RNTI allocated by the HNB is 4bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 24=16 UEs. If the capability information reported by the HNB-GW is that one HNB needs to support 64 UEs, the length of the S-RNTI prefix allocated by the HNB-GW is 14bits, namely that the maximum of 214=16384 HNBs may be supported under one HNB-GW, while the length of the HNB-RNTI allocated by the HNB is 6 bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 26=64 UEs.
  • In another embodiment of the present invention, the Home NodeB broadcasts the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation through a system message. The Home NodeB obtains the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation by reading a broadcast message of an adjacent HNB or by configuration.
  • In another embodiment of the present invention, the information for performing identity allocation is one or multiple prefix information for performing identity allocation with fixed length. The prefix information for performing identity allocation with fixed length is Cell Identity information.
  • During a register process of the HNB, a configuration process of the HNB or a reconfiguration process of the HNB, the Home NodeB reports the capability information or/and the number information of the cell identity information to the Home NodeB Gateway (HNB-GW) or the HNB management system (HMS).
  • For example, during the HNB initialing, or the HNB background configuring, or interacting with the HMS, or the HNB registering, or the HNB configuring, or the HNB reconfiguring, a capability interaction is performed, and the HMS or the HNB-GW allocates one or multiple Cell Identity information according to the capability information of the HNB.
  • Cell ID is comprised when the HNB allocates the U-RNTI. If the U-RNTI is of 23-bit, and if the Cell ID is of 28-bit, in the case that the Cell ID is comprised, 4 bits remains, which is allocated to identity users by the HNB, namely that there may be 24=16 connected users under each Cell ID.
  • The HNB notices the HMS the number of the connected users that may be supported thereby during the process of performing initiazition, and the HMS allocates, according to the capability of the HNB, the number of Cell IDs occupied by the HNB, wherein the allocation format of Cell ID is as follows.
  • The HNB-GW or the HMS allocates, according to the capability information of the HNB, one or multiple prefix information performing identity allocation with fixed length to the HNB. For example, the prefix information for performing identity allocation may be Cell identity (Cell ID) information.
  • For example, if the HNB may support maximum of 16 users in connected state, the HNB-GW or the HMS only needs to allocate one Cell ID to the HNB to use.
  • For example, if the HNB may support maximum of 16-32 users in connected state, the HNB-GW or the HMS only needs to allocate two consecutive Cell IDs to the HNB to use:
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx00;
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx01.
  • For example, if the HNB may support maximum of 32-48 users in connected state, the HNB-GW or the HMS only needs to allocate three consecutive Cell IDs to the HNB to use:
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx00;
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx01;
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx10.
  • For example, if the HNB may support maximum of 48-64 users in connected state, the HNB-GW or HMS only needs to allocate four consecutive Cell IDs to the HNB to use:
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx00;
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx01;
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx10;
    • xxxx,xxxx,xxxx,xxxx,xxxx,xxxx,xx11.
  • If the capability of the HNB is stronger, the rest may be deduced by analogy. One or multiple Cell ID may be allocated, and it may be defined that, among the Cell IDs allocated to the HNB to use, the first one is a primary Cell ID broadcasted to external, and other Cell IDs are visible for the HNBs, the HMS and the HNB-GW For UEs, only the Cell ID broadcasted by the HNB is visible.
  • For example, the relationship between the information lengths is that U-RNTI=Cell ID+HNB-RNTI. The HNB-GW or the HMS may allocate multiple consecutive Cell IDs to the HNB according to the capability of the HNB, thus the number of U-RNTIs that can be allocated by the HNB is also increased.
  • For example, if the HNB needs to allocate the U-RNTIs (32 bits) to 16 UEs, only one Cell ID (28bits) needs to be allocated to the HNB, and the remaining 4 bits are allocated by the HNB, namely 24=16.
  • If the U-RNTIs (32bits) need to be allocated to 17-32 UEs, two Cell IDs (28bits), namely, 0000, 0000, 0000, 0000, 0000, 0000, 0000 and 0000, 0000, 0000, 0000, 0000, 0000, 0001, need to be allocated to the HNB, and during the allocation, the number of the available U-RNTIs is totally 32, that is 0000, 0000, 0000, 0000, 0000, 0000,0000,0000∼0000, 0000, 0000, 0000, 0000, 0000,0000,1111 and 0000, 0000, 0000, 0000, 0000, 0000,0001,0000∼0000, 0000, 0000, 0000, 0000, 0000,0001,1111.
  • If the U-RNTIs (32bits) need to be allocated to 33-48 UEs, three cell IDs (28bits), namely, 0000, 0000, 0000, 0000, 0000, 0000,0000 and 0000, 0000, 0000, 0000, 0000, 0000,0001 and 0000, 0000, 0000, 0000, 0000, 0000,0010, need to be allocated to the HNB, and 48 U-RNTIs are available.
  • The HNB broadcasts the first configurated Cell ID in a system message, and the HNB needs to report the number of the allocated Cell ID information to the HNB-GW, during the register process or the configuration process or the reconfiguration process, when the configuration is performed by the HMS or by background, thus the HNB-GW may calculate what Cell iId information is configured to the HNB.
  • At this time, the number of the Cell Identity information occupied by the HNB needs to be further broadcasted in the system message.
  • In another embodiment of the present invention, the Home NodeB broadcasts the number information of the Cell Identity information by a system message. The Home NodeB obtains the number information of the Cell Identity information by reading the broadcast message of adjacent HNB or by configuration.
  • In another embodiment of the present invention, when the process of removing register or releasing configuration of the HNB occurs, the Home NodeB releases the prefix information for performing identity allocation. For example, the HNB-GW notices the HNB to release the allocated prefix information for performing identity allocation, or the HNB notices the HNB-GW to release the prefix information for performing identity allocation.
  • Therefore, during the process of communication, the U-RNTIs may be allocated dynamically according to the capability information reported by the HNBs. Thus the U-RNTIs may be allocated or used flexibly and reasonably according to different scenes, for example, home usage scene, corporation or marketplace and other different network deploying scenes. HNB-GW network deploying plan needs not to be re-performed, so as to save costs.
  • Furthermore, the HNB-GW needs not to manage the allocation operation of each U-RNTI, and needs not to traverse each stored U-RNTI to check whether a conflict is exist, which reduces the implementation complexity of the Home NodeB Gateway and the time delay brought by the allocation of U-RNTIs.
  • The following embodiment is described based on the following supposition which is taked as an example: the information for performing identity allocation is prefix information for performing identity allocation, and the lengths of prefix information for performing identity allocation are different when the capability information of Home NodeBs is different.
  • In an embodiment of the present invention, the Home NodeB Gateway (HNB-GW) or the HMS obtains the capability information of the Home NodeB (HNB), and the HNB may report its capability information to the HNB-GW or the HMS during the register process of the HNB, the configuration process of the HNB or the reconfiguration process of the HNB. The HNB-GW may otherwise obtain the capability information of the Home NodeB by the HMS or the Operation and Maintenance (OAM, Operation and Maintenance) and other configuration method. However, in order to describe conveniently, several cases are taken as an example.
  • As shown in Figure 5, the method of allocating UTRAN radio Network Temporary Identities is illustrated, which is described as follows.
  • 501, the HNB performs initialization and sets up connection with the HNB-GW
  • 502, the HNB sends a register request to the HNB-GW, for example, HNB register request of Home NodeB application Part (HNBAP, Home NodeB Application Part, HNB Register Request), wherein the register request carries the capability information of the HNB.
  • For example, the register request carries a HNB type, a HNB capability, a HNB usage scene, or other information, or the number of the UEs needed to be supported by the HNB, or the specific identity length needed by the HNB.
  • 503, the HNB-GW performs the management of U-RNTIs and allocates different S-RNTI prefixes to HNBs with different capabilities according to the capability information reported by the HNBs.
  • For the HNBs under a same HNB-GW, since the lengths of the S-RNTI prefixes used by the HNBs with different capabilities may be different, the lengths of the HNB-RNTIs reserved for the HNBs to allocate are different.
  • In the present embodiment, the process of the HNB-GW managing the U-RNTIs may be described as follows. The RNI-ID is used for identifying HNB-GWs under a same Core Network, thus the HNB-GW only needs to manage the allocation of the S-RNTIs. While, in the management of the S-RNTIs, the part of allocating S-RNTI prefixes only needs to be managed, thus the HNB-GW needs not to manage the allocation of each specific U-RNTI, which reduce the implementation complexity of the HNB-GW In the present embodiment, the HNB-GW manages the allocation of U-RNTIs by adopting a tree structure.
  • As shown in Figure 6, a schematic diagram illustrating a tree structure of HNB-GW managing U-RNTIs provided in another embodiment of the present invention is illustrated.
  • As shown in Figure 6, n denotes the number of layers of the tree in the tree structure, which is used for denoting the length of S-RNTI prefix. If the length of the RNC-ID is r bits, (32-r-n) bits may be remained for the HNB to perform the allocation of U-RNTIs. As the example taken in the figure, assuming that the S-RNTI prefix of the first HNB is 0000 0000 0000 00 and n=14, the HNB-GW needs to manage the branches, (0000 0000 0000 00xx..), deriving from itself, and the HNB-GW only may reallocate this branch and derived branches thereof, until that the first HNB and HNB-GW loss connection with each other caused by register removing of the first HNB or other reason and that the HNB-GW releases the S-RNTI prefix of the first HNB. When the HNB-GW needs to allocate S-RNTI prefix to the second HNB, the allocation needs to be started from another branch (0000 0000 0000 01..), for example, n=16, thus the S-RNTI prefix of the second HNB may be 0000 0000 000 0100. In the same way, the HNB-GW also needs not to maintain and allocate several branches below itself.
  • 504, the HNB-GW sends a register accept message to the HNB, wherein the register accept message carries the S-RNTI prefix allocated to the HNB.
  • In another embodiment of the present invention, the register accept message further carries the length information of the S-RNTI prefix.
  • In another embodiment of the present invention, the register accept message may further carry the RNC-ID.
  • 505, the HNB allocates corresponding amount of bits for identifying User Equipments under the HNB, according to the S-RNTI prefix and the RNC-ID.
  • The HNB stores the S-RNTI prefix and/or the length information of the S-RNTI prefix, and may broadcast these information.
  • The HNB may perform the U-RNTI allocation by combining the RNC-ID and S-RNTI information, and the HNB may allocate the remaining bits to different UEs. The specific description may be described as follows.
  • For example, the HNB allocates corresponding amount of bits for identifying User Equipments under the HNB according to the relationship between the information lengths, namely, U-RNTI=RNC-ID + S-RNTI prefix+ HNB-RNTI.
  • Wherein the S-RNTI prefix is of variable length and is allocated by the HNB-GW, and the HNB-RNTI is of variable length and is allocated by the HNB.
  • For example, when the length of the U-RNTI is limited to 32bits, if the length of the RNC-ID is 12 bits and if the capability information reported by the HNB is that one HNB only needs to support 16UEs, the length of the S-RNTI prefix allocated by the HNB-GW is 16 bits, namely, the maximum of 216=65536 HNBs may be supported under one HNB-GW, while the length of the HNB-RNTI is 4 bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 24=16UEs. If the capability information reported by the HNB is that one HNB only needs to support 64 UEs, the length of the S-RNTI prefix allocated by the HNB-GW is 14 bits, namely, the maximum of 214=16384 HNBs may be supported under one HNB-GW, while the length of the HNB-RNTI is 6 bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 26=64UEs.
  • In another embodiment of the present invention, the Home NodeB broadcasts the S-RNTI prefix and/or the length information of the S-RNTI prefix by a system message. The Home NodeB obtains the S-RNTI prefix and/or the length information of the S-RNTI prefix by reading the broadcast message of the adjacent HNB or by configuration.
  • In another embodiment of the present invention, when the process of removing register or releasing configuration of the HNB occurs, the Home NodeB releases the prefix information for performing identity allocation. For example, the HNB-GW notices the HNB to release the allocated prefix information for performing identity allocation, or the HNB notices the HNB-GW to release the prefix information for performing identity allocation.
  • Therefore, during the process of communication, the U-RNTIs may be allocated dynamically according to the capability information reported by the HNBs. Thus the U-RNTIs may be allocated or used flexibly and reasonably according to different scenes, for example, home usage scene, corporation or marketplace and other different network deploying scenes. HNB-GW network deploying plan needs not to be re-performed, so as to save costs.
  • Furthermore, the HNB-GW needs not to manage the allocation operation of each U-RNTI, and needs not to traverse each stored U-RNTI to check whether a conflict is exist, which reduces the implementation complexity of the Home NodeB Gateway and the time delay brought by the allocation of U-RNTIs.
  • As shown in Figure 7, a schematic diagram illustrating the method of allocating UTRAN Network Temporary Identities provided in another embodiment of the present invention is illustrated. The present embodiment describes UTRAN Radio Network temporary identity allocation in the process of UE seting up RRC connection.
  • 701, a UE decides to initiate a calling (Mo call) in a HNB.
  • 702, the UE sends a RRC connection Setup request (RRC Connection Request) to the HNB.
  • The RRC Connection Setup Request carries a temporary identity (TMSI, Temporary Mobile Subscriber Identity).
  • 703, the HNB sends s RRC connection Setup (RRC Connection Setup message) message to the UE, wherein the RRC Connection Setup message carries the U-RNTI allocated to the UE by the HNB.
  • For example, the Home NodeB implements the allocation of UTRAN Radio Network Temporary identities, according to the information for identifying HNB-GW and the S-RNTI prefix.
  • For example, the HNB allocates, according to the capability information itself, the information for identifying HNB-GW after receiving the RRC Connection Setup Request, then allocates corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationship that the sum of bits occupied by the prefix information for performing identity allocation, the information for identifying HNB-GW, and the information for identifying User Equipments under the Home NodeB is a predetermined value.
  • For example, the relationship between the information lengths is that U-RNTI=RNC-ID+S-RNTI prefix+HNB-RNTI. The HNB allocates the U-RNTI to the UE according to the relationship.
  • After allocating the U-RNTI to the UE, the HNB transfers the U-RNTI to the UE through the RRC Connection Setup message.
  • 704, after receiving the RRC Connection Setup message, the UE sends RRC Connection Setup Complete message. The entire process of RRC connection setup is finished.
  • Through the above description, it can be seen that the signaling overload and the time delay can be reduced when the U-RNTI is allocated to a certain UE.
  • In another embodiment of the present invention, the HNB-GW obtains, by the HMS, the OAM or other configuration method, the capability information of the HNB, or the HNB type information, or the HNB usage scene information. As shown in Figure 8, the schematic flowchart of allocating UTRAN Radio Network Temporary Identities provided in another embodiment of the present invention is illustrated.
  • 801, the HNB performs initialization and sets up connection with the HNB-GW, and obtains the capability information of the HNB by the HMS, the OAM or other configuration method.
  • For example, the HNB performs the initialization and sets up the connection with the HNB-GW, and the HNB-GW obtains the HNB type, or the HNB capability information, or the HNB usage scene information by the HMS or OAM configuration method.
  • 802, the HNB initiates a register request.
  • 803, the HNB-GW performs the management and allocation of U-RNTIs.
  • For example, the HNB-GW performs the managemnt of U-RNTIs and allocates different S-RNTI prefixes to HNBs with different capabilities, according to the obtained HNB capability information. For the specific allocation process, which is not described repeatedly, please refer to the processes of embodiments corresponding to Figure 5 and Figure 6.
  • 804, the HNB obtains the S-RNTI prefix by a HNB register accept message.
  • The Home NodeB completes the allocation of UTRAN Radio Network temporary Identities, according to the information for identifying HNB-GW and the S-RNTI prefix.
  • For example, the Home NodeB allocates corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationship that the sum of bits occupied by the length information of the S-RNTI prefix, the length information of the information for identifying HNB-GW and the information for identifying User Equipments under the Home NodeB is a predetermined value.
  • In another embodiment of the present invention, the register accept message further carries the length information of the S-RNTI prefix.
  • In another embodiment of the present invention, the register accept message further carries the RNC-ID.
  • 805, the HNB stores the S-RNTI prefix and /or its length information, and may broadcast these information.
  • For the method of managing the HNB-GW and allocating the U-RNTIs, and the process of the HNB allocating the information for identifying User Equipments under the Home NodeB to the UE, which are not described repeatedly, please refer to the processes of embodiments corresponding to Figure 5 and Figure 6.
  • In another embodiment of the present invention, the S-RNTI prefix with variable length used during the process of allocating U-RNTIs and the length thereof may be further noticed to the HNB, the HNB-GW and the adjacent HNBs by the method of background configuration.
  • In another embodiment of the present invention, the HNB obtains the S-RNTI prefix and/or the length information, and may broadcast the information in a broadcast message. Since the HNB has a function of downlink detection, the HNB may read the information of adjacent cells and implement configuration of related adjacent cells, namely that the adjacent HNB may read and store the S-RNTI prefix and/or the length information of the S-RNTI prefix, or obtain the S-RNTI prefix and/or the length information of the S-RNTI prefix through the background configuration. Therefore, the target HNB may find directly the source HNB according to the U-RNTI when the direct interface between the HNBs is introduced.
  • As shown in Figure 9, a schematic flowchart illustrating the method of allocating U-TRAN Radio Network Temporary Identities is illustrated. The present embodiment describes the allocation of UTRAN Radio Network Temporary Identities during the process of configuration or reconfiguration.
  • 901, the HNB sends a configuration or reconfiguration request to the HNB-GW, wherein the configuration or reconfiguration request carries the capability information of the HNB.
  • For example, the capability information of the Home NodeB may be HNB type information, HNB usage scene information, the number of UEs needed to be supported by the HNB, or specific identity length needed by the HNB.
  • 902, the HNB-GW performs the management and allocation of U-RNTIs.
  • For example, the HNB-GW allocates the prefix information (for example, S-RNTI prefix) for performing identity allocation with different lengths to HNBs with different capabilities after receiving the capability information of the HNBs, wherein different information for performing identity allocation corresponds to different Home NodeBs to implement the allocation of UTRAN Radio Network Temporary Identities.
  • 903, the HNB-GW sends a configuration or reconfiguration finish message carrying the S-RNTI prefix to the HNB.
  • The HNB-GW further sends the information for identifying HNB-GW to the HNB, for example, RNC-ID which is used for identifying HNB-GWs under a same Core Network.
  • 904, the HNB stores and broadcasts the S-RNTI prefix.
  • The Home NodeB allocates corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the prefix information for performing identity allocation and the information for identifying HNB-GW For example, the Home NodeB allocates corresponding amount of bits for the information for identifying User Equipments under the Home NodeB according to the relationshipthat the sum of bits occupied by the length information of the prefix information for performing identity allocation, the length information of the information for identifying HNB-GW and the information for identifying User Equipments under the Home NodeB is a predetermined value.
  • In another embodiment of the present invention, the Home NodeB broadcasts the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation through a system message. The Home NodeB obtains the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation, by reading a broadcast message of an adjacent HNB or by configuration.
  • In another embodiment of the present invention, when the process of removing register or releasing configuration of the HNB occurs, the Home NodeB releases the prefix information for performing identity allocation. For example, the HNB-GW notices the HNB to release the allocated prefix information for performing identity allocation or the HNB notices the HNB-GW to release the prefix information for performing identity allocation.
  • As shown Figure 10, a schematic flowchart illustrating the method of determining source HNB by obtaining U-RNTI during the process of UE cell updating is illustrated. When the UE in NON-CELL_DCH state moves from source Home NodeB (source HNB) to targetHome NodeB (target HNB), the process of cell updating is initiated.
  • 1001, the UE initiates the process of cell updating, and sends a Cell updating message to the target Home NodeB, wherein the Cell updating message carries the U-RNTI allocated by the source HNB.
  • 1002, the target Home NodeB detects the stored S-RNTI prefixes of adjacent cells, and finds the source HNB by the S-RNTI in the received U-RNTI allocated by the source HNB.
  • The target HNB receives the Cell updating message and obtains the U-RNTI of the source HNB therein, then finds that the U-RNTI is not allocated by the present cell.
  • Since the two HNBs are both connected to the same HNB-GW, the RNC-IDs corresponding to the two HNBs are same. Therefore, when the target HNB finds that the RNC-ID carried by the U-RNTI is same with the RNC-ID of the HNB-GW connected therewith, it may be determined that the target cell is also managed simultaneously by the same adjacently-connected HNB-GW.
  • The target Home NodeB detects the stored prefix information for the adjacent cells to perform identity allocation, and finds the source HNB by the prefix information for performing identity allocation in the received U-RNTI allocated by the source HNB.
  • For example, the target HNB may compare the S-RNTI prefix in the U-RNTI allocated by the source HNB with the stored S-RNTI prefix information of adjacent cells. For example, the matching is performed from the highest bit. When one matched S-RNTI prefix information is found, the HNB may find the source HNB by this information.
  • 1003, the target HNB sends a Cell updating message to the source HNB.
  • For example, the target HNB sends the Cell updating message to the source HNB by the interface between the target HNB and the source HNB, wherein the Cell updating message carries the U-RNTI allocated by the source HNB.
  • According to the above process, it can be seen that the target HNB may be found by the target HNB, through the interface between the HNBs, the U-RNTI allocated by the source HNB during the process of cell updating, which needs not the assistance and forwarding of the HNB-WG, thus the load of processing signaling in the HNB is decreased, and the time delay is reduced.
  • A system of allocating UTRAN Radio Network Temporary identities is further disclosed in another embodiment of the present invention. As shown in Figure 11, a schematic diagram illustrating a strcture of the system of allocating UTRAN Radio Network Temporary Identities provided in another embodiment of the present invention is illustrated.
  • As shown in Figure 11, the system of allocating UTRAN Radio Network Temporary Identities may comprise a Home NodeB 1110 and a Home NodeB Gateway 1120, wherein the Home NodeB 1110 and the Home NodeB Gateway 1120 connects with each other, for example, by optical fiber.
  • The Home NodeB 1120 further comprises an obtaining unit 1121, an allocating unit 1122, a sending unit 1123 and a management unit 1124.
  • The obtaining unit 1121 is used for obtaining capability information of the Home NodeB 1110.
  • For example, during a register process of the HNB, a configuration process of the HNB or a reconfiguration process of the HNB, the obtaining unit 1121 receives the capability information reported by the HNB 1110.
  • In another embodiment of the present invention, the obtaining unit 1121 obtains the capability information of the Home NodeB by a HNB managment system or an Operation and Maintenance configuration method.
  • In another embodiment of the present invention, the capability information of the Home NodeB may be HNB type information, HNB usage scene information, the number of UEs needed to be supported by the HNB, or specific identity length needed by the HNB.
  • The allocating unit 1122 is used for allocating information for performing identity allocation to the Home NodeB according to the capability information.
  • For example, the allocating unit 1122 is used for allocating prefix information for performing identity allocation with different lengths to Home NodeBs with different capabilities.
  • For example, the allocating unit 1122 is used for allocating one or multiple prefix information for performing identity allocation with fixed length to the Home NodeB according to the capability information.
  • The sending unit 1123 is used for sending the allocated information for performing identity allocation to the Home NodeB, so that the Home NodeB implements network temporary identity allocation. Wherein, the different information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  • For example, the sending unit 1123 is used for sending the allocated prefix information for performing identity allocation to HNBs(for example, HNB 1110), so that the Home NodeBs implement the UTRAN Radio Network Temporary Identity allocation according to the information for identifying HNB-GW and the prefix information for performing identity allocation, wherein the different information for performing identity allocation corresponds to different Home NodeBs to implement the UTRAN Radio Network Temporary Identity allocation.
  • The management unit 1124 is used for managing the allocation of U-RNTIs by adopting tree structure, according to the capability information reported by the HNB. For the specific management and allocation process which is not described repeatedly here, please refer to the contents described in the embodiment of Figure 6.
  • For example, the allocating unit 1122 is used for allocating the prefix information for performing identity allocation with different lengths to various HNBs according to different capability information of the various HNBs. In another embodiment of the present invention, the Home NodeB Gateway 1120 may further comprise a determining unit (not illustrated in the figure). The determining unit determines lengths of the information for performing identity allocation of various HNBs according to different capability information of the various HNBs, then the allocating unit 1122 allocates the prefix information for performing identity allocation with different lengths to the various HNBs.
  • The Home NodeB 1110 is used for implementing the UTRAN Radio Network Temporary Identity allocation, according to the prefix information for performing identity allocation and the information for identifying HNB-GW For example, the Home NodeB 1110 is used for allocating corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationship that the sum of bits occupied by the length information of the prefix information for performing identity allocation, the length information of the information for identifying HNB-GW, the information for identifying User Equipments under the Home NodeB is a predetermined value.
  • For example, the relationship between the information lengths of the UTRAN Radio Network Temporary Identities is that U-RNTI=RNC-ID+S-RNTI prefix+HNB-RNTI.
  • Here, the RNC-ID is used for identifying HNB-GWs under a same Core Network, the S-RNTI prefix is used for identifying HNB under a same HNB-GW, and the HNB-RNTI is used for identifying UEs under a same HNB.
  • The sending unit 1123 is further used for sending the length information of the prefix information for performing identity allocation to the Home NodeB 1110.
  • The sending unit 1123 is further used for sending the information for identifying HNB-GW to the HNB 1110, for example, RNC-ID for identifying HNB-GWs under a same Core Network.
  • Since the lengths of S-RNTI prefixes used by HNBs with different capabilities under a same HNB-GW 1120 may be different, the lengths of HNB-RNTIs reserved for the HNB1110 to allocate are also different.
  • For example, when the length of the U-RNTI is a certain predetermined value (N bits), and when the length of the allocated RNC-ID is a first value (n1 bits) and the length of the S-RNTI prefix allocated to the HNB 1110 by the allocating unit 1122 according to the capability of the HNB 1110 is a second value (n2 bits), the HNB 1110 allocates the remaining bits to the UEs under itself to identifying various UEs according to the relationship of information lengths, namely, U-RNTI=RNC-ID+S-RNTI prefix+HNB-RNTI.
  • For example, when the length of the U-RNTI is limited to 32bits, if the length of the RNC-ID is 12bits and if the capability information reported by the HNB 1110 is that one HNB only needs to support 16 UEs, then the length of the S-RNTI prefix allocated by the allocating unit 1122 is 16bits, namely that the maximum of 216=65536 HNBs may be supported under one HNB-GW 1120, while the length of the HNB-RNTI allocated by the HNB 1110 is 4bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 24=16 UEs. If the capability information reported by the HNB 1110 is that one HNB needs to support 64 UEs, the length of the S-RNTI prefix allocated by the allocating unit 1122 is 14bits, namely that the maximum of 214=16384 HNBs may be supported under one HNB-GW 1120, while the length of the HNB-RNTI allocated by the Home NodeB 1110 is 6 bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 26=64 UEs.
  • In another embodiment of the present invention, the HNB-GW1120 further comprises a releasing unit (not illustrated in the figures) for releasing the prefix information for performing identity allocation.
  • Therefore, during the process of communication, the U-RNTIs may be allocated dynamically according to the capability information reported by the HNBs. Thus the U-RNTIs may be allocated or used flexibly and reasonably according to different scenes, for example, home usage scene, corporation or marketplace and other different network deploying scenes. HNB-GW network deploying plan needs not to be re-performed, so as to save costs.
  • Furthermore, the HNB-GW needs not to manage the allocation operation of each U-RNTI, and needs not to traverse each stored U-RNTI to check whether a conflict is exist, which reduces the implementation complexity of the Home NodeB Gateway and the time delay brought by the allocation of U-RNTIs.
  • A system of allocating UTRAN Radio Network Temporary Identities is further disclosed in another embodiment of the present invention. As shown in Figure 12, a schematic diagram illustrated a structure of the system of allocating UTRAN Radio Network Temporary Identities provided in another embodiment of the present invention is illustrated.
  • As shown in Figure 12, the system of allocating UTRAN Radio Network Temporary Identities may comprise a Home NodeB 1210, and a Home NodeB Gateway 1220, wherein the Home NodeB 1210 and the Home NodeB Gateway 1120 connects with each other, for example, by optical fiber.
  • The Home NodeB 1210 further comprises a reporting unit 1211, an allocating unit 1212, a transceiving unit 1212 and a releasing unit 1214.
  • The reporting unit 1211 is used for reporting capability information of the Home NodeB to Home NodeB Gateway (HNB-GW) or HNB management system (HMS).
  • For example, during a register process of the HNB, a configuration process of the HNB or a reconfiguration process of the HNB, the reporting unit 1211 reports the capability information of Home NodeB 1210 to the Home NodeB Gateway 1220.
  • In another embodiment of the present invention, the capability information of the Home NodeB may be HNB type information, HNB usage scene information, the number of UEs needed to be supported by the HNB, or specific identity length needed by the HNB.
  • The Home NodeB Gateway 1220 is used for allocating prefix information for performing identity allocation with different lengths to HNBs with different capabilities, and sending the allocated prefix information for performing identity allocation to the HNBs (for example, HNB1210).
  • In another embodiment of the present invention, the Home NodeB Gateway 1220 is further used for sending the length information of the prefix information for performing identity allocation to the HNBs (for example, HNB1210).
  • The transceiving unit 1213 is used for receiving the information for performing identity allocation allocated according to the capability information of the Home NodeB.
  • For example, the transceiving unit 1213 is used for receiving the prefix information for performing identity allocation allocated by the Home NodeB Gateway 1220 according to the capability information of Home NodeB.
  • In another embodiment of the present invention, the transceiving unit 1213 is further used for receiving the length information of the prefix information for performing identity allocation sent by the Home NodeB Gateway 1220.
  • The allocating unit 1212 is used for implementing the allocation of Network Temporary Identities according to the information for performing identity allocation. Here, different information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  • For example, the allocating unit 1212 is used for implementing the allocation of UTRAN Radio Network Temporary Identities according to the information for identifying HNB-GW and the prefix information for performing identity allocation. Here, when the capability information is different, the lengths of corresponding prefix information for performing identity allocation are different. And the different information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  • For example, the information for performing identity allocation is prefix information for performing identity allocation, and the lengths of prefix information for performing identity allocation are different when the capability information of Home NodeBs is different.
  • For example, the information for performing identity allocation is one or multiple prefix information with fixed length for performing identity allocation.
  • For example, the allocating unit 1212 is used for allocating corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationship that the sum of bits occupied by the length information of the prefix information for performing identity allocation, the length information of the information for identifying HNB-GW, and the information for identifying User Equipments under the Home NodeB is a predetermined value.
  • In another embodiment of the present invention, the transceiving unit 1213 is further used for sending the information for identifying User Equipments under Home NodeB to UEs.
  • In another embodiment of the present invention, the transceiving unit 1213 is further used for sending the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation by a broadcast message.
  • The releasing unit 1214 is used for releasing the prefix information for performing identity allocation.
  • For example, the relationship between the information lengths of UTRAN Radio Network Temporary Identities is that U-RNTI=RNC-ID+S-RNTI prefix+HNB-RNTI.
  • Here, the RNC-ID is used for identifying HNB-GWs under a same Core Network, the S-RNTI prefix is used for identifying HNBs under a same HNB-GW, and the HNB-RNTI is used for identifying UEs under a same HNB.
  • The transceiving unit 1213 is further used for receiving the information for identifying HNB-GW sent by the Home NodeB 1220, for example, RNC-ID for identifying HNB-GWs under a same Core Network.
  • Since the lengths of S-RNTI prefixes used by the HNBs with different capabilities under a same HNB-GW 1220 may be different, the lengths of HNB-RNTIs reserved for the HNB1110 to allocate are also different.
  • For example, when the length of the U-RNTI is a certain predetermined value (N bits), and when the length of the allocated RNC-ID is a first value (n1 bits) and the length of the S-RNTI prefix allocated to the HNB 1210 by the Home NodeB Gateway 1220 according to the capability of HNB 1210 is a second value (n2 bits), the allocating unit 1212 allocates the remaining bits to the UEs under itself to identifying various UEs according to the relationship between the information lengths, namely, U-RNTI=RNC-ID+S-RNTI prefix+HNB-RNTI.
  • For example, when the length of the U-RNTI is 32bits, if the length of the RNC-ID is 12bits and if the capability information reported by the reporting unit 1211 is that the HNB 1210 only needs to support 16 UEs, then the length of the S-RNTI prefix allocated by the Home NodeB GW 1220 is 16bits, namely that the maximum of 216=65536 HNBs may be supported under one HNB-GW 1220, while the length of the HNB-RNTI allocated by the allocating unit 1212 is 4bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 24=16 UEs. If the capability information reported by the reporting unit 1211 is that the HNB 1210 needs to support 64 UEs, the length of the S-RNTI prefix allocated by the Home NodeB-Gateway 1220 is 14bits, namely that the maximum of 214=16384 HNBs may be supported under one HNB-GW 1220, while the length of the HNB-RNTI allocated by the allocating unit 1212 is 6 bits, which can meet the requirement that the HNB needs to allocate the U-RNTIs of 26=64 UEs.
  • Therefore, during the process of communication, the U-RNTIs may be allocated dynamically according to the capability information reported by the HNBs. Thus the U-RNTIs may be allocated or used flexibly and reasonably according to different scenes, for example, home usage scene, corporation or marketplace and other different network deploying scenes. HNB-GW network deploying plan needs not to be re-performed, so as to save costs.
  • Furthermore, the HNB-GW needs not to manage the allocation operation of each U-RNTI, and needs not to traverse each stored U-RNTI to check whether a conflict is exist, which reduces the implementation complexity of the Home NodeB Gateway and the time delay brought by the allocation of U-RNTIs.
  • As shown in Figure 13, a schematic diagram illustrating a structure of a Home NodeB providedin another embodiment of the present invention is illustrated. The Home NodeB 1300 comprises a reporting unit 1301, an allocating unit 1302, a transceiving unit 1303, a detecting unit 1304 and a determining unit 1305.
  • The reporting unit 1301 is used for reporting capability information of a Home NodeB to a Home NodeB Gateway (HNB-GW) or a HNB management system (HMS).
  • The transceiving unit 1303 is used for receiving the information for performing identity allocation, which is allocated according to the capability information of the Home NodeB.
  • For example, the transceiving unit 1303 is used for receiving the prefix information for performing identity allocation allocated and sent by the Home NodeB Gateway, wherein the lengths of corresponding prefix information for performing identity allocation are different when the capability information is different, and the different prefix information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  • For example, the transceiving unit 1303 is used for receiving one or multiple prefix information for performing identity allocation with fixed length.
  • In another embodiment of the present invention, the transceiving unit 1303 is further used for receiving the length information of the prefix information for performing identity allocation sent by the Home NodeB Gateway.
  • The allocating unit 1302 is used for implementing the allocation of UTRAN Radio Network Temporary Identities according to the information for identifying HNB-GW and the prefix information for performing identity allocation.
  • For example, the allocating unit 1302 is used for allocating corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationship that the sum of bits occupied by the length information of the prefix information for performing identity allocation, the length information of the information for identifying HNB-GW, and the information for identifying User Equipments under the Home NodeB is a predetermined value.
  • The transceiving unit 1303 is further used for sending the information for identifying UEs under the Home NodeB to the UEs.
  • When cell updating occurs to a user and the Home NodeB 1300 is used as a target Home NodeB, the transceiving unit 1303 is further used for receiving a cell updating message sent by the UE, and sending a cell updating message carrying the U-RNTI allocated by the source HNB to the found source HNB, when the prefix information for performing identity allocation in the U-RNTI allocated by the source HNB and the stored prefix information for adjacent cells to perform identity allocation match with each other.
  • For example, the transceiving unit 1303 transfers the cell updting message carrying the U-RNTI of the source HNB to the source HNB by an interface between the target HNB and source HNB.
  • The Home NodeB 1300 further comprises a storing unit (not illustrated in the figures) for storing the prefix information for adjacent cells to perform identity allocation.
  • The detecting unit 1304 is used for detecting the stored prefix information for adjacent cells to perform identity allocation, and finding the source HNB by the prefix information for performing identity allocation in the received U-RNTI allocated by the source HNB.
  • For example, after the target HNB receives the Cell updating message, the detecting unit 1304 obtains the U-RNTI therein allocated by the source HNB, and finds that the U-RNTI is not allocated by the present cell. When the detecting unit 1304 finds that the RNC-ID carried by the U-RNTI is same as the RNC-ID of the HNB-GW connected therewith, the determining unit 1305 may determine that the target cell is also managed by a same adjacently-connected HNB-GW simultaneously. For example, the detecting unit 1304 may compares the S-RNTI prefix in the U-RNTI allocated by the source HNB with the stored S-RNTI prefix information of adjacent cells, for example, the matching being performed from the highest bit. When one matched S-RNTI prefix information is found, it is determined that the source HNB has been found.
  • The transceiving unit 1303 is further used for sending the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation by a broadcast message.
  • In another embodiment of the present invention, the Home NodeB 1300 further comprises an obtaining unit (not illustrated in the figures) for obtaining the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation by reading broadcast messages of adjacent cells or by configuration.
  • From the above processes, it can be seen that the target HNB sends the source HNB the cell updating message carrying the U-RNTI allocated by the source HNB by an interface between the HNBs when cell updating is performed, which needs not the HNB-GW to forward, thereby decreases the load of processing signaling in the HNB-GW, and reduces the time delay.
  • Those skilled in the art may understand clearly that, for convenience and simplicity of description, corresponding processes of the aforementioned method embodiments may be referred to for specific operation processes of the above described systems, devices and units, which are not described repeatedly here.
  • In the several embodiments provided by the present application, it should be understood that disclosed systems, devices and methods may be implemented by other manners. For example, device embodiments described above are just indicative. For example, the division of units is just a division of logic functions, and there may be other division manners for practical implementations. For example, multiple units or components may be combined or integrated into other system, or some featuress may be neglected or may not be performed. At another point, the displayed or discussed mutual coupling or direct coupling or communication link may be indirect coupling or communication link through some interfaces, devices or units which may be in an electrical form, a mechanical form or other form.
  • The units describled as separated parts may be or may not be physically separated, and the parts displayed as units may be or may not be phycal units, which may be located in one place or distributed to multiple network elements. Part or all units therein may be selected to implement the target of solutions provided in the present invention according to the actual demands.
  • In addition, in various embodiments of the present invention, various functional units may be integrated into one processing unit, or each unit may exist sepatately and physically, or two or more units may be integrated into one unit. The above integrated units may be implemented in the form of hardware or may be implemented in the form of software functional unit.
  • When the intergrated unit is implemented in the form of a software functional unit and is sold or used as an independent product, the integrated unit may be stored in a computer readable storage medium. Based on this understanding, all technical solutions of the present invention or a part that makes comtributions to the prior art or all or part of the technical solutions may be essentially embodied in the form of a software product. The computer software product may be stored in a storage medium, and inclues a number of instructions that enable a piece of computer equipment (may be a personal computer, a server, or a network equipment) to execute all or part of steps of the method describled in various embodiments of the present invention. The preceding storage mediums comprises various mediums that can store codes, such as, a U disk, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Acess Memory), a magnetic disk, an optical disk, or the like.

Claims (31)

  1. A method of allocating Network Temporary Identities, characterized in that the method comprises:
    obtaining (401) capability information of a Home NodeB, wherein the capability information of the Home NodeB is Home NodeB type information, Home NodeB usage scene information, the number of user equipments needed to be supported by the Home NodeB, or specific identity length needed by the Home NodeB;
    allocating (402) prefix information for performing identity allocation to the Home NodeB, according to the capability information;
    sending (403) the allocated prefix information for performing identity allocation to the Home NodeB, so that the Home NodeB implements network temporary identity allocation according to the prefix information for performing identity allocation;
    wherein the network temporary identity comprises the prefix information for performing the temporary identity allocation, information for identifying a Home NodeB gateway and information for identifying a user equipment under the same Home NodeB; and
    wherein different prefix information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  2. The method according to Claim 1, wherein the process of allocating (402) prefix information for performing identity allocation to the Home NodeB comprises:
    allocating the prefix information for performing identity allocation with different lengths to Home NodeBs with different capabilities according to the capability information.
  3. The method according to Claim 2, further comprising:
    sending length information of the allocated prefix information for performing identity allocation to the Home NodeBs.
  4. The method according to Claim 2 or Claim 3, wherein the process of the Home NodeB implements network temporary identity allocation according to the prefix information for performing identity allocation comprises:
    the Home NodeB allocates a corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationship that the sum of bits occupied by the length information of the prefix information for performing identity allocation, and the length information of the information for identifying Home NodeB Gateway and the information for identifying User Equipments under the Home NodeB is a predetermined value.
  5. The method according to Claim 1, wherein the process of allocating (402) prefix information for performing identity allocation to the Home NodeB, according to the capability information comprises:
    allocating one or multiple pieces of the prefix information for performing identity allocation with a fixed length to the Home NodeB, according to the capability information.
  6. The method according to Claim 5, wherein the prefix information for performing identity allocation with a fixed length is Cell Identity information.
  7. The method according to Claim 1, 2, 3, 5 or 6, wherein the process of obtaining (401) capability information of a Home NodeB comprises:
    receiving the capability information reported by the Home NodeB, during a register process of the Home NodeB or a configuration process of the Home NodeB or a reconfiguration process of the Home NodeB; or
    obtaining the capability information of the Home NodeB according to configuration of a Home NodeB Management System (HMS) or an Operation and Maintenance system (OAM).
  8. The method according to Claim 1, 2, 3, 5 or 6, wherein when cell updating occurs, the method further comprises:
    receiving, by target Home NodeB, cell updating message sent by the UE, wherein the cell updating message carries U-RNTI allocated by source Home NodeB;
    detecting, by the target Home NodeB, the stored information for adjacent cells to perform identity allocation, and finding the source Home NodeB by the information for performing identity allocation in the received U-RNTI allocated by the source Home NodeB;
    sending, by the target Home NodeB, the cell updating message to the found source Home NodeB, wherein the cell updating message carries the U-RNTI allocated by the source Home NodeB.
  9. The method according to Claim 8, further comprising:
    comparing, by the target Home NodeB, the information for performing identity allocation in the U-RNTI allocated by the source Home NodeB with the information, stored in the target Home NodeB, for the adjacent cells to perform identity allocation;
    determining, by the target Home NodeB, the source Home NodeB has been found, when it is matched.
  10. A method of allocating Network Temporary Identities, characterized in that the method comprises:
    receiving, by a Home NodeB, prefix information for performing identity allocation, which is allocated according to capability information of the Home NodeB, wherein the capability information of the Home NodeB is Home NodeB type information, Home NodeB usage scene information, the number of user equipment needed to be supported by the Home NodeB, or specific identity length needed by the Home NodeB;
    implementing, by the Home NodeB, network temporary identity allocation according to the prefix information for performing identity allocation;
    wherein the network temporary identity comprises the prefix information for performing the temporary identity allocation, information for identifying a Home NodeB gateway and information for identifying a user equipment under the same Home NodeB; and
    different prefix information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  11. The method according to Claim 10, wherein length information of the prefix information is different when the capability information of Home NodeBs is different.
  12. The method according to Claim 11, further comprising:
    receiving, by the Home NodeB, the length information of the prefix information for performing identity allocation.
  13. The method according to Claim 11 or 12, wherein the process of implementing, by the Home NodeB, network temporary identity allocation according to the prefix information for performing identity allocation comprises:
    allocating, by the Home NodeB, a corresponding amount of bits for the information for identifying User Equipments under the Home NodeB, according to the relationship that the sum of bits occupied by the length information of the prefix information for performing identity allocation, and the length information of the information for identifying Home NodeB Gateway and the information for identifying User Equipments under the Home NodeB is a predetermined value.
  14. The method according to Claim 10, wherein the prefix information for performing identity allocation is one or multiple pieces of the prefix information for performing identity allocation with a fixed length.
  15. The method according to Claim 14, wherein the prefix information for performing identity allocation with a fixed length is Cell Identity information.
  16. The method according to Claim 15, further comprising:
    reporting, by the Home NodeB, number information of the Cell Identity information to the Home NodeB Gateway, during a register process of the Home NodeB or a configuration process of the Home NodeB or a reconfiguration process of the Home NodeB.
  17. The method according to Claim 10, 11, 12, 14, 15 or 16, further comprising:
    reporting, by the Home NodeB, the capability information to the Home NodeB Gateway or a Home NodeB management system, during a register process of the Home NodeB or a configuration process of the Home NodeB or a reconfiguration process of the Home NodeB.
  18. The method according to Claim 15, further comprising:
    broadcasting, by the Home NodeB, number information of the Cell Identity information by system message.
  19. The method according to Claim 18, further comprising:
    obtaining, by the Home NodeB, the number information of the Cell Identity information, by reading broadcast message of an adjacent Home NodeB or by configuration.
  20. The method according to Claim 11, further comprising:
    broadcasting, by the Home NodeB, the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation, by system message.
  21. The method according to Claim 20, further comprising:
    obtaining, by the Home NodeB, the prefix information for performing identity allocation and/or the length information of the prefix information for performing identity allocation, by reading broadcast message of an adjacent Home NodeB or by configuration.
  22. The method according to Claim 10, further comprising:
    initiating, by the Home NodeB or by the Home NodeB Gateway, a releasing of the information for performing identity allocation allocated to the Home NodeB, through the process of a Home NodeB removing register or releasing configuration.
  23. A Home NodeB Gateway (1120), characterized in that the Home NodeB Gateway (1120) comprises:
    an obtaining unit (1121) for obtaining capability information of a Home NodeB (1110), wherein the capability information of the Home NodeB (1110) is Home NodeB type information, Home NodeB usage scene information, the number of user equipment needed to be supported by the Home NodeB (1110), or specific identity length needed by the Home NodeB (1110);
    an allocating unit (1122) for allocating prefix information for performing identity allocation to the Home NodeB (1110) according to the capability information;
    a sending unit (1123) for sending the allocated prefix information for performing identity allocation to the Home NodeB (1110), so that the Home NodeB (1110) completes network temporary identity allocation according to the prefix information for performing identity allocation;
    wherein the network temporary identity comprises the prefix information for performing the temporary identity allocation, information for identifying the Home NodeB gateway (1120) and information for identifying a user equipment under the same Home NodeB (1110); and
    different prefix information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  24. The Home NodeB Gateway according to Claim 23, further comprising:
    a management unit (1124) for managing allocation of U-RNTIs by adopting a tree structure, according to the capability information reported by the Home NodeB (1110).
  25. The Home NodeB Gateway according to Claim 23, wherein the allocating unit (1122) is used for allocating prefix information for performing identity allocation with different lengths to Home NodeBs with different capabilities according to the capability information.
  26. The Home NodeB Gateway according to Claim 23, wherein the allocating unit (1122) is used for allocating one or multiple pieces of the prefix information for performing identity allocation with fixed length to the Home NodeB (1110) according to the capability information.
  27. A Home NodeB (1210), characterized in that the Home NodeB (1210) comprises:
    a reporting unit (1211) for reporting capability information of the Home NodeB (1210) to a Home NodeB Gateway (1220) or a Home NodeB management system, wherein the capability information of the Home NodeB (1210) is Home NodeB type information, Home NodeB usage scene information, the number of user equipment needed to be supported by the Home NodeB (1210), or specific identity length needed by the Home NodeB (1210);
    a transceiving unit (1213) for receiving prefix information for performing identity allocation, which is allocated according to the capability information of the Home NodeB (1210);
    an allocating unit (1212) for implementing network temporary identity allocation according to the prefix information for performing identity allocation;
    wherein the network temporary identity comprises the prefix information for performing the temporary identity allocation, information for identifying the Home NodeB gateway (1220) and information for identifying a user equipment under the same Home NodeB (1210); and
    different prefix information for performing identity allocation corresponds to different Home NodeBs to implement the network temporary identity allocation.
  28. The Home NodeB according to Claim 27, wherein length information of the prefix information for performing identity allocation is different when the capability information of Home NodeBs is different.
  29. The Home NodeB according to Claim 28, wherein the allocating unit (1212) is used for allocating a corresponding amount of bits for the information for identifying User Equipments under the Home NodeB (1210), according to the relationship that the sum of bits occupied by the length information of the prefix information for performing identity allocation, the length information of the information for identifying Home NodeB Gateway (1220), and the information for identifying User Equipments under the Home NodeB (1210) is a predetermined value.
  30. The Home NodeB according to Claim 27, wherein the prefix information for performing identity allocation is one or multiple pieces of the prefix information for performing identity allocation with a fixed length.
  31. The Home NodeB according to Claim 27, further comprising a storing unit and a detecting unit,
    wherein the storing unit is used for storing information for adjacent cells to perform identity allocation;
    the detecting unit (1304) is used for detecting the stored information for adjacent cells to perform identity allocation, and finding a source NodeB by the information for performing identity allocation in the received U-RNTI allocated by a source Home NodeB;
    the transceiving unit is further used for receiving cell updating message sent by UEs, and sending the cell updating message carrying the U-RNTI allocated by the source Home NodeB to the found source NodeB when the information for performing identity allocation in the U-RNTI allocated by the source Home NodeB and the stored information for adjacent cells to perform identity allocation match with each other, when cell updating occurs.
EP11768405.0A 2010-04-13 2011-04-07 Method and system for allocating network temporary identities Active EP2560423B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201010155157.3A CN102223621B (en) 2010-04-13 2010-04-13 A kind of method and system of distribution network temporary mark
PCT/CN2011/072485 WO2011127793A1 (en) 2010-04-13 2011-04-07 Method and system for allocating network temporary identities

Publications (3)

Publication Number Publication Date
EP2560423A1 EP2560423A1 (en) 2013-02-20
EP2560423A4 EP2560423A4 (en) 2013-05-01
EP2560423B1 true EP2560423B1 (en) 2017-07-12

Family

ID=44780020

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11768405.0A Active EP2560423B1 (en) 2010-04-13 2011-04-07 Method and system for allocating network temporary identities

Country Status (4)

Country Link
US (1) US8655360B2 (en)
EP (1) EP2560423B1 (en)
CN (1) CN102223621B (en)
WO (1) WO2011127793A1 (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220730B (en) 2012-01-20 2017-02-08 华为技术有限公司 Method and device for distributing wireless network temporary identifications
CN103369676B (en) * 2012-04-10 2017-04-12 华为技术有限公司 Message processing method between micro cells and macro cell, base-station gateway and system
CN103686845A (en) * 2012-09-07 2014-03-26 京信通信系统(中国)有限公司 Implementation method, device and system of network flattening framework
US10390333B2 (en) 2013-05-02 2019-08-20 Huawei Technologies Co., Ltd. System and method for transmission source identification
US9497751B2 (en) 2013-07-02 2016-11-15 Qualcomm Incorporated Methods to enhance neighbor PDCCH decoding by exploiting correlation of RNTIS
JP2019201352A (en) * 2018-05-17 2019-11-21 Nippon Telegr & Teleph Corp <Ntt> Radio communication system, relay communication device, and communication control method

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1401226A1 (en) * 2002-09-20 2004-03-24 Lucent Technologies Inc. A method, and apparatus, for addressing a message to mobile user terminals
US7546145B2 (en) * 2002-10-15 2009-06-09 Nokia Corporation Method, network node and system for managing interfaces in a distributed radio access network
CN100396152C (en) 2004-11-18 2008-06-18 华为技术有限公司 Discrimination for service wireless network sub-system transfer by user apparatus
CN100442931C (en) 2005-10-14 2008-12-10 华为技术有限公司 Method and apparatus for implementing mobile management of broadcasting service
CN100415004C (en) 2005-11-24 2008-08-27 华为技术有限公司 Realization method and apparatus of designating SCCPCH for user terminal
CN100387067C (en) 2005-12-09 2008-05-07 华为技术有限公司 Method for transmitting multi-business on downward sharing channel
CN101090364A (en) 2006-11-02 2007-12-19 华为技术有限公司 Sending/receiving method and device for high speed downlink group access correlation channel
CN101242553B (en) 2007-02-05 2011-01-05 华为技术有限公司 User data transmission method and device
US8204506B2 (en) 2007-03-08 2012-06-19 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatuses for allocating service area identifiers in a wireless system
CN100563375C (en) 2007-04-27 2009-11-25 上海华为技术有限公司 Urnti distribution method and device thereof
CN101483919A (en) 2008-01-08 2009-07-15 华为技术有限公司 Wireless resource allocation method used for stochastic access and base band equipment
CN101547479B (en) 2008-03-27 2010-12-22 华为技术有限公司 Method, device and system for scheduling data of base station
FI20085253A0 (en) 2008-03-28 2008-03-28 Nokia Siemens Networks Oy Cell IDs in a cellular communication system
CN101553014A (en) 2008-03-31 2009-10-07 华为技术有限公司 Method, device and system for switching serving cells
CN105472601B (en) * 2008-04-28 2019-05-28 华为技术有限公司 Distribution, acquisition methods and the device of identification information
CN101610579A (en) 2008-06-19 2009-12-23 上海华为技术有限公司 A kind of management method of Radio Network Temporary Identifier and device
US20100040023A1 (en) * 2008-08-15 2010-02-18 Gallagher Michael D Method and Apparatus for Inter Home Node B Handover in a Home Node B Group
CN101754410B (en) 2008-12-19 2012-09-05 华为技术有限公司 Network access method and device
CN101771942B (en) 2008-12-26 2014-04-30 华为技术有限公司 Method, equipment and system for grouping multimedia broadcasting/multicasting services (MBMS)
CN101998611B (en) 2009-08-11 2013-03-27 华为技术有限公司 Power control information communication method and device for uplink carrier wave
CN101998580B (en) 2009-08-13 2013-09-11 华为技术有限公司 Information processing method under multi-carrier mode and equipment

Also Published As

Publication number Publication date
CN102223621A (en) 2011-10-19
WO2011127793A1 (en) 2011-10-20
CN102223621B (en) 2016-03-30
EP2560423A4 (en) 2013-05-01
US8655360B2 (en) 2014-02-18
EP2560423A1 (en) 2013-02-20
US20130040642A1 (en) 2013-02-14

Similar Documents

Publication Publication Date Title
US9560514B2 (en) Method for establishing connection by HNB
US9794970B2 (en) Decentralizing core network functionalities
US20180317138A1 (en) Method and Apparatus for Accessing Legacy Networks Through Temporary ID of Evolved Network
US9210593B2 (en) System and apparatus for indicating cell identifiers
US9338708B2 (en) Method and apparatus of communication
US10455489B2 (en) Method for supporting PDN GW selection
US9510210B2 (en) Method and apparatus of physical cell identifier allocation
US8295837B2 (en) Scrambling code allocation and hand-in for wireless network radio access points
JP2014132775A (en) Cell type information sharing between neighbour base stations
CN102160416B (en) System and method for providing connection handoffs in wireless networks
CN102843739B (en) Method, device and system for handover among femtocells
EP2289264B1 (en) Handover of non-voice bearers in packet-switched and cicuit-switched networks
EP2018789B1 (en) Access control in a mobile communication system
EP1932379B1 (en) Automatic configuration of pico radio base station
US8675621B2 (en) Using identification sequences in wireless communication systems
US8509785B2 (en) Method and arrangements in a cellular network with femtocells
US8204506B2 (en) Method and apparatuses for allocating service area identifiers in a wireless system
EP1371247B1 (en) A network and method for sharing radio access nodes between core networks
US9775073B2 (en) Gateway configured to provide a handover, converting and routing function
US20150072699A1 (en) Cell Configuration for Self-Organized Networks with Flexible Spectrum Usage
KR101275652B1 (en) Access network, gateway and management server for a cellular wireless communication system
US9826457B1 (en) System and method for providing extending femtocell coverage
US7697935B2 (en) Transfer of a user equipment in a communication system
US9055518B2 (en) Resource sharing in communications systems
JP5021753B2 (en) Method and apparatus for estimating the location of an access point in a wireless communication network

Legal Events

Date Code Title Description
17P Request for examination filed

Effective date: 20120918

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 24/02 20090101ALI20130328BHEP

Ipc: H04W 8/02 20090101AFI20130328BHEP

A4 Supplementary search report drawn up and despatched

Effective date: 20130405

DAX Request for extension of the european patent (to any country) (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602011039525

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0008020000

Ipc: H04W0024020000

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 24/02 20090101AFI20160728BHEP

Ipc: H04W 84/04 20090101ALN20160728BHEP

RAP1 Rights of an application transferred

Owner name: HUAWEI TECHNOLOGIES CO., LTD.

INTG Intention to grant announced

Effective date: 20170119

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 909374

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170715

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011039525

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20170712

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 909374

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170712

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171012

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171012

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171112

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20171013

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011039525

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

26N No opposition filed

Effective date: 20180413

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170712

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20180430

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180407

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180430

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180430

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180407

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180430

PGFP Annual fee paid to national office [announced from national office to epo]

Ref country code: DE

Payment date: 20190326

Year of fee payment: 9

PGFP Annual fee paid to national office [announced from national office to epo]

Ref country code: GB

Payment date: 20190403

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180407