WO2012155677A1 - Procédé et système pour assurer la continuité de service lorsqu'un nœud relais dessert un équipement utilisateur - Google Patents

Procédé et système pour assurer la continuité de service lorsqu'un nœud relais dessert un équipement utilisateur Download PDF

Info

Publication number
WO2012155677A1
WO2012155677A1 PCT/CN2012/072889 CN2012072889W WO2012155677A1 WO 2012155677 A1 WO2012155677 A1 WO 2012155677A1 CN 2012072889 W CN2012072889 W CN 2012072889W WO 2012155677 A1 WO2012155677 A1 WO 2012155677A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
relay node
message
management entity
mobility management
Prior art date
Application number
PCT/CN2012/072889
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 中兴通讯股份有限公司
Publication of WO2012155677A1 publication Critical patent/WO2012155677A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular to a method and system for guaranteeing service continuity of a relay node (RN) serving user equipment (UE).
  • RN relay node
  • UE serving user equipment
  • LTE-Advanced Long-Term Evolution advance
  • LTE-Advanced retains the core of LTE for Long-Term Evolution (LTE). Based on this, a series of technologies are used to expand the frequency domain and airspace to improve spectrum utilization and increase system capacity.
  • Wireless Relay is a key technology in LTE-Advanced, designed to extend cell coverage, reduce dead zones in communications, balance load, transfer hotspot services, and save user equipment (UE, User Equipment) The transmission power.
  • the relay node (RN) provides similar functions and services to the accessing UE, and accesses an eNB serving the eNB in a manner similar to the normal UE through the radio interface. It is a Donor eNB, referred to as DeNB.
  • the DeNB is connected to a mobility management entity (MME, Mobility Management Entity).
  • MME Mobility Management Entity
  • the functions provided by the MME for the UE include: non-access stratum signaling, encryption, and integrity protection, and manage mobility of 3GPP users in 2G/3G/LTE networks, including user access control, authentication, and data encryption.
  • the plurality of MMEs serve to serve a common geographic area in which the eNB or DeNB is connected in a mesh structure to a plurality of MMEs in the area.
  • the MME set in the public geographic area constitutes an MME pool, which is also referred to as an MME pool area.
  • the DeNB needs to select an appropriate MME for the RN, and also select a suitable MME for the UE served by the RN.
  • the DeNB When selecting the MME for the RN and the UE, the DeNB should consider the load balancing of the MME, that is, ensure the load balancing of each MME in the MME pool area.
  • the MME initiates an S1 release procedure to the corresponding eNB, and the release causes the tracking area update caused by the load balancing.
  • the eNB After receiving the message, the eNB initiates an RRC connection release procedure to the UE, requesting release and The RRC connection between the UEs is also caused by the tracking area update caused by load balancing. After receiving the message, the UE releases the connection with the eNB. For the RN in the connected mode, the MME initiates the S1 release procedure for the tracking area update caused by the load balancing to the corresponding DeNB. After receiving the message, the DeNB releases the RRC connection with the RN. In addition, the RN needs to release the RRC connection with the RN. The RRC connection with the served UE is released.
  • the MME offloading of the normal UE only the UE itself is affected, and the MME offloading of the RN affects the service continuity of the UE served by the RN, for example, when the UE served by the RN does not belong to the same MME.
  • the MMEs connected to these UEs may not be uninstalled, so there is no need to perform RRC connection and S1 connection release caused by tracking area update caused by load balancing. Summary of the invention
  • the main purpose of the present invention is to provide a method and system for ensuring service continuity of a RN serving a UE, so as to solve the problem that the MME of the RN is affected by the RN when the RN and the RN do not belong to the same MME.
  • the problem of service continuity of the serving UE is to provide a method and system for ensuring service continuity of a RN serving a UE, so as to solve the problem that the MME of the RN is affected by the RN when the RN and the RN do not belong to the same MME.
  • An embodiment of the present invention provides a method for ensuring service continuity of a relay node serving user equipment, where the method includes:
  • a base station serving a relay node or user equipment receives the relay node or user equipment After the message sent by the connected mobility management entity to uninstall the relay node or the user equipment, the mobility management entity of the relay node or the user equipment is initiated to update.
  • the mobility management entity of the initiating relay node or the user equipment is updated, specifically: initiating a mobility management entity update of the relay node or the user equipment by means of S1 handover in the cell.
  • the initiating the mobility management entity update of the relay node or the user equipment in the manner of the S1 handover in the cell specifically includes:
  • the base station serving the relay node or the user equipment After receiving the message of uninstalling the relay node or the user equipment, the base station serving the relay node or the user equipment sends a reason value to the mobility management entity connected to the relay node or the user equipment, and performs an intra-cell S1 handover. Switching demand message;
  • the mobility management entity connected to the relay node or the user equipment selects a target mobility management entity as the source mobility management entity for the relay node or the user equipment, and sends a forwarding relocation request message. Giving the target a mobile management entity;
  • the target mobility management entity Receiving, by the target mobility management entity, the forwarding relocation request message, and determining that the relay node or the serving gateway of the user equipment can serve the relay node or the user equipment, to the serving relay node Or the base station of the user equipment sends a handover request message, and carries a control signaling identifier allocated by the target mobility management entity to the relay node or the user equipment;
  • the base station serving the relay node or the user equipment receives the handover request message, and according to the reason value, when the intra-s1 S1 handover determination is an intra-cell handover of the relay node or user equipment,
  • the control signaling identifier assigned by the source mobility management entity to the relay node or the user equipment is updated to a control signaling identifier allocated by the target mobility management entity to the relay node or the user equipment, and the handover request acknowledgement is sent.
  • a message is sent to the target mobility management entity.
  • the method further includes:
  • the target mobility management entity Transmitting, by the target mobility management entity, a forwarding relocation response to the source mobility management entity After receiving the forwarding relocation response message, the source mobility management entity sends a handover command message to the base station serving the relay node or the user equipment; the base station serving the relay node or the user equipment sends the handover command message To the relay node or user equipment;
  • the relay node or the user equipment After receiving the handover command message, the relay node or the user equipment updates its own security context, and sends a handover confirmation message to the base station serving the relay node or the user equipment; the service serves the relay node or After receiving the handover confirmation message, the base station of the user equipment sends a handover notification message to the target mobility management entity;
  • the target mobility management entity After receiving the handover notification message, the target mobility management entity sends a forwarding relocation complete notification message to the source mobility management entity;
  • the source mobility management entity After receiving the forwarding relocation completion notification message, the source mobility management entity returns a forwarding relocation complete confirmation message to the target mobility management entity;
  • the target mobility management entity After receiving the forwarding relocation complete confirmation message, the target mobility management entity sends a modify bearer request message to the relay node or the serving gateway of the user equipment;
  • the modify bearer request message After performing bearer modification, sending a modify bearer response message to the target mobility management entity; and then serving the relay node or user equipment
  • the base station sends a user equipment context release complete message or the mobility management entity uninstalls the relay node or user equipment acknowledgement message to the source mobility management entity;
  • the source mobility management entity releases the context information related to the relay node or the user equipment.
  • the message for offloading the relay node or the user equipment is carried by the user equipment context release command message, or the mobile management entity is used to uninstall the relay node or the user equipment to indicate the message bearer;
  • the release reason carried by the user equipment context release command message is : Load balancing caused Tracking area updates.
  • the embodiment of the present invention further provides a system for ensuring service continuity of a relay node serving user equipment, including: a relay node or user equipment, a base station serving the relay node or user equipment, and the relay a mobility management entity to which a node or user equipment is connected;
  • the mobility management entity that is connected to the relay node or the user equipment is configured to send a message to the base station to uninstall the relay node or the user equipment.
  • the base station is configured to initiate, after receiving the message of the offloading the relay node or the user equipment, a mobility management entity update of the relay node or the user equipment.
  • the base station is further configured to initiate a mobility management entity update of the relay node or user equipment in a manner of intra-cell S1 handover.
  • the system further includes: a target mobility management entity of the relay node or user equipment, and a serving gateway of the relay node or user equipment;
  • the base station is further configured to: after receiving the message of uninstalling the relay node or the user equipment, send, to the mobility management entity connected to the relay node or the user equipment, a handover requirement message whose cause value is an intra-S1 handover ;
  • the mobile management entity connected to the relay node or the user equipment is used as a source mobility management entity, and is further configured to select the target mobility management entity for the relay node or user equipment according to the handover requirement message, and send and forward the target a relocation request message to the target mobility management entity, where the target mobility management entity is configured to receive the forwarding relocation request message and determine that the serving gateway can serve the relay node or user equipment Transmitting, to the base station, a handover request message, carrying a control signaling identifier allocated by the target mobility management entity to the relay node or user equipment;
  • the base station is further configured to, when the handover request message is received, and the inter-cell S1 handover determination is an intra-cell handover of the relay node or user equipment according to the reason value, the source mobility management entity Updating the control signaling identifier assigned to the relay node or user equipment to the A control signaling identifier assigned by the target mobility management entity to the relay node or user equipment, and sending a handover request acknowledgement message to the target mobility management entity.
  • the target mobility management entity is further configured to: after receiving the handover request acknowledgement message sent by the base station, send a forward relocation response message to the source mobility management entity;
  • the source mobility management entity is further configured to: after receiving the forwarding relocation response message, send a handover command message to the base station; the base station sends the handover command message to the relay node or user equipment;
  • the relay node or user equipment after receiving the handover command message, updates its own security context, and sends a handover confirmation message to the base station;
  • the base station is further configured to: after receiving the handover confirmation message, send a handover notification message to the target mobility management entity;
  • the target mobility management entity is further configured to: after receiving the handover notification message, send a forwarding relocation complete notification message to the source mobility management entity;
  • the source mobility management entity is further configured to: after receiving the forwarding relocation completion notification message, return a forwarding relocation complete confirmation message to the target mobility management entity;
  • the target mobility management entity is further configured to: after receiving the forwarding relocation complete confirmation message, send a modify bearer request message to the serving gateway;
  • the service gateway is further configured to: after receiving the modify bearer request message, send a modify bearer response message to the target mobility management entity after performing bearer modification;
  • the base station is further configured to: after the serving gateway sends a modify bearer response message to the target mobility management entity, send a user equipment context release complete message or the mobility management entity uninstalls the relay node or user equipment acknowledgement message to the source Mobile management entity;
  • the source mobility management entity is further configured to release the context information related to the relay node or the user equipment after receiving the user equipment context release completion message or the mobility management entity uninstalling the relay node or the user equipment confirmation message.
  • the message for offloading the relay node or the user equipment is carried by the user equipment context release command message, or the mobile management entity is used to uninstall the relay node or the user equipment to indicate the message bearer; the release reason carried by the user equipment context release command message is : Tracking area update caused by load balancing.
  • the method and system for ensuring the service continuity of the RN to serve the UE in the embodiment of the present invention.
  • the base station serving the RN or the UE initiates the MME update of the RN or the UE.
  • the release procedure is directly initiated to the corresponding base station.
  • the source MME only uninstalls the RN and does not offload the part of the UE.
  • the MME's MME update is completed.
  • the RN can continue to provide services for the part of the UE, so as to prevent all UEs served by the RN from releasing all connections, and ensuring service continuity of the UE served by the RN.
  • FIG. 1 is a schematic flow chart of a method for ensuring service continuity of an RN serving UE according to an embodiment of the present invention
  • FIG. 2 is a schematic flow chart of a method for ensuring service continuity of an RN serving UE according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for ensuring service continuity of an RN serving UE according to Embodiment 2 of the present invention
  • FIG. 4 is a schematic flowchart of a method for uninstalling a UE according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic flowchart of a method for uninstalling a UE according to Embodiment 4 of the present invention. detailed description
  • the method for ensuring the service continuity of the RN serving the UE in the embodiment of the present invention is: when receiving the offload message sent by the MME, the base station initiates the MME update of the RN or the UE, instead of the MME offloading.
  • the method of the embodiment of the present invention includes:
  • Step 101 The MME connected to the RN or the UE sends a message for offloading the RN or the UE to the base station serving the RN or the UE.
  • the message that the RN or the UE is offloaded may be carried by the user equipment context release command message, or the MME or the UE is used to indicate the message bearer by the MME; further, the MME offloads the RN or the UE indication message to the MME to rebalance the offload RN or the UE indication message. .
  • the reason for the release of the user equipment context release command message is as follows: Tracking area update caused by load balancing.
  • Step 102 The base station serving the RN or the UE initiates an MME update of the RN or the UE. Specifically, the base station initiates a mobility management entity update of the RN or the UE in a manner of intra-cell S1 handover.
  • the MME needs to perform re-balancing all offloading, and the MME selects the RN of the monthly service to perform the offloading. Accordingly, the UE that is served by the RN and connected to the MME is also uninstalled, and the RN is also uninstalled. The UEs that are not connected to the MME are not uninstalled.
  • the MME may also select the serving UE to perform the offloading process, and the specific process is the same as the RN selecting the serving RN to perform the uninstall process.
  • the process of ensuring service continuity of the RN service UE is as follows:
  • Step 201 For the RN in the connected mode, the MME connected to it (the MME needs to be removed from the MME pool area) sends a user equipment context release command message to the corresponding DeNB (ie, the eNB serving the RN), and the release reason is load balancing. The resulting tracking area update. At this time, the MME continues to retain the context of the RN and the corresponding data.
  • the MME connected to it the MME needs to be removed from the MME pool area
  • the release reason is load balancing.
  • the resulting tracking area update At this time, the MME continues to retain the context of the RN and the corresponding data.
  • Step 202 After receiving the user equipment context release command message, the DeNB sends a handover request message to the MME connected to the RN, where the cause value is an intra-cell S1 handover, and the purpose is to initiate an MME update of the RN, and the target base station in the handover requirement message Still the DeNB.
  • the cause value is an intra-cell S1 handover, and the purpose is to initiate an MME update of the RN, and the target base station in the handover requirement message Still the DeNB.
  • Step 203 After receiving the handover request message of the S1 handover in the cell, the MME connected to the RN selects a new MME (referred to as a target MME in the present invention) as the source MME of the RN, and sends a forwarding relocation request.
  • the message is sent to the target MME, and the message includes the context of the RN in the source MME (such as the RN security context, the RN network capability, the S-GW address of the RN, and the context of the data bearer).
  • Step 204 After receiving the forwarding relocation request message, the target MME of the RN determines whether the serving gateway (S-GW) can still serve the RN. If yes, the target MME sends a handover request message to the DeNB; the handover request message includes the target MME. The control signaling identifier assigned to the RN.
  • S-GW serving gateway
  • Step 205 After receiving the handover request message, the DeNB determines that the handover is an intra-cell handover of the RN, and the DeNB updates the control signaling identifier allocated by the source MME of the RN to the control signaling identifier allocated by the target MME. Then, a handover request acknowledgement message is sent to the target MME of the RN.
  • Step 206 After receiving the handover request acknowledgement message, the target MME of the RN sends a forward relocation response message to the source MME of the RN.
  • Step 207 The source MME sends a handover command message to the DeNB, and the DeNB further forwards the handover command message to the RN.
  • Step 208 After receiving the handover command message, the RN updates its own security context, and then sends a handover confirmation message to the DeNB.
  • Step 209 After receiving the handover confirmation message, the DeNB sends a handover notification message to the target MME of the RN.
  • Steps 210 to 211 the target MME of the RN sends a Forward Relocation Complete Notification message to the RN.
  • the source MME; the source MME of the RN correspondingly forwards the relocation complete confirmation message to the target MME of the RN.
  • Step 212 The target MME of the RN sends an S-GW that modifies the bearer request message to the RN, including the target MME address, the TEID, and the like.
  • Step 213 The S-GW of the RN receives the modify bearer request message, performs corresponding modification of the bearer, and then sends a modify bearer response message to the target MME of the RN.
  • Step 214 Since the S-GW of the RN is also located in the DeNB, after the S-GW of the RN sends the modify bearer response message to the target MME of the RN, the DeNB may send a user equipment context release complete message to the source MME of the RN, the source of the RN. After receiving the message, the MME releases the context information related to the RN, and the process of the RN being offloaded from the source MME and migrating to the target MME is completed.
  • the process of this embodiment is basically the same as the process of FIG. 2, except that, as shown in FIG. 3, in step 301, the MME connected to the RN sends an MME offload RN indication message to the DeNB of the serving RN (better, The MME re-equalizes the RN indication message).
  • the DeNB after receiving the MME re-balancing offload RN indication message, the DeNB sends a handover request message to the MME connected to the RN.
  • the DeNB may send an MME offload RN acknowledgement message (preferably, the MME rebalances the offload RN acknowledgement message) to the source of the RN.
  • the source MME of the MME releases the context information related to the RN.
  • the cause value initiated by the DeNB is the MME update procedure of the RN in the intra-cell S1 handover.
  • the source MME is only The RN is offloaded, and the UE is not offloaded. Therefore, after the RN switches from the source MME to the target MME, the RN can continue to provide services for these UEs, ensuring continuity of UE services.
  • the embodiment of the present invention further proposes a process flow of uninstalling the UE when the MME is removed.
  • the MME needs to perform partial offloading, and then the normal user equipment node, that is, the UE, is preferentially uninstalled; of course, the RN may also be selected for offloading.
  • the process of ensuring service continuity of the RN serving UE includes:
  • Step 401 For the UE in the connected mode, the MME connected to the MME (the MME needs to be removed from the MME pool area) sends a user equipment context release command message to the corresponding eNB (ie, the eNB serving the UE), and the release reason is load balancing. The resulting tracking area update. At this time, the MME continues to retain the context of the UE (here, the UE served by the source MME) and the corresponding data bearer information.
  • Step 402 After receiving the user equipment context release command message, the eNB sends a handover request message to the MME connected to the UE, where the cause value is an intra-cell S1 handover, and the target base station in the handover requirement message is still the eNB.
  • Step 403 After receiving the handover request message of the S1 handover in the cell, the MME connected to the UE selects the target MME for the UE as the source MME of the UE, and sends a Forward Relocation Request message to the target MME, where the message includes the UE.
  • the context of the source MME such as UE security context, UE network capability, S-GW address of the UE, and the context of the data bearer).
  • Step 404 After receiving the forwarding relocation request message, the target MME of the UE determines whether the serving gateway (S-GW) of the UE can still serve the UE. If yes, the target MME sends a handover request message to the eNB; the handover request message includes The control signaling identifier assigned by the target MME to the UE.
  • S-GW serving gateway
  • Step 405 After receiving the handover request message, the eNB determines that the handover is an intra-cell handover of the UE. Then, the eNB updates the MME corresponding to the UE to the control signaling identifier allocated by the target MME to the UE, and then sends a handover request acknowledgement message to the target MME of the UE.
  • Step 406 After receiving the handover request acknowledgement message, the target MME of the UE sends a forward relocation response message to the source MME of the UE.
  • Step 407 The source MME sends a handover command message to the eNB, and the eNB further forwards the handover command message to the UE.
  • Step 408 After receiving the handover command message, the UE updates the information of the security context, and then sends a handover confirmation message to the eNB.
  • Step 409 After receiving the handover confirmation message, the eNB sends a handover notification message to the target MME of the UE.
  • Steps 410 to 411 the target MME of the UE sends a Forward Relocation Complete Notification message to the source MME of the UE, and the source MME of the UE forwards a Relocation Complete Confirmation Acknowledgement message to the target MME of the UE.
  • Step 412 The target MME of the UE sends a modify bearer request message to the S-GW of the UE, where the target MME address, the TEID, and the like are included.
  • Step 413 The S-GW of the UE sends a modify bearer response message to the target MME of the UE.
  • Step 414 Since the S-GW of the UE is also located in the eNB, after the S-GW of the UE sends the modify bearer response message to the target MME of the UE, the eNB may send a user equipment context release complete message to the source MME of the UE, the source of the UE. After receiving the message, the MME releases the context information related to the UE, and the process of the UE unloading from the source MME and migrating to the target MME is completed.
  • the process of this embodiment is basically the same as the process of FIG. 4, except that, as shown in FIG. 5, in step 501, the MME connected to the UE sends the MME to the eNB serving the UE.
  • the UE indication message (preferably, the MME rebalancing offloading the UE indication message); correspondingly, after receiving the MME re-balancing offloading UE indication message, the eNB sends a handover requirement message to the MME connected to the UE.
  • the eNB may send an MME offload UE acknowledgement message (preferably, the MME rebalances the UE acknowledgement message) to the source of the UE.
  • the MME after receiving the message, the source MME of the UE releases the context information related to the UE.
  • the embodiment of the present invention further provides a system for ensuring service continuity of an RN serving UE, including: an RN or a UE, a base station serving the RN or the UE, and an MME connected to the RN or the UE;
  • the MME connected to the RN or the UE is configured to send a message for offloading the RN or the UE to the base station;
  • the base station is configured to initiate an MME update of the RN or the UE after receiving the message of uninstalling the RN or the UE.
  • the base station is further configured to initiate an MME update of the RN or the UE in an intra-cell S1 handover manner.
  • the system further includes: a target MME of the RN or the UE and a serving gateway of the RN or the UE; the base station is further configured to: after receiving the message of the offloading the RN or the UE, send the cause value to the MME connected to the RN or the UE as the intra-s1 S1 Switching demand message for switching;
  • the MME connected to the RN or the UE is used as the source MME, and is further configured to select a target MME for the RN or the UE according to the handover requirement message, and send a forwarding relocation request message to the target MME.
  • the target MME is configured to receive the forwarding relocation request. And sending a handover request message to the base station, and carrying the control signaling identifier allocated by the target MME for the RN or the UE, when the service and the service gateway can serve the RN or the UE;
  • the base station is further configured to: when receiving the handover request message, and according to the cause value, the S1 handover criterion in the cell
  • the control signaling identifier allocated by the source MME for the RN or the UE is updated to the control signaling identifier allocated by the target MME to the RN or the UE, and the handover request acknowledgement message is sent to the target MME. .
  • the target MME is further configured to: after receiving the handover request acknowledgement message sent by the base station, send a forward relocation response message to the source MME;
  • the source MME is further configured to: after receiving the forwarding relocation response message, send a handover command message to the base station; the base station sends a handover command message to the RN or the UE;
  • the RN or the UE after receiving the handover command message, updates its own security context, and sends a handover confirmation message to the base station;
  • the base station is further configured to: after receiving the handover confirmation message, send a handover notification message to the target MME; the target MME is further configured to: after receiving the handover notification message, send a forwarding relocation complete notification message to the source MME;
  • the source MME is further configured to: after receiving the forwarding relocation complete notification message, return a forwarding relocation complete confirmation message to the target MME;
  • the target MME is further configured to: after receiving the forwarding relocation complete confirmation message, send a modify bearer request message to the serving gateway;
  • the service gateway is further configured to receive the modify bearer request message, and after the bearer modification, send the tamper-response response message to the target MME;
  • the base station is further configured to: after the serving gateway sends the modify bearer response message to the target MME, send a user equipment context release complete message or the MME uninstalls the RN or the UE acknowledge message to the source MME;
  • the source MME is further configured to release the context information related to the RN or the UE after receiving the user equipment context release complete message or the MME uninstalling the RN or the UE acknowledgement message.
  • the message of the RN or the UE is offloaded by the user equipment context release command message, or the MME or the UE indicates that the message is carried by the MME;
  • the release reason carried by the user equipment context release command message is: Tracking area update caused by load balancing.

Landscapes

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

Abstract

L'invention porte sur un procédé pour assurer la continuité de service lorsqu'un nœud relais (RN) dessert un équipement utilisateur (UE), comprenant l'opération suivante : lors de la réception d'un message de déchargement d'un RN ou d'un UE envoyé par une entité de gestion de mobilité connectée au RN ou à l'UE, une station de base, servant à desservir le RN ou l'UE, déclenche une mise à jour de l'entité de gestion de mobilité du RN ou de l'UE. L'invention porte également sur un système pour assurer la continuité de service lorsqu'un RN dessert un UE. Selon la présente invention, un UE desservi par un RN peut être empêché de libérer toutes les connexions, ce qui assure la continuité de service de l'UE desservi par le RN.
PCT/CN2012/072889 2011-07-08 2012-03-23 Procédé et système pour assurer la continuité de service lorsqu'un nœud relais dessert un équipement utilisateur WO2012155677A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2011101909639A CN102869055A (zh) 2011-07-08 2011-07-08 一种保证rn服务ue的服务连续性的方法和系统
CN201110190963.9 2011-07-08

Publications (1)

Publication Number Publication Date
WO2012155677A1 true WO2012155677A1 (fr) 2012-11-22

Family

ID=47176259

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/072889 WO2012155677A1 (fr) 2011-07-08 2012-03-23 Procédé et système pour assurer la continuité de service lorsqu'un nœud relais dessert un équipement utilisateur

Country Status (2)

Country Link
CN (1) CN102869055A (fr)
WO (1) WO2012155677A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11558788B2 (en) 2016-01-20 2023-01-17 Nokia Solutions And Networks Oy Methods, apparatuses and computer program product for improved service continuity with mobile edge computing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500270A (zh) * 2008-02-02 2009-08-05 华为技术有限公司 一种负荷均衡的方法和装置
CN101605316A (zh) * 2009-07-09 2009-12-16 华为技术有限公司 选择移动管理实体、提供负载信息的方法及装置
CN101754308A (zh) * 2008-12-19 2010-06-23 华为技术有限公司 切换方式选择方法、基站以及系统
CN102083155A (zh) * 2010-03-03 2011-06-01 大唐移动通信设备有限公司 S1接口切换过程中承载接纳处理方法及移动性管理实体

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541040B (zh) * 2008-03-21 2012-04-25 华为技术有限公司 一种过载处理的方法及装置
CN101925124B (zh) * 2010-08-20 2013-01-23 西安电子科技大学 中继系统中移动管理实体的选择方法
CN102076016A (zh) * 2011-02-12 2011-05-25 普天信息技术研究院有限公司 中继系统的过载控制方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500270A (zh) * 2008-02-02 2009-08-05 华为技术有限公司 一种负荷均衡的方法和装置
CN101754308A (zh) * 2008-12-19 2010-06-23 华为技术有限公司 切换方式选择方法、基站以及系统
CN101605316A (zh) * 2009-07-09 2009-12-16 华为技术有限公司 选择移动管理实体、提供负载信息的方法及装置
CN102083155A (zh) * 2010-03-03 2011-06-01 大唐移动通信设备有限公司 S1接口切换过程中承载接纳处理方法及移动性管理实体

Also Published As

Publication number Publication date
CN102869055A (zh) 2013-01-09

Similar Documents

Publication Publication Date Title
US20220159533A1 (en) Communication system
RU2668071C1 (ru) Способ и устройство оптимизации сигнализации
JP7349964B2 (ja) 非アクティブ使用に対するｒａｎにおけるｕｅコンテキストの格納
EP2560454B1 (fr) Procédé et système de mise en uvre d'interface directe entre noeuds de réseau d'accès
JP5553938B2 (ja) ハンドオーバ方法、通信デバイス及び通信システム
JP2018014734A (ja) Ｌｉｐａモビリティをサポートするための方法および装置
KR101493624B1 (ko) Ｘ2 핸드오버 절차 중에 타겟 셀의 가입자 액세스 그룹을 코어 네트워크에 통지하기 위한 기지국 장치, 이동 관리 엔티티, 시스템, 방법 및 컴퓨터 프로그램 제품
JP6198940B2 (ja) デフォルト・ベアラなしのハンドオーバのための方法および装置
WO2014190524A1 (fr) Procédé et dispositif pour commutation de cellules
WO2014173359A1 (fr) Procédé de commutation, nodeb, système d'agrégation de porteuses, et support de mémorisation
WO2014186968A1 (fr) Procédé de gestion de zone de localisation et contrôleur de coeur de réseau
WO2016180157A1 (fr) Procédé et appareil permettant de mettre en œuvre un transfert intercellulaire d'un équipement utilisateur (ue) entre des stations de base
JP6345336B2 (ja) 閉鎖加入者グループ身元状態のアップデート方法、システム及び基地局
WO2015161575A1 (fr) Procédé, station de base, entité de gestion mobile, et système de notification d'emplacement de terminal utilisateur
WO2013170673A1 (fr) Procédé d'accès, station de base, point d'accès et équipement utilisateur
WO2012155713A1 (fr) Système et procédé d'opération de commutation
WO2012062147A1 (fr) Procédé et dispositif pour la configuration de paramètres de cellules d'un noeud relais
JP2015008543A (ja) 無線通信ルーティング及びアクセスポイント基地局
US9848366B2 (en) Method for determining relocation process and method for determining handover process
WO2012041023A1 (fr) Procédé de transmission d'informations et nœud d'accès
WO2012167648A1 (fr) Procédé, système et dispositif pour effectuer une commande d'accès au support lipa
WO2022082544A1 (fr) Procédé et appareil de migration de nœud iab
WO2012155677A1 (fr) Procédé et système pour assurer la continuité de service lorsqu'un nœud relais dessert un équipement utilisateur
KR20130017709A (ko) 데이터 오프로딩 접속을 제어하는 기지국 장치 및 가상화 기지국 시스템
WO2010121457A1 (fr) Procédé de mise à jour de liste, unité de gestion de mobilité, équipement utilisateur et noeud b évolué de rattachement

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

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

Country of ref document: EP

Kind code of ref document: A1