WO2010075652A1 - Procédé et système de redirection - Google Patents

Procédé et système de redirection Download PDF

Info

Publication number
WO2010075652A1
WO2010075652A1 PCT/CN2008/073911 CN2008073911W WO2010075652A1 WO 2010075652 A1 WO2010075652 A1 WO 2010075652A1 CN 2008073911 W CN2008073911 W CN 2008073911W WO 2010075652 A1 WO2010075652 A1 WO 2010075652A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
home base
hnb
redirection
request
Prior art date
Application number
PCT/CN2008/073911
Other languages
English (en)
Chinese (zh)
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 PCT/CN2008/073911 priority Critical patent/WO2010075652A1/fr
Publication of WO2010075652A1 publication Critical patent/WO2010075652A1/fr

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller

Definitions

  • the present invention relates to the field of communications, and in particular, to a redirection method and system.
  • a home base station is a small, low-power base station that can be deployed in indoor places such as homes and offices. Its main function is to provide users with higher service rates and reduce the cost of using high-rate services. Some distributed cellular wireless communication systems have insufficient coverage. It can be seen that the home base station has the advantages of low price, convenient use, low power output, and plug and play.
  • the home base station user is connected to the core network (CN network) through a Home NodeB Access Network (HNB AN).
  • FIG. 1 illustrates a network connection relationship of a home base station. As shown in FIG.
  • the HNB AN includes a Home NodeB (HNB for short) and a Home NodeB Gateway (HNB GW for short), where the HNB GW is used.
  • the security of the home base station is handled, the registration and access control of the home base station are handled, the operation and maintenance management of the home base station is performed, the home base station is configured and controlled according to the operator's requirements, and the data of the CN and the home base station is exchanged, and the core network passes
  • the HNB GW communicates with the HNB. Before the user equipment (User Equipment, UE for short) of the home base station uses the HNB, the access control needs to be performed on the UE.
  • UE User Equipment
  • the access control can be divided into two mechanisms: Access control, this mechanism can be implemented in the HNB GW or HNB, where the mechanism is used for the pre-rel8 version of the access, that is, the UE that does not support the Closed Subscriber Group (CSG); The CSG-based access user is used for access control.
  • This mechanism can be implemented in the CN.
  • the mechanism is used for rel8 or subsequent version access, that is, UE supporting CSG.
  • RANAP Radio Access Network Application Part
  • FIG. 2 depicts the cross-RNC handover process of the macrocellular system in the related art. As shown in FIG. 2, the following processing is mainly included (step 201 to step 215).
  • Step 201 The source radio network controller (RNC) requests the UE to perform handover measurement. After the UE sends the measurement result to the source RNC, the source RNC decides the measurement result, and determines to initiate the handover process.
  • Step 204 Establish an RAB bearer between the target RNC and the CN.
  • Step 205 The target RNC sends a RANAP redirection request acknowledgement message to the CN.
  • Step 206 The CN forwards the redirection command message of the RANAP to the source RNC, and continues the handover process.
  • Step 207 The source RNC sends an RRC message (for example, a physical channel reconfiguration message, etc.) to the UE, and performs a handover procedure on the radio side.
  • Step 208 to step 209 the source RNC sends the SRNC context to the target RNC through the CN.
  • Step 212 The target RNC receives an RRC message (for example, a physical channel reconfiguration message, etc.) sent by the UE.
  • RRC message for example, a physical channel reconfiguration message, etc.
  • Step 213 The target RNC sends a RANAP redirection complete message to the CN.
  • the CN updates the PDP context.
  • Step 215 The resource release and information update process is completed between the source RNC and the CN, and specifically includes: releasing an Iu connection. Since the home base station is mainly used in large and medium-sized enterprises and shopping malls, if the coverage space is large, multiple home base stations need to be arranged consecutively. In order to prove the call quality, the UE often needs to perform handover between the home base stations. In this way, based on the access control mechanism described in FIG.
  • the present invention has been made in view of the problem that the terminal existing in the related art switches between home base stations, resulting in a complicated handover process and a large load on the CN. Therefore, the main object of the present invention is to provide a A redirection method and system to solve the above problem.
  • a redirection method for a terminal to handover from a source home base station to a target home base station, wherein the source home base station and the target home base station belong to the same gateway.
  • the redirection method according to the present invention includes: the gateway receiving the first redirection request from the source home base station, where the first redirection request carries the identifier of the active home base station, the identifier of the terminal, and the identifier of the target home base station;
  • the parameter in the redirection request determines whether the terminal is allowed to access the target home base station; if the determination result is yes, the gateway sends a second redirection request to the target home base station to enable the target home base station to perform handover.
  • the process of determining, by the gateway, whether the terminal is allowed to access the target home base station according to the first redirection request includes: determining, by the gateway, whether the terminal supports the closed user group access according to the identifier of the terminal; The gateway determines, according to the identifier of the source home base station and the identifier of the target home base station, whether the source home base station and the target home base station belong to the same closed subscriber group.
  • the gateway The core network sends an access control request message, where the access control request message carries the identifier of the terminal and the closed user group identifier of the target home base station, and the core network determines according to the list of closed user groups that the terminal is allowed to access. Whether the closed subscriber group to which the target home base station belongs allows the terminal to access, and returns the judgment result to the gateway. In the case that the terminal does not support the closed user group access, the gateway determines, according to the saved terminal list that the target home base station allows access, whether the target home base station allows the terminal to access the target home base station.
  • the process of determining the closed subscriber group identity of the target home base station includes: sending, in the registration process of the target home base station to the gateway, the identifier of the closed subscriber group to which the target home base station belongs, the gateway saves the identifier of the target home base station and Close the correspondence of the user group's identity.
  • the second redirection request includes: an identifier of the source home base station, an identifier of the terminal, and an identifier of the target home base station.
  • the first redirection request includes one of the following: a redirection request of the radio access network application part protocol, an enhanced redirection request of the radio network subsystem application part protocol, a redirection request of the home base station application part protocol, and a wireless connection A redirection request for the user adaptation protocol into the network application part.
  • the structure of the first redirection request is different from the structure of the second redirection request; if the first redirection request is a radio network subsystem Applying the enhanced redirect request of the partial protocol, the structure of the first redirect request is the same as the structure of the second redirect request; if the first redirect request is a redirect request of the partial base station application part of the home base station or a wireless access network application part
  • the user adapts the redirection request of the protocol, and the structure of the first redirection request is the same as or different from the structure of the second redirection request.
  • a redirection system is provided.
  • the redirection system includes: a transceiver module, configured to receive a first redirection request from a source home base station, where the first redirection request carries an identifier of the active home base station, an identifier of the terminal, and a target home base station
  • the determining module is configured to determine, according to the parameter in the redirect request, whether the terminal is allowed to access the target home base station
  • the sending module configured to send the second redirect request to the target home base station, so that the target home base station performs the handover.
  • the determining module includes: a first determining submodule, configured to determine whether the terminal supports closed user group access according to the identifier of the terminal; and a second determining submodule, configured to use, according to the identifier of the source home base station and the target home base station Identifying, determining whether the source home base station and the target home base station belong to the same closed user group; the third sub-determination module is configured to determine whether the closed user group allows the terminal to access the closed user group; and the fourth determining sub-module is configured to determine the target Whether the home base station allows the terminal to access the target home base station; the sub-module is called, and if the judgment result of the second judgment sub-module or the third sub-determination module or the fourth sub-module is YES, the sending module is called.
  • the second redirection request includes: an identifier of the source home base station, an identifier of the terminal, and an identifier of the target home base station. If the first redirection request is a redirection request of the radio access network application part protocol, the structure of the first redirection request is different from the structure of the second redirection request; if the first redirection request is a radio network subsystem Applying the enhanced redirect request of the partial protocol, the structure of the first redirect request is the same as the structure of the second redirect request; if the first redirect request is a home base station With the redirection request of the partial protocol or the redirection request of the user adaptation protocol of the radio access network application part, the structure of the first redirection request is the same as or different from the structure of the second redirection request.
  • the redirection process is performed on multiple home base stations belonging to the gateway in the gateway, and the message interaction is not required through the core network, and the present invention can be simplified compared with the prior art. Orient the processing flow and reduce the load on the core network.
  • the drawings are intended to provide a further understanding of the invention, and are intended to be a part of the description of the invention.
  • 1 is a network connection structure diagram of a home base station according to the related art
  • FIG. 2 is a flow chart of handover across an RNC in a macrocellular system according to the related art
  • FIG. 3 is a schematic diagram of handover between HNBs according to the related art; 4 is a flow chart of a redirection method according to an embodiment of the method of the present invention; FIG. 5 is a detailed process flow diagram of a redirection method according to an embodiment of the method of the present invention; FIG. 6 is an embodiment of the present invention.
  • the HNB GW uses the RANAP message to perform redirection processing on the UE accessed by the pre-rel8 version.
  • FIG. 7 is a diagram of the HNB GW according to the embodiment of the present invention using the RANAP message to re-enter the UE accessed by the rel8 or subsequent versions. Flowchart of the directional processing; FIG.
  • FIG. 8 is a flowchart of the redirection process performed by the HNB GW (or RUA) message to the UE accessed by the pre-rel8 version according to the embodiment of the present invention
  • the HNB GW of the embodiment of the present invention uses a HNBAP (or RUA) message to perform redirection processing on a UE accessed by rel8 or a subsequent version.
  • FIG. 10 is a diagram of a HNB GW using a new HNBAP message pair according to an embodiment of the present invention.
  • HNB GW home base station
  • Figure 12 is a block diagram showing the structure of a redirection system according to an embodiment of the system of the present invention
  • Figure 13 is a block diagram showing a preferred configuration of a redirection system according to an embodiment of the system of the present invention.
  • the main application scenarios of the home base station (HNB) are large and medium-sized enterprises and shopping malls. In order to ensure the quality of user calls, it is necessary to support redirection (handover) processing between HNBs. Moreover, in network planning, for configuration optimization and unified management, HNBs belonging to the same enterprise or shopping mall will try to be assigned to the same CSG group.
  • the present invention provides an improved redirection processing method, which optimizes the redirection processing flow shown in FIG. 2, and the main idea is: performing redirection processing on multiple home base stations belonging to the gateway within the gateway.
  • the interaction of messages through the core network is not required, which can simplify the redirection process and reduce the load on the core network.
  • the switching between HNBs can be divided into two categories.
  • the type 1 is the HNB GW internal handover, that is, the two HNBs that perform the handover belong to the same HNB GW;
  • the type 2 is the handover between the HNB GWs, that is, the two HNBs that perform the handover belong to different HNB GWs.
  • the parameters carried in the first redirection request described in the following include: an identifier of the source home base station, an identifier of the terminal, an identifier of the target home base station, and the second redirect request.
  • the parameters carried in the method include: the identifier of the source home base station, the identifier of the terminal, and the identifier of the target home base station.
  • FIG. 4 is a flowchart of a redirection method for a terminal to switch from a source home base station to a target home base station, where the source home base station and the target home base station belong to the same gateway, and the description is
  • the technical solution of the method embodiment of the present invention is shown and described in the form of steps in FIG. 4, and the steps shown in FIG. 4 may be in a computer system such as a set of computer executable instructions. carried out.
  • the logical order is illustrated in FIG. 4, in some cases, the steps shown or described may be performed in an order different than that herein.
  • the method includes the following steps (step S402 to step S406).
  • Step S402 the gateway receives the first redirection request from the source home base station, where the first redirection request carries the identifier of the active home base station, the identifier of the terminal, and the identifier of the target home base station, and the gateway may be the above The home base station gateway; Step S404, the gateway determines, according to parameters in the redirect request, whether the terminal is allowed to access the target home base station; Step S406, if the determination is yes, the gateway sends the second redirect to the target home base station. Request to make the target home base station switch. Before implementing the embodiment of the present invention, each home base station registers with the gateway.
  • the home base station sends the identifier of the closed subscriber group to the gateway, and the gateway saves the identity of the home base station and the closed user to which the home station belongs. The correspondence between the identifiers of the groups. Moreover, the gateway saves a list of terminals that each home base station is allowed to access.
  • the gateway receives the first redirection request from the source home base station, where the first redirection request carries the identifier of the active home base station, the identifier of the terminal, and the identifier of the target home base station.
  • the gateway is configured. According to the identifier of the terminal, it is determined whether the terminal supports the closed user group access.
  • the gateway determines that the terminal does not support the closed user group access according to the identifier of the terminal, and the gateway allows the connection according to the saved target home base station. Entering the terminal list, determining whether the target home base station allows the terminal to access the target home base station, and if the target home base station allows the terminal to access, that is, the terminal exists on the terminal list allowed by the target home base station, sending to the target home base station a second redirection request, so that the target home base station performs handover. If the target home base station does not allow the terminal to access, that is, the terminal does not exist on the terminal list that the target home base station allows access, the gateway terminates the redirection process. .
  • the gateway determines that the terminal supports the closed user group access according to the identifier of the terminal, and the gateway identifies the identity of the home base station and the identity of the target home base station, and determines whether the source home base station and the target home base station belong to In the same closed subscriber group, if the source home base station and the target home base station belong to the same closed subscriber group, the terminal is allowed to access the target home base station, and a second redirect request is sent to the target home base station to enable the target home base The base station performs handover.
  • the gateway sends an access control request message to the core network, where the access control request message carries the identifier of the terminal and the closed subscriber group to which the target home base station belongs.
  • the core network determines, according to the list of closed user groups that the terminal is allowed to access, the closed user group to which the target home base station belongs (for the sake of clarity, the closed user group is referred to as closed user group 1), whether the terminal is allowed to access And returning the judgment result to the gateway; if the closed user group 1 allows the terminal to access, that is, the terminal exists on the list of terminals allowed to be accessed by the closed user group 1, the gateway sends a second redirect request to the target home base station, In order to make the target home base station perform handover, if the closed user group 1 does not allow the terminal to access, that is, the terminal does not exist on the list of terminals allowed to be accessed by the closed user group 1, the gateway terminates the redirection process.
  • the technical solution provided by the embodiment of the present invention performs redirection processing on multiple home base stations belonging to the gateway in the gateway, and does not need to perform message interaction through the core network.
  • the present invention simplifies The directed processing process reduces the load on the core network.
  • the redirection method between the HNBs is described in detail below with reference to FIG. 5, as shown in FIG. 5, which specifically includes the following processing:
  • Step 501 The source HNB initiates handover by using a measurement decision, and sends a redirection request to the HNB GW.
  • Step 502 The HNB GW determines the handover type of the UE. If the HNB GW performs internal handover, the CN does not need to participate in the handover process control.
  • Step 504. If the HNB GW performs internal handover, the CN needs to be performed. Participate in the switching process control, and at this time, it proceeds to step 503.
  • Step 505 The UE is based on rel8 or subsequent version access (that is, the UE supports CSG access), and the HNB GW determines whether the redirection process needs to interact with the CN (eg, access control, update location area information, etc.), if The result is yes, proceeding to step 506; otherwise, proceeding to step 507.
  • Step 506 the interaction with the CN is completed, and after the interaction with the CN is completed, the process proceeds to the step.
  • Step 507 It is not necessary to interact with the CN (for example, the target HNB and the source HNB are in the same location area do not need to update the location area information, and the same CSG group does not need to perform access control, etc.), and then complete the HNB GW internal handover procedure. , the processing shown in FIG. 4 is performed.
  • Step S508 The UE performs access control based on the pre-rel8 version (that is, the UE does not support CSG access), determines whether it is necessary to interact with the CN (for example, updates the location area information, etc.), and if the judgment result is yes, enters Step 509; otherwise, proceed to step 510.
  • Step 509 the interaction with the CN is completed, and after the interaction with the CN is completed, the process proceeds to the step.
  • Step 510 The UE does not need to interact with the CN, performs access control on the UE on the HNB GW, and continues the HNB GW internal handover procedure, and performs the processing shown in FIG. 4 .
  • Step 511 Complete registration of the UE in the target HNB, and registration of the UE in the source HNB, and the handover is completed. According to the above process, it can be seen that during the handover process between the HNBs completed by the HNB GW, the CN does not need to perform the handover process control, and the load of the CN is reduced. For the pre-rel8 version of the UE access, during the handover process. The access control is performed on the UE, and the registration is performed after the handover is completed.
  • the access control process may be omitted.
  • the HNB GW can complete the redirection process in the following ways: Based on the existing radio access network application, the radio access network application part (RANAP) redirection process is processed, based on RANAP The protocol and the wireless network subsystem apply the enhanced redirection process of the Radio Network Subsystem Application Part (RNSAP), and the home base station application part (HNBAP) is added to the new redirect. Process, based on RANAP user adaptation ten (RANAP User Adaptation, RUA) For the new redirect process.
  • RNSAP Radio Network Subsystem Application Part
  • RUA home base station application part
  • the first redirection request is different from the second redirection request, and the HNB GW needs to reconstruct the parameters in the first redirection request to generate a second redirection request.
  • the RNSAP-based redirection process is performed, the first redirection request is the same as the second redirection request, and the HNB GW needs to forward the first redirection request to the target HNB; in particular, to the HNBAP-based and RANAP-based user adaptation.
  • the structure of the first redirection request and the second redirection request may be the same or different. The embodiments of the present invention are described in detail below with reference to the different protocols used in the redirection process.
  • FIG. 6 and Figure 7 are redirection procedures based on the existing RANAP protocol of the HNB GW.
  • the RANAP message transmission between the HNB and the HNB GW is carried by the message negotiated by the RUA.
  • FIG. 6 illustrates a procedure for the HNB GW to perform a redirection process on a pre-rel8 version (non-CSG, that is, a UE that does not support CSG access in the terminal, where the HNB GW parses the RANAP message in the example.
  • Step 601 source HNB requirement The UE performs handover measurement, and after the UE reports the measurement result, the source
  • the HNB decides on the measurement result and decides to initiate the handover process.
  • Step 602 The source HNB sends a RANAP redirection request message to the home HNB GW, and the HNB GW occupies the HNB information (the HNB GW acquires and saves when the HNB is registered) to determine whether the source HNB and the target HNB belong to the HNB GW. (a), if the target HNB is not attributed to the HNB GW, that is, the source HNB and the target HNB belong to different HNB GWs, then proceeds to step 603a;
  • Step 603b if the target HNB belongs to the HNB GW, that is, the source HNB and the target HNB belong to the same HNB GW, but need to interact with the CN (if the target HNB is different from the source HNB location area identifier, the location area information needs to be updated, etc.) Then, the process proceeds to step 603b; (c), if the target HNB belongs to the HNB GW, that is, the source HNB and the target HNB belong to the same HNB GW, and does not need to interact with the CN, then the process proceeds to step 603c.
  • Step 603a The HNB GW forwards the redirection request message of the RANAP to the CN, and performs a handover process across the HNB GW.
  • step 603b the HNB GW exchanges messages with the CN through the NAS, for example, updating the location area information, etc., and after the message interaction is completed, the process proceeds to step 603c.
  • Step 603c The HNB GW performs access control on the UE according to the list of allowed users corresponding to the target HNB. If the target HNB allows the UE to access, that is, the UE exists on the user list of the access allowed by the target HNB, the H1HNB GW sends a RANAP redirection request message to the target HNB, and performs a handover procedure inside the HNB GW.
  • Step 604 The target HNB establishes an RAB bearer between the HNB GW and the CN.
  • Step 605 The target HNB sends a RANAP redirect confirmation message to the HNB GW.
  • Step 606 The HNB GW sends a RANAP redirect command message to the source HNB, and continues the handover process.
  • Step 607 The source HNB sends an RRC message (for example, a physical channel reconfiguration message, etc.) to the UE, and performs a handover procedure on the radio side.
  • steps 608 to 609 the source HNB sends an SRNC context to the target HNB.
  • the target HNB detects the UE.
  • Step 611 The target HNB sends a RANAP redirection detection message to the HNB GW.
  • Step 612 the target HNB receives an RRC message (e.g., a physical channel reconfiguration message, etc.) from the UE.
  • Step 613 The target HNB sends a RANAP redirection complete message to the HNB GW, and the HNB GW saves the registration information of the UE on the target HNB after receiving the message.
  • Step 614 The HNB GW forwards the RANAP redirect complete message to the CN.
  • Step 615 the CN updates the PDP context.
  • Step 616 The resource release and information update process is performed between the source HNB and the HNB GW, and specifically includes: releasing the Iu connection, and deleting the UE registration information on the source HNB.
  • Step 7 illustrates a procedure for the HNB GW to perform redirection processing on the UE accessed by the rel8 or the subsequent version (supporting the CSG, that is, the terminal supports the CSG access).
  • the HNB GW is used to parse the RANAP message.
  • Step 702 The source HNB sends a RANAP redirection request message to the home HNB GW, and the HNB GW occupies the HNB information (the HNB GW acquires and saves when the HNB is registered) to determine whether the source HNB and the target HNB belong to the HNB GW. If the target HNB does not belong to the HNB GW, that is, the source HNB and the target HNB belong to different HNB GWs, go to step 703a; if the source HNB and the target HNB belong to the same HNB GW, the H HNB GW saves the data.
  • the HNB information is used to determine whether the source HNB and the target HNB belong to the same CSG group and the same location area (the HNB provides the CSG identifier and the location area identifier to the HNB GW for saving when registering), specifically, the following two cases: :
  • the HNB GW needs to interact with the CN.
  • the source HNB and the target HNB belong to different CSG groups and need to perform access control, or the target HNB and the source HNB location area identifier are different, and the location area information needs to be updated.
  • Step 703b The HNB GW forwards the RANAP redirection request message to the CN to perform a handover procedure across the HNB GW.
  • the HNB GW interacts with the CN by using the NAS message, for example, performing access control of the UE on the CSG of the target HNB, or updating the location area information, etc., and the message completion interaction proceeds to step 703c.
  • Step 703c The HNB GW sends a RANAP redirect request message to the target HNB, and performs a handover procedure inside the HNB GW.
  • Step 704 The target HNB establishes an RAB bearer between the HNB GW and the CN.
  • Step 705 The target HNB sends a RANAP redirect confirmation message to the HNB GW.
  • Step 706 The HNB GW sends a RANAP redirect command message to the source HNB, and continues the handover process.
  • Step 707 The source HNB sends an RRC message (for example, a physical channel reconfiguration message, etc.) to the UE, and performs a radio side handover procedure.
  • RRC message for example, a physical channel reconfiguration message, etc.
  • Step 710 The target HNB detects the UE.
  • Step 711 The target HNB sends a RANAP redirection detection message to the HNB GW.
  • the target HNB receives an RRC message (e.g., a physical channel reconfiguration message, etc.) from the UE.
  • Step 713 The target HNB sends a RANAP redirection complete message to the HNB GW, and after receiving the message, the HNB GW saves the UE registration information on the target HNB.
  • Step 714 The HNB GW forwards the RANAP redirection complete message to the CN.
  • Step 715 The CN updates the PDP context.
  • Step 716 The resource release and the information update process are completed between the source HNB and the HNB GW. Specifically, the method includes: releasing the Iu connection, and deleting the UE registration information on the source HNB.
  • 8 and FIG. 9 are enhanced redirection procedures based on the existing RANAP or RNSAP protocol of the HNB GW, where RANAP or RNSAP messaging between the ⁇ and the HNB GW is carried by the message negotiated by the RUA.
  • FIG. 8 illustrates a procedure for the HNB GW to perform redirection processing on a UE that is accessed by a pre-rel8 version (non-CSG, that is, the terminal does not support CSG access). In this example, the HNB GW is used to parse and send the RNSAP or RANAP message.
  • Step 801 The source HNB requests the UE to perform handover measurement, and after the UE reports the measurement result, the source
  • the HNB decides on the measurement result and decides to initiate the handover process.
  • Step 802 The source HNB determines that the HNB GW internal handover is performed according to the neighboring area configuration information or the measurement information, and sends an enhanced redirect request message of the RNSAP to the belonging HNB GW.
  • Step 803 The HNB GW confirms that the HNB GW is internally switched, and performs access control on the accessed UE according to the allowed access user list corresponding to the target HNB, and forwards the enhanced redirection of the RNSAP to the target HNB after the access control is completed. Request message.
  • Step 804 The target HNB sends an enhanced redirect response message of the RNSAP to the HNB GW.
  • Step 805 The HNB GW forwards the enhanced redirect response message of the RNSAP to the source HNB under control.
  • Step 808 The NB GW forwards the enhanced redirect acknowledgement message of the RNSAP to the target HNB.
  • the CN updates the PDP context.
  • Step 813 The CN returns an enhanced redirect completion response message of the RANAP to the HNB GW.
  • Step 814 The resource release and information update process is performed between the source HNB and the HNB GW, and specifically includes: releasing the Iu connection, and deleting the UE registration information on the source HNB.
  • FIG. 9 illustrates a procedure for the HNB GW to perform redirection processing on a UE accessed by a rel8 or a subsequent version (supporting CSG, that is, the terminal supports CSG access). In this example, the HNB GW is used to parse and send RNSAP and RANAP messages.
  • Step 901 The source HNB requests the UE to perform handover measurement.
  • Step 902 The source HNB determines that the HNB GW internal handover is performed according to the neighboring area configuration information or the measurement information, and sends an enhanced redirect request message of the RNSAP to the belonging HNB GW. After that, the HNB GW determines whether it needs to interact with the CN: if it needs to interact with the CN Then, the process proceeds to step 903a. If it is not necessary to interact with the CN, the process proceeds to step 903b. In step 903a, the HNB GW determines that it needs to interact with the CN.
  • Step 903b The HNB GW forwards the enhanced redirect request message of the RNSAP to the target HNB.
  • Step 904 The target HNB sends an enhanced redirect response message of the RNSAP to the HNB GW.
  • Step 905 The HNB GW forwards the enhanced redirect response message of the RNSAP to the source HNB.
  • Step 906 The source HNB sends an RRC physical channel reconfiguration message to the UE.
  • Step 907 After receiving the acknowledgement message of the RLC layer, the source HNB sends an enhanced redirect acknowledgement message of the RNSAP to the HNB GW.
  • Step 908 The NB GW forwards the enhanced redirect acknowledgement message of the RNSAP to the target HNB.
  • Step 909 After completing the L1 layer synchronization with the target HNB, and receiving the RL storage indication message of the NBAP, the UE sends an RRC physical channel reconfiguration message to the target HNB.
  • Step 910 The target HNB sends an enhanced redirection complete request message of the RANAP to the HNB GW, and the HNB GW saves the registration information of the UE on the target HNB after receiving the message.
  • Step 911 The HNB GW forwards the RANAP enhanced redirect complete request message to the CN.
  • the CN updates the PDP context.
  • Step 913 The CN returns an enhanced redirect completion response message of the RANAP to the HNB GW.
  • Step 914 The resource release and information update process is completed between the source HNB and the HNB GW. Specifically, the method includes: releasing the Iu connection, and deleting the UE registration information on the source HNB.
  • FIG. 10 and FIG. 11 are redirection processes based on the HNB GW protocol. The redirection process of the new RUA protocol may also be adopted. The specific implementation method and the following FIG. 10 and FIG.
  • FIG. 10 illustrates a procedure for the HNB GW to perform handover processing on a UE that is accessed by a pre-rel8 version (non-CSG, that is, the terminal does not support CSG access).
  • a manner of adding a HNBAP message between the HNB and the HNB GW is adopted.
  • Step 1001 The source HNB requests the UE to perform handover measurement. After the UE reports the measurement result, the source HNB determines the measurement result, and determines to initiate the handover process.
  • Step 1002 The source HNB sends a HNBAP redirection request message to the HNB GW, and the HNB GW occupies the HNB information (HNB GW acquires and saves when the HNB is registered). It is determined whether the source HNB and the target HNB of the handover belong to the HNB to which the HNB GW belongs. :
  • step 1003a if the target HNB is not attributed to the HNB GW, that is, the source HNB and the target HNB belong to different HNB GWs, then proceeds to step 1003a;
  • step 1003b if the target HNB belongs to the HNB GW, that is, the source HNB and the target HNB belong to the same HNB GW, but need to interact with the CN (if the target HNB is different from the source HNB location area identifier, the location area information needs to be updated, etc.) , then proceeds to step 1003b;
  • step 1003c if the target HNB belongs to the HNB GW, that is, the source HNB and the target HNB belong to the same HNB GW, and does not need to interact with the CN, then go to step 1003c.
  • the HNB GW forwards the RANAP redirection request message to the CN, and performs a handover procedure across the HNB GW.
  • the HNB GW interacts with the CN message through the NAS, for example, updating the location area information, etc., and after the message interaction is completed, the process proceeds to step 1003c.
  • Step 1003c The HNB GW performs access control on the UE according to the list of allowed users corresponding to the target HNB.
  • the H1HNB GW sends a RANAP redirection request message to the target HNB, and performs a handover procedure inside the HNB GW.
  • the target HNB establishes an RAB bearer between the HNB GW and the CN.
  • the target HNB sends a redirect acknowledgement message of the HNBAP to the HNB GW.
  • the HNB GW sends a redirect command message of the HNBAP to the target HNB, and continues the handover process.
  • Step 1007 The source HNB sends an RRC message (for example, a physical channel reconfiguration message, etc.) to the UE, and performs a radio side handover procedure.
  • Steps 1008 through 1009 pass the SRNC context to the target HNB for the source HNB.
  • the target HNB detects the UE.
  • Step 1011 The target HNB sends a redirection detection message of the HNBAP to the HNB GW.
  • Step 1012 The target HNB receives an RRC message (e.g., a physical channel reconfiguration message, etc.) from the UE.
  • Step 1013 The target HNB sends a HNBAP redirect complete message to the HNB GW.
  • the HNB GW After receiving the message, the HNB GW saves the registration information of the UE on the target HNB.
  • Step 1014 The HNB GW forwards the HNBAP redirection complete message to the CN.
  • the CN updates the PDP context.
  • Step 1016 The process of releasing the resource and updating the information between the source HNB and the HNB GW, including: releasing the Iu connection, and deleting the registration information of the UE on the source HNB.
  • FIG. 11 is a flowchart of a process in which the HNB GW performs redirection processing on a UE that is accessed by the NB8 or the subsequent version (supporting the CSG, that is, the terminal supports the CSG access).
  • the HNB GW is used to resolve the HNBAP protocol.
  • Step 1101 The source HNB requests the UE to perform handover measurement. After the UE reports the measurement result, the source HNB determines the measurement result, and determines to initiate the handover process.
  • Step 1102 The source HNB sends a RANAP redirection request message to the home HNB GW, and the HNB GW determines whether the source HNB and the target HNB belong to the HNB GW according to the HNB information (the HNB GW acquires and saves when the HNB is registered).
  • the H HNB GW saves the data.
  • the HNB information is used to determine whether the source HNB and the target HNB belong to the same CSG group and the same location area (the HNB provides its own CSG identifier and location area identifier to the HNB GW for saving when registering), specifically, the following two types.
  • Step 1103c the source of the source HNB and the target HNB belong to the same CSG group and the same location area, etc., then do not need to interact with the CN, go to step 1103c;
  • the HNB GW needs to interact with the CN.
  • the source HNB and the target HNB belong to different CSG groups and need to perform access control, or the target HNB and the source HNB location area identifier are different, and the location area information needs to be updated.
  • Step 1103b The HNB GW forwards the RANAP redirection request message to the CN, and performs a handover process across the HNB GW.
  • step 1103b the HNB GW interacts with the CN by using the NAS message, for example, performing the access control of the UE on the CSG of the target HNB, or updating the location area information, etc., and the message completion interaction proceeds to step 1103c.
  • Step 1103c The HNB GW sends a redirect request message of the HNBAP to the target HNB, and performs a handover process inside the HNB GW.
  • Step 1105 The target HNB sends a redirect acknowledgement message of the HNBAP to the HNB GW.
  • Step 1106 The HNB GW sends a redirect command message of the HNBAP to the target HNB, and continues the handover process.
  • Step 1107 The source HNB sends an RRC message (for example, a physical channel reconfiguration message, etc.) to the UE, and performs a radio side handover procedure.
  • Step 1108 to step 1109 the source HNB delivers the SRNC context to the target HNB.
  • the target HNB detects the UE.
  • Step 1111 The target HNB sends a redirect detection message of the HNBAP to the HNB GW.
  • Step 1112 The target HNB receives an RRC message (eg, a physical channel reconfiguration message, etc.) from the UE.
  • RRC message for example, a physical channel reconfiguration message, etc.
  • Step 1113 The target HNB sends a HNBAP redirect complete message to the HNB GW. After receiving the message, the HNB GW saves the registration information of the UE on the target HNB.
  • Step 1114 The HNB GW forwards the HNBAP redirection complete message to the CN.
  • the CN updates the PDP context.
  • Step 1116 The resource release and the information update process are completed between the source HNB and the HNB GW. Specifically, the method includes: releasing the Iu connection, and deleting the UE registration information on the source HNB.
  • the redirection process between the home base stations is implemented on the home base station gateway, and the home base station handover under the same home base station gateway can be completed within the home base station gateway by the judgment of the home base station gateway; and for the pre-rel8
  • the access of the UE is completed, and the access control of the UE is completed while the handover is being performed.
  • the registration of the UE in the target HNB is performed.
  • the HNB GW determines the source HNB of the handover. If the target HNB belongs to the same CSG group, the access control process can be omitted, the redirection process is simplified, and the load of the core network is reduced.
  • FIG. 12 is a structural block diagram of a redirection system according to an embodiment of the present invention. As shown in FIG. 12, the system includes a transceiver module 10, a judging module 20, and a sending module 30, wherein the transceiver module 10 and the judging module 20 And the sending module 30 can be located on the gateway side.
  • the transceiver module 10 is configured to receive a first redirection request from the source home base station, where the first redirection request carries an identifier of the active home base station, an identifier of the terminal, and an identifier of the target home base station, and the determining module 20 is connected to The transceiver module 10 is configured to determine, according to the parameter in the redirect request, whether the terminal is allowed to access the target home base station, and the sending module 30 is connected to the disconnecting module 20, configured to send a second redirect request to the target home base station to enable the target The home base station performs the handover, where the second redirect request includes: an identifier of the source home base station, an identifier of the terminal, and an identifier of the target home base station.
  • the determination module 20 includes a first judgment.
  • the first determining sub-module 202 is configured to determine whether the terminal supports the closed user group access according to the identifier of the terminal; the second determining sub-module 204 is connected to the first determining sub-module 202, and is configured to use the source home base station And identifying, by the identifier of the target home base station, whether the source home base station and the target home base station belong to the same closed user group; the third sub-determination module 206 is connected to the first determining sub-module 202 And the second determining sub-module 204 is configured to determine whether the closed user group allows the terminal to access the closed user group; the fourth determining sub-module 208 is connected to the first determining sub-module 202, and configured to determine whether the target home base station allows the terminal to access a target home base station; the calling sub-module 210 is connected to the first determining sub-module 202, the second determining sub-module 204, and the third sub-determining module 206, and if the judgment result of the third sub
  • the redirection system provided by the embodiment of the present invention performs redirection processing on multiple home base stations belonging to the gateway in the gateway, and does not need to perform message interaction through the core network. Compared with the prior art, the present invention simplifies. The redirection process reduces the load on the core network.
  • the specific processing procedure of the foregoing system is: First, the first determining sub-module 202 determines whether the terminal supports the closed user group access according to the identifier of the terminal, and if the judgment result of the first determining sub-module 202 is no, the saved target is The fourth basement sub-module 208 determines whether the target home base station allows the terminal to access the target home base station.
  • the target home base station allows the terminal to access the terminal list. That is, the terminal exists on the terminal list that the target home base station allows access, and the calling sub-module 210 calls the sending module 30 to send a second redirection request to the target home base station, so that the target home base station performs handover, if the fourth The judgment result of the determination sub-module 208 is no, that is, the target home base station does not allow the terminal to access, that is, the terminal does not exist on the terminal list that the target home base station allows access, and the gateway terminates the redirection process.
  • the second judging sub-module 204 determines the source home base station and the target according to the identifier of the source home base station and the identifier of the target home base station. Whether the home base station belongs to the same closed subscriber group, if the judgment result of the second judgment sub-module 204 is yes, that is, the source home base station and the target home base station belong to the same closed subscriber group, the terminal is allowed to access the target home base station, and the call is made.
  • the sub-module 210 invokes the sending module 30 to send a second redirection request to the target home base station to cause the target home base station to perform handover. If the second judging sub-module 204 determines that the source home base station and the target home base station do not belong to the same closed subscriber group, the transceiver module 10 sends an access control request message to the third sub-judging module 206 located in the core network, where The control request message carries the identifier of the terminal and the closed subscriber group identifier of the target home base station, and the third sub-judgment module 206 determines the closed subscriber group to which the target home base station belongs according to the list of closed subscriber groups that the terminal is allowed to access.
  • the closed subscriber group is referred to as closed subscriber group 1) Whether the terminal is allowed to access, and the judgment result is returned to the gateway; if the closed subscriber group 1 allows the terminal to access, that is, the terminal exists in the closed On the list of terminals allowed to be accessed by the user group 1, the calling sub-module 210 calls the sending module 30 to send a second redirection request to the target home base station to enable the target home base station to perform handover, if the third sub-judging module 206, that is, the closed user Group 1 does not allow access to the terminal, that is, the terminal does not exist on the list of terminals that the closed user group 1 is allowed to access, and the gateway terminates the redirection process.
  • the present invention only uses the home base station as an example to describe the redirection method in the embodiment of the present invention, but is not limited thereto, and the other base station still uses the redirection method within the protection scope of the present invention, for example, an evolved Other base stations such as home base stations (H eNBs).
  • H eNBs home base stations
  • a plurality of home base stations belonging to the gateway are redirected within the gateway, and the message interaction through the core network is not required.
  • the present invention simplifies the redirection process and reduces the load on the core network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un système de redirection, ledit procédé comprenant les étapes suivantes : une passerelle reçoit la première demande de redirection d'un nœud B domestique source (HNB), l'identifiant du HNB source, l'identifiant du terminal et l'identifiant du HNB cible étant contenus dans la première demande de redirection; selon le paramètre dans la demande de redirection, la passerelle évalue si le terminal est autorisé à accéder au HNB cible; si le résultat de l'évaluation est positif, la passerelle envoie la seconde demande de redirection au HNB cible pour que le HNB cible réalise un transfert intercellulaire. Grâce à l'emploi du schéma technique de l'invention, la procédure de traitement de redirection peut être simplifiée et la charge du réseau d'infrastructure peut être réduite.
PCT/CN2008/073911 2008-12-31 2008-12-31 Procédé et système de redirection WO2010075652A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2008/073911 WO2010075652A1 (fr) 2008-12-31 2008-12-31 Procédé et système de redirection

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2008/073911 WO2010075652A1 (fr) 2008-12-31 2008-12-31 Procédé et système de redirection

Publications (1)

Publication Number Publication Date
WO2010075652A1 true WO2010075652A1 (fr) 2010-07-08

Family

ID=42309760

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073911 WO2010075652A1 (fr) 2008-12-31 2008-12-31 Procédé et système de redirection

Country Status (1)

Country Link
WO (1) WO2010075652A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012089008A1 (fr) * 2010-12-29 2012-07-05 华为技术有限公司 Procédé, dispositif et système pour une commutation de voisinage
CN102892165A (zh) * 2011-07-22 2013-01-23 中兴通讯股份有限公司 一种家庭基站的切换方法及***

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1954623A (zh) * 2004-05-17 2007-04-25 日本电气株式会社 移动通信***及其用于切换到小尺寸无线电基站的方法
CN1997204A (zh) * 2006-01-04 2007-07-11 华为技术有限公司 一种实现小区间切换的方法
US20080132239A1 (en) * 2006-10-31 2008-06-05 Amit Khetawat Method and apparatus to enable hand-in for femtocells
CN101287294A (zh) * 2008-06-11 2008-10-15 中兴通讯股份有限公司 移动管理实体、终端转移方法和***

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1954623A (zh) * 2004-05-17 2007-04-25 日本电气株式会社 移动通信***及其用于切换到小尺寸无线电基站的方法
CN1997204A (zh) * 2006-01-04 2007-07-11 华为技术有限公司 一种实现小区间切换的方法
US20080132239A1 (en) * 2006-10-31 2008-06-05 Amit Khetawat Method and apparatus to enable hand-in for femtocells
CN101287294A (zh) * 2008-06-11 2008-10-15 中兴通讯股份有限公司 移动管理实体、终端转移方法和***

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012089008A1 (fr) * 2010-12-29 2012-07-05 华为技术有限公司 Procédé, dispositif et système pour une commutation de voisinage
CN102892165A (zh) * 2011-07-22 2013-01-23 中兴通讯股份有限公司 一种家庭基站的切换方法及***

Similar Documents

Publication Publication Date Title
US20220159533A1 (en) Communication system
US9007911B2 (en) Method and system for implementing direct interface between access network nodes
JP5492507B2 (ja) 基地局ゲートウェイ、基地局ゲートウェイによる基地局切り替え方法及びデータ処理方法
JP5568567B2 (ja) ハンドオーバ、変換、及びルーティング機能を提供するように構成されたネットワークゲートウェイ
EP2525602B1 (fr) Procédés et dispositif de traitement adaptés pour exécuter un transfert cellulaire à une cellule d'un groupe fermé d'abonnés
RU2547816C2 (ru) Устройства базовой станции, узел управления мобильностью, система, способ и компьютерный программный продукт для информирования базовой сети группы абонентского доступа целевой ячейки в процессе процедуры передачи обслуживания х2
JP2013051670A (ja) ＬＴＥネットワークにおける最適化したｅＮＢ（ＥｖｏｌｖｅｄＮｏｄｅＢ）ハンドオーバ
US8670764B2 (en) Wireless communication systems and methods for processing handover messages thereof and computer program products thereof
EP2465287B1 (fr) Commande d'accès de relocalisation d'équipement utilisateur à passerelle à noeud b de rattachement
JP2008507913A (ja) Ｓｉｐネットワークとセルラ通信システムとの間のハンドオフ
JP5910838B2 (ja) ホーム基地局失敗ｄｌパケット総計
WO2009086787A1 (fr) Procédé et système pour notifier un type de cellule basé sur le système lte
JP2015146654A (ja) 移動元基地局、移動先基地局、移動局、通信方法
US8675499B2 (en) Apparatus and method of user equipment relocation
WO2013020433A1 (fr) Procédé de commande de transfert intercellulaire de réseau, système de communication et dispositif associé
US9848366B2 (en) Method for determining relocation process and method for determining handover process
WO2014177075A1 (fr) Procédé et dispositif d'établissement de connexion, système et support de stockage
JP5670461B2 (ja) 無線通信ルーティング方法及びアクセスポイント基地局
EP2334128B1 (fr) Procédé de désenregistrement, noeud local, passerelle de noeud local
WO2012167648A1 (fr) Procédé, système et dispositif pour effectuer une commande d'accès au support lipa
WO2010075652A1 (fr) Procédé et système de redirection
WO2011038616A1 (fr) Procédé de mise à jour de liste de cellules voisines de station de base nominale, serveur de réseau à organisation automatique et station de base nominale de ce serveur
WO2013183316A1 (fr) Système de communication
WO2012041024A1 (fr) Procédé, système et dispositif d'accès pour mettre en œuvre un contrôle d'accès de terminaux
WO2012155705A1 (fr) Procédé de transfert et station de base permettant le transfert vers un hebn

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: 08879268

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: 08879268

Country of ref document: EP

Kind code of ref document: A1