WO2011124162A1 - 一种对终端进行切换的处理方法、基站和家庭网关 - Google Patents

一种对终端进行切换的处理方法、基站和家庭网关 Download PDF

Info

Publication number
WO2011124162A1
WO2011124162A1 PCT/CN2011/072588 CN2011072588W WO2011124162A1 WO 2011124162 A1 WO2011124162 A1 WO 2011124162A1 CN 2011072588 W CN2011072588 W CN 2011072588W WO 2011124162 A1 WO2011124162 A1 WO 2011124162A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
handover
user equipment
relay station
station
Prior art date
Application number
PCT/CN2011/072588
Other languages
English (en)
French (fr)
Inventor
张亮亮
彭炎
常俊仁
蔺波
李亚娟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2011124162A1 publication Critical patent/WO2011124162A1/zh

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
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • 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/06—Reselecting a communication resource in the serving access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations

Definitions

  • the invention relates to a method for processing a terminal, and a home gateway.
  • the present application claims to be submitted to the Chinese Patent Office on April 9, 2010, the application number is 201010149325.8, and the invention name is "a handover method, a base station and a home gateway". Priority of the application, the entire contents of which are incorporated herein by reference.
  • the present invention relates to the field of communications technologies, and in particular, to a processing method, a base station, and a home gateway for switching a terminal. Background technique
  • LTE-A LTE-Advance, Evolution of LTE
  • Relay technology may be used to improve system capacity and coverage.
  • the eNodeB (Evolved Base Station) and the MME/S-GW (Serving Gateway) interact with each other through the S1 interface, and the S1 interface between the MME and the eNodeB can It is represented as an S 1 -MME interface, and the S 1 interface between the S-GW and the eNodeB can be represented as an S1-U interface, and each eNodeB interacts with an X2 interface, and the air interface of the wireless link between the eNodeB and the UE Interaction.
  • the LTE-A network adds an RN (Relay Node, also called a relay station) to the LTE network architecture, and is set between the eNB (eNodeB, evolved base station, referred to as the base station) and the UE (User Equipment). .
  • the radio link between the UE and the RN is called a Uu air interface, and the radio link between the RN and the eNodeB is called an Un air interface.
  • the air interface between the relay station and its serving base station has an S1 interface and an X2 interface.
  • the relay station serves as a station (base station) for its terminal, it connects to its serving base station through the S1 and X2 interfaces.
  • the RN is equivalent to an eNodeB.
  • the base station transmits UE-dedicated SI and X2 signaling messages between its two side interfaces in order to provide services for the relay station's lower terminals.
  • the interfaces on both sides of the base station one side is the air interface between the base station and the relay station (S 1 and/or X2 interface), and the other side is the interface between the base station and other network nodes (S1 or X2 interface).
  • the base station is aware that the terminal is a terminal that is connected to the relay station.
  • FIG. 1 is a schematic diagram of an LTE-A radio access network, which includes a DeNB (Door eNB, a donor base station), an RN, and three UEs subordinate to the RN, which are labeled as UE1, UE2, and UE3, respectively.
  • the interface between the UE and the RN is the Uu interface; the interface between the RN and the DeNB is the Un interface; the interface between the DeNBs is called the X2 interface; the DeNB and the Mobility Management Entity (MME) or the gateway (GW)
  • MME Mobility Management Entity
  • GW Gateway
  • the interface between the Gateway is the SI interface.
  • Messages transmitted using the X2 interface are called X2 messages, and messages transmitted using the S1 interface are called S1 messages.
  • the service station of the terminal that is, the relay station, performs the same behavior as the base station of the LTE, and switches its terminal. There is an air interface between the relay station and the base station, and the message interaction between the relay station and the core network needs to pass through the base station.
  • the access link of the UE-eNB is changed from the original single-hop to two-hop or multi-hop, and the interface of the RN-eNB is the newly defined Un interface.
  • the specific technical details related to the relay handover are not involved in the LTE-A technology, including the handover decision entity, the handover decision basis, the handover procedure, and the like. If the switching mechanism of the existing LTE is used, that is, the relay station is regarded as an eNB, the entire handover procedure may adopt a handover procedure similar to Inter-eNB (inter-base station), and carry the handover related information on the original S1 or X2 interface on the Un interface. .
  • the LTE system performs the handover process of the terminal through S1 signaling, as shown in FIG. 2 .
  • the downlink data transmission path of the terminal Before the handover, the downlink data transmission path of the terminal first arrives at the source base station (the current serving base station of the terminal) from the gateway, and then the source base station arrives at the terminal.
  • the source base station the current serving base station of the terminal
  • the source base station receives a measurement report (Measure Report) from the user equipment.
  • S22 The source base station performs a handover decision (Handover decision).
  • S23 The source base station sends a handover request (S1AP: Handover Required) to the mobility management entity.
  • S24 The target base station receives a handover request message (S1AP: Handover Request) sent by the mobility management entity.
  • S1AP Handover Request
  • S25 The target base station sends a handover request response message to the mobility management entity (S1AP:
  • S26 The mobility management entity sends a handover command (S1AP: Handover Command) to the source base station.
  • S1AP Handover Command
  • the source base station sends a handover command Handover Command (the message is an R C message) to the user equipment, so that the user equipment switches to the target cell, or sends a radio resource control connection reconfiguration (RRC Connection Reconfiguration) message to the user equipment.
  • a handover command Handover Command the message is an R C message
  • RRC Connection Reconfiguration radio resource control connection reconfiguration
  • S28 The source base station sends a base station state transfer message (S1AP: eNB status transfer) to the MME of the user equipment.
  • S1AP base station state transfer message
  • S29 After receiving the base station state transition message (S1AP: eNB status transfer), the MME sends an MME status transfer message (S1AP: MME status transfer) to the target base station.
  • S1AP base station state transition message
  • the source base station processes the data in the buffer, and transmits the terminal data to the target station, where the target station is the target base station.
  • the data forwarding path is from the source base station to the gateway, and then sent by the gateway to the target base station. At this time, if there is a direct path between the source base station and the target base station, the forwarding path may also be that the source base station directly forwards the data to the target base station.
  • the user equipment After receiving the handover command of the source base station, the user equipment synchronizes with the target cell to access the target cell, and after handover to the target cell, sends a radio resource control connection reconfiguration redundancy to the target base station (RRC Connection Reconfiguration Complete). ) Message (or Handover Command complete message).
  • the target base station sends a handover notification (Handover Notify) to the mobility management entity.
  • the mobility management entity sends a user plane update request to the gateway (User Plane Update) Request ).
  • the gateway may include, but is not limited to, an SGW (Serving Gateway) and a PGW (Packet Data Network Gateway).
  • the downlink data transmission path of the terminal begins to change from the gateway to the target base station and then from the target base station to the terminal.
  • the gateway After completing the path update, the gateway returns a User Plane Update Response to the mobility management entity.
  • S216 The mobility management entity sends a UE Context Release Command to the source base station.
  • S217 The source base station performs resource release.
  • a method for processing handover of a terminal including: determining, by a base station, that a handover target of the user equipment is located in a coverage of the base station;
  • the base station directly performs handover to the user equipment without performing signaling interaction with the core network device.
  • a base station including:
  • a determining unit configured to determine that a handover target of the user equipment is located in a coverage of the base station
  • a release unit configured to perform handover on the user equipment directly without performing signaling interaction with the core network device
  • a processing method for switching a terminal including: The home gateway receives a handover request of the first home base station of the home gateway, where the handover request is used to request to perform handover on the user equipment;
  • the home gateway determines that the user equipment is handed over from the first home base station to the second home base station of the home gateway;
  • the home gateway sends a handover command to the first home base station to instruct the first home base station to perform handover without transmitting a handover request to the core network device.
  • a home gateway including:
  • a receiving unit configured to receive a handover request of the first home base station of the home gateway, where the handover request is used to request to perform handover on the user equipment;
  • a determining unit configured to determine that the user equipment is handed over from the first home base station to a second home base station of the home gateway;
  • a releasing unit configured to send a user equipment context release command to the first home base station without sending a handover notification to the core network device.
  • 1 is a schematic diagram of an LTE-A radio access network
  • FIG. 2 is a schematic flowchart of a handover of a terminal by using S1 signaling in the LTE system in the prior art
  • FIG. 3a is a schematic diagram of a handover method according to an embodiment of the present invention
  • FIG. 3b is a schematic diagram of another switching method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flow chart of a handover method according to an embodiment of the present invention
  • FIG. 5 is a schematic flow chart of another handover method according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of another handover method according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a process for a base station to update an NCC from an MME according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a process for a base station to update an NCC according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a base station according to an embodiment of the present invention
  • FIG. 9 is a schematic diagram of another handover method according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a home gateway according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of another base station according to an embodiment of the present invention. detailed description
  • the air interface between the trunk and the base station is called an Un interface, and the interface can be an S1 interface or an X2 interface.
  • the base station provides SI and X2 proxy (proxy flmctionality) to the relay station between the relay station and other network nodes (e.g., other base stations, MMEs, S-GWs, etc.).
  • This proxy function includes passing UE-dedicated S1 and X2 signaling messages between the two sides of the base station to facilitate servicing the terminals under the relay.
  • the interfaces on both sides of the base station, one side is the air interface between the base station and the relay station (S1 and / or X2 interface), and the other side is the interface between the base station and other network nodes (S1 or X2 interface).
  • the base station From the perspective of the relay, it believes that the information sent by the MME to the MME is directly sent by the MME, and the MME also believes that the information forwarded to it by the eNB is directly sent by the Trunk.
  • the base station has a proxy function. The base station can analyze the message sent by the MME to the RN or the message sent by the RN to the MME, thereby knowing
  • Correction page Terminal information under the relay.
  • S1 message such as a handover request message
  • the S1 message arrives at the MME from the relay station via the base station.
  • the base station Due to the SI proxy function, the base station is aware that the terminal is under the relay station.
  • the base station can modify the ID information of the interface message on both sides.
  • the base station can change the S1 interface ID (eNB UE I IAP ID or MME UE SIAP ID) of the S1 message sent by the MME, and then forward the packet to the RN. vice versa.
  • the X2 message especially for the X2 handover procedure, the X2 message arrives at the target base station from the relay station via the base station.
  • the base station can also parse the X2 message, and can modify the X2 interface ID.
  • the handover occurs under one base station, such as the terminal switching from one base station to its subordinate relay station, or from the subordinate relay of the base station to the base station, or from one relay of the base station to another under the base station
  • the related process on the core network side can be simplified, for example, because there is no need to perform the path update process, because the data transmission path of the terminal or the original gateway arrives at the base station, and the data path after reaching the base station can be controlled by the base station. .
  • many message signaling is not necessary to pass through the MME.
  • the target site may be a base station or a relay station under the base station, the message interaction from the source to the destination does not need to be transited through the MME.
  • the embodiment of the present invention provides a handover method.
  • FIG. 3a is a schematic diagram of a handover method according to an embodiment of the present invention.
  • the method includes: S31a: a donor base station determines that a user equipment is handed over from a first relay station subordinate to the donor base station to the donor base station or a second relay station subordinate to the donor base station .
  • the donor base station sends a user equipment context release command UE Context Release Command to the first relay station without transmitting a handover notification to the core network device.
  • the DeNB in this embodiment After receiving the handover request of the subordinate RN, the DeNB in this embodiment omits the information interaction process with the core network, and directly releases the context of the user equipment.
  • the method of this embodiment may further include: the donor base station receiving a handover request from the first relay station, where the handover request is used to request to perform handover on the user equipment; and the donor base station may determine handover according to the handover request.
  • Target and determining that the user equipment is from the first relay station of the base station
  • the handover command is sent to the first relay station to instruct the first relay station to perform handover.
  • the method can be implemented to switch the UE to the DeNB itself or other subordinate RNs, because it is a handover procedure in the base station, that is, the terminal switches from the relay station subordinate to the base station to the base station or to another relay station subordinate to the base station, for the handover process.
  • the core network side is not affected. Therefore, the handover process related to the core network side (MME, SGW/PGW, etc.) in the prior art can be simplified, and signaling overhead is saved.
  • the donor base station can obtain and store some context information related to the UE, such as: QoS information corresponding to the service supported by the UE, encryption or integrity protection algorithm supported by the UE, etc. Therefore, the relay station does not inform the eNB of the content in the handover related message in the prior art during the handover process; therefore, the message content and some signaling procedures transmitted on the air interface between the relay station and the base station can be simplified to save Signaling overhead.
  • the embodiment may further include: when the donor base station determines that the user equipment is handed over from the first relay station subordinate to the donor base station to the donor base station, the donor base station receives a radio resource control connection reestablishment complete message from the user equipment, RC Connection Reconfiguration Complete, sending a user equipment context release command to the first relay station without transmitting a handover notification Handover Notify to the core network device; when the donor base station determines that the user equipment switches from the first relay station subordinate to the donor base station to the donor base station subordinate When the second relay station is in use, the donor base station receives a handover notification Handover Notify from the second relay station, and transmits a user equipment context release command to the first relay station without transmitting a handover notification to the core network device.
  • the donor base station may further receive a base station state transition message eNB Status Transfer from the first relay station, and not send to the core network device.
  • the mobility management entity state transition message MME Status Transfer is sent to the first relay station; when the donor base station determines that the user equipment is handed over from the donor base station subordinate first relay station to the donor base station subordinate second relay station, The donor base station may receive a base station state transition message eNB Status Transfer from the first relay station, and not send the base station status to the core network device.
  • the mobile management entity state transition message MME Status Transfer 0 is sent to the second relay station.
  • the user equipment may be preferentially attempted to switch from the donor base station itself to its subordinate relay station, and the relay station subordinate to the donor base station is determined as the user.
  • the signaling interaction process with the network side can also be saved.
  • the data transmission path of the terminal is the service gateway of the terminal gateway-donor base station-terminal.
  • the data transmission path is the terminal gateway to the donor base station.
  • the terminal From the perspective of the core network, the data transmission path can remain unchanged, that is, still the gateway to the base station, and thus the gateway-related path update procedure in the prior art can be omitted.
  • the base station has the function of a proxy, the terminal changes from the perspective of the gateway side, but after receiving the terminal gateway information, the base station can confirm which terminal the data belongs to and which service station it belongs to.
  • FIG. 3b is a schematic diagram of another handover method according to an embodiment of the present invention, where the method includes:
  • the donor base station determines that the user equipment is handed over from the donor base station to the subordinate relay station of the donor base station;
  • the donor base station releases the context of the user equipment without sending a handover notification to the core network device.
  • This embodiment may not exchange a large amount of signaling with the core network device, complete the handover to the UE, and the UE context Release, simplifying the switching process.
  • the donor base station may send a handover command to the user equipment to notify the user equipment to perform handover without sending a handover request to the core network device.
  • the simplified procedure is not limited to the handover between the base station and the relay station. When the terminal switches between the two home base stations under the home gateway, a similar simplified procedure may be used. This embodiment is not limited.
  • FIG. 4 is a schematic flowchart diagram of a handover method according to an embodiment of the present invention, where the method includes:
  • the source relay station receives a measurement report (Measure Report) of the user equipment.
  • the source relay station performs a handover decision, and determines that the user equipment needs to be switched.
  • S43 The source relay node sends a handover request (S1AP: Handover Required) to its donor base station, requesting to perform handover on the user equipment.
  • S1AP Handover Required
  • S44 The donor base station sends a handover request message (S1AP: Handover Request) to the target relay station without sending a handover request to the core network device.
  • S1AP Handover Request
  • S45 The donor base station receives a handover request response message from the target relay station (S1AP:
  • S46a The donor base station does not have to receive a handover command from the core network device, and sends a handover command (S1AP: Handover Command) to the source relay station, indicating that the handover operation is performed.
  • S1AP Handover Command
  • S46b An optional step in which the source relay can process the data in the buffer and transmit it to the target site, the target relay station.
  • the source relay station sends a radio resource control connection reconfiguration (R C Connection Reconfiguration) message to the user equipment, or sends a handover command Handover Command message (the message is an RRC message), so that the user equipment switches to the target cell.
  • R C Connection Reconfiguration radio resource control connection reconfiguration
  • handover command Handover Command message the message is an RRC message
  • S47b After receiving the handover command, the user equipment synchronizes with the old cell and synchronizes with the target cell.
  • S48 The source relay station sends a base station state transition message to the donor base station (S1AP: eNB) Status Transfer ). This step is an optional step.
  • the donor base station does not send a base station state transition message to the core network device, and sends a mobility management entity state transition message (S1 AP: MME Status Transfer) to the target relay station. This step is optional.
  • S410a The source relay station forwards the user equipment data to the target relay station through the base station. This step is optional.
  • S410b The target relay station buffers a packet (Packet) from the source relay station. This step is optional.
  • S411 The user equipment sends a RRC Connection Reconfiguration Complete message to the target relay station. (CRRC Connection Reconfiguration Complete) c. It can be understood that if the user equipment receives the handover command Handover Command message (the message is an RRC message), then The reply is that the handover command completes the Handover Command compelete message (the message is an RRC message).
  • S412 The target relay station sends a handover notification (Handover Notify) to the donor base station.
  • S414a The source relay station releases resources related to the user equipment.
  • the handover process can be simplified and the signaling overhead in the handover can be saved.
  • the foregoing process is only a brief description of the complete handover process of the UE.
  • the specific implementation also includes other processes that have been omitted in this embodiment, but the omitted processes are all prior art, and do not affect the implementation of the embodiment.
  • the method is directed to a scenario in which the UE switches from one RN of the DeNB to another RN of the DeNB, and the UE switches from the RN1 to the DeNB to which it belongs, or switches from the DeNB to its subordinate RN or other phase.
  • the handover process of the UE may be performed by referring to this embodiment. For details, refer to the following description.
  • the base station especially for the base station to be able to buffer the terminal data, it is possible that when the terminal switches, the base station still retains the data of the terminal, and there is no need to perform the data forwarding process.
  • the process associated with the data transfer process can thus be omitted.
  • the above optional steps may selectively perform part or all of them.
  • the S1 message sent by the base station is a message sent by the MME, that is, the relay station directly communicates with the MME.
  • the base station acts as a proxy.
  • the message sent from the MME is actually generated and transmitted by the base station, and since the content of the message is basically known by the base station, the base station can generate such a message. . If a certain base station side of the message is not reserved, the base station can obtain it by going to the core network (such as MME, GW, etc.).
  • the base station can obtain a new security information (such as new NCC and NH) for the terminal from the MME side.
  • a new security information such as new NCC and NH
  • the MME may need to know some information transformation of the terminal, or need to know the change of the target cell after the handover of the terminal, the base station may separately notify the MME, for example, security information, and the security corresponding to the terminal in the target cell after the terminal handover.
  • the key needs to be changed, and the changed security key needs to be notified to the MME.
  • the relay station RN needs to switch the user equipment UE from the relay station RN to the donor base station DeNB of the relay station or other relay stations of the donor base station, or use the X2 signaling to transmit the handover request message Handover Request to other base stations.
  • the handover request Handover Required sent by the relay station may be simplified.
  • the specific handover request includes: a message type Message Type, an SI link identifier, a user equipment identifier, a handover type Handover Type, a handover cause Cause, and a handover target identifier Target ID.
  • the handover request does not include: a direct forwarding path information, a direct forwarding path information, and a single radio voice call continuation indication information (SRVCC).
  • the handover request may further include or not Includes the following: Mobile station classification tag MS Classmark, closed subscriber group cell identity CSG Id, cell access mode Cell Access Mode and enhanced wireless access bearer maximum number max no of E-RABs.
  • the handover request may further include: a source to target transparent container, the source to target transparent container includes: a radio resource control container RRC Container, an enhanced radio access bearer information table E-RABs Information List, The enhanced radio access bearer information item E-RABs Information Item, the enhanced radio access bearer identifier E-RAB ID and the user equipment history information UE History Information, and the Source to Target Transparent Container does not include the downlink forwarding message DL Forwarding.
  • the RRC Container may include or not include the following: radio resource management configuration information rrm-Config, as configuration information as Config, user equipment radio access capability information UE-Radio Access Capability Info, and as Context.
  • radio resource management configuration information rrm-Config as configuration information as Config
  • UE-Radio Access Capability Info user equipment radio access capability information
  • Context Context
  • S43 and S44 are X2AP: HO request message
  • S45 and S46 are X2AP: HO request ACK message
  • S48 and S49 are X2AP: SN status transfer message
  • S413 is X2AP: UE context release message.
  • S413 has no S414b step.
  • the target relay station sends a UE context release message to the donor base station.
  • the target site obtains a new NCC (Next Hop Chaining Count) through the MME in the process of path update (steps S212-S216 in the S1 handover).
  • the MME uses the NCC to calculate a new NH (Next Hop) parameter, so that the target station obtains a new NCC and a new NH in the path update process, and calculates a new key KeNB* through the two new parameters.
  • the NH parameter is calculated in the MME and the UE, and the eNB has no ability to calculate the NH parameter.
  • the base station can initiate a process of updating the NCC to the MME, thereby obtaining a new NCC and NH to the target site, or itself (when the handover target is the base station itself) to obtain new NCC and NH.
  • the base station initiates the process of updating the NCC to the MME, after the base station obtains the new NCC and the new NH from the MME, the base station transmits this information to the target station or to itself (when the target station is the base station itself) for key update use.
  • the sending process may be performed when the UE confirms that the terminal successfully switches to the target cell (such as receiving the handover confirmation information of the target site, in particular, the S413 base station receives the X2AP: UE context release message of the target site in the embodiment of the present invention). It can also be done at other times.
  • the base station can also have the function of generating or updating the NCC by the MME, and provide the new NCC and NH to the target site.
  • the base station may obtain the new NCC and NH from the MME to the relay station, and may also I configured my new NCC and NH to the relay station. If the station is configured by itself, the base station may also need to provide new NCC and NH to the MME. In summary, after the base station obtains the new NCC and NH, this information is provided to the target site. Or after S412, the base station confirms that the terminal has successfully switched to the target station, and thus the base station can obtain or configure a new NCC and NH to the relay station from the MME. If it is a base station configuration, then the base station may also need to provide new NCC and NH to the MME. In summary, after the base station obtains the new NCC and NH, this information is provided to the target site.
  • the foregoing base station may also be a home (e) NB or a home (e) NB Gateway, or a base station or a gateway of a pico cell.
  • FIG. 5 is a schematic flow chart of another handover method according to an embodiment of the present invention.
  • the method is similar to the method shown in FIG. 4, but only implements handover from a relay station to a donor base station of the relay station.
  • the method may include :
  • S51 The user equipment sends a measurement report to the relay station.
  • S52 The relay station performs a handover decision.
  • S53 The relay station sends a handover request to its donor base station (S1AP: Handover Required).
  • S54 The donor base station sends a handover command (SI AP: HO command message) to the relay station.
  • SI AP Handover command message
  • the relay station can process data in the buffer and transmit it to the donor base station. This step is optional.
  • the relay station sends a radio resource control connection reconfiguration (R C Connection Reconfiguration) message to the user equipment, or sends a handover command Handover Command message (the message is an RRC message), so that the user equipment switches to the target cell.
  • R C Connection Reconfiguration radio resource control connection reconfiguration
  • Handover Command message the message is an RRC message
  • S57 The user equipment performs synchronous access with the target cell.
  • the relay station sends a base station state transition message S1AP to the donor base station: eNBstatus transfer c
  • the relay station forwards data of the terminal stored in the relay station to the donor base station. This step is optional. For example, if the donor base station keeps the data of the terminal until it is confirmed that the terminal has received it, the base station may not need the relayed data during the handover.
  • the donor base station buffers a data packet from the relay station.
  • S512 The donor base station sends a user equipment context release command S1AP to the relay station: UE Context Release Command.
  • S513 The relay station releases resource and context information (Context) related to the terminal.
  • S514 The relay station sends a user equipment context release complete message to the donor base station.
  • S1AP UE context Release Complete.
  • the above process is mainly for the S1 handover process, but the similar method is similarly applicable to the simplification of the X2 handover process, that is, the path switch process in the X2 handover process can be omitted, except that the message between the relay station and the base station uses the X2 message.
  • the message of S53 can be X2AP: HO request message,
  • S54 can be X2AP: HO request ACK message
  • S58 is X2AP: SN status transfer message
  • S512 is the X2AP: UE context release message. In the X2 process, only S512 has no S514 steps. It can be understood that there is a certain difference between the specific process of the S1 handover and the X2 handover, but the difference is only a simple modification. A person skilled in the art can obtain a flowchart of the X2 handover from FIG. 5, which is not limited in this embodiment.
  • the base station simplifies the signaling interaction process with the core network, so that the handover complexity is reduced.
  • FIG. 6 is a schematic flow chart of another handover method according to an embodiment of the present invention. The method is similar to the method shown in FIG. 4, but only implements handover from a donor base station to a subordinate relay station of the donor base station, as shown in FIG. Includes:
  • S61 The user equipment sends a measurement report to its serving base station.
  • S62 The donor base station performs a handover decision.
  • S63 The donor base station sends a handover request message to its subordinate relay station (S1AP: Handover
  • S64 The relay station sends a handover request response message (S1AP: Handover Request ACK) to the donor base station.
  • S65 The donor base station buffers data and sends the data to the relay station.
  • the donor base station sends a radio resource control connection reconfiguration (R C Connection Reconfiguration) message to the user equipment, or sends a handover command Handover Command message (the message is an RRC message), so that the user equipment switches to the target cell.
  • R C Connection Reconfiguration radio resource control connection reconfiguration
  • RRC handover command Handover Command
  • S67 The user equipment synchronizes access to the target cell.
  • S68 The donor base station sends a mobility management entity state transition message MME status transfer message (S1AP: MME status transfer) to the relay station. .
  • S1AP mobility management entity state transition message MME status transfer message
  • S69 The donor base station forwards data to the relay station.
  • the relay station buffers data from a donor base station.
  • S612 The relay station sends a user equipment context release command (S1AP: UE Context Release Command) to the donor base station.
  • S1AP user equipment context release command
  • S614 The donor base station sends a user equipment context release complete message to the relay station.
  • X2 messages can also be used to implement the switching process.
  • the handover request may not be S1AP: Handover Required, but replaced by X2: Handover Request.
  • Other messages such as handover request message, handover response message, and handover command can be implemented by X2 message.
  • X2 When the Handover Request message is sent by the RN to the base station, since the base station is available to the terminal information of the relay station, the prior art is X2: The content that the Handover Request message needs to carry can be omitted. The information that can be included in the message is: Cause of Cause, Target Cell ID, RRC Context, and UE History Information. .
  • the above process is mainly for the SI switching process, but the similar method is similarly applied to the simplification of the X2 switching process. Only messages between the relay station and the base station use X2 messages. At this time, the path switch process during X2 switching can be omitted.
  • the message in S63 is X2AP: HO request message
  • S64 is X2AP: HO request ACK message
  • S68 is X2AP: SN status transfer message
  • S612 is X2AP: UE context release message.
  • S612 is X2AP: UE context release message.
  • a person skilled in the art can obtain the flow diagram of the X2 handover from FIG. 6, which is not limited in this embodiment.
  • the target node performs a path update process, and a new NCC is obtained by the MME, and the MME uses the NCC to calculate a new one.
  • the NH parameter whereby the target site obtains a new NCC and a new NH in the path update process, and the new key KeNB* is calculated by the two new parameters.
  • the NH parameter is calculated in the MME and the UE, and the eNB has no ability to calculate the NH parameter.
  • the handover request message sent by the MME is sent to the target station in the S1 handover process, and the handover request message carries the MME to calculate the new NCC locally and the NH calculated by the NCC.
  • the process related to the core network is simplified (for example, the path switching process is omitted), then the base station can initiate a process of updating the NCC to the MME, thereby obtaining a new NCC and NH to the target site, or the base station can itself ( When the handover target is the base station itself, a new NCC and NH are obtained.
  • the base station initiates a process of updating the NCC to the MME, when the base station obtains a new NCC from the MME After the new NH, the base station sends this information to the target site or to itself (when the target site is the base station itself) for key update use.
  • the foregoing process may be performed when the UE confirms that the terminal successfully switches to the target cell (such as receiving the handover confirmation information of the target site, in particular, the S612 base station receives the X2AP: UE context release message of the target site in the embodiment of the present invention). It can also be done at other times.
  • the above process is for the base station to obtain new NCC and NH processes from the MME. Another embodiment is shown in detail in FIG.
  • the base station can also have the function of generating or updating the NCC of the MME, and provide the new NCC and NH to the target station (for example, RN2, or the target station is the base station itself).
  • the S612 UE context release message may be implemented; or the path update message Path Swich message sent by the relay station may be included before the step S612.
  • the base station may acquire a new NCC and NH from the MME to the relay station, or may be a base station. I have configured the new NCC and NH to the relay station. If the base station is configured by itself, the base station may also need to provide new NCC and NH to the MME.
  • the base station After the base station obtains the new NCC and NH, this information is provided to the target site. Or after S612, the base station confirms that the terminal has successfully switched to the target station, whereby the base station can obtain or configure the new NCC and NH to the relay station from the MME.
  • the above process generates or updates the NCC for the base station itself, and obtains the new NCC and NH processes. Another embodiment is shown in detail in FIG.
  • the foregoing base station may also be a home (e) NB or a home (e) NB Gateway, or a base station or a gateway of a pico cell.
  • the relay station may also be a Home (e)NB
  • the target station may be a home (e)NB.
  • the base station or home (e)NB GW has the MME generated or calculated NCC or The function of the NH, then the base station can directly send new NCC and NH to the target site (such as relay station, home (e) NB, etc.).
  • the target site such as relay station, home (e) NB, etc.
  • the above mentioned safety isolation step is an optional step.
  • a schematic diagram of a process for a base station to update an NCC from an MME according to an embodiment of the present invention includes:
  • the base station sends a key update request to the mobility management. Specifically, after receiving the handover request message sent by the source relay station RN1, the base station sends a key update request to the mobility management. Specifically, the relay station 1 sends a handover request message.
  • the handover request message is a Handover Required message
  • the handover acknowledgement message is a Handover Request message.
  • S72a The mobility management entity locally adds NCC to 1, and calculates a new NH value
  • S73a the mobility management entity sends the newly calculated ⁇ NH, NCC ⁇ to the base station
  • S74a The base station provides the next hop link calculation and the next hop parameter to the target station; in particular, for the S1 handover, the next hop link calculation and the next hop parameter information are included in the S1 message: HO request message. For X2 handover, the next hop link calculation and next hop parameter information are included in the X2 message: HO request message.
  • the target station (such as the relay station RN2) calculates the KeNB or KeNB* according to the received NCC, and saves it in association with the NCC.
  • the method further includes: the target station (such as the relay station RN2) sends a handover request A confirmation command is given to the base station, and the handover request confirmation command includes new NCC information.
  • the handover request acknowledgement command is a Handover Request ACK message
  • the handover request message is a Handover Request ACK message.
  • the base station sends a handover request acknowledgement command to the source relay station RN1, and the handover request acknowledgement command includes new NCC information.
  • the RN1 sends a RRC connection re-establishment message to the terminal, and the terminal switches to the target site RN2, where the message contains new NCC information.
  • the terminal calculates the KeNB or KeNB* according to the received NCC, synchronizes the NH, and saves it in association with the NCC.
  • a schematic diagram of a process for a base station to update an NCC according to an embodiment of the present invention includes:
  • the relay station 1 sends a handover request message to the base station; for the S1 interface message, the handover application message is a Handover Required message; for the X2 interface message, the handover application message is a Handover Request message.
  • the base station receives the handover request of the source relay station, such as the S1 message: HO Required, or the X2 message: the HO request includes the UE security capability, the encryption algorithm and the integrity algorithm used by the source relay station side, and the KeNB*, NCC.
  • S72b After the base station receives the handover request message of the source relay station RN1 (such as S1 message: HO Required, or X2 message: HO request), the base station locally adds NCC to 1, and calculates a new NH value.
  • the handover request message of the source relay station RN1 such as S1 message: HO Required, or X2 message: HO request
  • S73b The base station sends the newly calculated ⁇ NH, NCC ⁇ to the target station, such as the relay station RN2, in the handover request message.
  • the handover request message is the S1AP: Handover Request message
  • the handover request message is the X2 AP: Handover Request message.
  • the target station (such as the relay station RN2) calculates the KeNB according to the received NCC and NH. And saved in association with NCC.
  • the target station (such as the relay station RN2) sends a handover request confirmation command to the base station, and the handover request confirmation command includes new NCC information.
  • the handover request acknowledgement command is a Handover Request ACK message; for the X2 interface message, the handover request message is a Handover Request ACK message.
  • the base station sends a handover request acknowledgement command to the source relay station RN1, and the handover request acknowledgement command includes new NCC information.
  • S77b The RN1 sends a radio resource control connection re-establishment message to the terminal, and causes the terminal to switch to the target station RN2, where the message includes new NCC information.
  • S78b The terminal calculates the KeNB or KeNB* according to the received NCC, synchronizes the NH, and
  • the base station sends the newly calculated ⁇ NH, NCC ⁇ to the MME. This step can occur after S72b.
  • the above embodiment can be applied to the scenario of Home (e) NB.
  • the base station in the above embodiment is equivalent to the Home (e) NB GW.
  • the relay station 1 in the above embodiment is equivalent to Home (e) NB1
  • the relay station in the above embodiment 2 is equivalent to Home ( e ) NB2. All the embodiments of the present invention can be applied to the scenario of the Home (e)NB.
  • the base station in the foregoing embodiment is equivalent to the Home (e)NB GW, and the relay station 1 in the above embodiment is equivalent to Home (e).
  • the relay station 2 in the above embodiment is equivalent to Home (e) NB2.
  • FIG. 8 is a schematic diagram of a base station according to an embodiment of the present invention.
  • the base station 80 includes: a determining unit 801, configured to determine that a user equipment is handed over from the first relay station 81 of the base station 80 to the base station 80 or the base station 80.
  • the subordinate second relay station 82 configured to, when the determining unit 801 determines that the user equipment is handed over from the first relay station 81 to the base station 80 or the second relay station 82, without transmitting a handover notification to the core network device,
  • the first relay station 81 sends a user equipment context release command UE Context Release Commando
  • the base station 80 in this embodiment can be simplified with the core network device during the handover process (specifically,
  • MME handover procedure and saves signaling overhead in handover.
  • the base station 80 may further include: a request receiving unit, configured to receive a handover request from the first relay station 81, where the handover request is used to request to perform handover on the user equipment; and the command sending unit is configured to When the handover request is sent to the core network device, a handover command is sent to the first relay station 81 to instruct the first relay station 81 to perform handover.
  • a request receiving unit configured to receive a handover request from the first relay station 81, where the handover request is used to request to perform handover on the user equipment
  • the command sending unit is configured to When the handover request is sent to the core network device, a handover command is sent to the first relay station 81 to instruct the first relay station 81 to perform handover.
  • the base station 80 may further include: a state transition unit, configured to:
  • the determining unit 801 determines that the first relay station 81 of the user equipment is handed over to the base station 80, receiving the base station state transition message eNB Status Transfer from the first relay station 81, and not transmitting the base station state transition message to the core network device.
  • the mobility management entity state transition message MME Status Transfer is sent to the first relay station 81;
  • the determining unit 801 determines that the user equipment is handed over from the first relay station 81 to the second relay station 82, receiving a base station state transition message from the first relay station 81, without transmitting a base station state transition message to the core network device In the case, a mobility management entity state transition message is sent to the second relay station 81.
  • the determining unit 801 is further configured to determine that the user equipment is handed over from the base station 80 to the third relay station of the base station 80; the releasing unit is further configured to: when the determining unit 801 determines that the user equipment is from the When the base station 80 switches to the third relay station, the context of the user equipment is released without transmitting a handover notification to the core network device.
  • the base station 80 may further include: a parameter obtaining unit configured to:
  • the next hop parameter is obtained from the core network side device or the next hop parameter is calculated by the NCC using the next hop link, and the next hop parameter is provided to the second relay station 82; or
  • the determining unit 801 determines that the user equipment is handed over from the first relay station 81 to the base station 80, acquiring the next hop parameter to the core network side device or calculating the next hop parameter by using the next hop link calculation NCC, and A new key KeNB* is generated according to the next hop parameter.
  • the signaling interaction process between the base station and the core network when the terminal is switched can be simplified.
  • the base station and the relay station in the embodiments of the present invention include not only various base stations and relay stations such as LTE, Wimax, and CDMA.
  • the base station may also be a home gateway home eNB Gateway; the relay station may be a home base station Home eNB.
  • the home gateway is used instead of the base station, or the home base station is used instead of the relay station, the method flow is only to perform the subject change, and the technical solution is substantially unchanged.
  • FIG. 9 is a schematic diagram of another handover method according to an embodiment of the present disclosure, which may include:
  • the home gateway receives a handover request of the first home base station of the home gateway, where the handover request is used to request to perform handover on the user equipment.
  • the home gateway determines that the user equipment is handed over from the first home base station to a second home base station of the home gateway;
  • the home gateway sends a handover command to the first home base station to notify the first home base station to perform handover, if the handover request is not sent to the core network device.
  • the method can further include:
  • the home gateway acquires, from the core network side device, a next hop link calculation NCC or next hop parameter to the core network side device, and provides the next hop link calculation or next hop parameter to the second home base station. ;
  • the home gateway acquires a next hop link calculation or a next hop parameter from the core network side device, and calculates a key KeNB or KeNB* according to the received one hop link calculation or the next hop parameter, The calculated key is saved in association with the next hop link calculation.
  • FIG. 10 is a schematic diagram of a home gateway according to an embodiment of the present disclosure, which may include:
  • the receiving unit 101 is configured to receive a handover request of the first home base station of the home gateway, where the handover request is used to request to perform handover on the user equipment;
  • the determining unit 102 is configured to determine that the user equipment is handed over from the first home base station to a second home base station of the home gateway;
  • the releasing unit 103 is configured to send a user equipment context release command to the first home base station without sending a handover notification to the core network device.
  • FIG. 11 is a schematic diagram of another base station according to an embodiment of the present invention, including:
  • the determining unit 111 is configured to determine that the user equipment is handed over from the donor base station to the donor base station subordinate relay station;
  • the releasing unit 112 is configured to release the context of the user equipment without sending a handover notification to the core network device.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Description

一种对终端进行切换的处理方法、 和家庭网关 本申请要求于 2010 年 4 月 9 日提交中国专利局、 申请号为 201010149325.8、 发明名称为"一种切换方法、 基站和家庭网关"的中国专利申 请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域， 尤其涉及一种对终端进行切换的处理方法、基 站和家庭网关。 背景技术
随着通信技术的发展， 通信业界对 IMT-Advanced (高级国际移动通信） 系统提出了很高的系统容量要求，但足以支撑高容量的大带宽频谱可能只在较 高频段找到， 而这样高的频段的路径损耗和穿透损耗都比较大，很难实现好的 覆盖。 LTE-A ( LTE-Advance， LTE的演进）为了满足 IMT-Advanced的容量需 求， Relay (中继）技术将可能被用于改善系统容量和覆盖范围。
在现有的 LTE ( Long Term Evolution, 长期演进） 系统中， eNodeB (演进 基站）与 MME/S-GW (服务网关）之间以 S1接口相交互， MME与 eNodeB之间 的 S 1接口又可以表示为 S 1 -MME接口， S-GW与 eNodeB之间的 S 1接口又可以表 示为 S1-U接口， 各 eNodeB之间以 X2接口相交互， eNodeB与 UE之间以无线链 路的空口相交互。
LTE-A网络在 LTE网络架构的基础上增加了 RN ( Relay Node， 中继节点， 又叫中继站） ， 设置在 eNB ( eNodeB , 演进基站， 简称基站） 与 UE ( User Equipment, 用户设备）之间。 UE与 RN之间的无线链路称之为 Uu空口， RN与 eNodeB之间的无线链路称之为 Un空口。 中继站与其服务基站之间的空口有一 个 S1接口和一个 X2接口， 中继站作为一个站点 （基站） 为其终端服务时， 通 过 S 1和 X2接口与其服务基站连接。 对于 UE而言， RN相当于是一个 eNodeB。基站在其两侧接口之间传递终端 专用 （ UE-dedicated )的 SI和 X2信令消息以便于为中继站下终端提供服务。 基 站两侧的接口， 一侧是基站与中继站之间的空口 （ S 1和 /或 X2接口） ， 另一侧 是基站与其他网络节点之间接口 （S1或者 X2接口） 。 基站能够意识到该终端 是接入到中继站下的终端。
图 1为一种 LTE-A无线接入网的示意图，该网络中包括 DeNB ( Donor eNB， 施主基站） 、 RN、 及该 RN下属的 3个 UE， 分别标记为 UE1、 UE2和 UE3。 UE 与 RN之间的接口为 Uu口； RN与 DeNB间的接口则为 Un口； DeNB彼此之间的 接口被称为 X2接口； DeNB与移动管理实体 ( MME， Mobility Management Entity )或网关（GW， Gateway )间的接口为 SI接口。 利用 X2接口传输的消息 称为 X2消息， 利用 S1接口传输的消息称为 S1消息。
按照在现有 LTE的切换流程， 考虑中继网络下终端的切换， 那么终端的服 务站点即中继站将执行如同 LTE的基站一样的行为， 为其终端进行切换。 中继 站和基站之间是一个空口， 中继站与核心网之间的消息交互都需要通过基站。
现有系统中引入中继站后， UE-eNB的接入链路由原来的单跳转变为两跳 或多跳， RN-eNB的接口为新定义的 Un接口。 目前， LTE-A技术中不涉及中继 切换相关的具体技术细节， 包括切换判决实体、 切换判决依据、 切换流程等。 如果沿用现有 LTE的切换机制， 即把中继站看作为 eNB， 整个切换流程可采用 类似于 Inter-eNB (基站间） 的切换流程， 在 Un接口上承载原 S 1或者 X2接口上 的切换相关信息。
现有技术 LTE系统下通过 S1信令对终端进行切换流程， 如图 2所示。
切换前， 终端下行数据传输路径是先从网关到达源基站（终端的当前服务 基站） ， 再由源基站到达终端。
S21 : 源基站接收来自用户设备的测量报告（ Measurement Report ) 。
S22: 源基站执行切换判决 ( Handover decision ) 。 S23： 所述源基站向移动管理实体发送切换申请 （ S1AP： Handover Required ) 。
S24: 所述目标基站接收所述移动管理实体发送的切换请求消息 （S1AP: Handover Request ) 。
S25: 所述目标基站向所述移动管理实体发送切换请求响应消息 （S1AP:
Handover Request ACK ) 。
S26: 所述移动管理实体向所述源基站发送切换命令（ S1AP: Handover Command ) 。
S27: 所述源基站向用户设备发送切换命令 Handover Command (该消息为 R C消息）， 让用户设备切换到目标小区去， 或者向用户设备发送无线资源控 制连接重配置 ( RRC Connection Reconfiguration ) 消息。
S28:源基站向用户设备的 MME发送基站状态转移消息（S1AP: eNB status transfer ) 。
S29: MME接收到基站状态转移消息（ S1AP: eNB status transfer )后， 向 目标基站发送 MME状态转移消息 （S1AP: MME status transfer ) 。
S210: 源基站处理緩存中的数据， 将所述终端数据传输给目标站点， 这里 所述的目标站点为所述目标基站。数据转发路径是从源基站到网关，再由网关 发送到目标基站。 此时如果源基站和目标基站之间有直接路径， 那么转发路径 也可以是源基站直接转发数据给目标基站。
S211 : 用户设备在收到源基站的切换命令后， 向目标小区进行同步以接入 到目标小区， 当切换到目标小区后， 向目标基站发送无线资源控制连接重配置 冗成 ( RRC Connection Reconfiguration Complete ) 消息 (或者是 Handover Command complete消息 ) 。
S212: 目标基站向移动管理实体发送切换通知（ Handover Notify ) 。
S213 : 移动管理实体向网关发送用户面更新请求 （User Plane Update Request ) 。 所述网关可包括但不限于 SGW ( Serving Gateway, 服务网关）和 PGW ( Packet Data Network Gateway, 分组数据网络网关） 。
S214: 所述网关执行路径更新。
此时终端的下行数据传输路径开始变为由网关到目标基站，然后由目标基 站到终端。
S215: 所述网关在完成路径更新后， 向移动管理实体返回用户面更新响应 ( User Plane Update Response ) 。
S216: 所述移动管理实体向源基站发送用户设备上下文释放命令（UE Context Release Command ) 。
S217: 源基站进行资源释放。
S218: 源基站在进行资源释放后， 向移动管理实体发送用户设备上下文释 放完成消息。
现有技术在任何切换场景下均执行上述切换流程， 流程复杂，增加了切换 延迟。 因此如何针对具体应用场景对切换流程进行简化就成为一个问题。 发明内容
根据本发明的一实施例， 提供一种对终端进行切换的处理方法， 包括： 基站确定用户设备的切换目标位于所述基站的覆盖范围内；
所述基站在未与核心网设备进行信令交互的情况下，直接执行对所述用户 设备的切换。
根据本发明的又一实施例， 提供一种基站， 包括：
确定单元， 用于确定用户设备的切换目标位于所述基站的覆盖范围内； 释放单元， 用于在未与核心网设备进行信令交互的情况下， 直接执行对所 述用户设备的切换。
根据本发明的又一实施例， 提供一种对终端进行切换的处理方法， 包括： 家庭网关接收该家庭网关下属第一家庭基站的切换申请，所述切换申请用 于请求对用户设备执行切换；
家庭网关确定所述用户设备从所述第一家庭基站切换至该家庭网关下属 第二家庭基站；
所述家庭网关在不向核心网设备发送切换申请的情况下，向所述第一家庭 基站发送切换命令， 以指示所述第一家庭基站进行切换。
根据本发明的又一实施例， 提供一种家庭网关， 包括：
接收单元， 用于接收该家庭网关下属第一家庭基站的切换申请， 所述切换 申请用于请求对用户设备执行切换；
确定单元，用于确定所述用户设备从所述第一家庭基站切换至该家庭网关 下属第二家庭基站；
释放单元， 用于在不向核心网设备发送切换通知的情况下， 向所述第一家 庭基站发送用户设备上下文释放命令。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施 例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地， 下面描述 中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付 出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为一种 LTE-A无线接入网的示意图；
图 2为现有技术 LTE系统下通过 S1信令进行对终端切换的流程示意图； 图 3a为本发明的实施例提供的一种切换方法的示意图；
图 3b为本发明的实施例提供的另一种切换方法的示意图；
图 4为本发明的实施例提供的一种切换方法的简要流程示意图； 图 5为本发明的实施例提供的另一种切换方法的简要流程示意图； 图 6为本发明的实施例提供的另一种切换方法的简要流程示意图； 图 7a为本发明实施例提供的一种基站从 MME处更新 NCC的过程的示意 图；
图 7b为本发明实施例提供的一种基站更新 NCC的过程的示意图； 图 8为本发明的实施例提供的一种基站的示意图；
图 9为本发明实施例提供的另一种切换方法的示意图；
图 10为本发明实施例提供的一种家庭网关的示意图；
图 11为本发明实施例提供的另一种基站的示意图。 具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
在中继网络中， 中继与基站之间的空口叫做 Un接口， 该接口可以是 S1 接口或者 X2接口。 该基站在中继站和其他网络节点 （如其他基站， MME， S-GWs 等）之间为中继站提供 SI和 X2 proxy (代理）功能（proxy flmctionality )。 这种 proxy功能包括在基站的两侧接口之间传递终端专用 （ UE-dedicated ) 的 S1和 X2信令消息以便于为中继站下终端提供服务。基站两侧的接口，一侧是 基站与中继站之间的空口 （S1和 /或 X2接口）， 另一侧是基站与其他网络节点 之间接口 （S1 或者 X2接口）。
从中继的角度来看， 它认为由 MME发出通过基站转发给它的信息， 就是 直接由 MME发来的， 而 MME也认为由中继发出通过基站转发给它的信息， 就是直接由中继发来的。 这里基站有一种 proxy (代理） 的功能。 基站可以解 析由 MME发出给 RN的消息或者由 RN发出给 MME的消息， 由此可以知道
更正页 (细则第 91条) 中继下的终端信息。 例如对于终端相应的 S 1消息（如切换请求消息）， 该 S1 消息从中继站经由基站到达 MME。 由于 S I proxy功能， 那么基站能够意识到 该终端是在中继站下的。 同时基站可以修改两侧接口消息的 ID信息， 如基站 可以更改 MME发来的 S 1消息的 S 1接口 ID( eNB UE S IAP ID ,或者 MME UE SIAP ID ), 再转发给 RN。 反之亦然。 对于 X2 消息， 特别对以 X2 切换流程 为例， X2消息从中继站经由基站到达目标基站。 基站同样可以解析该 X2消 息， 可以对 X2接口 ID进行修改。
由此如果切换发生在一个基站下， 如终端从一个基站切换到它下属中继 站，或者从该基站的下属中继切换到该基站，或者从该基站的一个中继切换到 该基站下的另一个中继的情况下，核心网侧的相关的流程可以得到简化， 例如 由于没有必要进行路径更新流程，因为终端的数据传输路径还是原来的网关到 达基站， 至于到达基站后的数据路径可以由基站控制。 由此很多消息信令也就 没有必要通过 MME。 另外由于目标站点可能是基站或者是基站下的中继站， 因此从源到目标的消息交互没有必要通过 MME 中转。 为了简化切换过程中 DeNB与核心网侧的信息交互， 本发明实施例提出一种切换方法。
图 3a为本发明的实施例提供的一种切换方法的示意图， 该方法包括： S31a:施主基站确定用户设备从该施主基站下属第一中继站切换至所述施 主基站或该施主基站下属第二中继站。
S32a: 所述施主基站在不向核心网设备发送切换通知的情况下， 向所述第 一中继站发送用户设备上下文释放命令 UE Context Release Command。
本实施例的 DeNB在收到其下属 RN的切换请求后，省略与核心网的信息 交互流程， 即可直接实现对用户设备上下文的释放。
本实施例方法还可进一步包括：所述施主基站接收来自所述第一中继站的 切换申请， 所述切换申请用于请求对所述用户设备执行切换； 所述施主基站可 根据该切换申请确定切换目标，并在确定出用户设备从该基站下属第一中继站 切换至所述基站或该基站下属第二中继站后，在不向核心网设备发送切换申请 的情况下，向所述第一中继站发送切换命令，以指示所述第一中继站进行切换。 该方法可实现将 UE切换至 DeNB 自身或其下属其它 RN， 由于是基站内的切 换过程，即终端从基站下属的中继站切换到基站或者是切换到基站下属的另外 一个中继站， 对于这种切换过程相应的变化， 核心网侧不受到影响。 因此现有 技术中与核心网侧（ MME和 SGW/PGW等）相关的切换流程都可以简化， 节 省信令开销。 另外中继站下的终端在入网时， 施主基站 （ Doner eNB )就可以 获得并存储该 UE相关的一些上下文信息， 如： UE所支持业务对应的 QoS信 息， UE所支持的加密或完整性保护算法等， 因此， 中继站在切换过程中不再 将现有技术中切换相关消息中的内容都告诉 eNB;因此在中继站和基站之间空 中接口上传输的消息内容和一些信令流程可以被简化， 以节省信令开销。
本实施例还可包括： 当施主基站确定用户设备从该施主基站下属第一中继 站切换至该施主基站时，所述施主基站接收来自所述用户设备的无线资源控制 连接重建立完成消息 R C Connection Reconfiguration Complete ,在不向核心网 设备发送切换通知 Handover Notify的情况下， 向所述第一中继站发送用户设 备上下文释放命令；当施主基站确定用户设备从该施主基站下属第一中继站切 换至该施主基站下属第二中继站时，所述施主基站接收来自所述第二中继站的 切换通知 Handover Notify,在不向核心网设备发送切换通知的情况下， 向所述 第一中继站发送用户设备上下文释放命令。当施主基站确定用户设备从该施主 基站下属第一中继站切换至该施主基站时，所述施主基站还可接收来自所述第 一中继站的基站状态转移消息 eNB Status Transfer, 在不向核心网设备发送基 站状态转移消息的情况下，向所述第一中继站发送移动管理实体状态转移消息 MME Status Transfer; 当施主基站确定用户设备从该施主基站下属第一中继站 切换至该施主基站下属第二中继站时，所述施主基站可接收来自所述第一中继 站的基站状态转移消息 eNB Status Transfer, 在不向核心网设备发送基站状态 转移消息的情况下， 向所述第二中继站发送移动管理实体状态转移消息 MME Status Transfer 0通过上述流程，施主基站可进一步简化与核心网设备的信令交 互流程， 节省信令开销。
在另一种情况下，如果施主基站进行切换判决，确定需要对用户设备进行 切换， 可首选地尝试将用户设备从该施主基站自身切换至其下属中继站，将该 施主基站下属的中继站确定为用户设备的切换目标，并在不向核心网设备发送 切换申请的情况下， 向用户设备发送切换命令。 同样地， 在本实现方案中， 在 将用户设备从一个基站切换至基站下属中继站时，也可节省与和信网侧的信令 交互流程。
路径更新流程简化： 当终端位于中继站下， 终端的数据传输路径为终端网 关 -施主基站-终端的服务中继站。 当位于施主基站下终端的数据传输路径为终 端网关至施主基站。对于上述切换情况（如终端从一个中继站切换到该中继站 的施主基站，或者切换到同一个施主基站下的另一个中继站，或者终端从施主 基站切换到该基站下的中继站）， 切换后， 终端的数据传输路径从核心网的角 度， 可以保持不变即依然还是网关至基站， 由此现有技术中的与网关相关的路 径更新流程可以省略。 由于基站具有 proxy的功能， 因此从网关侧看来， 终端 变， 但是基站在收到终端网关信息后， 能够确认该数据属于哪个终端， 其服务 站点是哪个。
图 3b为本发明的实施例提供的另一种切换方法的示意图， 该方法包括：
S31b:施主基站确定用户设备从所述施主基站切换至该施主基站下属中继 站；
S32b: 所述施主基站在不向核心网设备发送切换通知的情况下，释放所述 用户设备的上下文。
该实施例可不与核心网设备交互大量信令， 完成对 UE切换， UE上下文 释放， 简化切换流程。本实施例的施主基站与核心网其它信令流程以及相应切 换申请消息的简化可参考图 3a所示的步骤， 这里不再做重复描述。 例如， 该 施主基站可在不向核心网设备发送切换申请的情况下，向用户设备发送切换命 令， 以指示所述用户设备进行切换。所述简化流程不仅限于基站与中继站间的 切换， 当终端在家庭网关下的 2个家庭基站间切换时，也可采用类似的简化流 程， 本实施例不作为限定。
图 4为本发明的实施例提供的一种切换方法的简要流程示意图，该方法包 括：
S41： 源中继站接收用户设备的测量报告（ Measurement Report )。
S42: 源中继站进行切换判决， 确定需要对所述用户设备进行切换。
S43:源中继节点向其施主基站发送切换申请（ S1AP: Handover Required ), 请求对所述用户设备执行切换。
S44: 所述施主基站在未向核心网设备发送切换申请的情况下， 向目标中 继站发送切换请求消息 （S1AP: Handover Request )„
S45:所述施主基站接收来自所述目标中继站的切换请求响应消息（ S1AP:
Handover Request ACK )。
S46a: 所述施主基站不必接收来自核心网设备的切换命令， 向所述源中继 站发送切换命令（ S1AP: Handover Command ), 指示进行切换操作。
S46b: 可选步骤， 源中继站可处理緩存中的数据， 将其传输给目标站点， 即目标中继站。
S47a: 所述源中继站向用户设备发送无线资源控制连接重配置 （R C Connection Reconfiguration )消息，或者是发送切换命令 Handover Command 消 息（该消息为 RRC消息）， 让用户设备切换到目标小区去。
S47b: 用户设备接收到切换命令后， 脱离旧小区向目标小区进行同步。 S48: 所述源中继站向所述施主基站发送基站状态转移消息（ S1AP: eNB Status Transfer )。 该步骤为可选步骤。
S49: 所述施主基站不向核心网设备发送基站状态转移消息， 向所述目标 中继站发送移动管理实体状态转移消息 （ S 1 AP： MME Status Transfer )。 该步 骤为可选。
S410a: 源中继站通过基站将用户设备数据转发到目标中继站中。 该步骤 为可选。
S410b: 所述目标中继站緩存来自源中继站的数据包（Packet )。 该步骤为 可选。
S411：用户设备向所述目标中继站发送无线资源控制连接重建立完成消息 ( RRC Connection Reconfiguration Complete )c 可以理解， 如果此前用户设备 接收到的是切换命令 Handover Command 消息（该消息为 RRC消息），那么回 复的是切换命令完成 Handover Command compelete消息 （该消息为 RRC消 息）。
S412: 所述目标中继站向所述施主基站发送切换通知（ Handover Notify )。 S413: 所述施主基站在未向核心网设备发送切换通知的情况下， 向源中继 站发送用户设备上下文释放命令 UE Context Release Command。
S414a: 源中继站释放与用户设备相关的资源。
S414b: 源中继站释放与用户设备相关的资源后， 向所述施主基站返回用 户设备上下文释放完成消息 UE Context Release Complete。
本实施例通过省略 DeNB与核心网设备（具体可以为 MME )的信息交互 过程， 可简化切换流程和节省切换中的信令开销。 需要说明的是， 上述流程只 是对 UE完整切换过程的简要描述，具体实现中还包括本实施例已经省略的其 它过程， 但省略的过程均为现有技术， 不影响本实施例的实施， 而且该方法针 对的是 UE从 DeNB下属一个 RN切换至该 DeNB下属另一 RN的场景， 对于 UE从 RN1切换至其所属 DeNB、 或者从 DeNB切换至其下属 RN或者其它相 类似的应用场景， UE的切换过程可参照本实施例执行， 具体可参见后续的介 绍。
对于可选步骤，特别地针对基站能够緩存终端数据，有可能做到终端切换 时， 基站依然保留终端的数据， 而没有必要进行数据转发过程。 由此与数据转 发过程相关的流程可以省略。 上述可选步骤， 可以选择性执行部分或者全部。
上述流程中， 从中继站的角度， 以为基站发来的 S1消息是 MME发来的 消息，即中继站以为其直接与 MME通信。实际上基站作为一个 proxy (代理）。 可选地， 上述流程中， 从中继站角度， 它认为从 MME发来的消息实际上是基 站产生和发送的， 由于该消息的内容基本上都是基站能够获知的， 因此基站能 够产生这样的消息。如果该消息中的某项基站侧没有保留，基站可以通过向核 心网 （如 MME， GW等）获取。 例如安全信息基站侧没有保留， 那么基站可 以从 MME侧为该终端获得一个新的安全信息 （如新 NCC和 NH )。 或者由于 终端的切换， MME侧可能需要知道终端的某些信息变换， 或者需要知道终端 切换后目标小区的变化， 那么基站可以另行通知 MME， 例如安全信息， 终端 切换后目标小区中终端对应的安全密钥需要发生变化，需要将这个变化的安全 密钥要通知 MME。
对于本发明实施例中中继站 RN需要将用户设备 UE从中继站 RN切换至 该中继站的施主基站 DeNB 或该施主基站下属其它中继站， 或者对于 DeNB 使用 X2信令向其它基站发送切换请求消息 Handover Request的场景， 所述中 继站发送的切换申请 Handover Required可进行简化， 具体所述切换申请中包 括： 消息类型 Message Type、 SI链接标识、用户设备标识、切换类型 Handover Type, 切换原因 Cause和切换目标标识 Target ID， 且所述切换申请不包括： 可 用直接转发路径信息 Direct Forwarding Path Availability和单一无线语音呼叫连 续性切换指示信息 SRVCC ( Single Radio Voice Call Continuity ) HO Indication 进一步地， 所述切换申请中还可包括或不包括以下内容： 移动台分类标记 MS Classmark, 闭合用户群小区标识 CSG Id、 小区接入模式 Cell Access Mode 和增强无线接入承载的最大号码 max no of E-RABs。 所述切换申请中还可包 括： 源至目标透明容器 Source to Target Transparent Container, 所述 Source to Target Transparent Container内包括： 无线资源控制容器 RRC Container, 增强 无线接入承载信息表 E-RABs Information List, 增强无线接入承载信息条目 E-RABs Information Item, 增强无线接入 载标识 E-RAB ID和用户设备历史 信息 UE History Information,且所述 Source to Target Transparent Container不包 括下行转发消息 DL Forwarding。 进一步地， 所述 RRC Container可包括或不 包括以下内容： 无线资源管理配置信息 rrm-Config、 as配置信息 as Config、 用 户设备无线接入能力信息 UE-Radio Access Capability Info和 as Context。 以上实施例针对的是 SI消息的切换流程， 类似流程同理适用于 X2切换 的过程简化。 只是中继站与基站之间的消息使用 X2消息。 此时 X2切换过程 与核心网相关的流程， 如路径更新（path switch )过程可以省略。 S43和 S44 中的消息为 X2AP: HO request消息， S45和 S46为 X2AP: HO request ACK 消息， S48和 S49为 X2AP: SN status transfer消息， S413为 X2AP: UE context release 消息。 在 X2流程中可只有 S413没有 S414b步骤。 对于 S412， 是所述 目标中继站向所述施主基站发送 UE context release 消息。
现有技术中为了安全隔离， 终端切换过程中， 目标站点在路径更新 （如 S1切换中的步骤 S212-S216 )的过程中， 通过 MME获得一个新的 NCC ( Next Hop Chaining Count, 下一跳链接计算）， 同时 MME利用该 NCC计算出一个 新 NH ( Next Hop )参数， 由此目标站点在路径更新过程中获得了新 NCC和 新 NH， 通过这两个新参数计算出新密钥 KeNB*。 NH参数在 MME与 UE中 计算得出， eNB没有计算 NH参数的能力。 如果省略路径更新过程，那么基站可向 MME发起一个更新 NCC的过程， 由此获得新的 NCC和 NH给目标站点， 或者自己本身 （当切换目标是基站本 身时）获得新的 NCC和 NH。 基站向 MME发起更新 NCC的过程时， 当基站 从 MME获得新 NCC和新 NH后， 基站将这个信息发送给目标站点或者给自 身（当目标站点是基站本身 )进行密钥更新使用。 发送过程可以在 UE确认终 端成功切换到目标小区中时（如收到目标站点的切换确认信息， 特别地如在本 发明实施例中 S413基站收到目标站点的 X2AP: UE context release 消息）进 行， 也可以在其他时刻进行。 当然基站也可以自身具备 MME 的产生或更新 NCC的功能， 给目标站点提供新的 NCC和 NH。
上述， 可以通过 S412 UE context release 消息实现； 或者 S412步骤前还 可包含中继站发送的路径更新消息 Path Swich消息，基站收到该消息后，可从 MME中获取新 NCC和 NH给该中继站， 还可以是自己配置了新 NCC和 NH 给中继站。 如果^^站自己配置， 那么基站可能还需要将新的 NCC和 NH提 供给 MME。 总之基站获得新 NCC和 NH后， 将这个信息提供给目标站点。 或者是 S412 后， 基站确认了终端已经成功切换到目标站点， 由此基站可从 MME中获得或者自己配置新的 NCC和 NH给中继站。 如果是基站配置， 那 么基站可能还需要将新的 NCC和 NH提供给 MME。 总之基站获得新 NCC和 NH后， 将这个信息提供给目标站点。
上述安全密钥更新过程适用于所有省略路径更新过程的场景，也可适用于 其他网络和系统。 例如上述基站还可以是 home ( e ) NB或者是 home ( e ) NB Gateway, 或者是 pico cell的基站或者网关等。
可以理解， S1切换和 X2切换的具体过程存在一定差异，但这种不同只是 简单的变形， 本领域技术人员能够从图 4中得到 X2切换的流程图， 本实施例 对此不进行限定
图 5为本发明的实施例提供的另一种切换方法的简要流程示意图，该方法 于图 4所示方法类似， 只是实现从中继站切换至该中继站的施主基站， 如图 5 所示， 可包括：
S51 : 用户设备向中继站发送测量报告。
S52: 中继站进行切换判决。
S53: 中继站向其施主基站发送切换申请（ S1AP: Handover Required ) S54: 所述施主基站向所述中继站发送切换命令 (SI AP: HO command 消 息)。
S55: 所述中继站可处理緩存中的数据， 将其传输给所述施主基站。 该步 骤为可选。
S56 : 所述中继站向用户设备发送无线资源控制连接重配置 （ R C Connection Reconfiguration )消息，或者是发送切换命令 Handover Command 消 息（该消息为 RRC消息）， 让用户设备切换到目标小区去。
S57: 用户设备与目标小区执行同步接入。
S58:所述中继站向所述施主基站发送基站状态转移消息 S1AP: eNBstatus transferc
S59: 所述中继站向所述施主基站转发存储在中继站中的终端的数据。 该 步骤可选。 例如如果施主基站一直保存该终端的数据， 直到确认终端接收到后 才丟弃， 那么切换过程中基站可以不需要中继转发的数据。
S510: 所述施主基站緩存来自中继站的数据包。
S511 : 用户设备同步到目标小区后，发送无线资源控制连接重配置完成消 息给施主基站， 确认成功接入到施主基站。
S512: 所述施主基站向中继站发送用户设备上下文释放命令 S1AP: UE context Release Command。
S513: 所述中继站释放与该终端相关的资源和上下文信息 （ Context )。 S514 : 所述中继站向所述施主基站发送用户设备上下文释放完成消息
S1AP: UE context Release Complete。 上述流程主要针对 S1切换流程， 但类似方法同理适用于 X2切换的过程 简化， 即 X2切换过程中的路径更新（path switch )过程可以省略， 只是中继 站与基站之间的消息使用 X2消息。 S53的消息可为 X2AP: HO request消息，
S54可为 X2AP: HO request ACK消息， S58为 X2AP: SN status transfer消息,
S512为 X2AP: UE context release 消息。 在 X2流程中可只有 S512没有 S514 步骤。 可以理解， S1切换和 X2切换的具体过程存在一定差异， 但这种不同只 是简单的变形， 本领域技术人员能够从图 5中得到 X2切换的流程图， 本实施 例对此不进行限定
由于与前一实施例类似， 本实施例中对每一步骤进行简略描述， 具体实现 可参见前一实施例。 由于本实施例中基站简化了与核心网的信令交互流程，使 得切换复杂度降低。
图 6为本发明的实施例提供的另一种切换方法的简要流程示意图，该方法 与图 4所示方法类似， 只是实现从施主基站切换至该施主基站下属中继站，如 图 6所示， 可包括：
S61 : 用户设备向其服务基站发送测量报告。
S62: 施主基站进行切换判决。
S63： 施主基站向其下属中继站发送切换请求消息 （ S1AP： Handover
Request )。
S64:所述中继站向所述施主基站发送切换请求响应消息（ S1AP: Handover Request ACK )c S65: 所述施主基站緩存数据并发送给中继站。
S66 : 所述施主基站向用户设备发送无线资源控制连接重配置 （R C Connection Reconfiguration )消息，或者是发送切换命令 Handover Command 消 息（该消息为 RRC消息）， 让用户设备切换到目标小区去。
S67: 用户设备向目标小区同步接入。
S68: 所述施主基站向所述中继站发送移动管理实体状态转移消息 MME 状态转移消息 （S1AP: MME status transfer )。。
S69: : 所述施主基站向所述中继站转发数据。
S610: 所述中继站緩存来自施主基站的数据。
S611 : 用户设备同步到目标小区后，发送无线资源控制连接重配置完成消 息给中继站， 确认成功接入到该中继站。
S612: 所述中继站向施主基站发送用户设备上下文释放命令（ S1AP: UE Context Release Command )。
S613: 所述施主基站释放资源。
S614 : 所述施主基站向所述中继站发送用户设备上下文释放完成消息
( S1AP: UE Context Release Complete )。
由于于前一实施例类似， 本实施例中对每一步骤进行简略描述， 具体实现 可参见前一实施例， 以实现切换流程的简化。
上述几个实施例都是采用 S1 消息进行切换， 在实际应用中也可采用 X2 消息实现切换流程。 以图 6对应的实施例为例， 切换申请可以不是 S1AP: Handover Required, 而由 X2: Handover Request代替。 其它的切换清求消息、 切换响应消息和切换命令等消息都可以通过 X2消息来实现， 虽然采用的消息 类型有所改变， 并可能由此引起实施例流程的微调，但这些调整并未改变本发 明的实质， 本实施例对此不进行具体展开。 X2: Handover Request消息由 RN 发送给基站时， 由于基站对中继站下属终端信息是可获得的， 因此现有技术中 X2： Handover Request消息需要携带的内容可以省略， 其中该消息中可包含的 信息为： 切换原因 Cause, 目标小区 ID ( Target Cell ID ), RRC 上下文（R C Context )， 终端历史信息 （ UE History Information )。
上述流程主要针对 SI切换流程， 但类似方法同理适用于 X2切换的过程 简化。 只是中继站与基站之间的消息使用 X2消息。 此时 X2切换过程中的路 径更新 （ path switch )过程可以省略。 S63中的消息为 X2AP: HO request消 息， S64为 X2AP: HO request ACK消息， S68为 X2AP: SN status transfer消 息， S612为 X2AP: UE context release 消息。 在 X2流程中可以只有 S612而 没有 S614步骤。 可以理解， S1切换和 X2切换的具体过程存在一定差异， 但 这种不同只是简单的变形， 本领域技术人员能够从图 6中得到 X2切换的流程 图， 本实施例对此不进行限定。
现有技术中为了安全隔离， 终端 X2切换过程中， 在终端成功接入到目标 站点后， 目标节点进行路径更新的过程中， 通过 MME获得一个新的 NCC， 同时 MME利用该 NCC计算出一个新 NH参数， 由此目标站点在路径更新过 程中获得了新 NCC和新 NH， 通过这两个新参数计算出新密钥 KeNB*。 NH 参数在 MME与 UE中计算得出， eNB没有计算 NH参数的能力。 在 S1切换 过程中通过 MME发送的切换请求消息给目标站点， 该切换请求消息携带了 MME通过本地计算新的 NCC， 以及由 NCC计算的 NH。
由于切换优化， 与核心网相关的流程都简化（例如省略路径切换过程）， 那么基站可向 MME发起一个更新 NCC的过程，由此获得新的 NCC和 NH给 目标站点， 或者基站可自己本身 （当切换目标是基站本身时）获得新的 NCC 和 NH。 基站向 MME发起更新 NCC的过程时， 当基站从 MME获得新 NCC 和新 NH后，基站将这个信息发送给目标站点或者给自身（当目标站点是基站 本身 )进行密钥更新使用。
上述过程可以在 UE确认终端成功切换到目标小区中时（如收到目标站点 的切换确认信息， 特别地如在本发明实施例中 S612 基站收到目标站点的 X2AP: UE context release 消息）进行， 也可以在其他时刻进行。 上述对于基 站从 MME中获得新 NCC和 NH过程，另外一种实施例请见图 7详细的描述。
当然基站也可以自身具备 MME的产生或更新 NCC的功能， 给目标站点 (例如 RN2，或者目标站点是基站本身）提供新的 NCC和 NH。可以通过 S612 UE context release 消息实现； 或者 S612步骤前还可包含中继站发送的路径更 新消息 Path Swich消息，基站收到该消息后，可从 MME中获取新 NCC和 NH 给该中继站， 还可以是基站自己配置了新 NCC和 NH给中继站。 如果是基站 自己配置， 那么基站可能还需要将新的 NCC和 NH提供给 MME。 总之基站 获得新 NCC和 NH后， 将这个信息提供给目标站点。 或者是 S612后， 基站确 认了终端已经成功切换到目标站点，由此基站可从 MME中获得或者自己配置 新的 NCC和 NH给中继站。 上述对于基站自己产生或者更新 NCC, 获得新 NCC和 NH过程， 另外一种实施例请见图 8详细的描述。
上述安全密钥更新过程适用于切换优化流程特别是所有省略路径更新过 程的场景， 也可适用于其他网络和系统。 例如上述基站还可以是 home ( e ) NB或者是 home ( e ) NB Gateway, 或者是 pico cell的基站或者网关等。 当 上述基站是 home ( e ) NB Gateway时， 上述中继站还可以是 Home ( e ) NB， 上述的目标站点可以是 home ( e ) NB。
如果基站或者 home ( e ) NB GW具有所述 MME产生或者计算 NCC或 NH的功能， 那么基站可以直接发送新 NCC和 NH给目标站点 （如中继站， home ( e ) NB等）。
上述有关于安全隔离步骤是可选步骤。
可以理解， S1切换和 X2切换的具体过程存在一定差异，但这种不同只是 简单的变形， 本领域技术人员能够从图 6中得到 X2切换的流程图， 本实施例 对此不进行限定
如图 7a所示，为本发明实施例提供的一种基站从 MME处更新 NCC的过 程的示意图， 包括：
S71a: 基站向移动管理实发送密钥更新请求； 特别地， 基站在收到源中继 站 RN1发来的切换申请消息后， 向移动管理实发送密钥更新请求； 具体地， 中继站 1 发送切换申请消息给基站； 对于 S1 接口消息， 切换申请消息是 Handover Required消息；对于 X2接口消息，切换申清消息是 Handover Request 消息。
S72a: 所述移动管理实体在本地将 NCC加 1， 并计算出新的 NH值， S73a: 所述移动管理实体将新计算出的 {NH， NCC}发送给基站；
S74a: 基站将所述下一跳链接计算和下一跳参数提供给目标站点； 特别地 对于 S1 切换， 所述下一跳链接计算和下一跳参数信息包含在 S1 消息： HO request消息中。 对于 X2切换， 所述下一跳链接计算和下一跳参数信息包含在 X2消息： HO request消息中。
S75a: 目标站点 （如中继站 RN2 )， 根据收到的 NCC， NH计算 KeNB或 者 KeNB*， 并与 NCC关联保存。
进一步地， 所述方法还包括： 目标站点 （如中继站 RN2 )发送切换请求 确认命令给基站，该切换请求确认命令中包含新 NCC信息。对于 S1接口消息， 切换请求确认命令是 Handover Request ACK消息； 对于 X2接口消息， 切换申 请消息是 Handover Request ACK消息。 基站发送切换请求确认命令给源中继 站 RN1， 该切换请求确认命令中包含新 NCC信息。 RN1发送无线资源控制连 接重建立消息给终端， 让终端切换到目标站点 RN2， 该消息中包含了新 NCC 信息。 终端根据收到的 NCC， 同步 NH， 计算 KeNB或者 KeNB*， 并与 NCC 关联保存。
如图 7b所示，为本发明实施例提供的一种基站更新 NCC的过程的示意图， 包括：
S71b:中继站 1发送切换申请消息给基站； 对于 S1接口消息， 切换申请消 息是 Handover Required消息； 对于 X2接口消息， 切换申请消息是 Handover Request消息。
特别地， 在基站收到源中继站的切换请求， 如 S1 消息： HO Required, 或者 X2消息： HO request 中包含 UE安全能力、 源中继站侧使用的加密算法 和完整性算法， 以及 KeNB*， NCC。
S72b : 在基站收到源中继站 RN1 的切换申请消息 （如 S1 消息: HO Required, 或者 X2消息 ： HO request )后， 基站在本地将 NCC加 1， 并计算 出新的 NH值。
S73b: 基站在切换请求消息里将新计算出的 {NH， NCC}发送给目标站点 如中继站 RN2。 对于 S1接口消息， 切换请求消息是 S1AP: Handover Request 消息； 对于 X2接口消息， 切换申请消息是 X2 AP： Handover Request消息 .
S74b: 目标站点 （如中继站 RN2 )， 根据收到的 NCC、 NH计算 KeNB， 并与 NCC关联保存。
S75b: 目标站点 （如中继站 RN2 )发送切换请求确认命令给基站， 该切 换请求确认命令中包含新 NCC信息。对于 S1接口消息，切换请求确认命令是 Handover Request ACK消息； 对于 X2接口消息， 切换申请消息是 Handover Request ACK消息。
S76b: 基站发送切换请求确认命令给源中继站 RN1， 该切换请求确认命 令中包含新 NCC信息。
S77b: RN1 发送无线资源控制连接重建立消息给终端， 让终端切换到目 标站点 RN2， 该消息中包含了新 NCC信息。 S78b: 终端根据收到的 NCC， 同步 NH， 计算 KeNB或者 KeNB*， 并与
NCC关联保存。 另外， 可选地， 基站将新计算出的 {NH， NCC}发送 MME。 该步骤可以发 生在 S72b之后。 上述实施例可以适用于 Home ( e ) NB 的场景， 上述实施例中的基站相 当于 Home ( e ) NB GW, 上述实施例中的中继站 1相当于 Home ( e ) NB1， 上述实施例中的中继站 2相当于 Home ( e ) NB2。 本发明的所有实施例可以适用于 Home ( e ) NB的场景， 上述实施例中 的基站相当于 Home ( e )NB GW,上述实施例中的中继站 1相当于 Home ( e )
NB1， 上述实施例中的中继站 2相当于 Home ( e ) NB2。
图 8为本发明的实施例提供的一种基站的示意图， 所述基站 80包括： 确定单元 801， 用于确定用户设备从该基站 80下属第一中继站 81切换至 所述基站 80或该基站 80下属第二中继站 82。 释放单元 802， 用于当所述确定单元 801确定用户设备从所述第一中继站 81切换至所述基站 80或所述第二中继站 82，在不向核心网设备发送切换通知 的情况下， 向所述第一中继站 81 发送用户设备上下文释放命令 UE Context Release Commando
本实施例的基站 80 在切换过程中可以简化与核心网设备（具体可以为
MME ) 的切换流程并节省切换中的信令开销。
进一步地， 所述基站 80还可包括： 请求接收单元， 用于接收来自所述第 一中继站 81的切换申请， 所述切换申请用于请求对用户设备执行切换； 命令 发送单元， 用于在不向核心网设备发送切换申请的情况下， 向所述第一中继站 81发送切换命令， 以指示所述第一中继站 81进行切换。
所述基站 80还可包括： 状态转移单元， 用于：
当确定单元 801确定用户设备所述第一中继站 81切换至所述基站 80时， 接收来自所述第一中继站 81的基站状态转移消息 eNB Status Transfer,在不向 核心网设备发送基站状态转移消息的情况下， 向所述第一中继站 81发送移动 管理实体状态转移消息 MME Status Transfer;
当确定单元 801确定用户设备从所述第一中继站 81切换至所述第二中继 站 82时，接收来自所述第一中继站 81的基站状态转移消息，在不向核心网设 备发送基站状态转移消息的情况下， 向所述第二中继站 81发送移动管理实体 状态转移消息。
进一步地， 所述确定单元 801， 还用于确定用户设备从所述基站 80切换 至该基站 80下属第三中继站； 所述释放单元， 还用于当所述确定单元 801确 定用户设备从所述基站 80切换至所述第三中继站时， 在不向核心网设备发送 切换通知的情况下， 释放所述用户设备的上下文。
所述基站 80还可包括： 参数获取单元， 被配置为：
当确定单元 801确定用户设备从所述第一中继站 81切换至所述第二中继 站 82时，向核心网侧设备获取下一跳参数或者利用下一跳链接计算 NCC生成 所述下一跳参数， 并将所述下一跳参数提供给所述第二中继站 82; 或者
当确定单元 801 确定用户设备从所述第一中继站 81 切换至所述基站 80 时， 向核心网侧设备获取该下一跳参数或者利用下一跳链接计算 NCC生成所 述下一跳参数， 并根据下一跳参数产生新密钥 KeNB*。
通过在基站中实现所述功能，可简化终端切换时基站与核心网的信令交互 过程。
可以理解，本发明实施例中的基站和中继站不仅包括 LTE、 Wimax、 CDMA 等各类基站、 中继站。 所述基站还可以是家庭网关 home eNB Gateway; 所述 中继站可以为家庭基站 Home eNB。 当利用家庭网关代替所述基站， 或利用家 庭基站代替所述中继站时， 所述方法流程仅是执行主体变化，技术方案实质未 变。
图 9为本发明实施例提供的另一种切换方法的示意图， 可包括：
S91 : 家庭网关接收该家庭网关下属第一家庭基站的切换申请， 所述切换 申请用于请求对用户设备执行切换；
S92: 家庭网关确定所述用户设备从所述第一家庭基站切换至该家庭网关 下属第二家庭基站；
S93: 所述家庭网关在不向核心网设备发送切换申请的情况下， 向所述第 一家庭基站发送切换命令， 以指示所述第一家庭基站进行切换。
所述方法可进一步包括：
所述家庭网关向核心网侧设备获取向核心网侧设备获取下一跳链接计算 NCC 或者下一跳参数， 并将所述下一跳链接计算或者下一跳参数提供给所述 第二家庭基站； 或者
所述家庭网关向核心网侧设备获取下一跳链接计算或者下一跳参数，并根 据根据收到的一跳链接计算或者下一跳参数， 计算密钥 KeNB或者 KeNB*， 并将计算得到的密钥与下一跳链接计算关联保存。
图 10为本发明实施例提供的一种家庭网关的示意图， 可包括：
接收单元 101， 用于接收该家庭网关下属第一家庭基站的切换申请， 所述 切换申请用于请求对用户设备执行切换；
确定单元 102， 用于确定所述用户设备从所述第一家庭基站切换至该家庭 网关下属第二家庭基站；
释放单元 103， 用于在不向核心网设备发送切换通知的情况下， 向所述第 一家庭基站发送用户设备上下文释放命令。
图 11为本发明实施例提供的另一种基站的示意图， 包括：
确定单元 111， 用于确定用户设备从所述施主基站切换至该施主基站下属 中继站；
释放单元 112， 用于在不向核心网设备发送切换通知的情况下， 释放所述 用户设备的上下文。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程， 是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算 机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。 其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（Read-Only Memory, ROM )或随机存储记忆体 ( Random Access Memory, RAM )等。
以上所述仅为本发明的几个实施例，本领域的技术人员依据申请文件公开 的可以对本发明进行各种改动或变型而不脱离本发明的精神和范围。本领域普 况下可以互相结合形成新的实施例。

Claims

权 利 要 求
1、 一种对终端进行切换的处理方法， 其特征在于， 包括：
基站确定用户设备的切换目标位于所述基站的覆盖范围内；
所述基站在未与核心网设备进行信令交互的情况下，直接执行对所述用户 设备的切换。
2、 如权利要求 1所述的方法， 其特征在于， 所述基站确定用户设备的切 换目标位于所述基站的覆盖范围内包括：所述基站确定用户设备从该基站下属 第一中继站切换至所述基站或该基站下属第二中继站；
所述基站在未与核心网设备进行信令交互的情况下，执行对所述用户设备 的切换包括： 所述基站在不向核心网设备发送切换通知的情况下， 向所述第一 中继站发送用户设备上下文释放命令 UE Context Release Command。
3、 如权利要求 2所述的方法， 其特征在于， 所述基站在未与核心网设备 进行信令交互的情况下， 执行对所述用户设备的切换还包括：
所述基站在向所述第一中继站发送 UE Context Release Command之前，接 收来自所述第一中继站的切换申请，所述切换申请用于请求对所述用户设备执 行切换； 且所述基站在不向核心网设备发送切换申请的情况下， 向所述第一中 继站发送切换命令， 以指示所述第一中继站进行切换。
4、 如权利要求 2或 3所述的方法， 其特征在于，
如果所述基站确定用户设备从所述第一中继站切换至所述基站，所述基站 在未与核心网设备进行信令交互的情况下， 执行对所述用户设备的切换还包 括：
所述基站在向所述第一中继站发送 UE Context Release Command之前，接 收来自所述第一中继站的基站状态转移消息 eNB Status Transfer, 在不向核心 网设备发送基站状态转移消息的情况下，向所述第一中继站发送移动管理实体 状态转移消息 MME Status Transfer
5、 如权利要求 4所述的方法， 其特征在于， 还包括：
所述基站向核心网侧设备获取下一跳链接计算或者下一跳参数，根据所述 下一跳链接计算或下一跳参数， 计算密钥 KeNB或者 KeNB*， 并将计算得到 的密钥与下一跳链接计算关联保存。
6、 如权利要求 2或 3所述的方法， 其特征在于，
如果所述基站确定用户设备从所述第一中继站切换至所述第二中继站，所 述基站在未与核心网设备进行信令交互的情况下，执行对所述用户设备的切换 还包括：
所述基站在向所述第一中继站发送 UE Context Release Command之前，接 收来自所述第一中继站的基站状态转移消息，在不向核心网设备发送基站状态 转移消息的情况下， 向所述第二中继站发送移动管理实体状态转移消息。
7、 如权利要求 6所述的方法， 其特征在于， 还包括：
所述基站向核心网侧设备获取下一跳链接计算 NCC或者下一跳参数 NH， 并将所述下一跳链接计算或者下一跳参数提供给所述第二中继站。
8、 如权利要求 6所述的方法， 其特征在于， 还包括： 基站在收到第一中继站的切换申请消息后，将下一跳链接计算 NCC加 1， 并计算出新的下一跳参数 NH值； 基站在切换请求消息里将新计算出的所述下一跳参数 NH 和下一跳链接 计算 NCC发送给第二中继站。
9、 如权利要求 1所述的方法， 其特征在于， 所述基站确定用户设备的切 换目标位于所述基站的覆盖范围内包括：所述基站确定用户设备从所述基站切 换至该基站下属中继站；
所述基站在未与核心网设备进行信令交互的情况下，执行对所述用户设备 的切换包括： 所述基站在不向核心网设备发送切换通知的情况下，释放所述用 户设备的上下文。
10、 如权利要求 9所述的方法， 其特征在于， 所述基站在未与核心网设备 进行信令交互的情况下， 执行对所述用户设备的切换还包括：
在所述基站在不向核心网设备发送切换通知的情况下，释放所述用户设备 的上下文之前， 所述基站在不向核心网设备发送切换申请的情况下， 向用户设 备发送切换命令， 以指示所述用户设备进行切换。
11、 一种基站， 其特征在于， 包括：
确定单元， 用于确定用户设备的切换目标位于所述基站的覆盖范围内； 释放单元， 用于在未与核心网设备进行信令交互的情况下， 直接执行对所 述用户设备的切换。
12、 如权利要求 11所述的基站， 其特征在于， 所述确定单元， 具体用于 确定用户设备从该基站下属第一中继站切换至所述基站或该基站下属第二中 继站；
释放单元，具体用于当所述确定单元确定用户设备从所述第一中继站切换 至所述基站或所述第二中继站后， 在不向核心网设备发送切换通知的情况下， 向所述第一中继站发送用户设备上下文释放命令 UE Context Release Commando
13、 如权利要求 12所述的基站， 其特征在于， 还包括：
请求接收单元， 用于接收来自所述第一中继站的切换申请， 所述切换申请 用于请求对用户设备执行切换；
命令发送单元， 用于在不向核心网设备发送切换申请的情况下， 向所述第 一中继站发送切换命令， 以指示所述第一中继站进行切换。
14、 如权利要求 12所述的基站， 其特征在于， 还包括：
状态转移单元， 用于：
当确定单元确定用户设备从所述第一中继站切换至所述基站时，接收来自 所述第一中继站的基站状态转移消息 eNB Status Transfer, 在不向核心网设备 发送基站状态转移消息的情况下，向所述第一中继站发送移动管理实体状态转 移消息 MME Status Transfer;
当确定单元确定用户设备从所述第一中继站切换至所述第二中继站时，接 收来自所述第一中继站的基站状态转移消息，在不向核心网设备发送基站状态 转移消息的情况下， 向所述第二中继站发送移动管理实体状态转移消息。
15、 如权利要求 11所述的基站， 其特征在于，
所述确定单元，具体用于确定用户设备从所述基站切换至该基站下属第三 中继站；
所述释放单元，还用于当所述确定单元确定用户设备从所述基站切换至所 述第三中继站时， 在不向核心网设备发送切换通知的情况下，释放所述用户设 备的上下文。
16、 一种对终端进行切换的处理方法， 其特征在于， 包括：
家庭网关接收该家庭网关下属第一家庭基站的切换申请，所述切换申请用 于请求对用户设备执行切换；
家庭网关确定所述用户设备从所述第一家庭基站切换至该家庭网关下属 第二家庭基站；
所述家庭网关在不向核心网设备发送切换申请的情况下，向所述第一家庭 基站发送切换命令， 以指示所述第一家庭基站进行切换。
17、 如权利要求 16所述的方法， 其特征在于， 还包括：
所述家庭网关向核心网侧设备获取下一跳链接计算 NCC 或者下一跳参 数， 并将所述下一跳链接计算或者下一跳参数提供给所述第二家庭基站； 或者 所述家庭网关向核心网侧设备获取下一跳链接计算或者下一跳参数，并根 据所述一跳链接计算或者下一跳参数， 计算密钥 KeNB或者 KeNB*， 并将计 算得到的密钥与下一跳链接计算关联保存。
18、 如权利要求 16所述的方法， 其特征在于， 还包括： 所述家庭网关在收到第一家庭基站的切换申请消息后，将下一跳链接计算
NCC加 1， 并计算出新的下一跳参数 NH值；
所述家庭网关在切换请求消息里将新计算出的下一跳链接计算 NH和下 一跳参数 NCC发送给第二家庭基站。
19、 一种家庭网关， 其特征在于， 包括：
接收单元， 用于接收该家庭网关下属第一家庭基站的切换申请， 所述切换 申请用于请求对用户设备执行切换；
确定单元，用于确定所述用户设备从所述第一家庭基站切换至该家庭网关 下属第二家庭基站；
释放单元， 用于在不向核心网设备发送切换通知的情况下， 向所述第一家 庭基站发送用户设备上下文释放命令。
PCT/CN2011/072588 2010-04-09 2011-04-11 一种对终端进行切换的处理方法、基站和家庭网关 WO2011124162A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010149325.8A CN102215537B (zh) 2010-04-09 2010-04-09 一种切换方法、基站和家庭网关
CN201010149325.8 2010-04-09

Publications (1)

Publication Number Publication Date
WO2011124162A1 true WO2011124162A1 (zh) 2011-10-13

Family

ID=44746605

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072588 WO2011124162A1 (zh) 2010-04-09 2011-04-11 一种对终端进行切换的处理方法、基站和家庭网关

Country Status (2)

Country Link
CN (1) CN102215537B (zh)
WO (1) WO2011124162A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016101263A1 (zh) * 2014-12-26 2016-06-30 华为技术有限公司 通信方法和网元设备

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103108403B (zh) * 2011-11-10 2017-12-22 深圳市中洲科技有限公司 跨基站rrc连接重建方法及系统
CN102685888A (zh) * 2012-03-29 2012-09-19 北京三星通信技术研究有限公司 一种被叫业务的重定向方法和家庭基站
CN103379564B (zh) 2012-04-20 2016-08-03 电信科学技术研究院 一种小区内切换方法及装置
CN103582044B (zh) * 2012-08-10 2018-04-10 华为技术有限公司 一种切换控制方法及装置
CN104429109B (zh) * 2013-07-11 2018-11-16 华为技术有限公司 一种通信方法及装置
CN104349309B (zh) * 2013-07-25 2019-11-12 北京三星通信技术研究有限公司 一种移动通信系统中利用nh、ncc对解决安全问题的方法
CN104717705B (zh) 2013-12-12 2019-08-23 中兴通讯股份有限公司 一种处理选定的ip流量卸载连接的方法及基站
CN107277807B (zh) * 2013-12-27 2020-10-09 华为技术有限公司 一种安全密钥上下文分发方法，移动管理实体及基站
CN106211024A (zh) 2015-04-10 2016-12-07 中兴通讯股份有限公司 信息处理方法及通信节点
CN106211261B (zh) 2015-04-10 2020-10-16 中兴通讯股份有限公司 信息处理方法及通信节点
EP3297328A4 (en) * 2015-05-14 2018-06-13 ZTE Corporation Information processing method and communication node
WO2017078143A1 (ja) * 2015-11-05 2017-05-11 株式会社Ｎｔｔドコモ ユーザ装置、基地局、接続確立方法、及びコンテクスト情報取得方法
CN106900015B (zh) * 2015-12-18 2021-02-12 中兴通讯股份有限公司 一种跨基站切换过程中重建立的处理方法和装置
US10542570B2 (en) 2016-03-15 2020-01-21 Huawei Technologies Co., Ltd. System and method for relaying data over a communication network
US10615844B2 (en) 2016-03-15 2020-04-07 Huawei Technologies Co., Ltd. System and method for relaying data over a communication network
CN107659970A (zh) * 2016-07-25 2018-02-02 普天信息技术有限公司 一种用于s1切换的数据包路径转换方法
CN114040455A (zh) * 2016-08-10 2022-02-11 日本电气株式会社 无线接入网节点、无线终端及其方法
EP3793253A1 (en) 2016-08-10 2021-03-17 NEC Corporation Radio access network node, radio terminal, core network node, and method therefor
CN113676972A (zh) 2016-08-10 2021-11-19 日本电气株式会社 无线接入网节点及其方法
EP3499966A1 (en) 2016-08-10 2019-06-19 Nec Corporation Radio access network node, wireless terminal, and methods for these
CN107770825B (zh) * 2016-08-19 2021-03-16 中兴通讯股份有限公司 一种基于用户文本信息的路径切换方法及装置
CN109644387A (zh) * 2016-09-05 2019-04-16 华为技术有限公司 一种无线通信的方法和装置
CN107889080B (zh) * 2016-09-29 2023-06-06 中兴通讯股份有限公司 一种支持远端用户设备移动性的方法及装置
US10945179B2 (en) 2017-01-10 2021-03-09 Huawei Technologies Co., Ltd. Communication path switching method and device
WO2018188185A1 (zh) * 2017-04-14 2018-10-18 华为技术有限公司 一种远端设备在中继设备间切换的方法及切换装置
CN116367250A (zh) 2017-08-11 2023-06-30 北京三星通信技术研究有限公司 支持切换的方法及相应设备
CN109392043B (zh) * 2017-08-11 2023-04-14 北京三星通信技术研究有限公司 支持切换的方法及相应设备
CN111586765B (zh) * 2019-02-15 2023-01-13 华为技术有限公司 中继通信的方法和装置
CN111726841B (zh) * 2019-03-22 2022-05-24 启碁科技股份有限公司 用于物联网的通信方法及其系统
CN115699873A (zh) * 2020-08-19 2023-02-03 Oppo广东移动通信有限公司 中继节点切换方法、终端设备和网络设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841872A (zh) * 2009-03-17 2010-09-22 大唐移动通信设备有限公司 一种实现小区切换的方法和中继设备
CN101867984A (zh) * 2010-02-26 2010-10-20 新邮通信设备有限公司 长期演进增强系统中的切换方法、施主基站和中继节点
US20100322197A1 (en) * 2009-06-17 2010-12-23 Interdigital Patent Holdings, Inc. Method and apparatus for performing handover with a relay node
CN101938798A (zh) * 2009-07-03 2011-01-05 中兴通讯股份有限公司 一种无线中继系统中终端的移动性管理方法及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374324B (zh) * 2007-08-23 2012-03-14 电信科学技术研究院 一种移动终端实现小区切换的方法、系统及节点设备
CN101453745B (zh) * 2007-11-29 2012-09-19 电信科学技术研究院 一种小区切换过程中的测量方法、透明中继及基站
FI20085194A0 (fi) * 2008-02-29 2008-02-29 Nokia Siemens Networks Oy Menetelmä ja laite kanavanvaihtoproseduuria varten jatkolähetyslaajennuksen sisältävässä tietoliikenneverkossa
CN101626607B (zh) * 2008-07-11 2012-06-27 普天信息技术研究院有限公司 无线通信系统中中继场景下终端切换的方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841872A (zh) * 2009-03-17 2010-09-22 大唐移动通信设备有限公司 一种实现小区切换的方法和中继设备
US20100322197A1 (en) * 2009-06-17 2010-12-23 Interdigital Patent Holdings, Inc. Method and apparatus for performing handover with a relay node
CN101938798A (zh) * 2009-07-03 2011-01-05 中兴通讯股份有限公司 一种无线中继系统中终端的移动性管理方法及系统
CN101867984A (zh) * 2010-02-26 2010-10-20 新邮通信设备有限公司 长期演进增强系统中的切换方法、施主基站和中继节点

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
TEYEB, OUMER ET AL.: "Dynamic Relaying in 3GPP LTE-Advanced Networks", EURASIP JOURNAL ON WIRELESS COMMUNICATIONS AND NETWORKING, vol. 2009, 31 December 2009 (2009-12-31), pages 1 - 11 *
YANG, YANG ET AL.: "Relay Technologies for WiMAX and LTE-Advanced Mobile Systems", IEEE COMMUNICATION MAGAZINE, 31 October 2009 (2009-10-31), pages 100 - 105 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016101263A1 (zh) * 2014-12-26 2016-06-30 华为技术有限公司 通信方法和网元设备

Also Published As

Publication number Publication date
CN102215537B (zh) 2014-06-04
CN102215537A (zh) 2011-10-12

Similar Documents

Publication Publication Date Title
WO2011124162A1 (zh) 一种对终端进行切换的处理方法、基站和家庭网关
US10009798B2 (en) System and method for releasing user equipment context by a home gateway
KR101607738B1 (ko) 다중 핸드오버 준비의 향상
KR102206431B1 (ko) 다수의 E-NodeB들과 사용자 단말 간에 동시 접속을 제공하기 위한 방법 및 시스템
US9179376B2 (en) Relay node handover method, base station, and communication system
US9521600B2 (en) Handover mechanism in cellular networks
EP2351417B1 (en) Network gateway configured to provide a handover, converting and routing function
US9775073B2 (en) Gateway configured to provide a handover, converting and routing function
CN104349419B (zh) 终端多连接的管理方法、装置和系统
CN112088544A (zh) 通过施主基站切换来维持通信和信令接口
WO2014103098A1 (ja) 無線通信システム、基地局、移動局、通信制御方法、及びコンピュータ可読媒体
JP7483898B2 (ja) 通信方法及び装置
WO2011038690A1 (zh) 消息处理方法、装置
WO2016151653A1 (ja) 基地局装置および基地局間ゲートウェイ装置
WO2011000193A1 (zh) 一种无线中继系统中终端的移动性管理方法及系统
US20220141732A1 (en) Method and apparatus for reporting assistant information
WO2012094958A1 (zh) 一种安全隔离的方法和设备
WO2011000192A1 (zh) 一种无线中继系统中的切换方法及系统
WO2011098001A1 (zh) 切换小区时避免路径转换的方法、系统和设备
WO2011020413A1 (zh) 一种应用于无线中继的传输系统及传输方法
US20130301520A1 (en) Mobile communication system, relay-station mobility management apparatus, relay-station mobility control method, and computer-readable medium
WO2012155656A1 (zh) 一种宿主基站、中继节点设备及增强路径转换的方法
KR101324298B1 (ko) 이동통신시스템
JP6067145B2 (ja) Ｘ２プロキシを実現する方法およびシステム
WO2012034454A1 (zh) 一种un接口的承载复用方法及系统

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

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

Country of ref document: EP

Kind code of ref document: A1