WO2015096413A1 - 一种ue移动性的方法及装置 - Google Patents

一种ue移动性的方法及装置 Download PDF

Info

Publication number
WO2015096413A1
WO2015096413A1 PCT/CN2014/080145 CN2014080145W WO2015096413A1 WO 2015096413 A1 WO2015096413 A1 WO 2015096413A1 CN 2014080145 W CN2014080145 W CN 2014080145W WO 2015096413 A1 WO2015096413 A1 WO 2015096413A1
Authority
WO
WIPO (PCT)
Prior art keywords
rnc
message
identifier
cluster
rncs
Prior art date
Application number
PCT/CN2014/080145
Other languages
English (en)
French (fr)
Inventor
史莉荣
Original Assignee
中兴通讯股份有限公司
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
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP14875311.4A priority Critical patent/EP3089547B1/en
Priority to ES14875311T priority patent/ES2812573T3/es
Priority to US15/108,419 priority patent/US9967790B2/en
Publication of WO2015096413A1 publication Critical patent/WO2015096413A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information

Definitions

  • the present invention relates to a mobile communication system, and in particular, to a UE mobility method and apparatus.
  • UMTS Universal Mobile Telecommunication System
  • the Universal Mobile Telecommunication System (UMTS) belongs to the third generation communication system, and the network part of the UMTS is called the UMTS Terrestrial Radio Access Network (UTRAN).
  • the UTRAN structure is divided into wireless.
  • RAN Radio Access Network
  • CN Core Network
  • Exchange and routing of external networks The above two units together with User Equipment (UE) constitute the entire system.
  • UE User Equipment
  • the network unit of the radio access network includes a radio network controller (Radio Network Controller, RNC for short) and a transceiver base station (Node B, referred to as NodeB for short).
  • RNC Radio Network Controller
  • NodeB transceiver base station
  • U-RNTI UTRAN Radio Network Temple Identity
  • the U-RNTI is 32 bits in length and consists of two parts:
  • the radio network controller identifies the SRNC identity and the wireless.
  • the network controller temporarily identifies the S-RNTI (SRNC RNTI).
  • the SRNC identity indicates the service RNC identifier, which has the same meaning as the RNC ID.
  • the S-RNTI represents the wireless network temporary identity of the SRNC.
  • the SRNC identity is defined as 12 bits, and the S-RNTI is defined as 20 bits. If the SRNC ID is more than 12 bits, more than 12 bits are in the S-RNTI.
  • the UE in the public state moves between the RNCs, it sends a cell update message or a URA update message to the drift radio network controller DRNC (Drift RNC).
  • the message carries the U-RNTI, and the DRNC parses the RNC-ID according to the U_RNTI carried in the message. Determine which RNC the message should be sent to.
  • the DRNC does not know whether the SRNC uses the normal RNC ID or the extended RNC ID.
  • the DRNC does not know whether the SRNC uses the normal RNC ID or the extended RNC ID.
  • the target RNC ID is actually a normal RNC ID, the message will be correctly sent to the target RNC according to the normal RNC ID; (2) If the target RNC ID is actually the extended RNC ID, parsed according to the normal RNC ID, the message may be sent to the target RNC correctly, or may be sent incorrectly; (3) If the target RNC ID is actually the extended RNC ID, according to the extended RNC ID resolution, the message will be correctly sent to the target RNC; (4) If the target RNC ID is actually a normal RNC ID, the message will be sent incorrectly according to the extended RNC ID resolution.
  • the RNC that receives the message will discard the message, which will easily cause the call drop when the UE moves across the RNC.
  • the UE receives the measurement control message sent by the network side in the dedicated connection state, and assists in measuring the information of the new cell and reports the information to the network side, and the reported message includes the cell.
  • ANR Automatic Neighbor Relation
  • the UE receives the measurement control message sent by the network side in the dedicated connection state, and assists in measuring the information of the new cell and reports the information to the network side, and the reported message includes the cell.
  • ANR Automatic Neighbor Relation
  • the RNC finds a cell that is not in the RNC according to the identifier of the cell in the radio network, it needs to send the cell to the other RNC. Message acquisition information. However, the RNC does not know whether other RNCs use 12-bit or 16-bit RNCs. According to the related technologies, there are the following cases: (1) If the target RNC ID is actually a normal RNC ID, the message will be correct according to the normal RNC ID.
  • the target RNC ID is actually the extended RNC ID
  • the message may be correctly sent to the target RNC according to the normal RNC ID, and may also be sent incorrectly; (3) If the target RNC ID is actually an extended RNC ID, according to the extended RNC ID resolution, the message will be correctly sent to the target RNC; (4) If the target RNC ID is actually a normal RNC ID, according to the extended RNC ID resolution, the message will be sent incorrectly. If the message is sent incorrectly, the neighbor area of the RNC missed will not be recognized, so that when the UE moves across the RNC, it is easy to cause dropped calls.
  • the present invention provides a method and apparatus for UE mobility, so that a UE can be disconnected from a call between RNCs to ensure continuity of service reception.
  • the present invention provides a UE mobility method, the method includes: the radio network controller RNC receives a first message; the RNC determines, according to the determination rule, the target wireless corresponding to the first message.
  • the network controller group RNC Cluster is the RNC Cluster where the RNC is located, and the RNC Cluster is composed of one or more RNCs; if the determination result is yes, the RNC sends a second message to perform internal processing of the RNC Cluster; or, If the result is no, the RNC sends the second message to the target RNC Clusters.
  • the RNC Cluster has an RNC Cluster Identity ID, and the value of the RNC Cluster ID is the same as the RNC ID of the RNC in the RNC Cluster. The same bit.
  • the determining rule is: the first message carries a first identifier, and the RNC determines the target RNC Cluster ID according to the first identifier.
  • the second message further includes a second identifier
  • the RNC performs the RNC Cluster internal processing on the second message by using the following processing manner according to the second identifier:
  • the RNCs in the RNC Cluster share a message queue
  • the RNC puts the second message into the message queue, and sends an internal message request to other RNCs in the RNC Cluster, triggering each RNC to check the second a message
  • the respective RNCs determine, according to the second identifier, whether the respective RNCs determine whether the current RNC is processed according to the RNC ID of the second identifier according to the second identifier, or the RNC shares the same in the RNC Cluster.
  • the RNC determines, according to the second identifier, whether it belongs to its own processing, and if so, performs processing, such as otherwise placing the second message into the message queue, and sending the message to other RNCs in the RNC Cluster.
  • the internal message request triggers each RNC to check the external message, and the RNC or the RNC determines whether the current RNC is processed according to the second identifier and its own RNC ID.
  • the first message is a URA update message
  • the first identifier is a UTRAN wireless network temporary identifier.
  • the U-RNTI the second message is an uplink signaling transmission indication message, the second identifier is a radio network controller temporary identifier S-RNTI; or the first message is a cell update message, and the first identifier is a UTRAN radio network temporary identifier U-RNTI
  • the second message is an uplink signaling transmission indication message, the second identifier is a radio network controller temporary identifier S-RNTI, or the first message is a UE information response message UE INFORMATION RESPONSE, and the first identifier is a cell identifier in the PLMN.
  • Identity the second message is an information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST, and the second identifier is an identifier C-ID of the cell in the RNC.
  • an internal custom message or a standard Iur interface message is used between each RNC in the RNC Cluster.
  • the present invention further provides a radio network controller RNC, the RNC comprising: a receiving module, configured to receive a first message; a processing module, configured to determine, according to the determining rule, a target wireless network corresponding to the first message Whether the controller group RNC Cluster is the RNC Cluster where the RNC is located, and the RNC Cluster is composed of one or more RNCs; if the determination result is yes, the processing module sends a second message to perform internal processing of the RNC Cluster, or the judgment result is No, the RNC sends a second message to the target RNC Clusters.
  • the RNC Cluster has an RNC Cluster ID, and the value of the RNC Cluster ID is the same as the first n bits of the RNC ID of the RNC in the RNC Cluster.
  • the determining rule is: the first message carries a first identifier, and the processing module RNC determines the target RNC Clusters according to the first identifier.
  • the second message includes a second identifier.
  • the processing module performs internal processing of the RNC Cluster on the internal processing of the second message RNC Cluster according to the second identifier: the RNC in the RNC Cluster shares a message queue, and the processing module RNC puts the second message Initiating the message queue, and sending an internal message request to the other RNCs in the RNC cluster, triggering each RNC to check the second message, and each RNC determines whether the second identifier is combined with its own RNC ID.
  • the current RNC process or, the RNC in the RNC Cluster shares a message queue, and the processing module RNC determines whether it belongs to its own processing according to the second identifier, and if yes, performs processing, such as otherwise placing the second message
  • the message queue and sending an internal message request to other RNCs in the RNC Cluster, triggering each RNC to check the external message,
  • Each of said RNC or RNC RNC ID of its own according to the second identifier it is determined whether the current process RNC.
  • the first message is a URA update message
  • the first identifier is a UTRAN radio network temporary identifier U-RNTI
  • the second message is an uplink signaling transmission indication message
  • the second identifier is a radio network controller temporary identifier S-RNTI
  • the first message is a cell update message
  • the first identifier is a UTRAN radio network temporary identifier U-RNTI
  • the second message is an uplink signaling transmission indication message
  • the second identifier is a radio network controller temporary identifier S-RNTI
  • the first message For the UE information response message UE INFORMATION RESPONSE
  • the first identifier is the identifier Cell Identity of the cell in the PLMN
  • the second message is the information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST
  • the second identifier is the identifier C-ID of the cell in the RNC.
  • an internal custom message or a standard Iur interface message is used between each RNC in the RNC Cluster.
  • the present application provides a UE mobility method, so that the RNC can correctly perform message processing when the UE moves between the RNCs, ensuring continuity of service reception, improving user experience, and powerfully Improved performance metrics for the network.
  • the drawings are intended to provide a further understanding of the technical solutions of the present invention, and are intended to be a part of the specification, and are used to explain the technical solutions of the present invention, and do not constitute a limitation of the technical solutions of the present invention.
  • 1 is an improved wireless network architecture of the present invention
  • FIG. 2 is a flow chart of message processing across an RNC Cluster according to an embodiment of the present invention
  • FIG. 3 is a flowchart of URA Update processing across an RNC Cluster according to an embodiment of the present invention
  • 4 is a flowchart of a Cell Update process of an RNC Cluster according to an embodiment of the present invention
  • FIG. 5 is a flowchart of ANR processing of an RNC Cluster according to an embodiment of the present invention
  • FIG. 6 is a flowchart of message processing in an RNC Cluster according to an embodiment of the present invention
  • FIG. 7 is a structural diagram of an RNC according to an embodiment of the present method.
  • FIG. 1 is a structural diagram of an RNC group (RNC Cluster) according to Embodiment 1 of the present invention.
  • the RNC group (hereinafter referred to as the RNC Cluster) is composed of multiple RNCs, and the first n bits of the RNC ID of the RNC in the same RNC Cluster are the same, and each RNC communicates with the CN through the Iu port.
  • RNC and NodeB are connected through the Iub interface.
  • the RNC Cluster is connected through the Iur port.
  • the inter-RNC communication in the RNC Cluster can use the standard Iur interface message, or the standard lur interface message can be used, and the internal custom message is adopted.
  • the internal custom message is used to simplify the message structure, reduce the message processing length, and improve the processing efficiency.
  • the Iur port between the Iu port, the Iub port, and the RNC Cluster is still the same as the current standard interface.
  • the above n can be equal to 12 or other values.
  • the RNC Cluster defines an RNC Cluster ID, which is the first n bits of the RNC ID in the RNC Cluster.
  • One or more RNCs are included in the RNC Cluster.
  • the first identifier of the first identifier is used as the RNC Cluster ID, and the remaining bits are used to form the second identifier.
  • the first message carries the first identifier, and the second message carries the second identifier.
  • the RNC pre-configures the adjacent RNC Cluster ID.
  • FIG. 2 is a flow chart of message processing across the RNC Cluster according to the embodiment of the present invention.
  • the message processing procedure includes the following steps: Step 201: The RNC1 receives the first message sent by the UE, where the message includes the first
  • the RNC1 is located in a radio network controller group RNC Cluster, and the RNC Cluster has an RNC Cluster ID, and the value of the RNC Cluster ID is the same as the first n bits (bit) of the RNC ID of the RNC in the RNC Cluster. .
  • Step 202 The RNCl determines, according to the determining rule, whether the external message (that is, the first message) belongs to the radio network controller group RNC Cluster where the RNC1 is located; the determining rule is: the external message carries a first identifier. RNC1 resolves the first n bit according to the first identifier as the RNC Cluster ID of the target RNC Cluster. Step 203: If the judgment result of RNC1 is yes, that is, the RNC Cluster ID of the target RNC Cluster and
  • the RNC Cluster ID of the RNCl is the same, and the RNC Cluster where the RNCl is located is the target RNC Cluster, and the RNCl sends the second message to be processed by the RNC Cluster where the RNCl is located; or, if the RNC1 determines No, the RNC of the target RNC Cluster
  • the cluster ID is different from the RNC Cluster ID where the RNCl is located.
  • the RNC cluster where the RNC 1 is located is not the target RNC cluster.
  • the RNC 1 sends a second message to the target RNC Cluster according to the RNC Cluster ID of the target RNC Cluster obtained in step 202.
  • the second message is sent to the target RNC Cluster, which means that the second message is sent to any RNC in the target RNC Cluster (in this embodiment, it may be RNC2), or is sent to the main control module or the master RNC in the target RNC Cluster.
  • the main control module can be a single processing unit, or an RNC.
  • the method for determining the master RNC can be static configuration of a master RNC, or election of a master RNC according to load or other factors.
  • the RNC1 sends a second message, where the second message includes a second identifier, and the RNC1 performs the RNC Cluster internal processing on the second message to include any one of the following manners:
  • the RNCs in the RNC Cluster share a message queue, and the RNC1 puts the second message into the message queue, and sends an internal message request to other RNCs in the RNC Cluster, triggering each RNC to check the external message.
  • Each RNC determines whether it belongs to its own processing according to the second identifier; or the RNC in the RNC Cluster shares a message queue, and the RNC 2 determines whether it belongs to its own processing according to the second identifier, and if yes, performs processing, such as And placing the second message into the message queue, and sending an internal message request to the other RNCs in the RNC cluster, triggering each RNC to check the second message; and each RNC determines, according to the second identifier, whether If it is processed by itself or the RNC 2 determines whether it belongs to itself according to the second identifier, it means that the RNC according to the second standard in the second message , With its own RNC ID, a combination of the first identifier of the UE, whether the recording for messages according to the first UE identifier of the UE; in the case of NO refers to ignore the second message is not processed.
  • the first message, the first identifier, the second message, and the second identifier are any one of the following: the first message is a URA update message, and the first identifier is a UTRAN radio network temporary identifier U-RNTI, and the second The message is an uplink signaling transmission indication message, the second identifier is a radio network controller temporary identifier S-RNTI, or the first message is a cell update message, the first identifier is a UTRAN radio network temporary identifier U-RNTI, and the second message is an uplink.
  • the signaling identifier indicates that the second identifier is the radio network controller temporary identifier S-RNTI; or the first message is the UE information response message UE INFORMATION RESPONSE, the first identifier is the identifier of the cell in the PLMN, and the second message is The information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST, the second identifier is the identifier C-ID of the cell in the RNC.
  • Step 204 Only if the information of the recorded UE is found, the RNC processes the message, performs relocation or no relocation or other processes.
  • FIG. 3 is a flowchart of a URA Update process of an RNC cluster according to an embodiment of the present invention. As shown in FIG.
  • Step S301 The RNC1 receives a first message URA update message URAUpdate sent by the UE.
  • the first identifier U-RNTI is included therein;
  • Step S302 The RNC1 resolves the first 12 bits according to the first identifier U-RNTI as the RNC Cluster ID of the target RNC Cluster, and the RNC1 determines, according to the determination rule, whether the URA update message URA Update belongs to the radio network controller group RNC where the RNC is located.
  • Step 303 If the result of the determination is NO, the URA update message URAUpdate does not belong to the RNC Cluster processing where the RNC1 is located, and then sends a second message uplink signaling transmission indication message to the target RNC Cluster according to the obtained target RNC Cluster ID. Uplink Signalling Transfer Indication, the message includes a second identifier S-RNTI.
  • the RNC in the RNC Cluster shares a message queue, and the RNC 2 puts the second message uplink signaling transmission indication message Uplink Signalling Transfer Indication into the message queue, and sends the message to the other RNCs in the RNC Cluster.
  • the RNC 2 determines, according to the second identifier, whether it belongs to its own processing, and if yes, performs processing, such as otherwise placing the I uplink signaling transmission indication message Uplink Signalling Transfer Indication into the message queue, and to the RNC Cluster
  • the other RNC sends an internal message request, triggering each RNC to check the second message;
  • the RNC determines whether it belongs to its own processing or whether the RNC2 determines whether it belongs to its own processing.
  • the RNC In the case of its own processing, the RNC combines the U-RNTI of the UE according to the S-RNTI in the message and its own RNC ID, according to the U of the UE. - RNTI finds whether there is recorded UE information; if it is not its own processing, the second message is ignored and no processing is performed. In step S305, only if the recorded UE information is found, the RNC processes the message, performs relocation or no relocation or other processes.
  • 4 is a flowchart of a Cell Update process of an RNC cluster according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps: Step S401: The RNC1 receives a first message, a Cell Update message sent by the UE, in the message.
  • the first identifier U-RNTI is included.
  • Step S402 The RNCl resolves the first 12 bits according to the U-RNTI as the RNC Cluster ID of the target RNC Cluster, and the RNCl determines, according to the determination rule, whether the Cell URA Update message belongs to the radio network controller group RNC Cluster where the RNC is located;
  • S403 If the judgment result is no, the Cell Update message does not belong to the RNC Cluster processing where the RNC1 is located, and according to the obtained target RNC Cluster ID, the RNCl sends an uplink signaling transmission indication message to the target RNC Cluster, where the message includes the second identifier.
  • S-RNTI The RNCl resolves the first 12 bits according to the U-RNTI as the RNC Cluster ID of the target RNC Cluster, and the RNCl determines, according to the determination rule, whether the Cell URA Update message belongs to the radio network controller group RNC Cluster where the RNC is located;
  • S403 If the judgment result is no, the Cell Update message does not belong
  • Step 404 The RNC2 receives an uplink signaling transmission indication message according to the RNCl, and the message includes an S-RNTI.
  • the RNC2 performs the RNC Cluster internal processing on the Cell Update message, and includes any one of the following modes: the RNC in the RNC Cluster Sharing a message queue, the RNC2 puts the uplink signaling transmission indication message Uplink Signalling Transfer Indication message into the message queue, and sends an internal message request to each RNC in the RNC Cluster, triggering each RNC to check the message queue a second message, the respective RNCs determine, according to the second identifier, whether they belong to the self-processing; or the RNCs in the RNC Cluster share a message queue, and the RNC2 determines, according to the second identifier, whether it belongs to its own processing, if yes, Processing, if the uplink signaling transmission indication message Uplink Signalling Transfer Indication is put into the message queue, and sending an internal message request to other RNCs in the RNC Cluster, triggering each RNC to check
  • the RNC combines the U-RNTI of the UE according to the S-RNTI in the uplink signaling transmission indication message and the RNC ID of the UE, and searches according to the U-RNTI of the UE. Whether there is recorded UE information; if it is not processed by itself, if no processing is performed, the uplink signaling transmission indication message is ignored. Step S405, only if the recorded UE information is found, the RNC processes the message and sends a response message to the RNC1.
  • FIG. 5 is a flowchart of ANR processing of an RNC cluster according to an embodiment of the present invention. As shown in FIG.
  • Step S501 The RNC1 receives a UE information response message UE INFORMATION RESPONSE sent by the UE, in the message.
  • the identifier IC containing the first identifier is the cell in the PLMN.
  • Step 502 The RNCl, according to the Cell Identity, solves the first 12 bits, as the RNC Cluster ID of the target RNC Cluster, and the RNCl determines, according to the determination rule, whether the UE response message belongs to the radio network controller group RNC Cluster where the RNC is located; Step 503: If the judgment result is no, the UE response message does not belong to the RNC Cluster where the RNC1 is located, and according to the obtained target RNC Cluster ID, the RNC sends an information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST to the target RNC Clusters.
  • Step 504 RNC2 According to The information exchange initialization request message sent by the RNCl is an INFORMATION EXCHANGE INITIATION REQUEST, and the message includes the identifier C-ID of the cell in the RNC.
  • the RNC2 performs the RNC Cluster internal processing by the information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST.
  • Mode The RNC in the RNC Cluster shares a message queue, and the RNC 2 puts the information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST into the message queue, and sends an internal message to each RNC in the RNC Cluster.
  • the second message where the RNC determines, according to the second identifier, whether it belongs to its own processing; or the RNC in the RNC Cluster shares a message queue, and the RNC2 determines according to the second identifier.
  • the information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST is placed in the message queue, and an internal message request is sent to other RNCs in the RNC Cluster, triggering each RNC
  • the external message is checked according to whether the second RNC determines whether it belongs to its own processing or the RNC2 determines whether it belongs to its own processing.
  • FIG. 6 is a flowchart of message processing in an RNC Cluster according to an embodiment of the present invention. As shown in FIG. 6, the process includes the following steps: Step S601: The RNC1 receives a first message sent by the UE, where the first message is URA.
  • the first message carrying the corresponding first identifier is The UTRAN radio network temporarily identifies the U-RNTI or UTRAN radio network temporary identity U-RNTI or the identity of the cell in the PLMN Cell Identity.
  • Step S602 The RNC1 resolves the first 12 bits as the RNC Cluster ID of the target RNC Cluster according to the U-RNTI or the Cell Identity, and the RNC1 determines, according to the determination rule, whether the message belongs to the radio network controller group RNC Cluster where the RNC is located; 603: When the judgment result is yes, the RNC1 sends a second message, where the second message is an uplink signaling transmission indication message or an uplink signaling transmission indication message or an information exchange initialization request message, an INFORMATION EXCHANGE INITIATION REQUEST, where the second message is The second identifier is further included, and the second identifier corresponding to the second message is an S-RNTI or an S-RNTI or an identifier C-ID of the cell in the RNC, and the RNC1 performs the RNC Cluster internal processing on the second message, including In any one of the following manners: the RNC in the RNC cluster shares a message queue, the RNC1 puts the second message into the message queue, and sends an internal message request
  • the internal message request triggers each RNC to check the external message.
  • the determining, according to the second identifier, whether it belongs to its own processing or whether the RNC1 determines whether it belongs to itself according to the second identifier is:
  • the RNC is based on the S- in the message.
  • the RNTI or the cell ID combined with the RNC ID of the UE, combines the U-RNTI or the Cell Identity of the UE, and determines whether the message should be processed by the RNC according to the U-RNTI or the Cell Identity of the UE.
  • the RNC processes the message.
  • the embodiment of the present invention further provides a radio network controller RNC. As shown in FIG.
  • the radio network controller RNC700 includes: a receiving module, configured to receive a first message, and a processing module, configured to determine a rule, determining whether the target radio network controller group RNC Cluster corresponding to the first message is an RNC Cluster in which the RNC is located, where the RNC Cluster is composed of one or more RNCs; if the determination result is yes, the RNC sends a second The message is internally processed by the RNC Cluster; if the judgment result is no, the RNC sends a second message to the target RNC Clusters
  • the RNC Cluster has an RNC Cluster ID, and the value of the RNC Cluster ID is the same as the first n bits of the RNC ID of the RNC in the RNC Cluster.
  • the first message carries a first identifier
  • the processing module determines a target RNC Cluster according to the first identifier
  • the second message further includes a second identifier
  • the processing module uses the second message.
  • the RNC Cluster internal processing is performed by any of the following processing modes: the RNC in the RNC Cluster shares a message queue, and the processing module puts the second message into the message queue and sends the RNC to other RNCs in the RNC Cluster.
  • each RNC determines whether it belongs to itself according to the second identifier; or, the RNC in the RNC Cluster shares a message queue, and the processing module according to the Determining whether the second identifier is processed by itself, and if so, processing, if the second message is otherwise put into the message queue, and sending an internal message request to other RNCs in the RNC Cluster, triggering each RNC to Check the external message.
  • the first message, the first identifier, the second message, and the second identifier are any one of the following: the first message is a URA update message, and the first identifier is a UTRAN radio network temporary identifier U-RNTI, and the second The message is an uplink signaling transmission indication message, the second identifier is a radio network controller temporary identifier S-RNTI, or the first message is a cell update message, the first identifier is a UTRAN radio network temporary identifier U-RNTI, and the second message is an uplink.
  • the signaling identifier indicates that the second identifier is the radio network controller temporary identifier S-RNTI; or the first message is the UE information response message UE INFORMATION RESPONSE, the first identifier is the identifier of the cell in the PLMN, and the second message is The information exchange initialization request message INFORMATION EXCHANGE INITIATION REQUEST, the second identifier is the identifier C-ID of the cell in the RNC. While the embodiments of the present invention have been described above, the present invention is intended to be illustrative only, and is not intended to limit the invention. Any modification and variation in the form and details of the embodiments may be made by those skilled in the art without departing from the spirit and scope of the invention. The scope defined by the appended claims shall prevail.

Abstract

本发明提供一种UE移动性方法及装置，该方法包括：无线网络控制器RNC接收一第一消息；所述RNC根据判断规则，判断所述第一消息对应的目标无线网络控制器组RNC Cluster是否该RNC所在的RNC Cluster，所述RNC Cluster由一个或多个RNC 组成；判断结果为是，则所述RNC发送一第二消息进行RNC Cluster内部处理；或，判断结果为否，则所述RNC发送所述第二消息至所述目标RNC Cluster，通过本发明使得UE在RNC间移动时能够不掉话，保证业务的连续性接收。

Description

一种 UE移动性的方法及装置 技术领域 本发明涉及移动通信系统， 尤其涉及一种 UE移动性的方法和装置。 背景技术 通用移动电信系统（Universal Mobile Telecommunication System, 简称 UMTS)属 于第三代通信系统， UMTS 的网络部分称作 UMTS 陆地无线接入网 （Universal Terrestrial Radio Access Network,简称 UTRAN), UTRAN结构分为无线接入网络（Radio Access Network, 简称 RAN) 和核心网 （Core Network, 简称 CN)， 其中无线接入网 络用于处理所有与无线相关的功能， 而 CN处理系统内所有的话音呼叫和数据连接与 外部网络的交换和路由。 上述两个单元与用户设备 （User Equipment, 简称 UE) —起 构成了整个系统。 无线接入网络的网络单元包括无线网络控制器 （Radio Network Controller, 简称 RNC) 和收发基站 （节点 B， 简称 NodeB)。 为了在 UTRAN中能够 区分出各个 UE， 定义了一个 UTRAN 无线网络临时标识 U-RNTI (UTRAN Radio Network Temple Identity), U-RNTI长度是 32bit， 由两部分组成： 无线网络控制器标识 SRNC identity和无线网络控制器临时标识 S-RNTI ( SRNC RNTI)。其中 SRNC identity 表示的是服务 RNC标识， 含义同 RNC ID。 S-RNTI表示 SRNC的无线网络临时标识。 SRNC identity定义为 12bit， S-RNTI定义为 20bit， 如果 SRNC ID多于 12bit， 则多于 12bit的部分在 S-RNTI中。 公共态的 UE在 RNC间移动时， 会向漂移无线网络控制器 DRNC (Drift RNC) 发送小区更新消息或者 URA更新消息， 消息中携带 U-RNTI, DRNC根据消息中携带 的 U_RNTI解析出 RNC-ID确定应该向哪个 RNC发送消息。目前协议上 RNC ID共有 两种： 一种是普通的 RNC ID, 最多 12bit， 另外一种是扩展 RNC ID， 最多可以扩展为 16bit， 但是 DRNC并不知道 SRNC是采用普通的 RNC ID还是扩展 RNC ID, 按照相 关的技术， 有如下几种情况： （1 ) 如果目标 RNC ID实际是普通 RNC ID, 按照普通 RNC ID解析，消息会正确发送到目标 RNC; (2)如果目标 RNC ID实际是扩展 RNC ID, 按照普通 RNC ID解析， 消息可能会正确发送到目标 RNC， 也可能会错误发送； （3 ) 如果目标 RNC ID实际是扩展 RNC ID, 按照扩展 RNC ID解析， 消息会正确发送到目 标 RNC; (4) 如果目标 RNC ID实际是普通 RNC ID， 按照扩展 RNC ID解析， 消息 会错误发送。如果消息发送错误， 那么接收到消息的 RNC就会将消息丢弃掉， 这样当 UE跨 RNC移动时就容易导致掉话。 并且对于 UMTS中的自动关系功能 ANR ( Automatic Neighbor Relation),通过 UE 在专用连接态下接收到网络侧下发的测量控制消息， 辅助测量新小区的信息并上报给 网络侧， 上报的消息包括小区在无线网络中的标识， 网络侧获取后可以得知有哪些邻 区漏配了。 小区在无线网络中的标识 Cell Identity共 28bit， 包括 RNC标识 RNC ID和 RNC内小区标识 C-ID， 如果 RNC根据小区在无线网络中的标识发现有非本 RNC下 的小区， 需要向其他 RNC发送消息获取信息。 但是本 RNC并不知道其他 RNC采用 的是 12bit还是 16bit的 RNC， 按照相关的技术， 有如下几种情况： （1 )如果目标 RNC ID实际是普通 RNC ID, 按照普通 RNC ID解析， 消息会正确发送到目标 RNC; (2) 如果目标 RNC ID实际是扩展 RNC ID, 按照普通 RNC ID解析， 消息可能会正确发送 到目标 RNC， 也可能会错误发送； （3 ) 如果目标 RNC ID实际是扩展 RNC ID， 按照 扩展 RNC ID解析， 消息会正确发送到目标 RNC; (4) 如果目标 RNC ID实际是普通 RNC ID, 按照扩展 RNC ID解析， 消息会错误发送。如果消息发送错误， RNC漏配的 邻区就不能识别出来， 这样当 UE跨 RNC移动时就容易导致掉话。 发明内容 本发明提供了一种 UE移动性的方法和装置， 使得 UE在 RNC间移动时能够不掉 话， 保证业务的连续性接收。 为了解决上述技术问题， 本发明提供了一种 UE移动性的方法， 该方法包括： 无线网络控制器 RNC接收一第一消息； 所述 RNC根据判断规则， 判断所述第一消息对应的目标无线网络控制器组 RNC Cluster是否为该 RNC所在的 RNC Cluster,所述 RNC Cluster由一个或多个 RNC组成； 判断结果为是， 则所述 RNC发送一第二消息进行 RNC Cluster内部处理； 或， 判断结果为否， 则所述 RNC发送所述第二消息至所述目标 RNC Clusters 优选地， 述 RNC Cluster具有 RNC Cluster Identity ID, 该 RNC Cluster ID的值与 本 RNC Cluster内 RNC的 RNC ID的前 n位相同。 优选地， 所述判断规则为： 所述第一消息中携带一第一标识， 所述 RNC根据该第 一标识确定所述目标 RNC Cluster ID。 优选地，所述第二消息还包括一第二标识，所述 RNC根据第二标识将所述第二消 息对所述第二消息采用以下处理方式进行 RNC Cluster内部处理： 所述 RNC Cluster内 RNC共享一消息队列， 所述 RNC将所述第二消息放入所述 消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC 来检查该第二消息，所述各个 RNC根据所述第二标识判断是否属于自己处理所述各个 RNC根据所述第二标识结合自身的 RNC ID, 判断出是否当前 RNC处理； 或， 所述 RNC Cluster内 RNC共享一消息队列， 所述 RNC根据所述第二标识判断是 否属于自己处理， 如是， 则进行处理， 如否则将所述第二消息放入所述消息队列， 并 向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检查该外部 消息， 所述各个 RNC或所述 RNC根据所述第二标识结合自身的 RNC ID, 判断出是 否当前 RNC处理。 优选地， 第一消息为 URA 更新消息， 第一标识为 UTRAN无线网络临时标识
U-RNTI, 第二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为小区更新消息，第一标识为 UTRAN无线网络临时标识 U-RNTI,第二 消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为 UE信息响应消息 UE INFORMATION RESPONSE, 第一标识为小区 在 PLMN中的标识 Cell Identity,第二消息为信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST, 第二标识为小区在 RNC中的标识 C-ID。 优选地， 所述 RNC Cluster内的各个 RNC之间采用内部自定义消息或标准 Iur口 消息。 本发明还提供一种无线网络控制器 RNC， 所述 RNC包括： 一接收模块， 设置为接收一第一消息； 一处理模块， 设置为根据判断规则， 判断所述第一消息对应的目标无线网络控制 器组 RNC Cluster是否该 RNC所在的 RNC Cluster, 所述 RNC Cluster由一个或多个 RNC组成； 判断结果为是， 则所述处理模块发送第二消息进行 RNC Cluster内部处理， 或， 判断结果为否， 则所述 RNC发送第二消息至所述目标 RNC Clusters 优选地，所述 RNC Cluster具有 RNC Cluster ID,该 RNC Cluster ID的值与本 RNC Cluster内 RNC的 RNC ID的前 n位相同。 优选地， 所述判断规则为： 所述第一消息中携带一第一标识， 所述处理模块 RNC 根据该第一标识确定目标 RNC Clusters 优选地， 所述第二消息包括一第二标识， 所述处理模块根据第二标识对所述第二 消息 RNC Cluster内部处理采用以下处理方式进行 RNC Cluster内部处理： 所述 RNC Cluster内 RNC共享一消息队列， 所述处理模块 RNC将所述第二消息 放入所述消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各 个 RNC来检查该第二消息， 所述各个 RNC根据所述第二标识结合自身的 RNC ID, 判断出是否当前 RNC处理； 或， 所述 RNC Cluster内 RNC共享一消息队列， 所述处理模块 RNC根据所述第二标 识判断是否属于自己处理， 如是， 则进行处理， 如否则将所述第二消息放入所述消息 队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检 查该外部消息， 所述各个 RNC或所述 RNC根据所述第二标识结合自身的 RNC ID, 判断出是否当前 RNC处理。 优选地， 第一消息为 URA 更新消息， 第一标识为 UTRAN无线网络临时标识 U-RNTI, 第二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为小区更新消息，第一标识为 UTRAN无线网络临时标识 U-RNTI,第二 消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为 UE信息响应消息 UE INFORMATION RESPONSE, 第一标识为小区 在 PLMN中的标识 Cell Identity,第二消息为信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST, 第二标识为小区在 RNC中的标识 C-ID。 优选地， 所述 RNC Cluster内的各个 RNC之间采用内部自定义消息或标准 Iur口 消息。 与相关技术相比， 本申请提供了一种 UE移动性的方法， 使得 UE在 RNC之间移 动时 RNC能够正确进行消息处理， 保证了业务的连续性接收， 提高了用户的感受， 同 时有力地提升了网络的性能指标。 附图说明 附图用来提供对本发明技术方案的进一步理解， 并且构成说明书的一部分， 与本 申请的实施例一起用于解释本发明的技术方案， 并不构成对本发明技术方案的限制。 图 1为本发明的一种改进的无线网络架构； 图 2为本法实施例的跨 RNC Cluster的消息处理流程图； 图 3为本发明实施例的跨 RNC Cluster的 URA Update处理流程图； 图 4为本发明实施例的跨 RNC Cluster的 Cell Update处理流程图； 图 5为本发明实施例的跨 RNC Cluster的 ANR处理流程图； 图 6为本发明实施例的 RNC Cluster内的消息处理流程图； 图 7为本法实施例的 RNC 结构图。 具体实施方式 为使本发明的目的、 技术方案和优点更加清楚明白， 下面结合附图和具体实施例 对本发明所述技术方案作进一步的详细描述， 以使本领域的技术人员可以更好的理解 本发明并能予以实施， 但所举实施例不作为对本发明的限定。 需要说明的是， 在不冲 突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。 图 1为本发明实施例 1的 RNC 组 （RNC Cluster) 的结构图。 在本实施例中， RNC 组 （以下称 RNC Cluster) 由多个 RNC组成， 同一个 RNC Cluster内的 RNC的 RNC ID的前 n个 bit位相同， 每个 RNC与 CN之间通过 Iu口进 行通信， RNC和 NodeB通过 Iub接口相连。 RNC Cluster间通过 Iur口连接。 RNC Cluster内的 RNC间通信可以采用标准 Iur口消息， 也可以不用再采用标准 lur口消息， 采用内部自定义消息， 采用内部自定义消息有利于简化消息结构， 减少消 息处理长度， 提高处理效率。
Iu口、 Iub口以及 RNC Cluster间的 Iur口仍与目前的标准接口相同。 上述的 n可以等于 12或者其他值。 RNC Cluster定义一个 RNC Cluster ID, 值为 RNC Cluster内的 RNC ID的前 n个 bit。 RNC Cluster中包括一个或多个 RNC。 第一标识的前 nbit作为 RNC Cluster ID, 剩余的 bit位组成第二标识， 第一消息中 携带第一标识， 第二消息中携带第二标识。
RNC预先配置好邻接的 RNC Cluster标识。
RNC Cluster内的 RNC的数据区与消息队列可以共享。 图 2为本法实施例的跨 RNC Cluster的消息处理流程图， 如图 2所示， 该消息处 理流程包括如下步骤： 步骤 201 : RNC1收到 UE发送的第一消息， 消息中包含了第一标识； 所述 RNC1位于一无线网络控制器组 RNC Cluster中， 所述 RNC Cluster有一个 RNC Cluster ID,该 RNC Cluster ID的值与本 RNC Cluster内的 RNC的 RNC ID的前 n 位 （bit) 相同。 步骤 202: RNCl根据判断规则， 判断所述外部消息（即上述第一消息）是否属于 该 RNC1所在的无线网络控制器组 RNC Cluster处理； 所述判断规则为： 所述外部消息携带一第一标识， RNC1 根据第一标识解出前 n bit, 作为目标 RNC Cluster的 RNC Cluster ID。 步骤 203: 若 RNC1的判断结果为是， 即目标 RNC Cluster的 RNC Cluster ID与
RNCl所在的 RNC Cluster ID 相同， RNCl所在的 RNC Cluster即为目标 RNC Cluster, 则 RNCl发送第二消息在 RNCl所在的 RNC Cluster进行处理； 或， 若 RNC1的判断结果为否， 即目标 RNC Cluster的 RNC Cluster ID与 RNCl 所在的 RNC Cluster ID不同， RNC 1所在的 RNC Cluster不是目标 RNC Cluster, 则 RNC 1根据步骤 202得到的目标 RNC Cluster的 RNC Cluster ID， 发送第二消息给目标 RNC Cluster 其中， 发送第二消息给目标 RNC Cluster, 是指发送第二消息给目标 RNC Cluster 中的任意一 RNC (在本实施例中可以是 RNC2)， 或指发送给目标 RNC Cluster中的主 控模块或主控 RNC。 主控模块可以为一个单独的一个处理单元， 或者是一个 RNC， 主控 RNC的确定方式， 可以是静态配置一个主控 RNC， 或者根据负荷或其他因素选 举出一个主控 RNC。 根据上述步骤 203所述内部处理， RNC1发送一第二消息， 所述第二消息包含一 第二标识， 所述 RNC1将所述第二消息进行 RNC Cluster内部处理包括以下任一种方 式： 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC1将所述第二消息放入所述 消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC 来检查该外部消息， 所述各个 RNC根据所述第二标识判断是否属于自己处理； 或 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC2根据所述第二标识判断是 否属于自己处理， 如是， 则进行处理， 如否则将所述第二消息放入所述消息队列， 并 向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检查该第二 消息； 所述各个 RNC根据所述第二标识判断是否属于自己处理或 RNC2根据所述第二 标识判断是否属于自己处理在是的情况下是指 RNC根据第二消息中的第二标识，结合 自身的 RNC ID, 组合出 UE的第一标识， 根据 UE的第一标识查找是否有记录 UE的 消息； 在否的情况下是指忽视该第二消息， 不进行处理。 其中， 所述第一消息、 所述第一标识， 第二消息以及第二标识为以下任意一种： 第一消息为 URA更新消息， 第一标识为 UTRAN无线网络临时标识 U-RNTI, 第 二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为小区更新消息，第一标识为 UTRAN无线网络临时标识 U-RNTI,第二 消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为 UE信息响应消息 UE INFORMATION RESPONSE, 第一标识为小区 在 PLMN中的标识 Cell Identity,第二消息为信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST, 第二标识为小区在 RNC中的标识 C-ID。 步骤 204: 只有查找到有记录 UE的信息， RNC处理该消息， 执行重定位或不重 定位或其他流程。 图 3为本发明实施例的跨 RNC Cluster的 URA Update处理流程图， 如图 3所示， 该处理流程具体包括如下步骤： 步骤 S301 : RNC1收到 UE发送的第一消息 URA更新消息 URAUpdate, 消息中 包含了第一标识 U-RNTI； 步骤 S302: RNC1根据第一标识 U-RNTI, 解出前 12bit， 作为目标 RNC Cluster 的 RNC Cluster ID, RNC1根据判断规则， 判断所述 URA更新消息 URA Update是否 属于该 RNC所在的无线网络控制器组 RNC Cluster处理； 步骤 303 : 判断结果为否， 则该 URA更新消息 URAUpdate不属于 RNC1所在的 RNC Cluster处理， 则根据已经得到的目标 RNC Cluster ID， 向目标 RNC Cluster发送 第二消息上行信令传输指示消息 Uplink Signalling Transfer Indication, 消息中包含了第 二标识 S-RNTI。 步骤 304: RNC2根据收到的 RNC1发送的第二消息上行信令传输指示消息 Uplink Signalling Transfer Indication， 消息中包含了第二标识 S-RNTI； 将所述外部消息进行 RNC Cluster内部处理包括以下任一种方式： 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC2将所述第二消息上行信令 传输指示消息 Uplink Signalling Transfer Indication放入所述消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求 Information Request, 触发各个 RNC来检查 该第二消息， 所述各个 RNC根据所述第二标识 S-RNTI判断是否属于自己处理； 或 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC2根据所述第二标识判断是 否属于自己处理， 如是， 则进行处理， 如否则将所述 I上行信令传输指示消息 Uplink Signalling Transfer Indication放入所述消息队列， 并向所述 RNC Cluster内的其他 RNC 发送内部消息请求， 触发各个 RNC来检查该第二消息； 所述各个 RNC判断是否属于自己处理或 RNC2判断是否属于自己处理， 在是自 己处理的情况下， RNC根据消息中的 S-RNTI, 结合自身的 RNC ID, 组合出 UE的 U-RNTI, 根据 UE的 U-RNTI查找是否有记录的 UE信息； 在不是自己处理的情况下， 则忽视该第二消息， 不进行处理。 步骤 S305, 只有查找到有记录的 UE信息， RNC处理该消息， 执行重定位或不重 定位或其他流程。 图 4为本发明实施例的跨 RNC Cluster的 Cell Update处理流程图， 如图 4所示， 该处理流程具体包括如下步骤： 步骤 S401 : RNC1收到 UE发送的第一消息 Cell Update消息， 消息中包含了第一 标识 U-RNTI。 步骤 S402: RNCl根据 U-RNTI,解出前 12bit，作为目标 RNC Cluster的 RNC Cluster ID, RNCl根据判断规则， 判断所述 Cell URA Update消息是否属于该 RNC所在的无 线网络控制器组 RNC Cluster处理； 步骤 S403 :判断结果为否，则该 Cell Update消息不属于 RNC1所在的 RNC Cluster 处理， 根据已经得到的目标 RNC Cluster ID， RNCl向目标 RNC Cluster发送上行信令 传输指示消息， 消息中包含了第二标识 S-RNTI。 步骤 404: RNC2根据 RNCl发送的上行信令传输指示消息，消息中包含了 S-RNTI; 所述 RNC2将所述 Cell Update消息进行 RNC Cluster内部处理包括以下任一种方 式： 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC2将所述上行信令传输指示 消息 Uplink Signalling Transfer Indication 消息放入所述消息队列， 并向所述 RNC Cluster内的各个 RNC发送内部消息请求， 触发各个 RNC来检查该第二消息， 所述各 个 RNC根据所述第二标识判断是否属于自己处理； 或 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC2根据所述第二标识判断是 否属于自己处理， 如是， 则进行处理， 如否则将所述上行信令传输指示消息 Uplink Signalling Transfer Indication放入所述消息队列， 并向所述 RNC Cluster内的其他 RNC 发送内部消息请求， 触发各个 RNC来检查该第二消息； 所述 RNC根据 S-RNTI来判断消息是否属于自己处理或 RNC2根据 S-RNTI来判 断是否属于自己处理是指： 在是自己处理的情况下， RNC根据上行信令传输指示消息 中的 S-RNTI, 结合自身的 RNC ID, 组合出 UE的 U-RNTI, 根据 UE的 U-RNTI查找 是否有记录的 UE信息； 在不是自己处理的情况， 则不进行处理， 则忽视上行信令传 输指示消息。 步骤 S405, 只有查找到有记录的 UE信息， RNC处理该消息， 向 RNC1发送响应 消息。 图 5为本发明实施例的跨 RNC Cluster的 ANR处理流程图， 如图 5所示， 该处理 流程具体包括如下步骤： 步骤 S501 : RNC1 收到 UE 发送的 UE 信息响应消息 UE INFORMATION RESPONSE, 消息中包含第一标识为小区在 PLMN中的标识 Cell Identity。 步骤 S502: RNCl根据 Cell Identity,解出前 12bit， 作为目标 RNC Cluster的 RNC Cluster ID, RNCl根据判断规则， 判断所述 UE响应消息是否属于该 RNC所在的无线 网络控制器组 RNC Cluster处理； 步骤 503 : 判断结果为否， 则该 UE响应消息不属于 RNC1所在的 RNC Cluster处 理， 则根据已经得到的目标 RNC Cluster ID， 则 RNCl发送信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST给目标 RNC Clusters 步骤 504: RNC2 根据 RNCl 发送的信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST, 消息中包含了小区在 RNC中的标识 C-ID; 所述 RNC2 将信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST进行 RNC Cluster内部处理包括以下任一种方式： 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC2将所述信息交换初始化请 求消息 INFORMATION EXCHANGE INITIATION REQUEST放入所述消息队列，并向 所述 RNC Cluster内的各个 RNC发送内部消息请求， 触发各个 RNC来检查该第二消 息， 所述各个 RNC根据所述第二标识判断是否属于自己处理； 或 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC2根据所述第二标识判断是 否属于自己处理， 如是， 则进行处理， 如否则将所述信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST放入所述消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检查该外部消息； 所述各个 RNC根据所述第二标识判断是否属于自己处理或 RNC2判断是否属于 自己处理是指： RNC根据消息中的小区标识 C-ID, 结合自身的 RNC ID, 组合出 Cell Identity。 步骤 S505， 只有该小区属于本 RNC， RNC处理该消息， 向 RNC1发送响应消息。 图 6为本发明实施例的 RNC Cluster内的消息处理流程图， 如图 6所示， 该处理 流程具体包括如下步骤： 步骤 S601 : RNC1收到 UE发送的第一消息， 该第一消息为 URA更新消息 URA Update或者小区更新消息 Cell Update或者 UE 信息响应消息 UE INFORMATION RESPONSE, 所述第一消息携带对应的第一标识为 UTRAN无线网络临时标识 U-RNTI或 UTRAN无线网络临时标识 U-RNTI或小区在 PLMN中的标识 Cell Identity。 步骤 S602: RNC1根据 U-RNTI或者 Cell Identity, 解出前 12bit， 作为目标 RNC Cluster的 RNC Cluster ID, RNC1根据判断规则， 判断所述消息是否属于该 RNC所在 的无线网络控制器组 RNC Cluster处理； 步骤 603 : 判断结果为是时， 所述 RNC1发送第二消息， 所述第二消息为上行信 令传输指示消息或上行信令传输指示消息或信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST, 其中第二消息还包括一第二标识， 第二消息所 对应的第二标识为 S-RNTI或 S-RNTI或小区在 RNC中的标识 C-ID,所述 RNC1将所 述第二消息进行 RNC Cluster内部处理包括以下任一种方式： 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC1将所述第二消息放入所述 消息队列， 并向所述 RNC Cluster内的各个 RNC发送内部消息请求， 触发各个 RNC 来检查该外部消息， 所述各个 RNC根据所述第二标识判断是否属于自己处理； 或 所述 RNC Cluster内 RNC共享一消息队列，所述 RNC1根据所述第二标识判断是 否属于自己处理， 如是， 则进行处理， 如否则将所述第二消息放入所述消息队列， 并 向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检查该外部 消息； 所述各个根据所述第二标识判断是否属于自己处理或 RNC1根据所述第二标识 判断是否属于自己处理是指： RNC根据消息中的 S-RNTI或者小区 ID， 结合自身的 RNC ID,组合出 UE的 U-RNTI或者 Cell Identity,根据 UE的 U-RNTI或者 Cell Identity 确定是否应该本 RNC处理该消息。 步骤 S604， RNC处理该消息。 本发明的实施例还提供了一种无线网络控制器 RNC， 如图 7所示， 该无线网络控 制器 RNC700包括： 一接收模块， 设置为接收一第一消息， 一处理模块， 设置为根据判断规则， 判断所述第一消息对应的目标无线网络控制 器组 RNC Cluster是否该 RNC所在的 RNC Cluster, 所述 RNC Cluster由一个或多个 RNC组成； 判断结果为是， 则所述 RNC发送第二消息进行 RNC Cluster内部处理； 判断结果 为否， 则所述 RNC发送第二消息至所述目标 RNC Clusters 其中， 所述 RNC Cluster具有 RNC Cluster ID, 该 RNC Cluster ID的值与本 RNC Cluster内 RNC 的 RNC ID的前 n位相同。 其中， 所述第一消息中携带一第一标识， 所述处理模块根据第一标识确定目标 RNC Cluster 其中所述第二消息还包括一第二标识， 所述处理模块将所述第二消息采用以下任 意一种处理方式进行 RNC Cluster内部处理： 所述 RNC Cluster内 RNC共享一消息队列， 所述处理模块将所述第二消息放入所 述消息队列，并向所述 RNC Cluster内的其他 RNC发送内部消息请求，触发各个 RNC 来检查该第二消息， 所述各个 RNC根据所述第二标识判断是否属于自己处理； 或， 所述 RNC Cluster内 RNC共享一消息队列， 所述处理模块根据所述第二标识判断 是否属于自己处理， 如是， 则进行处理， 如否则将所述第二消息放入所述消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检查该外 部消息。 其中， 所述第一消息、 所述第一标识， 第二消息以及第二标识为以下任意一种： 第一消息为 URA更新消息， 第一标识为 UTRAN无线网络临时标识 U-RNTI, 第 二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为小区更新消息，第一标识为 UTRAN无线网络临时标识 U-RNTI,第二 消息为上行信令传输指示消息， 第二标识为无线网络控制器临时标识 S-RNTI; 或 第一消息为 UE信息响应消息 UE INFORMATION RESPONSE, 第一标识为小区 在 PLMN中的标识 Cell Identity,第二消息为信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST, 第二标识为小区在 RNC中的标识 C-ID。 虽然本发明所揭露的实施方式如上， 但所述的内容仅为便于理解本发明而采用的 实施方式， 并非用以限定本发明。 任何本发明所属领域内的技术人员， 在不脱离本发 明所揭露的精神和范围的前提下，可以在实施的形式及细节上进行任何的修改与变化， 但本发明的专利保护范围， 仍须以所附的权利要求书所界定的范围为准。

Claims

权 利 要 求 书
1. 一种 UE移动性的方法， 包括： 无线网络控制器 RNC接收一第一消息；
所述 RNC 根据判断规则， 判断所述第一消息对应的目标无线网络控制器 组 RNC Cluster是否为该 RNC所在的 RNC Cluster,所述 RNC Cluster由一个或 多个 RNC组成；
判断结果为是， 则所述 RNC发送一第二消息进行 RNC Cluster内部处理； 或， 判断结果为否， 则所述 RNC 发送所述第二消息至所述目标 RNC Cluster。
2. 如权利要求 1所述的 UE移动性的方法，其中，所述 RNC Cluster具有无线网络 控制器组标识 RNC Cluster ID,该 RNC Cluster ID的值与本 RNC Cluster内 RNC 的 RNC ID的前 n位相同。
3. 如权利要求 1所述的 UE移动性的方法， 其中， 所述判断规则为： 所述第一消 息中携带一第一标识， 所述 RNC根据该第一标识确定所述目标 RNC Clusters
4. 如权利要求 3所述的 UE移动性的方法， 其中， 所述第二消息还包括一第二标 识， 所述 RNC 根据第二标识对所述第二消息采用以下处理方式进行 RNC Cluster内部处理： 所述 RNC Cluster内 RNC共享一消息队列， 所述 RNC将所述第二消息放 入所述消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触 发各个 RNC来检查该第二消息， 所述各个 RNC根据所述第二标识结合自身的 RNC ID, 判断出是否当前 RNC处理； 或，
所述 RNC Cluster内 RNC共享一消息队列， 所述 RNC根据所述第二标识 判断是否属于自己处理， 如是， 则进行处理， 如否则将所述第二消息放入所述 消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检查该外部消息，所述各个 RNC或所述 RNC根据所述第二标识结合自 身的 RNC ID, 判断出是否当前 RNC处理。 如权利要求 4所述的 UE移动性的方法， 其中， 第一消息为 URA 更新消息， 第一标识为 UTRAN 无线网络临时标识 U-RNTI,第二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时 标识 S-RNTI; 或 第一消息为小区更新消息， 第一标识为 UTRAN 无线网络临时标识 U-RNTI,第二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时 标识 S-RNTI; 或 第一消息为 UE信息响应消息 UE INFORMATION RESPONSE, 第一标识 为小区在 PLMN中的标识 Cell Identity, 第二消息为信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST,第二标识为小区在 RNC 中的标识 C-ID。
6. 如权利要求 1所述的 UE移动性的方法，其中，所述 RNC Cluster内的各个 RNC 之间采用内部自定义消息或标准 Iur口消息。
7. 一种无线网络控制器 RNC， 包括： 一接收模块， 设置为接收一第一消息；
一处理模块， 设置为根据判断规则， 判断所述第一消息对应的目标无线网 络控制器组 RNC Cluster是否为该 RNC所在的 RNC Cluster, 所述 RNC Cluster 由一个或多个 RNC组成；
判断结果为是， 则所述处理模块发送第二消息进行 RNC Cluster内部处理， 或， 判断结果为否， 则所述 RNC发送第二消息至所述目标 RNC Clusters
8. 如权利要求 7所述的 RNC， 其中， 所述 RNC Cluster具有 RNC Cluster ID, 该 RNC Cluster ID的值与本 RNC Cluster内 RNC 的 RNC ID的前 n位相同。
9. 如权利要求 7所述的 RNC， 其中， 所述判断规则为： 所述第一消息中携带一第 一标识， 所述处理模块根据该第一标识确定目标 RNC Clusters
10. 如权利要求 7所述的 RNC， 其中， 所述第二消息包括一第二标识， 所述处理模 块根据第二标识对所述第二消息采用以下处理方式进行 RNC Cluster内部处理： 所述 RNC Cluster内 RNC共享一消息队列，所述处理模块将所述第二消息 放入所述消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各个 RNC来检查该第二消息， 所述各个 RNC根据所述第二标识结合自身 的 RNC ID, 判断出是否当前 RNC处理； 或， 所述 RNC Cluster内 RNC共享一消息队列，所述处理模块根据所述第二标 识判断是否属于自己处理， 如是， 则进行处理， 如否则将所述第二消息放入所 述消息队列， 并向所述 RNC Cluster内的其他 RNC发送内部消息请求， 触发各 个 RNC来检查该外部消息， 所述各个 RNC或所述 RNC根据所述第二标识结 合自身的 RNC ID, 判断出是否当前 RNC处理。
11. 如权利要求 7所述的 RNC， 其中， 第一消息为 URA 更新消息， 第一标识为 UTRAN 无线网络临时标识 U-RNTI,第二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时 标识 S-RNTI; 或 第一消息为小区更新消息， 第一标识为 UTRAN 无线网络临时标识 U-RNTI,第二消息为上行信令传输指示消息， 第二标识为无线网络控制器临时 标识 S-RNTI; 或 第一消息为 UE信息响应消息 UE INFORMATION RESPONSE, 第一标识 为小区在 PLMN中的标识 Cell Identity, 第二消息为信息交换初始化请求消息 INFORMATION EXCHANGE INITIATION REQUEST,第二标识为小区在 RNC 中的标识 C-ID。
12. 如权利要求 7所述的 RNC， 其中， 所述 RNC Cluster内的各个 RNC之间采用 内部自定义消息或标准 Iur口消息。
PCT/CN2014/080145 2013-12-26 2014-06-17 一种ue移动性的方法及装置 WO2015096413A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP14875311.4A EP3089547B1 (en) 2013-12-26 2014-06-17 Method and device for moving ue
ES14875311T ES2812573T3 (es) 2013-12-26 2014-06-17 Método y dispositivo para mover un UE
US15/108,419 US9967790B2 (en) 2013-12-26 2014-06-17 Method and device for moving UE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310733322.2 2013-12-26
CN201310733322.2A CN104754667B (zh) 2013-12-26 2013-12-26 一种ue移动性方法及装置

Publications (1)

Publication Number Publication Date
WO2015096413A1 true WO2015096413A1 (zh) 2015-07-02

Family

ID=53477457

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/080145 WO2015096413A1 (zh) 2013-12-26 2014-06-17 一种ue移动性的方法及装置

Country Status (5)

Country Link
US (1) US9967790B2 (zh)
EP (1) EP3089547B1 (zh)
CN (1) CN104754667B (zh)
ES (1) ES2812573T3 (zh)
WO (1) WO2015096413A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3394944B1 (en) * 2015-11-24 2020-11-11 Carestream Health, Inc. Cable system and method
CN108156589B (zh) * 2017-12-22 2022-01-25 横琴国际知识产权交易中心有限公司 一种基于家庭基站的寻呼方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068432A (zh) * 2007-04-18 2007-11-07 中兴通讯股份有限公司 一种为mbms业务统一分配资源的装置、系统和方法
CN101622903A (zh) * 2007-01-29 2010-01-06 诺基亚公司 提供传统和其他无线网络子系统之间互操作性的设备、方法和计算机程序产品
CN103392376A (zh) * 2011-02-14 2013-11-13 瑞典爱立信有限公司 无线网络控制器和无线网络控制器组件

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8195187B2 (en) * 2001-06-25 2012-06-05 Airvana Network Solutions, Inc. Radio network control
KR100896731B1 (ko) * 2002-06-27 2009-05-11 인터디지탈 테크날러지 코포레이션 사용자 장치 측정값 정보를 피어 투 피어 방식으로교환하는 무선 네트워크 제어기
US7546145B2 (en) * 2002-10-15 2009-06-09 Nokia Corporation Method, network node and system for managing interfaces in a distributed radio access network
CN101547493B (zh) * 2008-03-24 2012-04-04 中兴通讯股份有限公司 无线网络控制器标识解析方式的指示方法
WO2011000152A1 (zh) * 2009-06-30 2011-01-06 上海贝尔股份有限公司 在无线局域网中移动终端漫游的方法、相关的接入控制器和接入点设备
EP2826195B1 (en) * 2012-03-14 2015-12-23 Telefonaktiebolaget LM Ericsson (PUBL) Method to notify node in multi point transmission
US9781610B2 (en) * 2013-12-18 2017-10-03 Qualcomm Incorporated Small cell clusters for signaling load reduction, time synchronization, KPI filtering and spectrum coordination

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101622903A (zh) * 2007-01-29 2010-01-06 诺基亚公司 提供传统和其他无线网络子系统之间互操作性的设备、方法和计算机程序产品
CN101068432A (zh) * 2007-04-18 2007-11-07 中兴通讯股份有限公司 一种为mbms业务统一分配资源的装置、系统和方法
CN103392376A (zh) * 2011-02-14 2013-11-13 瑞典爱立信有限公司 无线网络控制器和无线网络控制器组件

Also Published As

Publication number Publication date
EP3089547A1 (en) 2016-11-02
US20160323793A1 (en) 2016-11-03
CN104754667B (zh) 2019-09-13
EP3089547B1 (en) 2020-05-27
ES2812573T3 (es) 2021-03-17
US9967790B2 (en) 2018-05-08
EP3089547A4 (en) 2016-11-02
CN104754667A (zh) 2015-07-01

Similar Documents

Publication Publication Date Title
CN109151924B (zh) 通信方法及接入网设备、核心网设备
JP5273223B2 (ja) 移動通信システム及びその通信方法並びに無線基地局装置
EP3675579B1 (en) Data scheduling methods, apparatus and computer-readable mediums
US10251208B2 (en) System and method for connection management
JP5185997B2 (ja) 通信ネットワークにおける無線リンク障害を取り扱うための技術
US8954079B2 (en) Mobile communication system and base station identifier management method thereof
JP5910840B2 (ja) ユーザ機器のコンテキストに関連するリソースを解放するための方法およびデバイス
US20100216471A1 (en) Link Layer Control Protocol Implementation
WO2010068154A1 (en) Interface setup for communications network with femtocells
WO2015170931A1 (ko) 무선 접속망 간 이동성을 지원하는 방법 및 장치
JP6174715B2 (ja) ヘテロジニアスネットワークにおけるセキュリティ検出を実現する方法、装置及びシステム
WO2012167547A1 (zh) 基站间的切换方法、基站、和通讯系统
EP2324661B1 (en) Method for user relocation triggered by home nodeb gateway
EP1763265A2 (en) Improved OpenRAN architecture for Radio Network Controller, Mobile Communication System and method of controlling Radio Base Station device
WO2015096413A1 (zh) 一种ue移动性的方法及装置
WO2015042869A1 (zh) 一种终端的切换方法和基站及系统
WO2016167592A1 (en) A method and apparatus for communicating with a wireless local area network in a mobile communcation system
US20230345323A1 (en) Data transmission method and apparatus
JP5643365B2 (ja) 無線通信システム及びユーザプレーン制御装置並びにその通信方法
KR100589953B1 (ko) 비동기 이동통신망으로부터 동기 이동통신망으로의핸드오버 방법
WO2016169220A1 (zh) 一种重定位处理方法、装置及无线网络控制器
WO2010130103A1 (zh) 实现高速分组接入业务本地交换的方法、设备及系统
WO2012034271A1 (zh) 获取无线网络控制器标识的方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14875311

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15108419

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2014875311

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014875311

Country of ref document: EP