WO2016070603A1 - Procédé et appareil de synchronisation d'informations de support durant un transfert - Google Patents

Procédé et appareil de synchronisation d'informations de support durant un transfert Download PDF

Info

Publication number
WO2016070603A1
WO2016070603A1 PCT/CN2015/078807 CN2015078807W WO2016070603A1 WO 2016070603 A1 WO2016070603 A1 WO 2016070603A1 CN 2015078807 W CN2015078807 W CN 2015078807W WO 2016070603 A1 WO2016070603 A1 WO 2016070603A1
Authority
WO
WIPO (PCT)
Prior art keywords
source
bearer information
packet system
evolved packet
management entity
Prior art date
Application number
PCT/CN2015/078807
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 WO2016070603A1 publication Critical patent/WO2016070603A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • the present invention relates to handover technologies in a long term evolution network, and in particular, to a method and apparatus for carrying information synchronization in a handover process.
  • an evolved packet system bearer between an evolved Node B (eNodeB), a Mobile Management Entity (MME), and a Serving Gateway (SGW) (Evolved Packet System Bearer, EPS bearer) information is consistent.
  • eNodeB evolved Node B
  • MME Mobile Management Entity
  • SGW Serving Gateway
  • EPS bearer Evolved Packet System Bearer
  • the EPS bearer information that they manage may be inconsistent. For example, the system load is large, and the inconsistency may cause the S1 handover of the user equipment (User Equipment, UE) to fail.
  • UE User Equipment
  • FIG. 1 is a flow chart of a handover failure caused by an EPS bearer being out of synchronization, as shown in FIG. 1 , the flow is as follows:
  • Step 1 The source eNodeB initiates a handover, and sends a handover request message to the source MME.
  • Step 2 the source MME receives the handover request message, and sends a relocation request message to the target MME according to the local EPS bearer information.
  • Step 3 Optionally, if the source MME determines that the SGW changes, the source MME initiates a bearer creation process to the target SGW according to the local EPS bearer information for the intra-office handover procedure, and initiates the target SGW to the target SGW for the inter-office handover procedure.
  • the bearer creation process there is no such step for the handover process in which the SGW does not change;
  • Step 4 If it is an inter-office handover procedure, the target MME sends a handover request message to the target eNodeB; if it is an intra-office handover procedure, the source MME sends a handover request message to the target eNodeB; the subsequent handover procedure remains unchanged.
  • Step 5 The target eNodeB sends a handover request response success or failure message to the source MME and the target MME. If the EPS bearer information is inconsistent, the target eNodeB may fail to respond to the handover request.
  • An object of the present invention is to provide a method and apparatus for carrying information synchronization in a handover process, which can better solve the problem of inconsistent bearer information of an evolved packet system between an evolved Node B, a mobility management entity, and a serving gateway in a handover process.
  • a method for carrying out information synchronization in a handover process including: in a handover process, a source mobility management entity obtains an evolved packet system bearer information of a source evolved Node B by communicating with a source evolved Node B.
  • the source mobility management entity compares the evolved packet system bearer information of the source evolved Node B with its saved evolved packet system bearer information; when the evolved packet system bearer information of the source evolved Node B and the saved evolved packet system bearer information When the information is inconsistent, the source mobility management entity performs the consistency processing on the evolved packet system bearer information and the evolved packet system bearer information of the source evolved Node B, so that the evolved packet system bearer information is synchronized.
  • the step of the source mobility management entity performing the consistency processing on the evolved packet system bearer information and the evolved packet system bearer information of the source evolved Node B comprises: the source mobility management entity synchronizing the evolved packet system bearer information to The evolved packet system of the source evolved Node B carries information.
  • the step of the source mobility management entity synchronizing its evolved packet system bearer information to the evolved packet system bearer information of the source evolved Node B includes: the evolved packet system bearer information saved by the source mobility management entity When not in the evolved packet system bearer information of the source evolved Node B, the source mobility management entity notifies the source serving gateway to delete the evolved packet system bearer information to delete the corresponding evolved packet system bearer.
  • the step that the source mobility management entity synchronizes its evolved packet system bearer information to the evolved packet system bearer information of the source evolved Node B includes: when the evolved packet system bearer information of the source evolved Node B is not in the When the source mobile management entity saves the evolved packet system bearer information, the source mobility management entity notifies the source service gateway to create the evolved packet system bearer information to create a corresponding evolved packet system bearer.
  • the method further includes: when the source mobility management entity synchronizes the evolved packet system bearer information to the evolved packet system bearer information of the source evolved Node B, the source mobility management entity communicates with the source evolved node B, The evolved packet system bearer information is sent to the source evolved node B. According to the evolved packet system bearer information of the source mobility management entity, the source evolved Node B synchronizes its evolved packet system bearer information to the evolved packet system bearer information of the source mobility management entity.
  • the step that the source evolved Node B synchronizes its evolved packet system bearer information to the evolved packet system bearer information of the source mobility management entity includes: the source evolved Node B according to the source mobility management entity
  • the evolved packet system carries information, and deletes the evolved packet system bearer information that is stored in the evolved packet system bearer information of the source mobility management entity.
  • the method further includes: after the evolved packet system bearer information is synchronized, the source mobility management entity determines whether the current handover is an intra-office handover or an inter-office handover; if it is determined that the handover is an intra-office handover, the source mobility management entity uses the synchronization.
  • the evolved packet system carries information to perform intra-office handover; if it is determined that the handover is an inter-office handover, the source mobility management entity sends a relocation request to the target mobility management entity, and the target mobility management entity uses the synchronized evolved packet system to carry information. Perform interoffice switching.
  • an apparatus for synchronizing bearer information in a handover process including: a source mobility management entity information acquisition module, configured to acquire a source evolved node by communicating with a source evolved Node B during a handover process The evolved packet system bearer information of B; the source mobility management entity information comparison module is configured to compare the evolved packet system bearer information of the source evolved Node B with the saved evolved packet system bearer information; the source mobility management entity information synchronization module, When the evolved packet system bearer information of the source evolved Node B is inconsistent with the saved evolved packet system bearer information, the evolving packet system bearer information and the evolved packet system bearer information of the source evolved Node B are uniformly processed, thereby The evolved packet system bears information synchronization.
  • the method further includes: a source mobility management entity information sending module, configured to: when the source mobility management entity synchronizes its evolved packet system bearer information to the evolved packet system bearer information of the source evolved Node B, The evolved Node B communicates and transmits its evolved packet system bearer information to the source evolved Node B.
  • the source evolved Node B information synchronization module is configured to synchronize the evolved packet system bearer information according to the evolved packet system bearer information of the source mobility management entity.
  • the evolved packet system of the source mobility management entity carries information.
  • the method further includes: a source mobility management entity switching module, configured to determine whether the current handover is an intra-office handover or an inter-office handover after the eNodeB bearer information synchronization, and if it is determined that the handover is an intra-office handover, Performing intra-office handover using the synchronized evolved packet system bearer information; if it is determined that the current handover is an inter-office handover, transmitting a relocation request to the target mobility management entity, so that the target mobility management entity uses the synchronized evolved packet system bearer information. Inter-office switching.
  • the benefit of the embodiment of the present invention is that the embodiment of the present invention implements synchronization of the bearer information of the evolved packet system between the evolved Node B, the mobility management entity, and the serving gateway, thereby improving the handover success rate.
  • FIG. 2 is a schematic block diagram of a method for synchronizing bearer information in a handover process according to a first embodiment of the present invention
  • FIG. 3 is a block diagram of a device for synchronizing bearer information in a handover process according to a first embodiment of the present invention
  • FIG. 4 is a schematic block diagram of a method for synchronizing bearer information in a handover process according to a second embodiment of the present invention
  • FIG. 5 is a block diagram of a device for synchronizing bearer information in a handover process according to a second embodiment of the present invention.
  • FIG. 6 is a schematic block diagram of a method for synchronizing bearer information in a handover process according to a third embodiment of the present invention.
  • FIG. 7 is a block diagram of a device for synchronizing bearer information in a handover process according to a third embodiment of the present invention.
  • FIG. 8 is a flowchart of the MME maintaining the EPS bearer synchronization in the handover process according to the fourth embodiment of the present invention.
  • FIG. 9 is a flowchart of the MME triggering the eNodeB to maintain the EPS bearer synchronization in the handover process according to the fifth embodiment of the present invention.
  • FIG. 2 is a schematic block diagram of a method for synchronizing bearer information in a handover process according to a first embodiment of the present invention. As shown in FIG. 2, the steps include:
  • Step S11 During the handover process, the source MME obtains the EPS bearer information of the source eNodeB by communicating with the source eNodeB.
  • the source MME receives the handover request message from the source eNodeB, and parses the handover request message to obtain the EPS bearer information of the source eNodeB carried therein.
  • Step S12 The source MME compares the EPS bearer information of the eNodeB with the saved EPS bearer information.
  • Step S13 When the EPS bearer information of the source eNodeB is inconsistent with the saved EPS bearer information, the source MME performs the unification processing on the EPS bearer information and the EPS bearer information of the source eNodeB, so as to synchronize the EPS bearer information.
  • the source MME synchronizes its EPS bearer information to the EPS bearer information of the source eNodeB. Further, when the EPS bearer information saved by the source MME is not in the EPS bearer information of the source eNodeB, the source MME notifies the source SGW to delete the EPS bearer information to delete the corresponding EPS bearer. When the EPS bearer information of the source eNodeB is not in the EPS bearer information saved by the source MME, the source MME notifies the source SGW to create the EPS bearer information to create a corresponding EPS bearer.
  • the source MME may send the synchronized EPS bearer information to the target eNodeB or the target MME for S1 handover.
  • FIG. 3 is a block diagram of a device for synchronizing bearer information in a handover process according to a first embodiment of the present invention. As shown in FIG. 3, the method includes:
  • the source mobility management entity information obtaining module 11 is configured to obtain the EPS bearer information of the source eNodeB by communicating with the source eNodeB during the handover process. Specifically, when the source eNodeB initiates a handover request to the source MME, the source MME receives the handover request message from the source eNodeB, and parses the handover request message to obtain the EPS bearer information of the source eNodeB carried therein.
  • the source mobility management entity information comparison module 12 is configured to compare the EPS bearer information of the eNodeB with the saved EPS bearer information.
  • the source mobility management entity information synchronization module 13 is configured to: when the EPS bearer information of the source eNodeB is inconsistent with the saved EPS bearer information, perform consistency processing on the EPS bearer information and the EPS bearer information of the source eNodeB, thereby implementing the evolved packet
  • the system carries information synchronization. Specifically, the source mobility management entity information synchronization module 13 synchronizes its EPS bearer information to the EPS bearer information of the source eNodeB.
  • the source MME when the EPS bearer information saved by the source MME is not in the EPS bearer information of the source eNodeB, the source MME notifies the source SGW to delete the EPS bearer information to delete the corresponding EPS bearer; and the EPS bearer information of the source eNodeB.
  • the source MME notifies the source SGW to create the EPS bearer information to create a corresponding EPS bearer, so that the EPS bearer information between the source eNodeB, the source MME, and the source SGW is synchronized after the EPS bearer information is saved.
  • the source MME may send the synchronized EPS bearer information to the target eNodeB or the target MME for S1 handover.
  • FIG. 4 is a schematic block diagram of a method for synchronizing bearer information in a handover process according to a second embodiment of the present invention. As shown in FIG. 4, the steps include:
  • Step S21 During the handover process, the source MME obtains the EPS bearer information of the source eNodeB by communicating with the source eNodeB.
  • the source MME receives the handover request message from the source eNodeB, and parses the handover request message to obtain the EPS bearer information of the source eNodeB carried therein.
  • Step S22 The source MME compares the EPS bearer information of the eNodeB with the saved EPS bearer information.
  • Step S23 When the EPS bearer information of the source eNodeB is inconsistent with the saved EPS bearer information, the source MME synchronizes its EPS bearer information with the EPS bearer information of the source eNodeB.
  • the source MME when the EPS bearer information saved by the source MME is not in the EPS bearer information of the source eNodeB, the source MME notifies the source SGW to delete the EPS bearer information to delete the corresponding EPS bearer.
  • the source MME When the EPS bearer information of the source eNodeB is not in the EPS bearer information saved by the source MME, the source MME notifies the source SGW to create the EPS bearer information to create a corresponding EPS bearer.
  • the source MME may send the synchronized EPS bearer information to the target eNodeB or the target MME for S1 handover.
  • Step S24 When the EPS bearer information of the MME is synchronized to the EPS bearer information of the source eNodeB, the source MME sends the EPS bearer information to the source eNodeB by communicating with the source eNodeB.
  • the source MME sends a handover pre-processing failure message carrying its EPS bearer information and bearer deletion indication information to the source eNodeB.
  • Step S25 The source eNodeB synchronizes its EPS bearer information with the EPS bearer information of the source MME according to the EPS bearer information of the source MME.
  • the source eNodeB receives the handover pre-processing failure message and parses the EPS bearer information and the bearer deletion indication information of the source MME, and deletes the saved eNodeB bearer that is not in the source mobility management entity according to the bearer deletion indication information.
  • the evolved packet system in the information carries information.
  • the source MME may send the synchronized EPS bearer information to the target eNodeB or the target MME for S1 handover.
  • FIG. 5 is a block diagram of a device for synchronizing bearer information in a handover process according to a second embodiment of the present invention. As shown in FIG. 5, compared with the embodiment provided in FIG. 3, the following two modules are further included:
  • the source mobility management entity information sending module 14 is configured to: when the MME fails to communicate with the source eNodeB, the EPS bearer information is sent to the source eNodeB, and the EPS bearer information is sent to the source eNodeB.
  • the source eNodeB specifically, the source MME sends a handover pre-processing failure message carrying its EPS bearer information and bearer deletion indication information to the source eNodeB.
  • the source evolved Node B information synchronization module 15 is configured to synchronize the EPS bearer information of the source MME to the EPS bearer information of the source MME according to the EPS bearer information of the source MME. Specifically, the source eNodeB receives the handover pre-processing failure message and parses the EPS bearer information and the bearer deletion indication information of the source MME, and deletes the saved eNodeB bearer that is not in the source mobility management entity according to the bearer deletion indication information.
  • the evolved packet system in the information carries the information, so that after the EPS bearer information is synchronized between the source eNodeB, the source MME, and the source SGW, the source MME may send the synchronized EPS bearer information to the target eNodeB or the target MME for S1 handover.
  • FIG. 6 is a schematic block diagram of a method for synchronizing bearer information in a handover process according to a third embodiment of the present invention. As shown in FIG. 6, the steps include:
  • Step S31 During the handover process, the source MME obtains the EPS bearer information of the source eNodeB by communicating with the source eNodeB.
  • Step S32 The source MME compares the EPS bearer information of the eNodeB with the saved EPS bearer information.
  • Step S33 It is determined whether the EPS bearer information of the eNodeB is consistent with the EPS bearer information of the source MME. If yes, step S38 is performed; otherwise, step S34 is performed.
  • Step S34 The source MME synchronizes its EPS bearer information with the EPS bearer information of the source eNodeB.
  • Step S35 It is determined whether the EPS bearer information of the source MME is synchronized as the EPS bearer information of the source eNodeB is successful. If yes, step S38 is performed; otherwise, step S36 is performed.
  • Step S36 The source MME sends its EPS bearer information to the source eNodeB by communicating with the source eNodeB.
  • Step S37 The source eNodeB synchronizes its EPS bearer information to the EPS bearer information of the source MME, and after the synchronization, communicates with the source MME to send its EPS bearer information to the source MME.
  • Step S38 The source MME determines whether the current handover is an intra-office handover or an inter-office handover, and if it is an intra-office handover, step S41 is performed, and if it is an inter-office handover, step S39 is performed.
  • the source MME determines its link with the target eNodeB. If the link with the target eNodeB exists, it determines that the current handover is an intra-office handover, otherwise it determines that the current handover is an inter-office handover.
  • Step S39 The source MME sends a relocation request to the target MME.
  • Step S40 The target MME sends the synchronized EPS bearer information to the target eNodeB for S1 handover.
  • the source MME needs to determine whether the SGW is changed in the current handover. If the change occurs, the bearer creation process to the target SGW needs to be initiated. Otherwise, the handover request is directly initiated to the target eNodeB.
  • Step S41 The source MME sends the synchronized EPS bearer information to the target eNodeB for S1 handover.
  • the target MME needs to determine whether the SGW is changed in the current handover. If it changes, the bearer creation process to the target SGW needs to be initiated. Otherwise, the handover request is directly sent to the target eNodeB.
  • FIG. 7 is a block diagram of a device for synchronizing bearer information in a handover process according to a third embodiment of the present invention. As shown in FIG. 7, compared with the embodiment provided in FIG. 5, the following modules are further included:
  • the source mobility management entity switching module 16 is configured to determine whether the current handover is an intra-office handover or an inter-office handover after the eNodeB bearer information synchronization. If it is determined that the handover is an intra-office handover, the synchronized eNodeB bearer information is used. Performing an intra-office handover; if it is determined that the handover is an inter-office handover, transmitting a relocation request to the target mobility management entity, so that the target mobility management entity uses the synchronized evolved packet system bearer information for inter-office handover.
  • the specific processes of intra-office handover and inter-office handover are detailed in the fourth and fifth embodiments.
  • the MME can initiate synchronization of EPS bearer information during handover between the eNodeB, the MME, and the SGW.
  • the MME in the embodiment of the present invention can trigger the eNodeB to initiate modification of the EPS bearer to synchronize the EPS bearer information.
  • the source eNodeB sends a Handover Required message to the MME
  • the E-UTRAN Radio Access Bearer (E-RAB) list field that is currently managed by itself is added.
  • the MME compares the bearer list saved by itself with the bearer list of the source eNodeB.
  • the SGW is notified to delete; if the MME does not have bearer information of the bearer list of the eNodeB, the SGW is notified to create the bearer. Finally, the bearer information between the eNodeB, the MME and the SGW is synchronized.
  • the MME sends the synchronized bearer information to the target eNodeB or the target MME for S1 handover.
  • the source eNodeB adds an E-RAB list field in the handover request message, and the purpose is to synchronize the EPS bearer information between the eNodeB, the MME, and the SGW, and improve the handover success rate.
  • FIG. 8 is a flowchart of the MME maintaining the EPS bearer synchronization in the handover process according to the third embodiment of the present invention. As shown in FIG. 8, the method includes:
  • Step 101 The source eNodeB initiates a handover, and adds an E-RAB list field in the handover request message to carry the EPS bearer list to the source MME.
  • Step 102 The source MME receives the handover request message, and compares the E-RAB list field added in the handover request message with the locally managed EPS bearer information, and if the local EPS bearer is found to be more than the EPS bearer of the source eNodeB, the local redundant The deletion process of EPS bearer;
  • Step 103 The source MME receives the handover request message, and compares the E-RAB list field added in the handover request message with the locally managed EPS bearer information. If the local EPS bearer is found to be less than the EPS bearer of the source eNodeB, the origination is locally missing but The source eNodeB carries the creation process of the EPS bearer;
  • Step 104 the source MME determines whether the handover procedure is an inter-office handover procedure that is changed by the MME. For the inter-office handover procedure, the source MME sends a relocation request message to the target MME, where the step is not performed for the intra-office handover procedure.
  • Step 105 Optionally, if the MME determines that the SGW changes, for the intra-office handover procedure, the source MME initiates a bearer creation process to the target SGW; for the inter-office handover procedure, the target MME initiates a bearer creation process to the target SGW; for the SGW The switching process that does not change does not have this step;
  • Step 106 If it is an inter-office handover procedure, the target MME sends a handover request message to the target eNodeB; if it is an intra-office handover procedure, the source MME sends a handover request message to the target eNodeB; the subsequent handover procedure remains unchanged.
  • Step 107 The target eNodeB applies for a resource according to the consistent bearer list, and sends a handover request response success message to the corresponding MME.
  • the source MME may fail to create a bearer because there is not enough EPS bearer information. Since the resource release of the eNodeB is more frequent, in most cases, the MME holds more EPS bearer information than the EPS bearer information saved by the eNodeB.
  • FIG. 9 is a flowchart of the MME triggering the eNodeB to maintain the EPS bearer synchronization in the handover process according to the fourth embodiment of the present invention. As shown in FIG. 9, the method includes:
  • Step 201 The source eNodeB initiates a handover, and adds an E-RAB list field to the source MME in the handover request message.
  • Step 202 The source MME receives the handover request message, and compares the E-RAB list field added in the handover request message with the locally managed EPS bearer information. If the local EPS bearer is found to be more than the EPS bearer of the source eNodeB, the local redundant The deletion process of EPS bearer;
  • Step 203 The source MME receives the handover request message, and compares the E-RAB list field added in the handover request message with the locally managed EPS bearer information. If the local EPS bearer is found to be less than the EPS bearer of the source eNodeB, the origination is locally absent but The source eNodeB carries the creation process of the EPS bearer, but the bearer creation fails. The source MME notifies the source eNodeB that the handover pre-processing fails, and carries the EPS bearer information saved by the source MME. The reason for the failure is that the bearer is inconsistent, indicating that the source eNodeB deletes the inconsistent bearer, and then re-initiates the handover request.
  • Step 204 The source eNodeB determines that the handover failure is caused by the bearer inconsistency, deletes the inconsistent EPS bearer information according to the EPS bearer information carried by the MME, and re-initiates the handover procedure, where the handover request message carries a new EPS bearer list consistent with the source MME.
  • Step 205 the source MME determines that the handover process is an inter-office handover procedure that is changed by the MME, and sends a relocation request message to the target MME, where the step is not performed for the intra-office handover procedure;
  • Step 206 Optionally, if the MME determines that the SGW changes, for the intra-office handover procedure, the source MME initiates a bearer creation process to the target SGW; for the inter-office handover procedure, the target MME initiates a bearer creation process to the target SGW; for the SGW The switching process that does not change does not have this step;
  • Step 207 If it is an inter-office handover procedure, the target MME sends a handover request message to the target eNodeB; if it is an intra-office handover procedure, the source MME sends a handover request message to the target eNodeB; the subsequent handover procedure remains unchanged;
  • Step 208 The target eNodeB requests the resource according to the consistent bearer list, and sends a handover request response success message to the MME.
  • the embodiment of the invention relates to a handover function in an LTE network, which ensures that the EPS bearer information synchronization between the eNodeB, the MME and the SGW in the handover operation improves the handover success rate.
  • the foregoing embodiment and the preferred implementation manner implement the synchronization of the evolved packet system bearer information between the evolved Node B, the mobility management entity, and the serving gateway, thereby improving the handover success rate.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil de synchronisation d'informations de support durant un transfert. L'invention appartient au domaine technique des transferts dans des réseaux d'évolution à long terme. Le procédé comprend les étapes suivantes : durant un transfert, une entité source de gestion de mobilité acquiert des informations de support de système par paquets évolué d'un nœud B évolué source en communiquant avec le nœud B évolué source ; l'entité source de gestion de mobilité compare les informations de support de système par paquets évolué du nœud B évolué source à des informations de support de système par paquets évolué mémorisées par l'entité source de gestion de mobilité ; lorsque les informations de support de système par paquets évolué du nœud B évolué source ne correspondent pas aux informations de support de système par paquets évolué mémorisées, l'entité source de gestion de mobilité fait en sorte que ces informations de support de système par paquets évolué correspondent aux informations de support de système par paquets évolué du nœud B évolué source. En synchronisant les informations de support de système par paquets évolué du nœud B évolué source, l'entité source de gestion de mobilité et une passerelle de desserte source, la présente invention améliore le taux de réussite d'un transfert.
PCT/CN2015/078807 2014-11-05 2015-05-12 Procédé et appareil de synchronisation d'informations de support durant un transfert WO2016070603A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410617356.XA CN105636009A (zh) 2014-11-05 2014-11-05 一种切换过程中承载信息同步的方法及装置
CN201410617356.X 2014-11-05

Publications (1)

Publication Number Publication Date
WO2016070603A1 true WO2016070603A1 (fr) 2016-05-12

Family

ID=55908498

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/078807 WO2016070603A1 (fr) 2014-11-05 2015-05-12 Procédé et appareil de synchronisation d'informations de support durant un transfert

Country Status (2)

Country Link
CN (1) CN105636009A (fr)
WO (1) WO2016070603A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109996324B (zh) * 2017-12-29 2022-03-01 展讯通信（上海）有限公司 Eps承载状态同步方法、装置及网络侧设备
US11134371B2 (en) 2019-02-19 2021-09-28 Huawei Technologies Co., Ltd. Communication method and communications apparatus
CN111586774B (zh) * 2019-02-19 2021-06-29 华为技术有限公司 通信方法和通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102119540A (zh) * 2008-08-11 2011-07-06 株式会社Ntt都科摩 移动通信方法、交换台和移动台
CN103582075A (zh) * 2012-08-03 2014-02-12 北京三星通信技术研究有限公司 一种rn支持多种无线接入系统的方法
CN103874151A (zh) * 2012-12-17 2014-06-18 电信科学技术研究院 分层组网时的承载转移方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102119540A (zh) * 2008-08-11 2011-07-06 株式会社Ntt都科摩 移动通信方法、交换台和移动台
CN103582075A (zh) * 2012-08-03 2014-02-12 北京三星通信技术研究有限公司 一种rn支持多种无线接入系统的方法
CN103874151A (zh) * 2012-12-17 2014-06-18 电信科学技术研究院 分层组网时的承载转移方法和设备

Also Published As

Publication number Publication date
CN105636009A (zh) 2016-06-01

Similar Documents

Publication Publication Date Title
US11711736B2 (en) Apparatus, system and method for DC (dual connectivity)
US10433188B2 (en) Control apparatus, base station apparatus, radio terminal, and method for updating neighbour relation table
JP6610731B2 (ja) 専用コアネットワークのための装置、システム、及び方法
US8804667B2 (en) Method, system and evolved NodeB apparatus for implementing inter-evolved NodeB handover
US11751107B2 (en) Apparatus, system and method for security management
EP3379778B1 (fr) Procédé et dispositif d'émission de paquets de données
JP2017528993A (ja) デュアルコネクティビティ（ｄｕａｌ ｃｏｎｎｅｃｔｉｖｉｔｙ）のための装置
US9585013B2 (en) Generation of multiple shared keys by user equipment and base station using key expansion multiplier
WO2016070603A1 (fr) Procédé et appareil de synchronisation d'informations de support durant un transfert
WO2014205735A1 (fr) Procédé et dispositif de communication
KR20150006274A (ko) 제어 메시지 송수신 방법 및 장치
WO2016078352A1 (fr) Procédé de mise à jour de ssd, centre de changement de support, système de communications et support de stockage apparenté

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

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

Country of ref document: EP

Kind code of ref document: A1