WO2012149864A1 - Procédé permettant à un nœud relais de libérer un terminal, nœud relais et terminal - Google Patents

Procédé permettant à un nœud relais de libérer un terminal, nœud relais et terminal Download PDF

Info

Publication number
WO2012149864A1
WO2012149864A1 PCT/CN2012/074140 CN2012074140W WO2012149864A1 WO 2012149864 A1 WO2012149864 A1 WO 2012149864A1 CN 2012074140 W CN2012074140 W CN 2012074140W WO 2012149864 A1 WO2012149864 A1 WO 2012149864A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
accessing
accessed
same
release
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2012/074140
Other languages
English (en)
Chinese (zh)
Inventor
游世林
梁爽
卢飞
李志军
奚进
吴婴哲
翟恒星
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2012149864A1 publication Critical patent/WO2012149864A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • 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 present invention relates to the field of communications technologies, and in particular, to a method for releasing a terminal by a relay node (RN), a relay node, and a terminal.
  • RN relay node
  • Background technique
  • FIG. 1 is a schematic structural diagram of an EPS system in the related art.
  • the EPS system mainly includes an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and an EPC (Evolved Packet Core).
  • the packet core network two parts.
  • the EPC of the system can support users' access from GERAN (GSM EDGE radio access network, GSM EDGE radio access network) and UTRAN (Universal Terrestrial Radio Access Network).
  • the HSS Home Subscriber Server
  • the MME Mobility Management Entity
  • the S-GW Serving Gateway
  • the P-GW PDN Gateway
  • Packet Data Network Gateway Packet Data Network Gateway
  • SGSN Serving GPRS Support Node
  • PCRF Policy and Charging Enforcement Function
  • HSS is the permanent storage location of user subscription data, located in the home network that the user subscribes to;
  • MME is the location where the user subscription data is stored in the current network, and is responsible for the NAS-to-network (Non-Access Stratum, non-access layer) letter. Let management, user tracking in idle mode And paging management functions and bearer management;
  • the S-GW is a gateway from the core network to the wireless system, and is responsible for the user plane of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating a service request by the network side, the legal eavesdropping, and the packet data routing and forwarding function;
  • P-GW is an evolved packet domain system (EPS) and a gateway of the external network of the system, and is responsible for functions such as IP address allocation, charging function, packet filtering, and policy application of the terminal;
  • EPS evolved packet domain system
  • the SGSN is a service support point for GERAN and UTRAN users to access the EPC network. It functions similarly to the MME and is responsible for user location update, paging management, and bearer management.
  • the PCRF is responsible for providing policy control and charging rules to the PCEF.
  • FIG. 2 is a schematic diagram of a network architecture after the introduction of a relay in the related art, as shown in FIG. 2, in the network architecture,
  • the RN contains two parts of functions, UE and relay node.
  • the RN-side acts as a UE accessing the network, establishes a bearer and other related operations, and on the other hand, provides an access for the UE as an eNB;
  • the DeNB ( Donor eNodeB, donor base station) provides radio access for the RN, terminates the RRC signaling of the RN-UE, and terminates the S1AP signaling and the X2 signaling of the RN-eNB. Simultaneously setting the SGW and PGW of the RN-UE;
  • RN OAM Relay Node Operator and Management
  • the MME and the eNB that provide services for the RN-UE need to have corresponding enhancement functions. Therefore, it is necessary to ensure that the RN can select the enhanced eNB and the MME.
  • the terminal can access the network through the RN, and the DeNB selects the MME for the terminal, and the UE-MME can be an enhanced MME or an ordinary MME. Due to the introduction of the RN function, the MME function is enhanced. Therefore, when establishing a connection for the RN, the DeNB needs to select an MME supporting the RN function for the RN.
  • the MME accessing the RN in the network may be overloaded due to the number of terminals accessed and the number of RNs and the number of services established by the terminal. In this case, the MME may choose to uninstall certain terminals or RNs. . In addition, due to operational reasons, some MMEs need to be removed from the network, and the UEs and RNs on the MMEs accessed by these RNs also need to be uninstalled.
  • the MME that the RN accesses to the RN is as shown in FIG. 3, where the UE1 accesses through the RN, and the accessed MME is the same as the MME of the RN, and the UE2 accesses through the RN, and the accessed MME Unlike the MME of the RN, the process includes:
  • Step 301 The MME selects the RN to perform the uninstallation.
  • the MME sends an RN context release command to the DeNB, where the reason is carried, indicating that the reason for the release is offload (loadBalancingTAUrequired).
  • Step 302 The DeNB initiates the release of the radio air interface resource (RRC), where the reason is carried, and the reason for the release is the offload.
  • RRC radio air interface resource
  • Step 302A The RN initiates release of the radio air interface resource (RRC) to the UE2, where the reason is carried, and the cause of the release is the other cause value.
  • RRC radio air interface resource
  • Step 302B The RN initiates release of the radio air interface resource (RRC) to the UE1, where the reason is carried, and the cause of the release is the cause value of the other (other).
  • RRC radio air interface resource
  • Step 303 The DeNB returns a UE context release complete message to the MME.
  • Step 304 The RN initiates an RRC Connection Request/Tracking Area Update (TAU) request, where the RRC connection request does not include the registered MME identification information.
  • TAU RRC Connection Request/Tracking Area Update
  • Step 305 The DeNB selects an un-loaded MME for the RN according to the request of the RN.
  • Step 306 Complete the remaining process of the TAU.
  • steps 302A and 302B release UE1 and UE2 to select the same cause value.
  • both UE1 and UE2 initiate a TAU process, they all carry the registered MME identity, so that the mechanism selected in the MME
  • the UE1 continues to select the MME to be accessed by the RN in FIG. 3, but the MME is overloaded and performs overload control.
  • the UE1 continues to select the MME to increase the load of the MME, which is not conducive to overload control, which may affect system stability.
  • the main object of the present invention is to provide a method for a relay node to release a terminal, a relay node, and a terminal, which are convenient for overload control of the MME accessed by the RN, and improve system stability.
  • a method for a relay node (RN) to release a terminal (UE) includes:
  • the RN After receiving the release message containing the offload reason value from the donor base station, the RN determines whether the mobility management entity (MME) of the UE accessing the RN is the same as the MME accessed by the RN, and accesses the RN. If the MME of the UE is the same as the MME that is accessed by the RN, the UE sends a release message with the uninstallation cause value to the corresponding UE. If the MME of the UE accessing the RN is different from the MME accessed by the RN, the MME sends the message to the corresponding UE. A release message containing other reason values.
  • MME mobility management entity
  • the determining whether the MME of the UE accessing the RN is the same as the MME accessing the RN is: determining whether the MME identity of the UE accessing the RN is the same as the access MME identity of the RN.
  • the method further includes: after receiving the release message containing the offload reason value sent by the RN, the UE accessing the RN selects an MME that is not accessed by the RN to perform access when initiating a tracking area update (TAU).
  • TAU tracking area update
  • An RN configured to determine, after receiving a release message containing an offload cause value from a donor base station, whether a mobility management entity (MME) of a UE accessing the RN is the same as an MME accessed by the RN, The MME of the UE accessing the RN is the same as the MME accessed by the RN, and then sends a release message including the offload reason value to the corresponding UE; the MME of the UE accessing the RN is different from the MME accessed by the RN. And sending a release message containing other cause values to the corresponding UE.
  • MME mobility management entity
  • the RN determines whether the MME of the UE accessing the RN is the same as the MME accessed by the RN: determining that the MME identity of the UE accessing the RN and the access MME identity of the RN are None the same.
  • a UE is configured to select an MME that is not accessed by the RN to perform access when a TAU is initiated after receiving a release message that is sent by an RN that is accessed by the RN.
  • the RN checks whether the MME of the UE accessing the RN is The MMEs that are accessed by the RN are the same. If they are the same, the UE sends a release message containing the unloading cause value to the corresponding UE to release the UE. If not, the UE sends a release message including the other cause value to the corresponding UE to release the UE.
  • the MME may be selected to perform access, so that the MME accessed by the RN may perform overload control and improve system stability.
  • FIG. 1 is a schematic structural diagram of a system of an EPS in a related art
  • FIG. 2 is a schematic diagram of a network architecture after the introduction of Relay in the related art
  • FIG. 3 is a schematic flowchart of an MME that an RN accesses an RN
  • FIG. 4 is a schematic flowchart of a relay node releasing a terminal according to an embodiment of the present invention.
  • the RN After receiving the release message containing the offloading cause value from the donor base station, the RN determines whether the MME of the UE accessing the RN is the same as the MME accessed by the RN, and accessing the MME.
  • the MME of the UE of the RN is the same as the MME accessed by the RN, and then sends a release message including the offload reason value to the corresponding UE to release the UE, the MME accessing the UE of the RN, and the MME accessed by the RN.
  • a release message including other (other) cause values is sent to the corresponding UE to release the UE.
  • the RN determines whether the MME of the UE that accesses the RN is the same as the MME that is accessed by the RN, where the RN uses the MME identifier of the UE that accesses the RN and the RN. If the MME identity of the UE accessing the RN is the same as the MME identity of the RN, the MME that accesses the UE of the RN is determined to be the MME that is accessed by the RN. the same.
  • the UE accessing the RN selects another MME (ie, the MME that is not accessed by the RN) to access the RN when the TAU is initiated, and accesses the RN.
  • the UE may choose to access the MME when the TAU is initiated.
  • the embodiment of the present invention further provides an RN, which is configured to determine, after receiving the release message containing the offload reason value from the donor base station, whether the mobility management entity (MME) of the UE accessing the RN is The MME accessing the RN is the same, and the MME of the UE accessing the RN is the same as the MME accessed by the RN, and then sends a release message including the offload reason value to the corresponding UE; If the MMEs accessed by the RN are different, a release message including other cause values is sent to the corresponding UE.
  • MME mobility management entity
  • the RN determines whether the MME of the UE accessing the RN is the same as the MME accessed by the RN: determining whether the MME identity of the UE accessing the RN is the same as the access MME identity of the RN.
  • the embodiment of the present invention further provides a UE, which is configured to select an MME that is not accessed by the RN to perform access when the TAU is initiated after receiving the release message with the offload reason value sent by the RN that it accesses.
  • FIG. 4 is a schematic flowchart of a relay node releasing a terminal according to an embodiment of the present invention. As shown in FIG. 4, the process includes:
  • Step 401 The MME selects the RN to perform offloading. For the RN that needs to be offloaded, the MME sends an RN context release command to the DeNB, where the reason is carried, indicating that the reason for the release is offloading ( loadBalancingTAUrequired ).
  • Step 402 The DeNB initiates release of the radio air interface resource (RRC), where the reason is carried, and the reason for the release is offload (loadBalancingTAUrequired).
  • RRC radio air interface resource
  • Step 403 The RN compares the identifier of the MME accessed by the RN with the MME identifier of the UE that accesses the RN, and determines which MMEs that the UE accesses are the same as the MMEs that the RN accesses, and which MMEs that the UE accesses are connected to the RN.
  • the MME is different.
  • the MME accessed by the UE1 is the same as the MME accessed by the RN, and the MME accessed by the UE2 is different from the MME accessed by the RN.
  • Step 404 The RN initiates release of the radio air interface resource (RRC) to the UE1, where the reason is carried, and the reason for the release is offload (loadBalancingTAUrequired).
  • RRC radio air interface resource
  • Step 405 The RN initiates release of the radio air interface resource (RRC) to the UE2, where the reason is carried, and the reason for the release is the other cause value.
  • RRC radio air interface resource
  • Step 406 The DeNB returns a UE context release complete message to the MME.
  • Step 407 The RN initiates an RRC connection request and a TAU request, where the RRC connection request does not include the registered MME identification information.
  • Step 408 The DeNB selects an un-loaded MME for the RN according to the request of the RN.
  • Step 409 Complete the remaining process of the TAU.
  • Step 410 The UE1 accesses through the DeNB or other eNB or even the RN, and selects the non-RN MME to make an area update request.
  • Step 411 UE2 accesses through the DeNB or other eNB or even the RN, and the MME of the UE may not change.
  • the above solution enables other OLT registrations to be selected when the RN accesses the UE of the same MME to re-register, which avoids the load of the RN to access the MME and accelerates the MME load reduction speed.

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é permettant à un nœud relais (RN) de libérer un terminal (UE), comprenant les opérations suivantes : après réception d'un message de libération avec une valeur de cause de désinstallation envoyé par une station de base donneuse (DeNB); un RN détermine si une entité de gestion de mobilité (MME) de l'UE accédant au RN est la même que la MME à laquelle le RN accède; si la MME de l'UE accédant au RN est la même que la MME à laquelle le RN accède, alors envoi à l'UE correspondant du message de libération avec la valeur de cause de désinstallation; autrement, envoi à l'UE correspondant d'un message de libération avec une autre valeur de cause. L'invention porte également d'une manière correspondante sur un nœud relais et un terminal. La présente invention est avantageuse pour la MME pour effectuer une limitation de surcharge, ce qui permet d'améliorer la stabilité du système.
PCT/CN2012/074140 2011-05-04 2012-04-16 Procédé permettant à un nœud relais de libérer un terminal, nœud relais et terminal Ceased WO2012149864A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110114160.5A CN102769931B (zh) 2011-05-04 2011-05-04 中继节点释放终端的方法及中继节点、终端
CN201110114160.5 2011-05-04

Publications (1)

Publication Number Publication Date
WO2012149864A1 true WO2012149864A1 (fr) 2012-11-08

Family

ID=47097147

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/074140 Ceased WO2012149864A1 (fr) 2011-05-04 2012-04-16 Procédé permettant à un nœud relais de libérer un terminal, nœud relais et terminal

Country Status (2)

Country Link
CN (1) CN102769931B (fr)
WO (1) WO2012149864A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500271A (zh) * 2008-02-01 2009-08-05 华为技术有限公司 一种实现核心网设备负载均衡的方法和设备
CN101848554A (zh) * 2010-05-19 2010-09-29 新邮通信设备有限公司 一种无线接口恢复方法和一种施主基站
US20100311419A1 (en) * 2009-06-04 2010-12-09 Motorola, Inc. Mobility Management Entity Tracking for Group Mobility in Wireless Communication Network
CN102118808A (zh) * 2011-03-03 2011-07-06 电信科学技术研究院 触发切换及移动管理实体池标识信息的传递方法和设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500270B (zh) * 2008-02-02 2010-12-08 华为技术有限公司 一种负荷均衡的方法和装置
CN101541040B (zh) * 2008-03-21 2012-04-25 华为技术有限公司 一种过载处理的方法及装置
CN101674223B (zh) * 2008-09-13 2012-07-04 华为技术有限公司 网关设备负载处理方法、网络设备和网络系统
IN2011KN03309A (fr) * 2009-01-09 2015-07-10 Ericsson Telefon Ab L M
CN102026313B (zh) * 2010-06-21 2012-03-21 华为技术有限公司 切换处理方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500271A (zh) * 2008-02-01 2009-08-05 华为技术有限公司 一种实现核心网设备负载均衡的方法和设备
US20100311419A1 (en) * 2009-06-04 2010-12-09 Motorola, Inc. Mobility Management Entity Tracking for Group Mobility in Wireless Communication Network
CN101848554A (zh) * 2010-05-19 2010-09-29 新邮通信设备有限公司 一种无线接口恢复方法和一种施主基站
CN102118808A (zh) * 2011-03-03 2011-07-06 电信科学技术研究院 触发切换及移动管理实体池标识信息的传递方法和设备

Also Published As

Publication number Publication date
CN102769931B (zh) 2017-08-25
CN102769931A (zh) 2012-11-07

Similar Documents

Publication Publication Date Title
US12167319B2 (en) Service gap control for a wireless device
US11606734B2 (en) Handover method in wireless communication system and apparatus therefor
JP6335989B2 (ja) 住居／企業ネットワーク接続管理およびハンドオーバのシナリオ
CN103210682B (zh) 住宅/企业网络连接管理和csfb场景
CN101568149B (zh) 一种实现优选服务网关的方法及系统
US20120100823A1 (en) Method, system, network side device, and ue of managing csg membership
EP2790457B1 (fr) Procédé et dispositif pour la gestion d'une connexion d'accès à un réseau local
WO2012126302A1 (fr) Procédé et système prenant en charge la communication simultanée pour un terminal à double mode, à double veille
WO2013004121A1 (fr) Procédé et dispositif de traitement d'informations de passerelle locale
WO2011017979A1 (fr) Procede et dispositif de gestion de ressources dans un systeme de communication soutenant le shuntage ip
JP6446546B2 (ja) データ処理方法、装置、端末、モビリティ管理エンティティ、およびシステム
CN102625366B (zh) 中继系统的过载控制方法及系统
CN102448186A (zh) 一种中继节点启动的方法及其实现系统
CN101959176B (zh) 建立本地ip访问连接的实现方法和系统
CN101998364B (zh) 一种对本地网际协议访问连接实施管理的方法及系统
CN102769931B (zh) 中继节点释放终端的方法及中继节点、终端
CN102625411B (zh) 一种网元过载的用户释放方法及系统
WO2012106985A1 (fr) Procédé et système de transfert de nœud relais

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

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

Country of ref document: EP

Kind code of ref document: A1