WO2013139200A1 - 一种小区切换的寻址方法以及寻址装置 - Google Patents
一种小区切换的寻址方法以及寻址装置 Download PDFInfo
- Publication number
- WO2013139200A1 WO2013139200A1 PCT/CN2013/072089 CN2013072089W WO2013139200A1 WO 2013139200 A1 WO2013139200 A1 WO 2013139200A1 CN 2013072089 W CN2013072089 W CN 2013072089W WO 2013139200 A1 WO2013139200 A1 WO 2013139200A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mobile
- ecgi
- base station
- interface
- mobility anchor
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
Definitions
- the present invention relates to the field of communications technologies, and in particular, to an addressing method for a cell handover and an addressing device. Background technique
- an RN (Relay Node) is introduced to increase network coverage, and the RN is connected to De B (Door evolved Node B) in a wireless manner.
- De B Door evolved Node B
- an important aspect of RN application is the application in high-speed mobile environments such as railways.
- the signal shield can be enhanced in the vehicle body, and the UE can be reduced by group switching (User Equipment, user equipment).
- the number of handovers can also reduce the number of times the UE performs location update.
- the RN deployed in a high-speed mobile environment is generally referred to as a mobile RN.
- FIG. 1 shows a schematic diagram of a network node relationship after the mobile RN and the mobile anchor point are deployed, wherein the connection interface indicated by the thick line indicates The interface associated with the mobile RN, the connection interface labeled by the thin line represents the interface associated with the UE.
- the mobile RN accesses the core network through the donor cell under the DeNB, and has no direct wired interface with the core network.
- Each mobile RN can control one or more cells.
- the interface between the UE and the mobile RN is called the Uu interface
- the interface between the mobile RN and the DeNB is called the Un interface.
- the interface between the DeNB and the mobility anchor is called the S1-C interface.
- the interface between the MME (Mobility Management Entity, Mobility Management Entity) and the RN (the Mobility Management Entity) is called the S5 interface.
- the interface between the mobility anchor and the SGW (Serving Gateway) of the UE is called the S1-U interface.
- the interface between the SGW and the MME of the UE is an S11 interface.
- the mobile RN has the dual identity of the UE and the base station (eNB).
- an EPS (Evolved Packet System) bearer is established between the mobile RN and the network, and has its own control plane management node MME, and a gateway node SGW and a PGW (Packet Data Network Gateway, packet). Data domain gateway) Node;
- the mobile RN acts as an eNB, the mobile RN provides a wireless backhaul link for the accessed UE to manage radio resources.
- the mobility anchor can provide SGW and PGW functionality for the mobile RN and can establish an EPS bearer for the mobile RN.
- the mobility anchor provides the SGW and PGW functions for the mobile RN, it is equivalent to placing the SGW and PGW of the mobile RN in independent nodes (ie, mobile anchor points), thereby preventing the mobile RN from replacing the SGW during the mobile process. And the processing of the PGW.
- the mobile RN when the mobile RN needs to switch to another DeNB, the mobile RN only replaces the serving base station (ie, DeNB), and the MME of the mobile RN establishes an S1-C signaling connection with the target DeNB, and the mobility anchor will The S1-U tunnel of the EPS bearer of the mobile RN is transferred from the source DeNB to the target De B.
- DeNB serving base station
- the mobility anchor can provide proxy functions based on the S1 interface or the X2 interface. Based on this function, for the UE accessing from the mobile RN, in the uplink direction, the mobile RN sends the UE-related signaling to the mobility anchor, and the mobility anchor sends the UE-related signaling to the MME of the UE; In the downlink direction, the MME of the UE sends the S1 signaling to the mobility anchor first, and then sends the mobility anchor to the serving base station (ie, the mobile RN) of the UE.
- the serving base station ie, the mobile RN
- the SGW For the data of the UE, in the uplink direction, the SGW is sent by the mobility anchor to the UE; in the downlink direction, the SGW of the UE sends the data of the UE to the mobility anchor, and then is sent by the mobility anchor to the serving base station of the UE (ie, Mobile RN). Therefore, with respect to the core network device of the UE (such as the MME or the SGW), the function of the mobility anchor is similar to that of the UE. In this case, after the mobile RN switches to a different DeNB, the core network device of the UE cannot perceive The movement of the UE, thereby reducing the impact of the entire handover process on the core network node of the UE.
- the core network device of the UE such as the MME or the SGW
- FIG. 2 is a schematic diagram of another network node relationship after the mobile RN and the mobile anchor point are deployed.
- the difference between FIG. 2 and FIG. 1 is that the UE data is directly sent from the DeNB to the SGW of the UE, instead of being moved by the anchor point.
- the SGW is sent to the UE, thereby reducing the path of data transmission and reducing the burden of data processing of the mobile anchor point.
- the core network of the UE needs to know the mobility of the UE, thereby transferring the data forwarding path to the new De B.
- the DeNB may provide a proxy function based on the S1 or X2 interface for the mobile RN, that is, the mobile RN and the DeNB establish a connection based on the S1 interface or the X2 interface, and the DeNB establishes an S1 interface or X2 with the mobility anchor point.
- the connection of the interface is basically the same as that of Figure 1, for details, please refer to the description for Figure 1.
- an eNB In a communication system, an eNB generally manages multiple cells, and e B needs to determine the cell identity of each cell it manages before serving the UE, that is, determine the cell identity used by each cell on the Uu interface.
- the cell identifier mainly includes a TAI (Tracking Area Identity) and an ECGI (E-UTRAN Cell Global Identity), and an E-UTRAN, Evolved Universal Terrestrial Radio Access Network
- TAI represents a location area to which the cell belongs
- the ECGI generally consists of 28 bits of data, and the first 20 bits of the ECGI are globally unique identifiers of the base stations to which the identified cell belongs, and the remaining The 8 bits are allocated by the base station to which the identified cell belongs, and when allocating the 8-bit data, it is necessary to ensure that the ECGI of each cell is unique.
- the source eNB of the UE When there is a UE that needs to switch to another cell, the source eNB of the UE carries the cell identifier of the target cell in the handover request to the determined target e B.
- the OAM is configured by the OAM, that is, the TAI and the ECGI allocated by the OAM to the eNB are configured to the eNB, where the OAM needs to ensure that the ECGI configured for each cell is different.
- De B may provide an SI interface or an X2 interface proxy function for the UE accessed from the mobile RN. Based on this function, when the DeNB accesses the network, it establishes an S1-C interface-based connection with the MME and establishes a connection with the mobility anchor.
- the DeNB establishes a connection with the mobility anchor.
- the DeNB considers the mobility anchor as the MME. In this case, the DeNB establishes a connection based on the S1-C interface with the mobility anchor. The other is The DeNB regards the mobility anchor as a neighboring base station. In this case, the DeNB establishes an X2 interface-based connection with the mobility anchor.
- FIG. 3 is a schematic diagram showing a signaling interaction process of a cell addressing when a UE is handed over in an existing communication system. As shown in FIG. 3, the interaction process mainly includes the following steps:
- Step 301 When the UE needs to perform the S1 handover, the UE reports a measurement report to the source e B (Source e B );
- Step 302 The source base station of the UE performs a handover decision according to the measurement result in the measurement report reported by the UE, determines a target cell that is suitable for handover, and sends a handover request message (Handover Required) to the source MME of the UE, where the handover request message is Carrying the determined TAI and global base station identity (Global eNB ID) of the target cell;
- Step 303 The source MME finds a target MME according to the TAI of the target cell carried in the handover request message, and sends a Forward Relocation Request to the determined target MME, where the request carries the TAI of the target cell. And the global base station identifier; wherein, the source MME may query the IP address of the MME serving the TAI according to the TAI to the Domain Name System (DNS) server of the target cell, and the result returned by the DNS server may be multiple MMEs, and the source MME One of them can be selected as the target MME;
- DNS Domain Name System
- Step 304 The target MME determines a target base station (Target eNB) according to the target global base station identifier, and sends a handover request (Handover Request) to the target base station, where the handover request carries the TAI of the target cell and the global base station identifier.
- Target eNB target base station
- Handover Request handover request
- Step 305 The target base station obtains the target cell information selected by the source base station from the handover request message, and reserves a resource for the UE, and then returns a handover request acknowledgement message (Handover Request Acknowledge) to the target MME.
- Handover Request Acknowledge a handover request acknowledgement message
- Step 306 The target MME sends a Forward Relocation Response to the source MME.
- Step 307 The source MME sends a handover command (Handover Command) generated by the target base station to the source eNB.
- Step 308 The source eNB sends an RRC link to the UE.
- Reconfiguration message (RRC Connection Reconfiguration);
- Step 309 The UE establishes an RRC connection with the target cell, and returns an RRC Connection Reconfiguration Complete message to the target base station for confirmation;
- Step 310 The target base station sends a handover notification message (Handover Notify) to the target MME.
- Step 311 The target MME updates the location information of the UE, and converts the downlink data transmission path. Finally, the target MME sends a Forward Relocation Complete Notification to the source MME.
- Step 312 The source MME sends a UE Context Release Command to the source eNB to release the UE resources.
- the mobility anchor point is generally deployed between the De B and the MME of the UE (as shown in FIG. 1 or FIG. 2), and the DeNB is no longer directly connected to the MME of the UE, that is, the mobility anchor point.
- the topology relationship between the DeNB and the MME of the UE is shielded, so that when the cell handover is performed, the target MME may not be able to find a suitable mobility anchor, and the mobility anchor may not accurately send the handover-related signaling to the correct one.
- the RN is moved, resulting in low accuracy of addressing during cell handover. Summary of the invention
- the embodiments of the present invention provide an addressing method for a cell handover and an addressing device.
- the technical solution can improve the accuracy of addressing in a cell handover process.
- a method for addressing a cell handover including:
- the mobile anchor receives the handover request message
- a method for addressing a cell handover is further provided, where: the target mobility management entity MME receives a handover request message;
- the target MME determines, according to the global base station identifier of the target cell that is carried in the handover request message, a mobility anchor point corresponding to the global base station identifier, where the mobile base station RN corresponding to the target cell belongs to the global base station Identifying the same global base station identity as the mobile anchor; or
- the target MME determines, according to the tracking area identifier TAI of the target cell carried in the handover request message, a mobility anchor point corresponding to the TAI of the target cell from each mobile anchor point corresponding to the different TAI.
- an apparatus for addressing a cell handover including: a handover request message receiving unit, configured to receive a handover request message;
- a mobile RN determining unit configured to perform an extended universal land based on the target cell carried by the handover request message a line access network cell global identifier ECGI and the determined ECGI corresponding to each mobile relay node RN, determining a mobile RN corresponding to the ECGI of the target cell; or, according to the target cell carried in the handover request message
- the global base station identifier and the acquired global base station identifier corresponding to each mobile RN determine a mobile RN corresponding to the global base station identifier of the target cell.
- a mobility anchor comprising the above-mentioned cell switching addressing device.
- an apparatus for addressing a cell handover including: a handover request message receiving unit, configured to receive a handover request message;
- a mobility anchor determining unit configured to determine, according to a global base station identifier of the target cell that is carried in the handover request message, a mobility anchor point corresponding to the global base station identifier, where the mobile relay node RN to which the target cell belongs Corresponding global base station identifier is the same as the global base station identifier of the mobile anchor point; or, # ⁇ according to the tracking area identifier TAI of the target cell carried in the handover request message, determined from each mobile anchor point corresponding to different TAIs respectively A mobility anchor corresponding to the TAI of the target cell.
- a mobility management entity MME comprising the above-mentioned cell switching addressing device.
- the mobility anchor in the addressing process of the cell handover, that is, after the mobility anchor receives the handover request message, the mobility anchor can be based on the target cell carried by the received handover request message.
- the ECGI determines the mobile RN to be handed over (ie, the target mobile RN), or the mobile anchor determines the target mobile RN to be handed over according to the global base station identity of the target cell carried in the received handover request message, and The handover request message is processed.
- the mobility anchor after the mobility anchor is introduced in the wireless communication system, the mobility anchor can accurately determine the target mobile RN according to the ECGI information or the global base station identification information of the target cell to be handed over, and switch the related signaling. It is sent to the determined target mobile RN, thereby improving the accuracy of addressing during cell handover.
- the target MME in the addressing process of the cell handover, that is, after the target MME receives the handover request message, the target MME can obtain the global base station of the target cell according to the received handover request message. And determining, by the identifier, the mobility anchor point corresponding to the global base station identifier, where the global base station identifier corresponding to the mobile relay node RN to which the target cell belongs is the same as the global base station identifier of the determined mobility anchor point; or, the target MME receives the The TAI of the target cell carried by the handover request message determines a mobility anchor point corresponding to the TAI of the target cell to be handed over from each mobility anchor point corresponding to the different TAI.
- the target MME can accurately determine the target mobility anchor according to the global base station identity or TAI of the target cell to be handed over, and send the handover related signaling to Determine the mobile anchor point, thus The accuracy of addressing during cell handover is high.
- FIG. 1 is a schematic diagram of a network node relationship after a mobile RN and a mobile anchor point are provided by the prior art
- FIG. 2 is another schematic diagram of a relationship between a network node after deploying a mobile RN and a mobile anchor point provided by the background technology
- the schematic diagram of the signaling interaction process of the cell addressing when the UE is switched in the existing communication system is provided.
- FIG. 4 is a schematic flowchart of performing cell configuration and addressing in the specific embodiment 1 according to the second embodiment of the present invention
- FIG. 6 is a schematic flowchart of performing cell configuration and addressing in a specific embodiment 3 according to Embodiment 2 of the present invention
- FIG. 8 is a schematic diagram of a logical structure of a cell switching addressing apparatus according to Embodiment 3 of the present invention
- FIG. 9 is a schematic diagram of a logical structure of a cell switching apparatus according to Embodiment 3 of the present invention
- a further logical structure diagram of the cell switching addressing device provided in Embodiment 3 is provided. detailed description
- an embodiment of the present invention provides a method for addressing a cell handover and an addressing device, and a preferred embodiment of the present invention is described below with reference to the accompanying drawings.
- the preferred embodiments described herein are for illustrative purposes only and are not intended to limit the invention. And in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.
- Embodiment 1 is a diagrammatic representation of Embodiment 1:
- the first embodiment of the present invention provides a cell handover addressing method, which provides a specific implementation process for the process of addressing the mobile RN by the mobile anchor point and the process of addressing the mobile anchor point by the target MME.
- the main principles behind the two implementations are as follows:
- the target MME addresses the mobility anchor, that is, the target MME determines the target mobility anchor point after receiving the handover request message.
- the handover request message carries the cell identity information of the target cell to which the UE is to be handed over, that is, the TAI of the target cell and the global base station identity.
- the determining process of the target MME for UE handover is an existing process, and is not described in detail herein.
- the target MME determines a mobility anchor point for performing subsequent processing on the handover request message, mainly by Two ways:
- the target MME After receiving the handover request message, the target MME obtains the global base station identifier of the target cell carried in the handover request message from the received handover request message, and determines that the mobility anchor corresponding to the global base station identifier is the target mobility anchor. To determine the processing procedure in the mode 1 of the mobile anchor point, the system pre-configures that the global base station identifier corresponding to the mobile RN is the same as the global base station identifier of the mobile anchor point to which the mobile RN belongs. Specifically, the configuration process can be configured by an OAM (Operation and Maintenance) system.
- OAM Operaation and Maintenance
- the target MME After receiving the handover request message, the target MME obtains the TAI of the target cell carried in the handover request message from the received handover request message, and determines, from each mobile anchor point corresponding to the different TAI, the TAI corresponding to the target cell.
- the move anchor is the target move anchor.
- the system will pre-configure different TAIs for different mobile anchor points, that is, the mobile anchor points are different, and the corresponding TAIs are also different.
- the configuration process can be configured by the OAM system.
- the system configures the mobile RN to have the same global base station identifier as the home mobility anchor point, or the system configures each mobile anchor point to correspond to a different TAI, so that the target MME can be based on
- the corresponding information included in the cell identifier carried in the received handover request message determines a mobility anchor that performs subsequent processing on the handover request message, and completes the addressing process of the mobility anchor point.
- the mobile anchor addresses the mobile RN, that is, the mobile anchor determines the mobile RN for subsequent processing of the handover request message after receiving the handover request message.
- the handover request message received by the mobility anchor is sent by the target MME of the UE handover.
- the mobility anchor determines the mobile RN used for subsequent processing of the received handover request message, mainly in two ways:
- the mobile anchor obtains the ECGI of the target cell carried in the handover request message from the received handover request message, and determines the mobility corresponding to the ECGI of the target cell according to the ECGI of the target cell and the ECGI corresponding to each mobile RN.
- the RN is the target mobile RN.
- the mobile anchor point In order to implement the processing in the first method of determining the mobile RN, the mobile anchor point needs to determine the ECGI corresponding to each mobile RN in advance.
- the manner in which the mobility anchor determines the ECGI corresponding to the mobile RN will be described in detail in the following embodiments. It is not described here.
- the mobility anchor obtains the global base station identifier of the target cell and the global base station identifier corresponding to each mobile RN obtained from the received handover request message, and determines that the mobile RN corresponding to the global base station identifier of the target cell is the target mobile RN.
- the mobility anchor needs to obtain the global base station identifier corresponding to each mobile RN in advance.
- the mobile anchor point obtains the global base station identifier corresponding to the mobile RN, and may be reported by the mobile RN or the donor base station of the mobile RN, that is, the mobile anchor point receives the mobile RN or the global base station corresponding to the mobile RN reported by the donor base station of the mobile RN.
- logo the donor base station can update the information of the mobile RN stored in the mobility anchor point after detecting the changed mobile RN, that is, the mobile anchor station receives the report from the donor base station of the mobile RN.
- the global base station identifier corresponding to the changed mobile RN reported by the donor base station after detecting the changed mobile RN may be received, thereby improving each donor base station saved by the mobile anchor point.
- the mobility anchor point can determine the target mobile RN according to the ECGI information of the target cell to be switched or the global base station identifier, and complete the addressing process of the target mobile RN.
- the mobility anchor needs to determine the ECGI corresponding to each mobile RN in advance. Specifically, the manner in which the mobility anchor determines the ECGI corresponding to the mobile RN will be described in detail below.
- two mobile anchor points are provided to determine an implementation manner of the ECGI corresponding to the mobile RN.
- the following two implementation manners are respectively described:
- Mobile anchor point determines the implementation of ECGI corresponding to the mobile RN
- the mobility anchor determines the ECGI corresponding to the mobile RN, that is, the mobility anchor receives the composition information of the ECGI corresponding to the RN reported by the mobile RN.
- the mobile RN may report the composition information of the ECGI based on the S1 interface or the X2 interface between the mobile anchor point, that is, the mobile anchor receives the mobile RN through the S1 interface or the X2 interface.
- the composition information of the ECGI corresponding to the mobile RN may be reported.
- the mobile RN may report the composition information of the ECGI corresponding to the mobile RN after detecting that the UE needs to be handed over, that is, the mobile anchor RN receives the composition information of the ECGI corresponding to the mobile RN reported by the mobile RN after detecting that the managed UE needs to be handed over.
- the composition information of the ECGI may be all the ECGI information.
- the mobile RN directly reports the corresponding ECGI information to the mobility anchor.
- the composition information of the ECGI may also be bit data other than the global base station identifier in the ECGI, where
- the mobile RN reports the bit data other than the global base station identifier in the corresponding ECGI, that is, the last 8 bits in the ECGI, through the reporting of the bit data other than the global base station identifier in the ECGI.
- the amount of reported data can be effectively reduced, thereby achieving the purpose of saving network transmission resources.
- the mobile anchor receives the bit data other than the global base station identifier in the ECGI reported by the mobile RN, the mobility anchor needs to further base the same global base station identifier and the received bit data corresponding to the mobile RN.
- the ECGI corresponding to the mobile RN is determined, that is, the global base station identifier corresponding to the mobile RN corresponding to the mobile RN is combined with the received bit data to obtain an ECGI.
- the mobile RN If the mobile RN reports a complete ECGI, the mobile RN needs to obtain its corresponding ECGL from the OAM system.
- the first implementation manner of determining the ECGI corresponding to the mobile RN by using the mobility anchor point is that the mobile RN actively sends all or part of the message of the corresponding ECGI, so that the mobility anchor point can determine the ECGI corresponding to each mobile RN. It is convenient to address the mobile RN according to the received handover request message.
- the mobile anchor determines the implementation of ECGI corresponding to the mobile RN.
- the mobility anchor determines the ECGI corresponding to the mobile RN, and is mainly allocated by the mobility anchor point, that is, the mobility anchor point determines the corresponding mobile RN according to the same global base station identifier that corresponds to the mobile RN. ECGI.
- the mobile anchor needs to further allocate the determined ECGI to the corresponding mobile RN, specifically, moving the anchor point.
- the determined composition of the ECGI corresponding to the mobile RN may be allocated to the mobile RN through the S1 interface or the X2 interface.
- the response message (SI Setup Response message) and mobility management may be specifically established through S1.
- the entity MME configures an update message (MME Configuration Update message) or a dedicated ECGI allocation message, and allocates the determined composition information of the ECGI corresponding to the mobile RN to the mobile RN.
- the mobility anchor allocates the determined ECGI corresponding to the mobile RN to the mobile RN through the X2 interface
- the response message (X2 Setup Response message) and the base station configuration update message (e B Configuration Update) may be established through X2.
- the message or the dedicated ECGI allocation message, and the determined composition information of the ECGI corresponding to the mobile RN is allocated to the mobile RN.
- the composition information of the ECGI may be all the ECGI information.
- the mobility anchor allocates the determined ECGI corresponding to the mobile RN to the mobile RN through the S1 interface or the X2 interface.
- the composition information that is, the mobility anchor points are allocated to the mobile RN through the S1 interface or the X2 interface, and the mobile RN is determined to be corresponding to the mobile RN. ECGI.
- the composition information of the ECGI may also be bit data other than the global base station identifier in the ECGI.
- the mobility anchor allocates the determined mobile node to the mobile RN through the S1 interface or the X2 interface.
- the composition information of the ECGI that is, the mobility anchor allocates the bit data other than the global base station identifier in the ECGI corresponding to the mobile RN that is determined to the mobile RN through the S1 interface or the X2 interface, and the mobile RN further responds according to itself.
- the same global base station identity and bit data as the mobile anchor point determine the ECGI.
- the second implementation manner of determining the ECGI corresponding to the mobile RN by using the mobility anchor point is that the mobile anchor point allocates the ECGI corresponding to the mobile RN, so that the mobility anchor point can determine the ECGI corresponding to each mobile RN, so as to facilitate the handover request according to the received handover.
- the message addresses the mobile RN.
- Embodiment 2 is a diagrammatic representation of Embodiment 1:
- the second embodiment is directed to the addressing method in the cell handover process provided by the foregoing embodiment 1, and the specific implementation process of the addressing method in several specific application scenarios is given.
- the global base station identifier of the mobile RN is configured to be the same as the global base station identifier of the mobile mobility anchor.
- the MME can address the global base station identifier of the target cell to the unique mobile anchor point.
- the TAI of each mobility anchor is configured differently.
- the MME may address the unique mobility anchor according to the TAI of the target cell.
- the corresponding application scenario of the specific embodiment 1 is based on the case where the S1 interface is directly established between the mobile RN and the mobility anchor, and the mobility anchor is based on the ECGI to address the mobile RN, and the ECGI corresponding to the mobile RN is configured by the OAM.
- FIG. 4 is a schematic flowchart of performing cell configuration and addressing in the specific embodiment 1. Specifically, the method includes the following steps:
- Step 401 After the mobile RN registers with the network, the global base station identifier configured by the operator (specifically through the OAM system) for the mobile RN is equal to the global base station identifier of the home mobility anchor.
- the ECGI corresponding to the mobile RN refers to the ECGI used by the mobile RN on the Uu interface, and the mobile RN can obtain the ECGI used by the mobile terminal on the Uu interface.
- the OAM needs to ensure that the ECGI allocated for each mobile RN is different.
- the mobile RN may send related information (such as an APN (Access Point Name)) of the home mobility anchor to the OAM, thereby facilitating the OGM and the mobile anchor assigned by the OAM to the mobile RN.
- related information such as an APN (Access Point Name)
- APN Access Point Name
- Step 402 An S1 interface is established between the mobile RN and the mobility anchor, and the mobile RN notifies the mobile anchor point of the ECGI used by the Uu interface through the SI interface.
- the mobile RN establishes an X2 interface with the mobility anchor, and the mobile RN Self The ECGI that has been used at the Uu port notifies the mobility anchor through the X2 interface.
- the mobile RN may notify the mobile anchor point of the last 8 bits of its own ECGI, and the mobile anchor point may be based on The same global base station identifier as the mobile RN is combined with the 8-bit data reported by the mobile RN to determine the ECGI of the mobile RN, thereby reducing the amount of data transmitted and saving network transmission resources.
- the mobile RN may notify the mobile anchor point of its own ECGI in the scenario where the UE may be handed over, that is, after detecting that there is a UE handover requirement, report the ECGI of the mobile RN.
- Step 403 When the UE needs to switch to the mobile RN through S1, the handover request message is sent to the target MME, and the target MME addresses the mobile anchor point corresponding to the global base station identifier according to the global base station identifier of the target cell, and The mobility anchor sends a handover request message.
- the handover request message carries the TAI of the target cell to be handed over and the global base station identifier.
- the target MME may be the global base station identifier of the target cell, that is, the first 20 bits of the ECGI.
- the ID is replaced with the locally assigned value, and then the handover request message is mapped to the EPS bearer of the target RN and sent to the target mobile RN.
- Step 405 After the target RN receives the handover request message, the operation returns a handover request confirmation message to the mobility anchor.
- Step 406 The mobility anchor performs the necessary proxy operation on the handover request acknowledgement message, for example, replacing the identifier (eNB UE S 1 AP ID) used by the base station to distinguish the UE based on the S1 interface access in the handover request acknowledgement message with The locally assigned value is then sent to the target MME.
- the follow-up process is the same as the prior art.
- the application scenario corresponding to the specific embodiment 2 is based on the case where the S1 interface is directly established between the mobile RN and the mobility anchor, and the mobility anchor is based on the ECGI to address the mobile RN, and the ECGI corresponding to the mobile RN is configured by the mobility anchor.
- FIG. 5 is a schematic flowchart of performing cell configuration and addressing in the specific embodiment 2. Specifically, the method mainly includes the following steps:
- Step 501 After the mobile RN registers with the network, the global base station identifier configured for the mobile RN by the operator (specifically through the OAM system) is equal to the global base station identifier of the home mobility anchor.
- Step 502 The mobility anchor allocates the ECGI used by the Uu port to the managed mobile RN.
- the mobile anchor needs to ensure that the ECGI allocated for each mobile RN is different.
- the mobile anchor allocates the ECGI used by the Uu interface (ie, the ECGI corresponding to the mobile RN)
- the mobile anchor can establish an S1 interface with the mobile RN.
- the ECRN is allocated to the mobile RN, more specifically, when the ECGI is allocated to the mobile RN based on the S1 interface, the allocated ECGI list may be carried in the S1 setup response message (SI Setup Response message); or the mobile anchor point passes through the S1.
- the interface update process allocates ECGI to the mobile RN, for example, carrying the assigned ECGI list in the MME configuration update message (MME Configuration Update message), or assigning the ECGI through other dedicated ECGI allocation messages.
- MME Configuration Update message MME Configuration Update message
- the mobility anchor may also allocate an ECGI to the mobile RN when establishing an X2 interface with the mobile RN, and more specifically, when the ECGI is allocated to the mobile RN based on the X2 interface, may be carried in an X2 Setup Response message (X2 Setup Response message).
- X2 Setup Response message X2 Setup Response message
- the assigned ECGI list; or the mobility anchor assigns an ECGI to the mobile RN through the X2 interface update procedure, such as carrying the assigned ECGI list in the base station configuration update message (e B Configuration Update message); or moving the anchor through other dedicated ECGI assigns messages to assign ECGI.
- the mobility anchor may only send the last 8 bits of the ECGI allocated for the mobile RN to the mobile RN to reduce the amount of data transmitted and save network transmission resources.
- Step 503 When the UE needs to switch to the mobile RN through S1, the handover request message is sent to the target MME, and the target MME may address the mobile anchor point corresponding to the global base station identifier according to the global base station identifier of the target cell, and The mobility anchor sends a handover request message.
- the handover request message carries the TAI and the ECGI of the target cell to be handed over.
- Step 504 The mobility anchor resolves the received handover request message, obtains the ECGI of the target cell, determines the target RN corresponding to the ECGI according to the ECGI of the target cell, and performs the necessary proxy operation on the handover request message by the mobility anchor, for example, The MME UE S1AP ID in the handover request message is replaced with the locally assigned value, and then the handover request message is mapped to the EPS bearer of the target RN and sent to the target mobile RN.
- Step 505 The operation after the target RN receives the handover message is the same as the prior art, and returns a handover request acknowledgement message to the mobility anchor.
- Step 506 The mobility anchor performs the necessary proxy operation on the handover request acknowledgement message, for example, replacing the eNB UE S1AP ID in the handover request acknowledgement message with the locally allocated value, and then sending the message to the target MME.
- the follow-up process is the same as the prior art.
- each mobile RN managed by the mobility anchor point allocates an ECGI, so the mobility anchor point knows the ECGI used by each mobile RN managed, and does not need to The mobile RN actively notifies the mobility anchor; in the first embodiment, since the ECGI used by the mobile RN is allocated by the OAM, The mobility anchor may not know the ECGI used by each mobile RN (unless the OAM and the mobility anchor communicate with each other), so the mobile RN is required to actively notify the mobile anchor of the ECGI that it supports.
- the foregoing specific embodiment 1 and the specific embodiment 2 are also applicable to the handover based on the X2 interface.
- the neighboring base station regards the mobile RN cell as the cell of the mobility anchor point, and moves the anchor.
- the point can be obtained by the mobile RN through the X2 interface.
- the main processing flow is basically the same as the above processing flow, and will not be described in detail here.
- the application scenario corresponding to the specific embodiment 3 is based on the case where the S1 interface is directly established between the mobile RN and the mobility anchor, and the target MME addresses the mobility anchor based on the TAI.
- FIG. 6 is a schematic flowchart of performing cell configuration and addressing in the specific embodiment 3. Specifically, the method mainly includes the following steps:
- Step 601 The operator (specifically through the OAM system) configures different TAI lists for each mobility anchor.
- Step 602 An S1-C interface is established between the mobile RN and the mobility anchor, and the mobile RN notifies the mobile anchor point of the TAI and the global base station identifier supported by the mobile RN.
- the global base station identifier corresponding to the mobile RN may be different from the global base station identifier of the mobile anchor point, but the mobility anchor needs to support all TAIs supported by the mobile RNs.
- Step 603 When the UE needs to switch to the mobile RN through S1, the handover request message is sent to the target MME, and the target MME addresses the mobility anchor point corresponding to the TAI according to the TAI of the target cell, and sends a handover to the mobility anchor point. Request message.
- Step 604 After receiving the handover request message, the mobility anchor obtains the global base station identifier of the target cell, and determines a target RN corresponding to the global base station identifier according to the global base station identifier of the target cell, and the mobility anchor performs the handover request message.
- the proxy operation for example, replaces the MME UE S1AP ID in the handover request message with a locally assigned value, and then maps the handover request message to the EPS bearer of the target RN and sends it to the target mobile RN.
- Step 605 The operation after the target RN receives the handover message is the same as the prior art, and returns a handover request acknowledgement message to the mobility anchor.
- Step 606 The mobility anchor performs the necessary proxy operation on the handover request acknowledgement message, for example, replacing the e B UE S1AP ID in the handover request acknowledgement message with a locally allocated value, and then sending the message to the target MME.
- the follow-up process is the same as the prior art.
- the application scenario corresponding to the specific embodiment 4 is based on the situation that the S1 interface is indirectly established between the mobile RN and the mobility anchor, and the target MME addresses the mobility anchor based on the TAI.
- FIG. 7 is a schematic flowchart of performing cell configuration and addressing in the specific embodiment 4. Specifically, the method mainly includes the following steps:
- Step 701 The operator (specifically, the OAM system) configures different TALs for each mobility anchor.
- Each mobility anchor needs to support all TALs supported by each mobile RN.
- Step 702 After the mobile RN switches to a new donor base station (DeNB), the DeNB notifies the mobile base station identity of the mobile RN of the mobile anchor point, that is, the mobility anchor saves the global base station identifier of the mobile RN connected under each DeNB.
- the DeNB notifies the mobile base station identity of the mobile RN of the mobile anchor point, that is, the mobility anchor saves the global base station identifier of the mobile RN connected under each DeNB.
- the mobile RN may establish an S1 interface or an X2 interface with the DeNB to notify De B of its global base station identity.
- the DeNB may notify the mobility anchor point of the global base station identifier of the mobile RN that is currently connected to it through the S1 configuration update process or the X2 configuration update process (including a scenario in which the mobile RN is switched over and the mobile RN is switched out of the DeNB). Specifically, the DeNB may add a global base station identifier carrying the mobile RN in the base station configuration update message (SI AP eNB Configuration Update message) based on the S1 interface or in the base station configuration update message (X2 AP eNB Configuration Update message) based on the X2 interface. IE list.
- SI AP eNB Configuration Update message base station configuration update message
- X2 AP eNB Configuration Update message base station configuration update message
- the DeNB may notify the mobile anchor point of the global eNB identity of the mobile RN in a scenario where the UE may switch to the mobile RN.
- Step 703 When the UE needs to switch to the mobile RN through S1, the handover request message is sent to the target MME, and the target MME addresses the mobility anchor corresponding to the TAI according to the TAI of the target cell, and sends a handover request to the mobility anchor. Message.
- Step 704 After receiving the handover request message, the mobility anchor acquires the global base station identifier of the target cell, determines a DeNB corresponding to the global base station identifier according to the global base station identifier of the target cell, and sends a handover request message to the determined De muscle.
- Step 705 After receiving the handover request message sent by the mobility anchor, the DeNB acquires the global base station identifier of the target cell, determines the target RN according to the global base station identifier of the target cell, and sends the handover request message to the target RN.
- Step 706 The operation after the target RN receives the handover message is the same as the prior art, and returns a handover request acknowledgement message to the DeNB.
- the follow-up process is the same as the prior art.
- the handover related signaling can be correctly routed, thereby avoiding the problem of handover failure and avoiding signaling error routing. Communication security issues.
- Embodiment 3 is a diagrammatic representation of Embodiment 3
- the third embodiment provides a corresponding cell handover addressing device, by which the accuracy of addressing during cell handover can be improved.
- FIG. 8 is a schematic diagram showing a logical structure of the cell switching apparatus provided in the third embodiment. As shown in FIG. 8, the apparatus mainly includes:
- a handover request message receiving unit 801 configured to receive a handover request message
- the mobile RN determining unit 802 is configured to: according to the evolved universal terrestrial radio access network, the cell global identifier ECGI of the target cell carried by the handover request message received by the handover request message receiving unit 801, and the predetermined mobile relay node RN
- the ECGI determines the mobile RN corresponding to the ECGI of the target cell; or, according to the global base station identifier of the target cell carried in the handover request message and the global base station identifier corresponding to each mobile RN obtained in advance, the global destination with the target cell is determined.
- the base station identifies the corresponding mobile RN.
- the mobile RN determining unit 802 included in the apparatus shown in FIG. 8 may specifically include an ECGI determining module (not shown in the figure) for receiving the corresponding mobile RN reported by the mobile RN.
- the foregoing ECGI determining module is specifically configured to receive an ECGI corresponding to the mobile RN reported by the mobile RN; or, the receiving mobile RN reports the ECGI corresponding to the mobile RN, except the global base station identifier.
- the bit data is determined, and the ECGI corresponding to the mobile RN is determined according to the same global base station identifier corresponding to the mobile RN and the bit data of the mobile RN.
- the ECGI determining module is configured to receive the composition information of the ECGI corresponding to the mobile RN reported by the mobile RN through the S1 interface or the X2 interface.
- the mobile RN determining unit 802 included in the apparatus shown in FIG. 8 may further include an ECGI allocation module (not shown in the figure) on the basis of including the ECGI determining module. After determining, by the ECGI determining module, the same global base station identifier as the mobile RN, the ECGI determines the ECGI corresponding to the mobile RN, and then allocates the determined composition information of the ECGI corresponding to the mobile RN to the mobile RN through the S1 interface or the X2 interface.
- the foregoing ECGI allocation module is specifically configured to: when the composition information of the ECGI is allocated through the S1 interface, establish a response message by using the S1, configure an update message by the mobility management entity MME, or Dedicated ECGI allocation message, the mobile RN is allocated the determined composition information of the ECGI corresponding to the mobile RN; when the composition information of the ECGI is allocated through the X2 interface, the X2 establishment response message, the base station configuration update message or the dedicated ECGI allocation message is sent to The mobile RN allocates the determined composition information of the ECGI corresponding to the mobile RN.
- the foregoing ECGI allocation module is specifically configured to allocate, by using an S1 interface or an X2 interface, the determined ECGI corresponding to the mobile RN to the mobile RN; or, through the S1 interface or the X2 interface. And allocating, to the mobile RN, the bit data other than the global base station identifier in the determined ECGI corresponding to the mobile RN, and determining, by the mobile RN, the same global base station identifier and bit data corresponding to the home mobile anchor point that the mobile RN corresponds to. Out of ECGL
- the mobile RN determining unit 802 included in the apparatus shown in FIG. 8 may specifically include a global base station identifier acquiring module (not shown in the figure) for receiving the mobile RN or the mobile RN.
- the global base station identifier acquiring module is further configured to: after receiving the global base station identifier corresponding to the mobile RN reported by the donor base station of the mobile RN, receive the mobile RN that the donor base station detects the management. The global base station identifier corresponding to the changed mobile RN after the change.
- the unit or module included in the cell switching addressing device corresponding to FIG. 8 is only logically divided according to the functions implemented by the device. In actual applications, the superposition or splitting of the above units or modules may be performed.
- the function implemented by the cell switching addressing device provided in the third embodiment corresponds to the corresponding method flows in the first embodiment and the second embodiment, and is specifically implemented in the foregoing embodiment 1 and the second embodiment.
- a more detailed processing flow implemented by the device has been described in detail in the foregoing method embodiments, and will not be described in detail herein.
- the addressing device of the cell handover corresponding to FIG. 8 further has corresponding functional modules that can implement the corresponding steps in the first embodiment and the second embodiment, which are not described herein.
- the addressing means of the cell handover shown in FIG. 8 may be included in the mobility anchor.
- FIG. 9 is a schematic diagram showing a logical structure of an address switching apparatus provided by the third embodiment. As shown in FIG. 9, the apparatus mainly includes:
- a handover request message receiving unit 901 configured to receive a handover request message
- the mobile anchor determining unit 902 is configured to determine, according to the global base station identifier of the target cell carried by the handover request message received by the handover request message receiving unit 901, a mobility anchor corresponding to the identifier of the base station, where the target cell belongs
- the global base station identifier corresponding to the mobile relay node RN is the same as the global base station identifier of the mobile anchor point; or, according to The tracking area identifier TAI of the target cell carried in the handover request message determines a mobility anchor point corresponding to the TAI of the target cell from each mobile anchor point corresponding to the different TAI.
- the unit or module included in the cell switching addressing device corresponding to FIG. 9 is only logically divided according to the functions implemented by the device. In actual applications, the superposition or splitting of the above units or modules may be performed.
- the function implemented by the addressing device of the cell handover provided by the third embodiment corresponds to the corresponding method flows provided by the first embodiment and the second embodiment, and is specifically implemented by the target MME in the first embodiment and the second embodiment.
- a more detailed processing flow implemented by the device has been described in detail in the foregoing method embodiments, and will not be described in detail herein.
- the addressing device of the cell handover corresponding to FIG. 9 further has corresponding functional modules that can implement the corresponding steps performed by the target MME in the first embodiment and the second embodiment, and details are not described herein again.
- the addressing means of the cell handover shown in FIG. 9 may be included in the MME.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention can be embodied in the form of a computer program product embodied on one or more computer-usable storage interfaces (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
- computer-usable storage interfaces including but not limited to disk storage, CD-ROM, optical storage, etc.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种小区切换的寻址方法以及寻址装置,在移动锚点接收切换请求消息后,该移动锚点能够根据接收的切换请求消息携带的目标小区的ECGI确定出要切换到的目标移动RN,或者该移动锚点根据接收的切换请求消息中携带的目标小区的全球基站标识确定出要切换到的目标移动RN。根据该技术方案,移动锚点能够准确地根据要切换到的目标小区的ECGI确定出目标移动RN,并将切换相关的信令发往确定出的移动RN,从而提高了小区切换过程中寻址的准确性。
Description
一种小区切换的寻址方法以及寻址装置
本申请要求在 2012年 3月 21 日提交中国专利局、 申请号为 201210076742.3、 发明名称 为"一种小区切换的寻址方法以及寻址装置"的中国专利申请的优先权, 其全部内容通过引 用结合在本申请中。 技术领域
本发明涉及通信技术领域, 尤其涉及一种小区切换的寻址方法以及寻址装置。 背景技术
在 LTE-A ( Long Term Evolution- Advanced, 长期演进升级 ) 系统, 为了增加网络覆盖 引入了 RN (中继节点), RN以无线的方式与 De B ( Donor evolved Node B , 施主基站) 相连。 目前, RN应用的一个重要方面是应用在铁路等高速移动环境中, 通过在高速移动 环境中部署 RN, 可以增强车体内的信号盾量, 也可以通过群切换来减少 UE ( User Equipment, 用户设备)的切换次数, 还可以减少 UE进行位置更新的次数, 一般将在高速 移动环境中部署的 RN称为移动 RN。
为了更好的支持 RN的移动性, 可以引入一个提供移动锚点功能的节点, 图 1示出了 部署了移动 RN以及移动锚点后的网络节点关系示意图, 其中, 粗线标注的连接接口表示 与移动 RN相关的接口, 细线标注的连接接口表示与 UE相关的接口。 在图 1中, 移动 RN 通过 DeNB下的施主小区 ( donor cell )接入到核心网, 和核心网没有直接的有线接口, 每 个移动 RN可以控制一个或多个小区。 在此架构下, UE和移动 RN之间的接口称为 Uu接 口, 移动 RN和 DeNB之间的接口称为 Un接口, DeNB与移动锚点之间的接口称为 S1-C 接口, 移动锚点与 RN的 MME ( Mobility Management Entity, 移动性管理实体 )之间的接 口称为 S5接口, 移动锚点与 UE的 SGW ( Serving Gateway, 服务网关)之间的接口称为 S1-U接口, UE的 SGW与 UE的 MME之间的接口为 S11接口。在图 1所示的网络节点关 系示意图中, 移动 RN具有 UE和基站(eNB )的双重身份。 当移动 RN作为 UE时, 移动 RN与网络之间建立了 EPS ( Evolved Packet System, 演进的分组系统)承载, 有自己的控 制面管理节点 MME , 以及网关节点 SGW和 PGW ( Packet Data Network Gateway , 分组数 据域网关) 节点; 当移动 RN作为 eNB时, 移动 RN为接入的 UE提供无线回程链路, 管 理无线资源。
在无线通信系统中引入移动锚点后, 能够带来如下优点:
一方面, 移动锚点能够为移动 RN提供 SGW和 PGW功能, 并且能够为移动 RN建立 EPS承载。 在移动锚点为移动 RN提供 SGW和 PGW功能时, 相当于将移动 RN的 SGW 和 PGW放置在独立的节点中 (即移动锚点), 从而避免移动 RN在移动过程中更换 SGW
和 PGW的处理过程。 并且, 引入移动锚点后, 当移动 RN需要切换到另一个 DeNB时, 移动 RN只更换服务基站(即 DeNB ), 该移动 RN的 MME与目标 DeNB建立 S1-C信令 连接, 移动锚点将移动 RN的 EPS承载的 S1-U隧道从源 DeNB转移到目标 De B。
另一方面, 移动锚点能够提供基于 S1接口或 X2接口的代理功能。 基于此功能, 对于 从移动 RN接入的 UE来说, 在上行方向, 移动 RN将 UE相关的信令发到移动锚点, 由移 动锚点将 UE相关的信令发往 UE的 MME; 在下行方向, UE的 MME将 S1信令先发往移 动锚点, 再由移动锚点发往 UE的服务基站(即移动 RN )。 对于 UE的数据, 在上行方向, 由移动锚点发给 UE的 SGW; 在下行方向, UE的 SGW将 UE的数据发给移动锚点, 然后 由移动锚点再发给 UE的服务基站(即移动 RN )。 所以相对于 UE的核心网设备 (如 MME 或 SGW ), 移动锚点的功能类似于 UE的服务基站, 在此情况下, 当移动 RN切换到不同 的 DeNB之后, UE的核心网设备不能感知到 UE的移动, 从而减少了整个切换过程对 UE 的核心网节点的影响。
图 2示出了另一种部署移动 RN以及移动锚点后的网络节点关系示意图, 该图 2与图 1的区别在于: UE数据从 DeNB直接发给 UE的 SGW, 而不是经移动锚点再发给 UE的 SGW, 从而减少了数据传输的路径, 也减少了移动锚点的数据处理的负担。 基于此架构, 当移动 RN切换到不同的 DeNB之后, UE的核心网需要知道 UE的移动,从而将数据转发 路径转移到新的 De B。 在图 2所示的架构中, DeNB可以为移动 RN提供基于 S1或 X2 接口的代理功能, 即移动 RN和 DeNB建立基于 S1接口或 X2接口的连接, DeNB与移动 锚点建立基于 S1接口或 X2接口的连接。 除上述区别外, 图 2的情况与图 1的情况基本相 同, 具体请参见针对图 1的描述。
在通信系统中, 一个 eNB—般管理多个小区, e B为 UE服务前需要确定其管理的每 个小区的小区标识, 即确定每个小区在 Uu接口使用的小区标识。 具体地, 小区标识主要 包括 TAI ( Tracking Area Identity, 跟踪区标识)和 ECGI ( E-UTRAN Cell Global Identity, 演进的通用陆地无线接入网小区全局标识符; E-UTRAN, Evolved Universal Terrestrial Radio Access Network,演进的通用陆地无线接入网),其中, TAI代表该小区所属的位置区; ECGI 一般由 28比特数据组成, ECGI的前 20比特是所标识的小区归属的基站的全球唯一标识, 剩余的 8比特由所标识的小区归属的基站分配, 在分配该 8比特数据时, 需要保证每个小 区的 ECGI唯一。 当有 UE需要切换到另一个小区的时候, 该 UE的源 eNB会将目标小区 的小区标识携带在切换请求中发往确定出的目标 e B。 目前, 主要是由 OAM进行小区标 识配置, 即由 OAM将为 eNB分配的 TAI和 ECGI配置到 eNB, 其中, OAM需要保证为 每个小区配置的 ECGI不同。
De B可以为从移动 RN接入的 UE提供 SI接口或 X2接口代理功能, 基于此功能, 当 DeNB接入网络的时候, 会与 MME建立基于 S1-C接口的连接, 并与移动锚点建立连 接, 其中, DeNB与移动锚点建立连接有两种方式, 一种是 DeNB视移动锚点为 MME, 在此情况下, DeNB与移动锚点建立基于 S1-C接口的连接; 另一种是 DeNB视移动锚点为 邻基站, 在此情况下, DeNB与移动锚点建立基于 X2接口的连接。
在引入移动 RN以及移动锚点的通信系统中, 面临的一个重要的问题是在面临 UE切 换时如何进行小区寻址, 继续沿用现有通信系统中 UE切换时小区寻址的方法显然是不适 用的, 以下结合现有通信系统中 UE切换时小区寻址的信令交互流程进行具体分析:
图 3示出了现有通信系统中 UE切换时小区寻址的信令交互流程的示意图, 如图 3所 示, 该交互过程主要包括如下步骤:
步骤 301、 UE 在需要进行 S1 切换时, 向其源基站 (Source e B ) 上报测量报告 ( Measurement Report );
步骤 302、 UE的源基站根据 UE上报的测量报告中的测量结果进行切换判决, 确定出 适合切换的目标小区, 并向 UE的源 MME发送切换请求消息( Handover Required ),其中, 切换请求消息中携带确定出的目标小区的 TAI和全球基站标识( Global eNB ID );
步骤 303、 源 MME根据切换请求消息携带的目标小区的 TAI找到目标 MME ( Target MME ), 并向确定出的目标 MME发送前转重定位请求( Forward Relocation Request ), 该 请求中携带目标小区的 TAI和全球基站标识; 其中, 源 MME可以根据目标小区的 TAI去 域名系统 (Domain Name System, DNS)服务器查询服务该 TAI的 MME的 IP地址信, DNS 服务器返回的结果可能是多个 MME, 源 MME可以从中选择一个作为目标 MME;
步骤 304、 目标 MME根据目标全球基站标识确定唯一的目标基站( Target eNB ), 并 向该目标基站发送切换请求(Handover Request ), 该切换请求中携带目标小区的 TAI和全 球基站标识;
步骤 305、 目标基站从切换请求消息中获得源基站选择的目标小区信息, 为 UE预留 资源后, 向目标 MME返回切换请求确认消息 ( Handover Request Acknowledge );
步骤 306、 目标 MME向源 MME发送前转重定位响应( Forward Relocation Response ); 步骤 307、 源 MME向源基站发送目标基站生成的切换命令 ( Handover Command ); 步骤 308、源基站向 UE发送 RRC链接重配置消息( RRC Connection Reconfiguration ); 步骤 309、 UE与目标小区建立 RRC连接, 向目标基站返回 RRC连接重配置完成消息 ( RRC Connection Reconfiguration Complete )进行确认;
步骤 310、 目标基站向目标 MME发送切换通知消息 ( Handover Notify );
步骤 311、 目标 MME更新 UE的位置信息, 并转换下行数据传输路径。 最后, 目标 MME向源 MME发送前转重定位完成通知 ( Forward Relocation Complete Notification ); 步骤 312、 源 MME向源 eNB发送 UE资源释放命令 ( UE Context Release Command ), 释放 UE的资源。
至此, 现有通信系统中 UE切换时小区寻址的流程结束。
在通信系统引入移动锚点后, 移动锚点一般会部署在 De B与 UE的 MME之间 (如 图 1或图 2所示), DeNB不再与 UE的 MME直接相连, 也即移动锚点屏蔽了 DeNB与 UE的 MME之间的拓朴关系,从而在进行小区切换时, 目标 MME可能无法找到合适的移 动锚点, 移动锚点也可能无法准确地将切换相关的信令发往正确的移动 RN, 从而导致小 区切换过程中寻址的准确性低。 发明内容
有鉴于此, 本发明实施例提供一种小区切换的寻址方法以及寻址装置, 釆用该技术方 案, 能够提高小区切换过程中寻址的准确性。
本发明实施例通过如下技术方案实现:
根据本发明实施例的一个方面, 提供了一种小区切换的寻址方法, 包括:
移动锚点接收切换请求消息;
所述移动锚点根据所述切换请求消息携带的目标小区的演进的通用陆地无线接入网 小区全局标识符 ECGI以及确定的各移动中继节点 RN对应的 ECGI,确定出与所述目标小 区的 ECGI对应的移动 RN;或才 居所述切换请求消息中携带的目标小区的全球基站标识以 及获取的各移动 RN对应的全球基站标识, 确定出与所述目标小区的全球基站标识对应的 移动 RN。
根据本发明实施例的另一个方面, 还提供了一种小区切换的寻址方法, 包括: 目标移动性管理实体 MME接收切换请求消息;
所述目标 MME根据所述切换请求消息携带的目标小区的全球基站标识, 确定出与所 述全球基站标识对应的移动锚点, 其中, 所述目标小区归属的移动中继节点 RN对应的全 球基站标识与所述移动锚点的全球基站标识相同; 或
所述目标 MME根据所述切换请求消息携带的目标小区的跟踪区标识 TAI, 从分别对 应不同 TAI的各移动锚点中, 确定出与所述目标小区的 TAI对应的移动锚点。
才艮据本发明实施例的另一个方面, 还提供了一种小区切换的寻址装置, 包括: 切换请求消息接收单元, 用于接收切换请求消息;
移动 RN确定单元, 用于根据所述切换请求消息携带的目标小区的演进的通用陆地无
线接入网小区全局标识符 ECGI以及确定的各移动中继节点 RN对应的 ECGI,确定出与所 述目标小区的 ECGI对应的移动 RN;或,根据所述切换请求消息中携带的目标小区的全球 基站标识以及获取的各移动 RN对应的全球基站标识, 确定出与所述目标小区的全球基站 标识对应的移动 RN。
居本发明实施例的另一个方面, 还提供了一种移动锚点, 包括上述的小区切换的寻 址装置。
才艮据本发明实施例的另一个方面, 还提供了一种小区切换的寻址装置, 包括: 切换请求消息接收单元, 用于接收切换请求消息;
移动锚点确定单元, 用于根据所述切换请求消息携带的目标小区的全球基站标识, 确 定出与所述全球基站标识对应的移动锚点, 其中, 所述目标小区归属的移动中继节点 RN 对应的全球基站标识与所述移动锚点的全球基站标识相同; 或, # ^据所述切换请求消息携 带的目标小区的跟踪区标识 TAI, 从分别对应不同 TAI的各移动锚点中, 确定出与所述目 标小区的 TAI对应的移动锚点。
根据本发明实施例的另一个方面, 还提供了一种移动性管理实体 MME, 包括上述的 小区切换的寻址装置。
通过本发明实施例提供的上述至少一个技术方案, 在进行小区切换的寻址过程中, 即 在移动锚点接收切换请求消息后, 该移动锚点能够根据接收的切换请求消息携带的目标小 区的 ECGI确定出与要切换到的移动 RN (即目标移动 RN ), 或者该移动锚点根据接收的 切换请求消息中携带的目标小区的全球基站标识确定出与要切换到的目标移动 RN, 并对 该切换请求消息进行处理。 根据该技术方案, 在无线通信系统中引入移动锚点后, 移动锚 点能够准确地根据要切换到的目标小区的 ECGI信息或全球基站标识信息确定出目标移动 RN, 并将切换相关的信令发往确定出的目标移动 RN, 从而提高了小区切换过程中寻址的 准确性。
通过本发明实施例提供的上述至少一个技术方案, 在进行小区切换的寻址过程中, 即 在目标 MME接收切换请求消息后, 该目标 MME能够根据接收的切换请求消息携带的目 标小区的全球基站标识, 确定出与该全球基站标识对应的移动锚点, 其中, 目标小区归属 的移动中继节点 RN对应的全球基站标识与确定出的移动锚点的全球基站标识相同;或者, 目标 MME根据接收的切换请求消息携带的目标小区的 TAI, 从分别对应不同 TAI的各移 动锚点中, 确定出与要切换到的目标小区的 TAI对应的移动锚点。 根据该技术方案, 在无 线通信系统中引入移动锚点后, 目标 MME能够准确地根据要切换到的目标小区的全球基 站标识或 TAI确定出目标移动锚点, 并将切换相关的信令发往确定出的移动锚点, 从而提
高了小区切换过程中寻址的准确性。
本发明的其它特征和优点将在随后的说明书中阐述, 并且, 部分地从说明书中变得显 而易见, 或者通过实施本发明而了解。 本发明的目的和其他优点可通过在所写的说明书、 权利要求书、 以及附图中所特别指出的结构来实现和获得。 附图说明
附图用来提供对本发明的进一步理解, 并且构成说明书的一部分, 与本发明实施例一 起用于解释本发明, 并不构成对本发明的限制。 在附图中:
图 1为背景技术提供的部署移动 RN以及移动锚点后的网络节点关系的一个示意图; 图 2为背景技术提供的部署移动 RN以及移动锚点后的网络节点关系的又一个示意图; 图 3为背景技术提供的现有通信系统中 UE切换时小区寻址的信令交互流程的示意图; 图 4为本发明实施例二提供的具体实施例 1中进行小区配置与寻址的流程示意图; 图 5为本发明实施例二提供的具体实施例 2中进行小区配置与寻址的流程示意图; 图 6为本发明实施例二提供的具体实施例 3中进行小区配置与寻址的流程示意图; 图 7为本发明实施例二提供的具体实施例 4中进行小区配置与寻址的流程示意图; 图 8为本发明实施例三提供的小区切换的寻址装置的一个逻辑结构示意图; 图 9为本发明实施例三提供的小区切换的寻址装置的又一个逻辑结构示意图。 具体实施方式
为了给出提高小区切换过程中寻址的准确性的实现方案, 本发明实施例提供了一种小 区切换的寻址方法以及寻址装置, 以下结合说明书附图对本发明的优选实施例进行说明, 应当理解, 此处所描述的优选实施例仅用于说明和解释本发明, 并不用于限定本发明。 并 且在不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。
实施例一:
本发明实施例一提供了一种小区切换的寻址方法, 该方法分别针对移动锚点对移动 RN进行寻址的过程以及目标 MME对移动锚点进行寻址的过程给出了具体实现过程, 该 两个实现过程基于的主要原理如下:
一、 目标 MME对移动锚点进行寻址的过程。
目标 MME对移动锚点进行寻址, 即目标 MME在接收到切换请求消息后, 确定目标 移动锚点。 其中, 该切换请求消息中携带 UE要切换到的目标小区的小区标识信息, 即该 目标小区的 TAI以及全球基站标识。 其中, UE切换的目标 MME的确定过程为现有流程, 此处不再详细描述。
具体地, 目标 MME确定用于对该切换请求消息进行后续处理的移动锚点, 主要通过
两种方式:
确定移动锚点的方式一。
目标 MME在接收切换请求消息后, 从接收的切换请求消息中获取该切换请求消息携 带的目标小区的全球基站标识, 并确定出与该全球基站标识对应的移动锚点为目标移动锚 为实现该确定移动锚点的方式一中的处理过程, 系统会预先配置移动 RN对应的全球 基站标识与该移动 RN归属的移动锚点的全球基站标识相同。 具体地, 该配置过程可以由 OAM ( Operation and Maintenance, 操作与维护) 系统进行配置。
确定移动锚点的方式二。
目标 MME在接收切换请求消息后, 从接收的切换请求消息中获取该切换请求消息携 带的目标小区的 TAI, 从分别对应不同 TAI的各移动锚点中, 确定出与该目标小区的 TAI 对应的移动锚点为目标移动锚点。
为实现该确定移动锚点的方式二中的处理过程, 系统会预先为不同的移动锚点配置不 同的 TAI, 即移动锚点不同, 则对应的 TAI也不同。 具体地, 该配置过程可以由 OAM系 统进行配置。
基于上述确定移动锚点的方式一或方式二, 系统会配置移动 RN与归属的移动锚点具 有相同的全球基站标识, 或者, 系统配置各移动锚点分别对应不同的 TAI, 从而目标 MME 能够基于接收的切换请求消息携带的小区标识中包括的相应信息确定出对切换请求消息 进行后续处理的移动锚点, 完成对移动锚点的寻址过程。
二、 移动锚点对移动 RN进行寻址的过程。
移动锚点对移动 RN进行寻址, 即移动锚点在接收到切换请求消息后, 确定用于对该 切换请求消息进行后续处理的移动 RN。其中,移动锚点接收的切换请求消息为 UE切换的 目标 MME发送的。
具体地, 移动锚点确定用于对接收的切换请求消息进行后续处理的移动 RN, 主要通 过两种方式:
确定移动 RN的方式一。
移动锚点从接收的切换请求消息中获取该切换请求消息携带的目标小区的 ECGI, 并 根据目标小区的 ECGI以及预先确定的各移动 RN对应的 ECGI, 确定出与该目标小区的 ECGI对应的移动 RN为目标移动 RN。
为实现该确定移动 RN的方式一中的处理过程, 移动锚点需要预先确定各移动 RN对 应的 ECGI。其中,移动锚点确定移动 RN对应的 ECGI的方式将在后续实施例中详细说明,
此处暂不描述。
确定移动 RN的方式二。
移动锚点从接收的切换请求消息中获取目标小区的全球基站标识以及预先获取的各 移动 RN对应的全球基站标识, 确定出与该目标小区的全球基站标识对应的移动 RN为目 标移动 RN。
为实现该确定移动 RN的方式二中的处理过程, 移动锚点需要预先获取各移动 RN对 应的全球基站标识。 其中, 移动锚点获取移动 RN对应的全球基站标识, 可以由移动 RN 或移动 RN的施主基站上报, 即移动锚点会接收移动 RN或该移动 RN的施主基站上报的 该移动 RN对应的全球基站标识。 并且, 根据本发明实施例一提供的实施方式, 施主基站 能够在检测到管理的移动 RN变化后, 更新移动锚点中保存的移动 RN的信息, 即移动锚 点接收移动 RN的施主基站上报的移动 RN对应的全球基站标识之后, 还可能会接收到该 施主基站在检测到管理的移动 RN变化后上报的变化后的移动 RN对应的全球基站标识, 从而提高移动锚点保存的每个施主基站下连接的移动 RN的全球基站标识的准确性。
基于上述确定移动 RN 的方式一或方式二, 移动锚点能够根据要切换的目标小区的 ECGI信息或全球基站标识, 确定出目标移动 RN, 完成对目标移动 RN的寻址过程。
上述确定移动 RN的方式一中,移动锚点需要预先确定各移动 RN对应的 ECGI,具体 地, 以下对移动锚点确定移动 RN对应的 ECGI的方式进行详细说明。
本实施例一提供了两种移动锚点确定移动 RN对应的 ECGI的实现方式, 以下针对这 两种实现方式分别进行说明:
移动锚点确定移动 RN对应的 ECGI的实现方式一
较佳地, 实现方式一中, 移动锚点确定移动 RN对应的 ECGI, 即移动锚点接收移动 RN上报的 RN对应的 ECGI的组成信息。
较佳地, 移动 RN在上报 ECGI的组成信息时, 可以基于与移动锚点之间的 S 1接口或 X2接口上报, 即移动锚点接收移动 RN通过 S 1接口或 X2接口上 4艮的所述移动 RN对应 的 ECGI的组成信息。
较佳地, 移动 RN可以在检测到 UE需要切换后上报自身对应的 ECGI的组成信息, 即移动锚点接收移动 RN在检测到管理的 UE需要切换后上报的移动 RN对应的 ECGI的组 成信息。
较佳地, 实现方式一中, ECGI的组成信息可以为全部的 ECGI信息, 在此情况下, 移 动 RN是直接向移动锚点上报对应的 ECGI信息。
较佳地, ECGI的组成信息也可以为 ECGI中除全球基站标识之外的比特位数据,在此
情况下, 移动 RN是向移动锚点上报对应的 ECGI中除全球基站标识之外的比特位数据, 也即 ECGI中最后 8比特,通过该上报 ECGI中除全球基站标识之外的比特位数据的方式, 能够有效减少上报的数据量, 从而达到节省网络传输资源的目的。 如果移动锚点接收到的 是移动 RN上报的 ECGI中除全球基站标识之外的比特位数据, 则移动锚点需要进一步根 据自身对应的与移动 RN相同的全球基站标识以及接收的比特位数据 , 确定出该移动 RN 对应的 ECGI,即自身对应的与移动 RN相同的全球基站标识与接收的比特位数据进行组合 得到 ECGI。
其中, 如果移动 RN上报的是完整的 ECGI, 则移动 RN需要从 OAM系统中获取其对 应的 ECGL
通过上述的移动锚点确定移动 RN对应的 ECGI的实现方式一, 主要由移动 RN主动 上 4艮其对应的 ECGI的全部或部分消息, 以便移动锚点能够确定出其各移动 RN分别对应 的 ECGI , 便于根据接收的切换请求消息对移动 RN进行寻址。
移动锚点确定移动 RN对应的 ECGI的实现方式二。
较佳地, 实现方式二中, 移动锚点确定移动 RN对应的 ECGI, 主要由移动锚点进行分 配, 即移动锚点根据自身对应的与移动 RN相同的全球基站标识, 确定出移动 RN对应的 ECGI。
具体地, 移动锚点根据自身对应的与移动 RN相同的全球基站标识, 确定移动 RN对 应的 ECGI之后, 还需要进一步将确定出的 ECGI分别分配给相应的移动 RN, 具体地, 移 动锚点向移动 RN分配 ECGI时, 可以通过 S 1接口或 X2接口, 向移动 RN分配确定出的 与该移动 RN对应的 ECGI的组成信息。
较佳地,当移动锚点通过 S 1接口,向移动 RN分配确定出的与该移动 RN对应的 ECGI 的组成信息时, 具体可以通过 S 1建立响应消息 ( S I Setup Response消息)、 移动性管理实 体 MME配置更新消息( MME Configuration Update消息)或专用 ECGI分配消息, 向该移 动 RN分配确定出的与该移动 RN对应的 ECGI的组成信息。
较佳地,当移动锚点通过 X2接口,向移动 RN分配确定出的与该移动 RN对应的 ECGI 时, 可以通过 X2 建立响应消息 (X2 Setup Response 消息)、 基站配置更新消息 ( e B Configuration Update消息 )或专用 ECGI分配消息, 向该移动 RN分配确定出的与该移动 RN对应的 ECGI的组成信息。
较佳地, 实现方式二中, ECGI的组成信息可以为全部的 ECGI信息, 在此情况下, 移 动锚点通过 S 1接口或 X2接口向移动 RN分配确定出的与该移动 RN对应的 ECGI的组成 信息, 即移动锚点通过 S 1接口或 X2接口向移动 RN分配确定出的与该移动 RN对应的
ECGI。
较佳地, ECGI的组成信息也可以为 ECGI中除全球基站标识之外的比特位数据,在此 情况下, 移动锚点通过 S1接口或 X2接口向移动 RN分配确定出的与该移动 RN对应的 ECGI的组成信息, 即移动锚点通过 S1接口或 X2接口向移动 RN分配确定出的与该移动 RN对应的 ECGI中除全球基站标识之外的比特位数据,由该移动 RN进一步根据自身对应 的与该移动锚点相同的全球基站标识以及比特位数据确定出 ECGI。
通过上述的移动锚点确定移动 RN对应的 ECGI的实现方式二, 主要由移动锚点分配 移动 RN对应的 ECGI, 以便移动锚点能够确定出各移动 RN分别对应的 ECGI, 便于根据 接收的切换请求消息对移动 RN进行寻址。
实施例二:
本实施例二针对上述实施例一提供的小区切换过程中的寻址方法, 给出了几个具体应 用场景下该寻址方法的具体实现过程。
该实施例二提供的应用场景中, 主要基于如下两种预配置:
1、配置移动 RN的全球基站标识与归属的移动锚点的全球基站标识相同,在目标 MME 寻址移动锚点时, MME可以才 居目标小区的全球基站标识寻址到唯一的移动锚点; 或者 2、 配置每个移动锚点的 TAI互不相同, 在目标 MME寻址移动锚点时, MME可以根 据目标小区的 TAI寻址到唯一的移动锚点。
具体实施例 1。
该具体实施例 1对应的应用场景,是基于移动 RN和移动锚点之间直接建立 S1接口的 情况, 且移动锚点基于 ECGI寻址移动 RN, 移动 RN对应的 ECGI由 OAM配置。
图 4示出了该具体实施例 1中进行小区配置与寻址的流程示意图, 具体地, 主要包括 如下步骤:
步骤 401、 移动 RN注册到网络之后, 运营商 (具体可以通过 OAM系统)为移动 RN 配置的全球基站标识等于归属的移动锚点的全球基站标识。
具体地, 移动 RN对应的 ECGI是指移动 RN在 Uu接口使用的 ECGI, 移动 RN可以 从 OAM获取自己在 Uu口使用的 ECGI, OAM需要保证为每个移动 RN分配的 ECGI不同。
较佳地, 移动 RN可以将归属的移动锚点的相关信息 (如 APN ( Access Point Name, 接入点名称))发给 OAM, 从而有助于 OAM为移动 RN分配的 ECGI具备与移动锚点相 同的全球基站标识。
步骤 402、移动 RN与移动锚点之间建立 S1接口,移动 RN将自己在 Uu口使用的 ECGI 通过 SI接口通知移动锚点; 或者, 移动 RN与移动锚点之间建立 X2接口, 移动 RN将自
己在 Uu口使用的 ECGI通过 X2接口通知移动锚点。
较佳地,由于 ECGI—般由 20比特的全球基站标识与 8比特的基站内部分配数据组成, 因此, 移动 RN可以将自己的 ECGI的后面 8比特通知移动锚点即可, 移动锚点可以基于 与移动 RN相同的全球基站标识, 将该全球基站标识与移动 RN上报的 8比特数据组合确 定出移动 RN的 ECGI, 从而减少了传输的数据量, 节省网络传输资源。
较佳地, 移动 RN可以在可能有 UE发生切换的场景才将自己的 ECGI通知移动锚点, 即检测到存在 UE切换需求后上报自己的 ECGI。
步骤 403、UE需要经过 S1切换到移动 RN的时候,切换请求消息被发送到目标 MME, 目标 MME根据目标小区的全球基站标识寻址到与该全球基站标识唯一对应的移动锚点, 并向该移动锚点发送切换请求消息。
其中, 切换请求消息中携带要切换到的目标小区的 TAI以及全球基站标识。
其中, 目标 MME可以才 居目标小区的全球基站标识, 即该 ECGI的前 20比特。 步骤 404、 移动锚点解析收到的切换请求消息, 获得目标小区的 ECGI, 根据目标小区 的 ECGI确定与该 ECGI对应的目标 RN, 移动锚点对切换请求消息进行必要的代理操作 , 例如,将切换请求消息中的用于 MME区分基于 S1接口接入的 UE的标识( MME UE S1AP
ID )替换为本地分配的值, 然后将切换请求消息映射到目标 RN的 EPS承载上, 发给目标 移动 RN。
步骤 405、 目标 RN收到切换请求消息后的操作同现有技术, 向移动锚点返回切换请 求确认消息。
步骤 406、 移动锚点对切换请求确认消息进行必要的代理操作, 例如, 将切换请求确 认消息中的用于基站区分基于 S 1接口接入的 UE的标识( eNB UE S 1 AP ID )替换为本地 分配的值, 然后将该消息发给目标 MME。 后续流程同现有技术。
至此, 该具体实施例 1提供的进行小区配置与寻址的流程结束。
具体实施例 2。
该具体实施例 2对应的应用场景,是基于移动 RN和移动锚点之间直接建立 S1接口的 情况, 且移动锚点基于 ECGI寻址移动 RN, 移动 RN对应的 ECGI由移动锚点配置。
图 5示出了该具体实施例 2中进行小区配置与寻址的流程示意图, 具体地, 主要包括 如下步骤:
步骤 501、 移动 RN注册到网络之后, 运营商 (具体可以通过 OAM系统)为移动 RN 配置的全球基站标识等于归属的移动锚点的全球基站标识。
步骤 502、 移动锚点为管理的移动 RN分配在 Uu口使用的 ECGI。
其中, 移动锚点需要保证为每个移动 RN分配的 ECGI不同, 移动锚点为移动 RN分 配在 Uu口使用的 ECGI (即该移动 RN对应的 ECGI )时, 可以在与移动 RN建立 S 1接口 的时候, 为移动 RN分配 ECGI, 更具体地, 在基于 S1接口为移动 RN分配 ECGI时, 可 以在 S1建立响应消息( SI Setup Response消息)中携带分配的 ECGI列表; 或是移动锚点 通过 S1 接口更新过程为移动 RN 分配 ECGI , 例如在 MME 配置更新消息 ( MME Configuration Update消息)中携带分配的 ECGI列表; 或是通过其他专用的 ECGI分配消 息来分配 ECGI。
移动锚点还可以在与移动 RN建立 X2接口的时候,为移动 RN分配 ECGI,更具体地, 在基于 X2接口为移动 RN分配 ECGI时, 可以在 X2建立响应消息( X2 Setup Response消 息 )中携带分配的 ECGI列表;或是移动锚点通过 X2接口更新过程为移动 RN分配 ECGI, 比如在基站配置更新消息 ( e B Configuration Update消息 ) 中携带分配的 ECGI列表; 或是移动锚点通过其他专用的 ECGI分配消息来分配 ECGI。
较佳地,移动锚点可以只将为移动 RN分配的 ECGI的后面 8比特发送给移动 RN, 以 减少传输的数据量, 节省网络传输资源。
步骤 503、UE需要经过 S1切换到移动 RN的时候,切换请求消息被发送到目标 MME, 目标 MME可以根据目标小区的全球基站标识寻址到与该全球基站标识唯一对应的移动锚 点, 并向该移动锚点发送切换请求消息。
其中, 切换请求消息中携带要切换到的目标小区的 TAI以及 ECGI。
步骤 504、 移动锚点解析收到的切换请求消息, 获得目标小区的 ECGI, 根据目标小区 的 ECGI确定与该 ECGI对应的目标 RN, 移动锚点对切换请求消息进行必要的代理操作 , 例如, 将切换请求消息中的 MME UE S1AP ID替换为本地分配的值, 然后将切换请求消息 映射到目标 RN的 EPS承载上, 发给目标移动 RN。
步骤 505、 目标 RN收到切换消息后的操作同现有技术, 向移动锚点返回切换请求确 认消息。
步骤 506、 移动锚点对切换请求确认消息进行必要的代理操作, 例如, 将切换请求确 认消息中的 eNB UE S1AP ID替换为本地分配的值, 然后将该消息发给目标 MME。后续流 程同现有技术。
至此, 该具体实施例 2提供的进行小区配置与寻址的流程结束。
上述具体实施例 2与具体实施例 1的区别是, 具体实施例 2中由移动锚点为管理的每 个移动 RN分配 ECGI, 因此移动锚点知道管理的每个移动 RN使用的 ECGI, 不需要移动 RN主动通知移动锚点; 具体实施例 1中, 由于移动 RN使用的 ECGI是由 OAM分配的,
移动锚点可能并不知道每个移动 RN使用的 ECGI(除非 OAM与移动锚点之间互通这些分 配信息), 所以需要移动 RN主动将自己支持的 ECGI通知移动锚点。
上述具体实施例 1和具体实施例 2同样适用于基于 X2接口的切换, 在移动锚点和邻 基站建立了 X2接口的情况下, 邻基站将移动 RN小区视为移动锚点的小区, 移动锚点可 以通过 X2接口获得移动 RN支持的 ECGI, 主要处理流程与上述处理流程基本相同, 此处 不再详细描述。
具体实施例 3。
该具体实施例 3对应的应用场景,是基于移动 RN和移动锚点之间直接建立 S1接口的 情况、 且目标 MME基于 TAI寻址移动锚点。
图 6示出了该具体实施例 3中进行小区配置与寻址的流程示意图, 具体地, 主要包括 如下步骤:
步骤 601、 运营商 (具体可以通过 OAM系统) 为每个移动锚点分别配置不同的 TAI 列表。
步骤 602、 移动 RN和移动锚点之间建立 S1-C接口, 移动 RN将自己支持的 TAI和全 球基站标识通知移动锚点。
其中, 移动 RN对应的全球基站标识可以与移动锚点的全球基站标识不同, 但移动锚 点需要支持管理的各移动 RN支持的所有 TAI。
步骤 603、UE需要经过 S1切换到移动 RN的时候,切换请求消息被发送到目标 MME, 目标 MME根据目标小区的 TAI寻址到与该 TAI对应的移动锚点, 并向该移动锚点发送切 换请求消息。
步骤 604、 移动锚点接收到切换请求消息后, 从中获取目标小区的全球基站标识, 根 据目标小区的全球基站标识确定与该全球基站标识对应的目标 RN, 移动锚点对该切换请 求消息进行必要的代理操作, 例如, 将该切换请求消息中的 MME UE S1AP ID替换为本地 分配的值, 然后将切换请求消息映射到目标 RN的 EPS承载上, 发给目标移动 RN。
步骤 605、 目标 RN收到切换消息后的操作同现有技术, 向移动锚点返回切换请求确 认消息。
步骤 606、 移动锚点对切换请求确认消息进行必要的代理操作, 例如, 将该切换请求 确认消息中的 e B UE S1AP ID替换为本地分配的值, 然后将该消息发给目标 MME。后续 流程同现有技术。
至此, 该具体实施例 3提供的进行小区配置与寻址的流程结束。
具体实施例 4。
该具体实施例 4对应的应用场景,是基于移动 RN和移动锚点之间间接建立 S1接口的 情况、 且目标 MME基于 TAI寻址移动锚点。
图 7示出了该具体实施例 4中进行小区配置与寻址的流程示意图, 具体地, 主要包括 如下步骤:
步骤 701、 运营商 (具体可以为 OAM系统) 为每个移动锚点分别配置不同的 TAL 其中, 每个移动锚点需要支持管理的各移动 RN支持的所有 TAL
步骤 702、 当移动 RN切换到一个新的施主基站(DeNB )之后, DeNB将该移动 RN 的全球基站标识通知移动锚点, 即移动锚点保存每个 DeNB下面连接的移动 RN的全球基 站标识。
具体地, 移动 RN可以与 DeNB建立 S1接口或是 X2接口, 从而将自己的全球基站标 识通知 De B。
具体地, DeNB可以通过 S1配置更新过程或 X2配置更新过程将当前与之相连的移动 RN的全球基站标识通知移动锚点(包括有移动 RN切换过来和有移动 RN切换出该 DeNB 的场景)。具体地, DeNB可以在基于 S1接口的基站配置更新消息( SI AP eNB Configuration Update消息 )或在基于 X2接口的基站配置更新消息 ( X2 AP eNB Configuration Update消 息 ) 中增加一个携带移动 RN的全球基站标识的 IE列表。
较佳地, DeNB可以在可能有 UE切换到移动 RN的场景才将移动 RN的全球基站标识 通知移动锚点。
步骤 703、UE需要经过 S1切换到移动 RN的时候,切换请求消息被发送到目标 MME, 目标 MME根据目标小区的 TAI寻址到与该 TAI对应的移动锚点, 向该移动锚点发送切换 请求消息。
步骤 704、 移动锚点收到切换请求消息后, 获取目标小区的全球基站标识, 根据目标 小区的全球基站标识确定与该全球基站标识对应的 DeNB , 将切换请求消息发给确定出的 De肌
步骤 705、 DeNB 收到移动锚点发来的切换请求消息后, 获取目标小区的全球基站标 识, 根据目标小区的全球基站标识确定目标 RN, 将切换请求消息发给目标 RN。
步骤 706、 目标 RN收到切换消息后的操作同现有技术, 向 DeNB返回切换请求确认 消息。 后续流程同现有技术。
至此, 该具体实施例 4提供的进行小区配置与寻址的流程结束。
通过本发明实施二中的技术方案,在 UE经 S1接口或 X2接口切换到移动 RN的时候, 切换相关信令可以正确路由, 从而避免了切换失败的问题, 以及避免了信令错误路由而导
致的通信安全问题。
实施例三:
对应于上述实施例一以及实施例二提供的小区切换的寻址方法, 本实施例三给出了相 应的小区切换的寻址装置, 通过该装置, 能够提高小区切换时寻址的准确性。
图 8示出了本实施例三提供的小区切换的寻址装置的一个逻辑结构示意图, 如图 8所 示, 该装置主要包括:
切换请求消息接收单元 801以及移动 RN确定单元 802;
其巾:
切换请求消息接收单元 801 , 用于接收切换请求消息;
移动 RN确定单元 802, 用于根据切换请求消息接收单元 801接收的切换请求消息携 带的目标小区的演进的通用陆地无线接入网小区全局标识符 ECGI以及预先确定的各移动 中继节点 RN对应的 ECGI, 确定出与目标小区的 ECGI对应的移动 RN; 或, 才 据切换请 求消息中携带的目标小区的全球基站标识以及预先获取的各移动 RN对应的全球基站标 识, 确定出与目标小区的全球基站标识对应的移动 RN。
本实施例三提供的一个实施方式中, 图 8所示装置包括的移动 RN确定单元 802可以 具体包括一个 ECGI确定模块(未在图中示出), 用于接收移动 RN上报的移动 RN对应的 ECGI的组成信息; 或, 根据自身对应的与移动 RN相同的全球基站标识, 确定移动 RN对 应的 ECGL
本实施例三提供的一个实施方式中, 上述的 ECGI确定模块, 具体用于接收移动 RN 上报的移动 RN对应的 ECGI; 或, 接收移动 RN上报与移动 RN对应的 ECGI中除全球基 站标识之外的比特位数据 ,并根据自身对应的与移动 RN相同的全球基站标识以及移动 RN 上 4艮的比特位数据确定移动 RN对应的 ECGI。
本实施例三提供的一个实施方式中, 上述的 ECGI确定模块, 具体用于接收移动 RN 通过 S 1接口或 X2接口上报的移动 RN对应的 ECGI的组成信息。
本实施例三提供的一个实施方式中, 图 8所示装置包括的移动 RN确定单元 802在包 括 ECGI确定模块的基础上, 还可以进一步包括一个 ECGI分配模块(未在图中示出), 用 于在 ECGI确定模块根据自身对应的与移动 RN相同的全球基站标识, 确定移动 RN对应 的 ECGI之后,通过 S1接口或 X2接口, 向移动 RN分配确定出的与移动 RN对应的 ECGI 的组成信息。
本实施例三提供的一个实施方式中,上述的 ECGI分配模块,具体用于在通过 S1接口 分配 ECGI的组成信息时, 通过 S1建立响应消息、移动性管理实体 MME配置更新消息或
专用 ECGI分配消息, 向移动 RN分配确定出的与移动 RN对应的 ECGI的组成信息;在通 过 X2接口分配 ECGI的组成信息时, 通过 X2建立响应消息、 基站配置更新消息或专用 ECGI分配消息, 向移动 RN分配确定出的与移动 RN对应的 ECGI的组成信息。
本实施例三提供的一个实施方式中,上述的 ECGI分配模块,具体用于通过 S1接口或 X2接口, 向移动 RN分配确定出的与移动 RN对应的 ECGI; 或,通过 S 1接口或 X2接口, 向移动 RN分配确定出的与移动 RN对应的 ECGI中除全球基站标识之外的比特位数据, 由移动 RN根据自身对应的与所归属的移动锚点相同的全球基站标识以及比特位数据确定 出 ECGL
本实施例三提供的一个实施方式中, 图 8所示装置包括的移动 RN确定单元 802可以 具体包括一个全球基站标识获取模块(未在图中示出), 用于接收移动 RN或移动 RN的施 主基站上 4艮的移动 RN对应的全球基站标识。
本实施例三提供的一个实施方式中, 上述的全球基站标识获取模块, 还用于在接收移 动 RN的施主基站上报的移动 RN对应的全球基站标识之后, 接收施主基站在检测到管理 的移动 RN变化后上 4艮的变化后的移动 RN对应的全球基站标识。
应当理解, 图 8对应的小区切换的寻址装置包括的单元或模块仅为根据该装置实现的 功能进行的逻辑划分, 实际应用中, 可以进行上述单元或模块的叠加或拆分。 并且该实施 例三提供的小区切换的寻址装置所实现的功能与上述实施例一以及实施例二提供的相应 方法流程——对应, 具体与上述实施例一以及实施例二中移动锚点执行的流程对应, 对于 该装置所实现的更为详细的处理流程, 在上述方法实施例中已做详细描述, 此处不再详细 描述。
并且, 图 8对应的小区切换的寻址装置还具有能够实现实施例一和实施例二中由移动 锚点完成的相应步骤的对应功能模块, 此处不再赘述。
具体地, 图 8所示的小区切换的寻址装置可以包括在移动锚点中。
图 9示出了本实施例三提供的小区切换的寻址装置的一个逻辑结构示意图, 如图 9所 示, 该装置主要包括:
切换请求消息接收单元 901以及移动锚点确定单元 902;
其巾:
切换请求消息接收单元 901 , 用于接收切换请求消息;
移动锚点确定单元 902, 用于根据切换请求消息接收单元 901接收的切换请求消息携 带的目标小区的全球基站标识, 确定出与全 ί求基站标识对应的移动锚点, 其中, 目标小区 归属的移动中继节点 RN对应的全球基站标识与移动锚点的全球基站标识相同; 或, 根据
切换请求消息携带的目标小区的跟踪区标识 TAI, 从分别对应不同 TAI的各移动锚点中, 确定出与目标小区的 TAI对应的移动锚点。
应当理解, 图 9对应的小区切换的寻址装置包括的单元或模块仅为根据该装置实现的 功能进行的逻辑划分, 实际应用中, 可以进行上述单元或模块的叠加或拆分。 并且该实施 例三提供的小区切换的寻址装置所实现的功能与上述实施例一以及实施例二提供的相应 方法流程——对应, 具体与上述实施例一以及实施例二中目标 MME执行的流程对应, 对 于该装置所实现的更为详细的处理流程, 在上述方法实施例中已做详细描述, 此处不再详 细描述。
并且, 图 9对应的小区切换的寻址装置还具有能够实现实施例一和实施例二中由目标 MME完成的相应步骤的对应功能模块, 此处不再赘述。
具体地, 图 9所示的小区切换的寻址装置可以包括在 MME中。
本领域内的技术人员应明白, 本发明的实施例可提供为方法、 系统、 或计算机程序产 品。 因此, 本发明可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实 施例的形式。 而且, 本发明可釆用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介盾 (包括但不限于磁盘存储器、 CD-ROM、 光学存储器等)上实施的计算机程 序产品的形式。
本发明是参照根据本发明实施例的方法、 设备(系统)、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器 以产生一个机器, 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用 于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中, 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品, 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上, 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理, 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的实施例, 但本领域内的技术人员一旦得知了基本创造性概念 , 则可对这些实施例做出另外的变更和修改。 所以, 所附权利要求意欲解释为包括较佳实施 例以及落入本申请范围的所有变更和修改。
显然, 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和 范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在内。
Claims
1、 一种小区切换的寻址方法, 其特征在于, 包括:
移动锚点接收切换请求消息;
所述移动锚点根据所述切换请求消息携带的目标小区的演进的通用陆地无线接入网 小区全局标识符 ECGI以及确定的各移动中继节点 RN对应的 ECGI,确定出与所述目标小 区的 ECGI对应的移动 RN;或才 居所述切换请求消息中携带的目标小区的全球基站标识以 及获取的各移动 RN对应的全球基站标识, 确定出与所述目标小区的全球基站标识对应的 移动 RN。
2、 如权利要求 1所述的方法, 其特征在于, 所述移动锚点确定移动 RN对应的 ECGI 的方式, 包括:
所述移动锚点接收移动 RN上 4艮的所述移动 RN对应的 ECGI的组成信息; 或 所述移动锚点根据自身对应的与移动 RN相同的全球基站标识, 确定所述移动 RN对 应的 ECGL
3、 如权利要求 2所述的方法, 其特征在于, 所述移动锚点接收移动 RN上报的所述移 动 RN对应的 ECGI的组成信息, 包括:
所述移动锚点接收移动 RN上 4艮的所述移动 RN对应的 ECGI; 或
所述移动锚点接收移动 RN上 4艮与所述移动 RN对应的 ECGI中除全球基站标识之外 的比特位数据 , 并根据自身对应的与所述移动 RN相同的全球基站标识以及所述移动 RN 上报的所述比特位数据确定所述移动 RN对应的 ECGI。
4、 如权利要求 3所述的方法, 其特征在于, 所述移动 RN上报的所述移动 RN对应的
ECGI从操作与维护 OAM系统中获取。
5、 如权利要求 2所述的方法, 其特征在于, 所述移动锚点接收移动 RN上报的所述移 动 RN对应的 ECGI的组成信息, 包括:
所述移动锚点接收移动 RN通过 S1接口或 X2接口上 4艮的所述移动 RN对应的 ECGI 的组成信息。
6、 如权利要求 2所述的方法, 其特征在于, 所述移动锚点根据自身对应的与移动 RN 相同的全球基站标识, 确定所述移动 RN对应的 ECGI之后, 还包括:
所述移动锚点通过 S1接口或 X2接口, 向所述移动 RN分配确定出的与所述移动 RN 对应的 ECGI的组成信息。
7、 如权利要求 6所述的方法, 其特征在于, 所述移动锚点通过 S1接口, 向所述移动
RN分配确定出的与所述移动 RN对应的 ECGI的组成信息, 包括: 所述移动锚点通过 SI建立响应消息、移动性管理实体 MME配置更新消息或专用 ECGI 分配消息, 向所述移动 RN分配确定出的与所述移动 RN对应的 ECGI的组成信息。
8、 如权利要求 6所述的方法, 其特征在于, 所述移动锚点通过 X2接口, 向所述移动 RN分配确定出的与所述移动 RN对应的 ECGI , 包括:
所述移动锚点通过 X2建立响应消息、 基站配置更新消息或专用 ECGI分配消息, 向 所述移动 RN分配确定出的与所述移动 RN对应的 ECGI的组成信息。
9、 如权利要求 6所述的方法, 其特征在于, 所述移动锚点通过 S1接口或 X2接口, 向所述移动 RN分配确定出的与所述移动 RN对应的 ECGI的组成信息, 包括:
所述移动锚点通过 S1接口或 X2接口, 向所述移动 RN分配确定出的与所述移动 RN 对应的 ECGI; 或
所述移动锚点通过 S1接口或 X2接口, 向所述移动 RN分配确定出的与所述移动 RN 对应的 ECGI中除全球基站标识之外的比特位数据 , 由所述移动 RN根据自身对应的与所 述移动锚点相同的全球基站标识以及所述比特位数据确定出 ECGI。
10、 如权利要求 1所述的方法, 其特征在于, 所述移动锚点获取移动 RN对应的全球 基站标识, 包括:
所述移动锚点接收移动 RN或所述移动 RN的施主基站上 4艮的所述移动 RN对应的全 球基站标识。
11、 如权利要求 10所述的方法, 其特征在于, 所述移动锚点接收所述移动 RN的施主 基站上报的所述移动 RN对应的全球基站标识之后 , 还包括:
所述移动锚点接收所述施主基站在检测到管理的移动 RN变化后上报的变化后的移动
RN对应的全球基站标识。
12、 一种小区切换的寻址方法, 其特征在于, 包括:
目标移动性管理实体 MME接收切换请求消息;
所述目标 MME根据所述切换请求消息携带的目标小区的全球基站标识, 确定出与所 述全球基站标识对应的移动锚点, 其中, 所述目标小区归属的移动中继节点 RN对应的全 球基站标识与所述移动锚点的全球基站标识相同; 或
所述目标 MME根据所述切换请求消息携带的目标小区的跟踪区标识 TAI, 从分别对 应不同 TAI的各移动锚点中, 确定出与所述目标小区的 TAI对应的移动锚点。
13、 一种小区切换的寻址装置, 其特征在于, 包括:
切换请求消息接收单元, 用于接收切换请求消息;
移动 RN确定单元, 用于根据所述切换请求消息携带的目标小区的演进的通用陆地无 线接入网小区全局标识符 ECGI以及确定的各移动中继节点 RN对应的 ECGI,确定出与所 述目标小区的 ECGI对应的移动 RN;或,根据所述切换请求消息中携带的目标小区的全球 基站标识以及获取的各移动 RN对应的全球基站标识, 确定出与所述目标小区的全球基站 标识对应的移动 RN。
14、 如权利要求 13所述的装置, 其特征在于, 所述移动 RN确定单元具体包括:
ECGI确定模块,用于接收移动 RN上报的所述移动 RN对应的 ECGI的组成信息;或, 根据自身对应的与移动 RN相同的全球基站标识, 确定所述移动 RN对应的 ECGI。
15、 如权利要求 14所述的装置, 其特征在于, 所述 ECGI确定模块具体用于: 接收移动 RN上 4艮的所述移动 RN对应的 ECGI; 或, 接收移动 RN上 4艮与所述移动 RN对应的 ECGI中除全球基站标识之外的比特位数据, 并根据自身对应的与所述移动 RN 相同的全球基站标识以及所述移动 RN上 4艮的所述比特位数据确定所述移动 RN对应的 ECGI。
16、 如权利要求 14所述的装置, 其特征在于, 所述 ECGI确定模块具体用于: 接收移动 RN通过 S1接口或 X2接口上报的所述移动 RN对应的 ECGI的组成信息。
17、 如权利要求 14所述的装置, 其特征在于, 所述移动 RN确定单元, 还包括:
ECGI分配模块,用于在所述 ECGI确定模块根据自身对应的与移动 RN相同的全球基 站标识, 确定所述移动 RN对应的 ECGI之后, 通过 S 1接口或 X2接口, 向所述移动 RN 分配确定出的与所述移动 RN对应的 ECGI的组成信息。
18、 如权利要求 17所述的装置, 其特征在于, 所述 ECGI分配模块具体用于: 在通过 S1接口分配所述 ECGI的组成信息时, 通过 S1建立响应消息、 移动性管理实 体 MME配置更新消息或专用 ECGI分配消息, 向所述移动 RN分配确定出的与所述移动 RN对应的 ECGI的组成信息; 在通过 X2接口分配所述 ECGI的组成信息时, 通过 X2建 立响应消息、 基站配置更新消息或专用 ECGI分配消息, 向所述移动 RN分配确定出的与 所述移动 RN对应的 ECGI的组成信息。
19、 如权利要求 17所述的装置, 其特征在于, 所述 ECGI分配模块具体用于: 通过 S 1接口或 X2接口, 向所述移动 RN分配确定出的与所述移动 RN对应的 ECGI; 或, 通过 S1接口或 X2接口, 向所述移动 RN分配确定出的与所述移动 RN对应的 ECGI 中除全球基站标识之外的比特位数据 , 由所述移动 RN根据自身对应的与所归属的移动锚 点相同的全球基站标识以及所述比特位数据确定出 ECGI。
20、 如权利要求 13所述的装置, 其特征在于, 所述移动 RN确定单元, 具体包括: 全球基站标识获取模块, 用于接收移动 RN或所述移动 RN的施主基站上报的所述移 动 RN对应的全球基站标识。
21、 如权利要求 20所述的装置, 其特征在于, 所述全球基站标识获取模块还用于: 在接收所述移动 RN的施主基站上报的所述移动 RN对应的全球基站标识之后, 接收 所述施主基站在检测到管理的移动 RN变化后上报的变化后的移动 RN对应的全球基站标 识。
22、 一种移动锚点, 其特征在于, 包括权利要求 13至 21任一项所述的小区切换的寻 址装置。
23、 一种小区切换的寻址装置, 其特征在于, 包括:
切换请求消息接收单元, 用于接收切换请求消息;
移动锚点确定单元, 用于根据所述切换请求消息携带的目标小区的全球基站标识, 确 定出与所述全球基站标识对应的移动锚点, 其中, 所述目标小区归属的移动中继节点 RN 对应的全球基站标识与所述移动锚点的全球基站标识相同; 或, # ^据所述切换请求消息携 带的目标小区的跟踪区标识 TAI, 从分别对应不同 TAI的各移动锚点中, 确定出与所述目 标小区的 TAI对应的移动锚点。
24、 一种移动性管理实体 MME, 其特征在于, 包括权利要求 23所述的小区切换的寻 址装置。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210076742.3A CN103327475B (zh) | 2012-03-21 | 2012-03-21 | 一种小区切换的寻址方法以及寻址装置 |
CN201210076742.3 | 2012-03-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013139200A1 true WO2013139200A1 (zh) | 2013-09-26 |
Family
ID=49195955
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/072089 WO2013139200A1 (zh) | 2012-03-21 | 2013-03-01 | 一种小区切换的寻址方法以及寻址装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN103327475B (zh) |
WO (1) | WO2013139200A1 (zh) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106162732A (zh) * | 2015-04-01 | 2016-11-23 | 中兴通讯股份有限公司 | 用户数据的传输处理方法、装置及系统 |
KR102350842B1 (ko) | 2018-02-11 | 2022-01-12 | 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 | 이동 통신 시스템, 방법 및 장치 |
CN116762403A (zh) * | 2021-01-14 | 2023-09-15 | 华为技术有限公司 | 一种通信方法、装置及系统 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101938734A (zh) * | 2009-06-29 | 2011-01-05 | 华为技术有限公司 | 切换控制方法、装置和通信系统 |
CN102118812A (zh) * | 2009-12-31 | 2011-07-06 | 华为技术有限公司 | 中继网络中的切换方法和系统、中继站、控制基站及基站 |
CN102118809A (zh) * | 2009-12-31 | 2011-07-06 | 华为技术有限公司 | 一种通信系统切换准备方法、中继节点、通信系统 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101578782B (zh) * | 2006-11-14 | 2013-02-27 | 韩国电子通信研究院 | 利用移动中继站的切换方法 |
CN101453765B (zh) * | 2007-12-04 | 2012-07-04 | 华为技术有限公司 | 网络切换的方法、系统及装置 |
US8943174B2 (en) * | 2010-02-19 | 2015-01-27 | Telefonaktiebolaget L M Ericsson (Publ) | Identification of relay nodes in a communication network |
US8620302B2 (en) * | 2010-04-02 | 2013-12-31 | Telefonaktiebolaget Lm Ericsson (Publ) | Configuring relay cell identities in cellular networks |
EP2387279A1 (en) * | 2010-05-11 | 2011-11-16 | Panasonic Corporation | Cell (re)selection in a heterogeneous mobile communication system |
CN102404732B (zh) * | 2010-09-17 | 2014-04-02 | 华为技术有限公司 | 中继系统中用户切换时的安全处理方法及基站 |
-
2012
- 2012-03-21 CN CN201210076742.3A patent/CN103327475B/zh active Active
-
2013
- 2013-03-01 WO PCT/CN2013/072089 patent/WO2013139200A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101938734A (zh) * | 2009-06-29 | 2011-01-05 | 华为技术有限公司 | 切换控制方法、装置和通信系统 |
CN102118812A (zh) * | 2009-12-31 | 2011-07-06 | 华为技术有限公司 | 中继网络中的切换方法和系统、中继站、控制基站及基站 |
CN102118809A (zh) * | 2009-12-31 | 2011-07-06 | 华为技术有限公司 | 一种通信系统切换准备方法、中继节点、通信系统 |
Also Published As
Publication number | Publication date |
---|---|
CN103327475A (zh) | 2013-09-25 |
CN103327475B (zh) | 2017-05-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106162771B (zh) | 一种小小区系统中不同MeNB间切换的方法及设备 | |
WO2019042000A1 (zh) | 实例切换方法及相关装置 | |
US9516561B2 (en) | Method and device for supporting group handover | |
US9445336B2 (en) | Method and device for supporting group handover | |
KR20130041996A (ko) | 기지국 사이의 핸드오버를 관리하기 위한 방법 및 장치 | |
US9326225B2 (en) | Method of providing communication over a mobile communication network | |
WO2014026560A1 (zh) | 一种本地网关地址更新方法及装置 | |
WO2008106880A1 (fr) | Procédés, systèmes de communication sans fil, stations de relais mobiles et stations de base d'entrée de réseau ms | |
TWI506978B (zh) | Support the mobile relay station and fixed relay station coexistence method and the corresponding equipment | |
CN106162774B (zh) | 跨MeNB切换方法、装置及基站 | |
JP6169717B2 (ja) | ローカルipアクセス接続解放方法及びmrn | |
KR101390030B1 (ko) | 통신 시스템 | |
WO2013139200A1 (zh) | 一种小区切换的寻址方法以及寻址装置 | |
WO2014026564A1 (zh) | 一种地址分配方法及宿主基站 | |
WO2014044117A1 (zh) | 一种网关重定位的方法及移动性管理实体 | |
WO2011124135A1 (zh) | 一种切换过程中寻址核心网节点的方法及其装置 | |
CN114079980B (zh) | 一种切换方法及基站设备 | |
WO2011147098A1 (zh) | 一种获取上下文的处理方法及设备 | |
CN102118734B (zh) | 一种可实现无固定锚点切换的Wimax系统及其切换方法 | |
CN103024838B (zh) | 一种支持中继节点服务网关重定位的方法 | |
CN103220735A (zh) | 一种rn移动后的用户平面建立方法 | |
US10993102B2 (en) | Localized routing in mobile networks | |
WO2013107260A1 (zh) | 中继节点移动过程中路由标识的处理方法、装置及系统 | |
CN111226460A (zh) | 小区切换方法及装置 | |
CN105657829A (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: 13763728 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13763728 Country of ref document: EP Kind code of ref document: A1 |