WO2023230934A1 - 一种失败信息的传输方法及装置 - Google Patents

一种失败信息的传输方法及装置 Download PDF

Info

Publication number
WO2023230934A1
WO2023230934A1 PCT/CN2022/096493 CN2022096493W WO2023230934A1 WO 2023230934 A1 WO2023230934 A1 WO 2023230934A1 CN 2022096493 W CN2022096493 W CN 2022096493W WO 2023230934 A1 WO2023230934 A1 WO 2023230934A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
mcg
terminal device
target
identity
Prior art date
Application number
PCT/CN2022/096493
Other languages
English (en)
French (fr)
Inventor
熊艺
吴昱民
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280001909.1A priority Critical patent/CN117501744A/zh
Priority to PCT/CN2022/096493 priority patent/WO2023230934A1/zh
Publication of WO2023230934A1 publication Critical patent/WO2023230934A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a method and device for transmitting failure information.
  • Dual connectivity (DC) terminal equipment can access two cell groups, namely the master cell group (MCG) and the secondary cell group (SCG).
  • MCG corresponds to the network-side master node.
  • SCG corresponds to the network side secondary node (secondary node, SN).
  • the terminal device can implement mobility management of the cell group by executing MCG or SCG mobility.
  • MCG Mobility Management Entity
  • SCG Session Control Protocol
  • the terminal device can implement mobility management of the cell group by executing MCG or SCG mobility.
  • the terminal device performs mobility of MCG and SCG at the same time, the SCG access may succeed but the MCG fails.
  • how to reliably report MCG failure information is an urgent problem that needs to be solved.
  • Embodiments of the present disclosure provide a method and device for transmitting failure information.
  • embodiments of the present disclosure provide a method for transmitting failure information.
  • the method is executed by the target master node MN.
  • the method includes:
  • the target MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the source master node MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring the reliability of cell group mobility management.
  • embodiments of the present disclosure provide a method for transmitting failure information.
  • the method is executed by the source master node MN.
  • the method includes:
  • the source master node MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the target MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring the reliability of cell group mobility management.
  • embodiments of the present disclosure provide a method for transmitting failure information.
  • the method is executed by the target master node MN.
  • the method includes:
  • the target MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the SN. Therefore, the target master node MN can instruct the terminal device to restore or release the MCG connection, thereby ensuring the reliability of cell group mobility management.
  • embodiments of the present disclosure provide a communication device applied to the target master node MN side, including:
  • the transceiver module is used to exchange information about the failure of the terminal equipment main cell group MCG with the source master node MN.
  • embodiments of the present disclosure provide a communication device, applied to the source master node MN side, including:
  • the transceiver module is used to exchange information about the failure of the terminal equipment main cell group MCG with the target master node MN.
  • the embodiment of the present disclosure provides a communication device applied to the target master node MN side, including:
  • the transceiver module is used to exchange information about the failure of the terminal equipment primary cell group MCG with the secondary node SN.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the second aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the third aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device Perform the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device Perform the method described in the third aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause The device performs the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause The device performs the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause The device performs the method described in the third aspect above.
  • an embodiment of the present disclosure provides a failure information transmission system, which system includes the communication device described in the fourth aspect, the communication device described in the fifth aspect, and the communication device described in the sixth aspect, or,
  • the system includes the communication device described in the seventh aspect, the communication device described in the eighth aspect, and the communication device described in the ninth aspect, or the communication device described in the tenth aspect, the communication device described in the eleventh aspect
  • the communication device according to the twelfth aspect, or the system includes the communication device according to the thirteenth aspect, the communication device according to the fourteenth aspect and the communication device according to the fifteenth aspect.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned terminal device. When the instructions are executed, the terminal device is caused to execute the method described in the first aspect. method.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned terminal device. When the instructions are executed, the terminal device is caused to execute the steps described in the second aspect. method.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned terminal equipment. When the instructions are executed, the terminal equipment is caused to execute the above-mentioned third aspect. method.
  • the present disclosure also provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the second aspect.
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the third aspect.
  • the present disclosure provides a chip system.
  • the chip system includes at least one processor and an interface for supporting the terminal device to implement the functions involved in the first aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting the terminal device to implement the functions involved in the second aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting the terminal device to implement the functions involved in the third aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the second aspect.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the third aspect.
  • Figure 1a is a schematic diagram of a signaling flow when MCG and SCG mobility are executed simultaneously according to an embodiment of the present disclosure
  • Figure 1b is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 2 is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 3 is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 4a is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 4b is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 4c is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 4d is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 5a is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 5b is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 5c is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 5d is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 5e is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 6 is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 7a is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 7b is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 7c is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 7d is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure
  • Figure 8 is an interactive schematic diagram of a failure information transmission method provided by an embodiment of the present disclosure.
  • Figure 9a is an interactive schematic diagram of a failure information transmission method provided by an embodiment of the present disclosure.
  • Figure 9b is an interactive schematic diagram of a failure information transmission method provided by an embodiment of the present disclosure.
  • Figure 9c is an interactive schematic diagram of a failure information transmission method provided by an embodiment of the present disclosure.
  • Figure 10 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 11 is a schematic structural diagram of another communication device provided by an embodiment of the present disclosure.
  • Figure 12 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • the MN currently serving the terminal device.
  • the MN is used to prepare one or more of the target PCell, the target MCG, the candidate target PCell, and the candidate target MCG for the terminal device.
  • the target MN that prepares the candidate target PCell and/or the candidate target MCG may also be called a candidate target MN.
  • the target MCG is a target MCG or a candidate target MCG that can provide network services for the terminal device after the MCG change is initiated, and corresponds to the target MN.
  • a terminal device can link to two network devices at the same time, where the network device used to mainly control the communication of the terminal device is called the master node MN.
  • a terminal device can link to two network devices at the same time, where the network device used to assist the terminal device in communicating is called a secondary node SN.
  • the terminal device can select the target network device according to the preconfigured conditions, initiate the handover execution process, and initiate random access to the target network device.
  • the terminal device can realize the mobility of the master cell group (MCG) by executing CHO.
  • MCG master cell group
  • Conditional primary and secondary cell addition conditional PSCell addition, CPA
  • the terminal device can determine the PSCell that can be added based on preconfigured conditions.
  • the terminal device can realize the mobility of the secondary cell group (SCG) by executing CPA.
  • SCG secondary cell group
  • the terminal device can determine the accessible target PSCell based on preconfigured conditions.
  • the terminal device can realize SCG mobility by executing CPC.
  • the network device may provide a preconfigured candidate target cell group or target cell to the terminal device.
  • the subsequent terminal device can activate or deactivate the preconfigured candidate cell group or cell according to the configuration (such as activation message) issued by the network device or the corresponding activation event, without re-providing the configuration of the cell group.
  • the configuration delivered by the network device may include any of the following: configuration ID, activation conditions, and configuration of the cell group/cell to be activated. In other words, in cell group selective activation, after activating a new cell or cell group, or applying a new cell configuration or cell group configuration, or after accessing a new cell or cell group, the terminal device will not delete the corresponding cell. Configuration information for group selective activation.
  • the configuration information for cell group activation may include: a configuration ID and the configuration of the target cell or the configuration of the target cell group.
  • the configuration information for cell group activation may also include trigger conditions (which may also be called execution conditions and activation conditions).
  • cell group activation is a mobility management process, including any configuration of cell group activation by configuring the UE terminal device according to the signaling sent by the network, or the criteria specified by the protocol, or the terminal device UE autonomously, etc.
  • the method activates or deactivates the corresponding cell or cell group, or applies the corresponding cell configuration or cell group configuration or accesses the mobility management process of the cell or cell group.
  • cell group activation is a mobility management process, including any mobility management process that does not delete or release corresponding part or all of the configuration information after executing the mobility process. Not deleting or releasing the corresponding part or all of the configuration information can also be called retaining the corresponding part or all of the configuration information.
  • Mobility management based on conditional triggering 10. Mobility management based on conditional triggering:
  • R16/R17 mobility management based on conditional triggering is introduced.
  • the UE implements mobility management based on conditional triggering based on network configuration conditions and associated candidate cells. After the UE meets the conditions, it triggers mobility management and then Enter its associated candidate cells.
  • the network configuration conditions can be specific events based on measurement results, or events based on location or time.
  • the associated candidate cells may be candidate primary cells and primary and secondary cells, which respectively correspond to the corresponding condition-triggered mobility management CHO and CPC/CPA.
  • R17 supports MN-initiated CHO, MN-initiated CPA/CPC, and SN-initiated CPC.
  • the configuration of CHO, CPA/CPC respectively includes the corresponding configuration ID, execution conditions and configuration of the candidate target cell.
  • Network equipment configuration The method for configuring terminal equipment to perform MCG and SCG mobility at the same time is:
  • Configuring simultaneous CHO and CPA may include the following situations:
  • the configurations of CHO and CPA are included in the same conditional reconfiguration entry and are associated with the same conditional reconfiguration identification ID.
  • the configuration identification can be the conditional reconfiguration number, etc. Any one can determine the joint configuration. Information.
  • CHO and CPA can correspond to the same execution condition or different execution conditions.
  • CHO and CPA can correspond to the same candidate target configuration.
  • the configuration of the target MCG and the configuration of the target SCG can be configured through RRCReconfiguration, or they can also correspond to different candidate target configurations.
  • the configuration of CHO's candidate target cell includes the configuration of its associated CPA (or CPC).
  • the configuration of CHO's candidate target cell includes the execution conditions of its associated CPA (or CPC) and the configuration of the candidate PSCell. .
  • the configurations of MCG activation and SCG activation are included in the selective activation entries of the same cell group, corresponding to the same activation configuration identification ID, where the activation configuration identification can be an activation reconfiguration number or any other number that can determine the activation configuration. information.
  • MCG activation and SCG activation correspond to the same activation condition or different activation conditions (activation conditions may be configured).
  • MCG activation and SCG activation may correspond to the same "cell to be activated" configuration, for example, the configuration of the target MCG and the configuration of the target SCG are configured through RRCReconfiguration), or may correspond to different "cell to be activated” configurations .
  • the configurations of MCG activation and SCG activation are independent conditional reconfiguration entries.
  • the conditional reconfiguration entries of MCG activation configuration and the conditional reconfiguration entries of SCG activation configuration are related.
  • the "cell to be activated" configuration of the MCG includes the configurations of its associated multiple SCG "cells to be activated".
  • the source master node may send a master cell group MCG change request message to one or more target MNs for requesting one or more target MNs to prepare resources for dual connectivity terminal equipment. Afterwards, the target MN may determine the target according to the MCG change request message. Candidate MCG and target candidate SCG, or by interacting with the target SN, prepare the target candidate SCG for the DC terminal equipment. Then, the target MN can feed back a resource preparation success or failure message to the source MN, thereby enabling the MCG and SCG to be changed at the same time or Change MCG and increase SCG at the same time. As shown in Figure 1a, Figure 1a is a schematic diagram of the signaling flow when MCG and SCG mobility are executed simultaneously.
  • the network in MR-DC, if the network is configured to change MCG and SCG at the same time, it may involve multiple target MNs and multiple target SNs at the same time. It is necessary to change MCG and SCG at the same time or add SCG while changing MCG, which requires multiple MNs and SNs. Nodes perform signaling interactions. Different from the mobility of a single SCG, the target SN will be connected to the corresponding target MN and will not be associated with the source MN.
  • the cell group is one or more of a main cell group (MCG) and a secondary cell group (SCG).
  • MCG includes one or more of the primary cell (Primary Cell, PCell) and the secondary cell (Secondary Cell, SCell).
  • SCell Secondary Cell
  • PSCell Primary Secondary Cell
  • SCell Secondary Cell
  • cell group selective activation may include cell selective activation or cell activation, for example, one or more of PCell activation, PSCell activation, and SCell activation.
  • the cell group may also be a cell, wherein the MCG may also be a primary cell and the SCG may also be a primary and secondary cell.
  • the source master node MN may also be called an old MN
  • the target MN may also be called a new MN
  • the SN may be at least one of the target SN, the new SN, the source SN, and the old SN.
  • Figure 1b is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • the communication system may include but is not limited to a network device and a terminal device.
  • the number and form of devices shown in Figure 1b are only for examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more devices may be included.
  • the communication system shown in FIG. 1 b takes as an example a master node 11 , a terminal device 12 and a slave node 13 .
  • LTE long term evolution
  • 5th generation fifth generation
  • 5G new radio (NR) system 5th generation new radio
  • the master node 11 and the slave node 13 in the embodiment of the present disclosure are entities on the network side that are used to transmit or receive signals, and they may be the master node and slave node corresponding to the terminal device 12 respectively.
  • the primary node 11 and the secondary node 13 can be respectively an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in the NR system, and other future mobile Base stations in communication systems or access nodes in wireless fidelity (WiFi) systems, etc.
  • eNB evolved NodeB
  • TRP transmission reception point
  • gNB next generation base station
  • WiFi wireless fidelity
  • the embodiments of the present disclosure do not limit the specific technologies and specific equipment forms used by network equipment.
  • the network equipment provided by the embodiments of the present disclosure may be composed of a centralized unit (CU) and a distributed unit (DU).
  • the CU may also be called a control unit (control unit).
  • CU-DU is used.
  • the structure can separate the protocol layers of network equipment, such as base stations, and place some protocol layer functions under centralized control on the CU. The remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • the terminal device 12 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal equipment (mobile terminal, MT), etc.
  • the terminal device can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the terminal equipment.
  • the terminal device can perform cell group failure recovery by reporting failure information.
  • the network device configures the mobility of MCG and SCG for the terminal device at the same time
  • the terminal device may successfully access the SCG but fail to access the MCG.
  • the terminal device since the terminal device can only send the MCG failure information to the successfully accessed SCG, and the successfully accessed SCG has no direct connection with the source MN, the source MN cannot obtain the MCG failure information of the terminal device. , and the source MN cannot send the instruction information for restoring or releasing the MCG connection to the terminal device through the successfully accessed SCG, so MCG failure recovery cannot be performed.
  • the terminal device when the network device configures the mobility of MCG and SCG for the terminal device at the same time, and the terminal device succeeds in SCG access but fails in MCG access, the terminal device can communicate with the source through the interaction of each network node.
  • the master node MN or the target master node MN reports MCG failure information.
  • the source master node MN or the target master node MN receives the MCG failure information, it can send instruction information to the terminal device through the interaction of each network node to instruct the terminal device to restore MCG. connection or release the MCG connection, thereby ensuring the reliability of cell group mobility management.
  • failure information transmission method provided by any embodiment can be executed alone, or in combination with possible implementation methods in other embodiments, or in combination with any method in related technologies. A technical solution is implemented together.
  • Figure 2 is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure. The method is executed by the secondary node SN. As shown in Figure 2, the method may include but is not limited to the following steps:
  • the SN can be either a target SN or a source SN, which is not limited by the present invention.
  • Step 201 Receive primary cell group MCG failure information sent by the terminal device.
  • the terminal device when the network device configures the mobility of MCG and SCG for the terminal device at the same time, the terminal device may succeed in SCG access but fail in MCG access. At this time, the terminal device can generate MCG failure information and send the MCG failure information to the secondary node SN to synchronize the MCG access failure of the terminal device to the SN.
  • the secondary node SN may be the SN corresponding to the SCG that the terminal device successfully accesses when performing mobility of MCG and SCG.
  • the network device can implement simultaneous MCG and SCG mobility by configuring joint CHO and CPA for the terminal device, or configuring joint CHO and CPC, or configuring selective activation of MCG and SCG.
  • the network device can implement MCG mobility by performing CHO or MCG selective activation, and can implement SCG mobility by performing CPA (or CPC) or SCG selective activation.
  • the combined CHO and CPC may include a CPC configuration included in the CHO, and the combined CHO and CPA may include a CPA configuration included in the CHO.
  • Step 202 Send a first message to the target master node MN, where the first message contains MCG failure information.
  • the secondary node SN may generate a first message based on the received MCG failure information sent by the terminal device, and send the first message to the target master node MN to synchronize the MCG failure of the terminal device to the target MN.
  • the MCG failure information may be included in the first message in the form of a radio resource control (RRC) container Container.
  • RRC radio resource control
  • the first message may also include at least one of the following: the identity of the terminal device, the identity of the SN, the identity of one or more cells in the source main cell group MCG, and the identity of one or more cells in the target MCG. , and the identifier of one or more cell groups in the secondary cell group SCG.
  • the identifier of the terminal device may be information used to determine the terminal device, and may be at least one of the following: the identifier of the terminal device in the SN, the identifier of the terminal device in the target MN, and the identifier of the terminal device in the source MN.
  • the identification for example: XnAP ID
  • the identifier of the SN can be the SN number or any other information that can determine the SN.
  • the identification of the target MN may be the number of the target MN or any other information that can determine the target MN.
  • the identity of the source MN may be the number of the source MN or any other information that can determine the source MN.
  • the identification of the cell may be the cell number or any other information that can determine the cell.
  • the first message may also be an RRC transfer TRANSFER message.
  • Step 203 Receive a second message sent by the target MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • the second message may include at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG, and the identification of one or more cell groups in the secondary cell group SCG.
  • the items contained in the second message and the first message, as well as the values of each item may be the same or different.
  • the second message may include the identity of the terminal device on the target MN interface and the identity of the target MN
  • the first message may include the identity of the terminal device on the SN interface and the identity of the SN, etc. This disclosure does not limit this.
  • the target MN after receiving the first message, can determine that an MCG failure has occurred in the terminal device. After that, the target MN can instruct the terminal device to connect or release the MCG based on the MCG failure information, and will include instructions for instructing the terminal device to connect. or a second message of release indication information, sent to the SN.
  • the target MN may also send the MCG failure information to the source MN, receive the instruction information sent by the source MN to instruct the terminal device to connect or release, and generate a second message based on the instruction information and send it to the SN.
  • the indication information may be an RRC message
  • the RRC message may be any of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, or universal mobile telecommunications system UMTS ) terrestrial wireless access (Evolved-UMTS Terrestrial Radio Access, EUTRA) mobility command message, RRC connection release message, and RRC release message, etc., this disclosure does not limit this.
  • the indication information (that is, the RRC message used to instruct the terminal device to connect or release) may be included in the second message in the form of an RRC container Container.
  • the second message may also be an RRC transfer TRANSFER message.
  • the transmission direction of the RRC TRANSFER message can be sent by the target MN to the SN, or the SN can be sent to the target.
  • Master node MN when the first message and the second message correspond to the same message, for example, when the first message and the second message are both RRC TRANSFER messages, the transmission direction of the RRC TRANSFER message can be sent by the target MN to the SN, or the SN can be sent to the target. Master node MN.
  • the message when the message is used to transmit MCG failure information, it can be determined that the transmission direction of the message is sent to the target MN to the SN.
  • the message when the message is used to transmit indication information, it can be determined that the transmission direction of the message is sent to the SN by the SN. Target MN.
  • the transmission direction of the same message is applicable to a scenario where the mobility of MCG and SCG is configured at the same time.
  • Step 204 Send a message containing indication information to the terminal device.
  • the secondary node SN may determine the indication information according to the received second message sent by the target MN, and may send a message containing the indication information to the terminal device. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • the secondary node SN after receiving the primary cell group MCG failure information sent by the terminal device, the secondary node SN can send the first message containing the MCG failure information to the target primary node MN, and then can receive the first message containing the MCG failure information sent by the target MN to instruct the terminal device.
  • a second message containing the indication information for connection or release is performed, and then the message containing the indication information can be sent to the terminal device. Therefore, the terminal device reports the MCG failure message to the target MN through the interaction of each network node, and the target MN can instruct the terminal device to connect or release the MCG according to the MCG failure message and through the interaction of each network node, thereby ensuring that the cell group Reliability of mobility management.
  • Figure 3 is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure. The method is executed by a terminal device. As shown in Figure 3, the method may include but is not limited to the following steps:
  • Step 301 Send primary cell group MCG failure information to the secondary node SN.
  • the terminal device when the network device configures the mobility of MCG and SCG for the terminal device at the same time, the terminal device may succeed in SCG access but fail in MCG access. At this time, the terminal device can generate MCG failure information and send the MCG failure information to the secondary node SN to synchronize the MCG access failure of the terminal device to the SN.
  • the secondary node SN may be the SN corresponding to the SCG that is successfully accessed when the terminal device performs mobility of MCG and SCG at the same time.
  • the network device can implement simultaneous MCG and SCG mobility by configuring joint CHO and CPA for the terminal device, or configuring joint CHO and CPC, or configuring selective activation of MCG and SCG.
  • the network device can implement MCG mobility by performing CHO or MCG selective activation, and can implement SCG mobility by performing CPA (or CPC) or SCG selective activation.
  • the combined CHO and CPC may include a CPC configuration included in the CHO, and the combined CHO and CPA may include a CPA configuration included in the CHO.
  • Step 302 Receive a message sent by the SN containing instruction information instructing the terminal device to connect or release.
  • the secondary node after the secondary node receives the instruction information sent by the target master node MN for instructing the terminal device to connect or release, it can send a message containing the instruction information to the terminal device, so that the terminal device can follow the instruction.
  • the indication information may be determined by the target master node MN based on the received MCG failure information of the terminal device.
  • the terminal device performs MCG and SCG mobility at the same time.
  • MCG failure information may not be sent to the SN.
  • the terminal device performs MCG and SCG mobility at the same time. In the case of MCG failure, the terminal device is not allowed to send MCG failure information.
  • the terminal device when the terminal device performs MCG and SCG mobility at the same time, in the case of MCG failure, the terminal device is not allowed to send MCG failure information.
  • MCG and SCG mobility are performed simultaneously on the terminal device, and the terminal device is not supported in sending failure information, where the failure information includes MCG failure information.
  • MCG and SCG mobility are performed on the terminal device at the same time, and only the terminal device is supported to send SCG failure information.
  • the terminal device when the terminal device performs MCG mobility and SCG mobility is not configured, when MCG fails, the MCG connection can be restored by reporting MCG failure information.
  • the terminal device after the terminal device sends the primary cell group MCG failure information to the secondary node SN, it can receive a message sent by the SN containing instruction information instructing the terminal device to connect or release. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • Figure 4a is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure. The method is executed by the target master node MN. As shown in Figure 4a, the method may include but is not limited to the following steps:
  • Step 401a exchange information about the failure of the terminal equipment primary cell group MCG with the secondary node SN.
  • the terminal device when the network device configures the mobility of MCG and SCG at the same time for the terminal device, the terminal device may succeed in SCG access but fail in MCG access.
  • the terminal device can generate MCG failure information and send the MCG failure information to the secondary node SN.
  • the target MN can exchange relevant information about the terminal device primary cell group MCG failure with the SN.
  • the target MN can receive the MCG failure information sent by the SN.
  • MCG failure information, and/or the target MN can indicate to the SN the indication information that the terminal device connects or releases.
  • the terminal equipment can release or restore the MCG connection according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • the target MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the SN. Therefore, the target master node MN can instruct the terminal device to restore or release the MCG connection, thereby ensuring the reliability of cell group mobility management.
  • Figure 4b is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 401b Receive the first message sent by the secondary node SN, where the first message contains MCG failure information of the terminal device.
  • the terminal device may succeed in SCG access but fail in MCG access.
  • the terminal device can generate MCG failure information and send the MCG failure information to the secondary node SN to synchronize the MCG access failure of the terminal device to the SN.
  • the secondary node SN can generate a first message based on the received MCG failure information sent by the terminal device, and send the first message to the target master node MN to synchronize that the MCG failure has occurred in the target master node terminal device.
  • the secondary node SN may be the SN corresponding to the SCG that is successfully accessed when the terminal device performs mobility of MCG and SCG at the same time.
  • the network device can implement simultaneous MCG and SCG mobility by configuring joint CHO and CPA for the terminal device, or configuring joint CHO and CPC, or configuring selective activation of MCG and SCG.
  • the network device can implement MCG mobility by performing CHO or MCG selective activation, and can implement SCG mobility by performing CPA (or CPC) or SCG selective activation.
  • the combined CHO and CPC may include a CPC configuration included in the CHO, and the combined CHO and CPA may include a CPA configuration included in the CHO.
  • the MCG failure information may be included in the first message in the form of a radio resource control (RRC) container Container.
  • RRC radio resource control
  • the first message may include at least one of the following: the identity of the terminal device, the identity of the SN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG, and the identification of one or more cell groups in the secondary cell group SCG.
  • the identifier of the terminal device may be information used to determine the terminal device, and may be at least one of the following: the identifier of the terminal device in the SN, the identifier of the terminal device in the target MN, and the identifier of the terminal device in the source MN.
  • the identification for example: XnAP ID
  • the identifier of the SN can be the SN number or any other information that can determine the SN.
  • the identification of the target MN may be the number of the target MN or any other information that can determine the target MN.
  • the identity of the source MN may be the number of the source MN or any other information that can determine the source MN.
  • the identification of the cell may be the cell number or any other information that can determine the cell.
  • the first message may also be an RRC transfer TRANSFER message.
  • the target MN can respond to the MCG failure information.
  • the target MN can instruct the terminal device to connect, or release the connection, etc.; or, the target MN can also transparently transmit the MCG failure information to the source MN, and the source MN responds to the failure information, etc. This disclosure does not limit this. .
  • the target MN can receive the first message containing the MCG failure information of the terminal device sent by the secondary node SN. After that, the target master node MN can instruct the terminal device to restore or release the MCG connection, thereby ensuring the mobility management of the cell group. reliability.
  • Figure 4c is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 401c Send a second message to the SN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • the second message may include at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG, and the identification of one or more cell groups in the secondary cell group SCG.
  • the identity of the terminal device the identity of the target MN
  • the identity of one or more cells in the source main cell group MCG the identity of one or more cells in the target MCG
  • the identification of one or more cell groups in the secondary cell group SCG the identification of one or more cell groups in the secondary cell group SCG.
  • the target MN may instruct the terminal device to connect or release the MCG based on the MCG failure information, and will include the second instruction information for instructing the terminal device to connect or release the MCG.
  • the SN can send the instruction message to the terminal device to instruct the terminal device to connect or release the MCG, thereby ensuring the reliability of cell group mobility management.
  • the target MN may determine that an MCG failure has occurred in the terminal device based on one or more of the received MCG failure information, the measurement results of the terminal device, and its own current load, which is not limited by this disclosure.
  • the indication information may be an RRC message
  • the RRC message may be any of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, mobility command message from EUTRA, RRC connection release message, and RRC release messages, etc., this disclosure does not limit this.
  • the indication information (that is, the RRC message used to instruct the terminal device to connect or release) may be included in the second message in the form of an RRC container Container.
  • the second message may also be an RRC transfer TRANSFER message.
  • the transmission direction of the same message is applicable to a scenario where the mobility of MCG and SCG is configured at the same time.
  • the target MN can send a second message containing instruction information for instructing the terminal device to connect or release to the SN. After that, the terminal device can restore or release the MCG connection according to the instruction information, thereby ensuring cell group mobility management. reliability.
  • Figure 4d is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 401d Receive the first message sent by the secondary node SN, where the first message contains MCG failure information of the terminal device.
  • Step 402d Send a second message to the SN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • steps 402d to 403d please refer to the detailed description of any embodiment of this disclosure, and will not be described again here.
  • the items contained in the second message and the first message, as well as the values of each item may be the same or different.
  • the second message may include the identity of the terminal device on the target MN interface and the identity of the target MN
  • the first message may include the identity of the terminal device on the SN interface and the identity of the SN, etc. This disclosure does not limit this.
  • the transmission direction of the RRC TRANSFER message can be sent by the target MN to the SN, or the SN can be sent to the target master node. MN.
  • the message when the message is used to transmit MCG failure information, it can be determined that the transmission direction of the message is sent to the target MN to the SN.
  • the message when the message is used to transmit indication information, it can be determined that the transmission direction of the message is sent to the SN by the SN. Target MN.
  • the transmission direction of the same message is applicable to a scenario where the mobility of MCG and SCG is configured at the same time.
  • the target MN may send a second message containing instruction information for instructing the terminal device to connect or release to the SN. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • Figure 5a is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 501a Exchange information related to the failure of the terminal equipment primary cell group MCG with the source master node MN.
  • the terminal device when the network device configures the mobility of MCG and SCG for the terminal device at the same time, the terminal device may succeed in SCG access but fail in MCG access.
  • the terminal device can generate MCG failure information and send the MCG failure information to the target MN through the interaction of network nodes.
  • the target MN can exchange relevant information about the terminal device primary cell group MCG failure with the source master node MN, such as , the target MN may send the MCG failure information to the source MN, and/or the target MN may receive the instruction information sent by the source MN instructing the terminal device to connect or release.
  • the terminal equipment can release or restore the MCG connection according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • the target MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the source master node MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring the reliability of cell group mobility management.
  • Figure 5b is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 501b Send a first message to the source MN, where the first message contains MCG failure information of the terminal device.
  • the target master node MN may generate a first message based on the received MCG failure information of the terminal device sent by the secondary node SN, and send the first message to the source MN to synchronize the MCG occurrence of the terminal device to the source MN. Connection failed.
  • the network device can implement simultaneous MCG and SCG mobility by configuring joint CHO and CPA for the terminal device, or configuring joint CHO and CPC, or configuring selective activation of MCG and SCG.
  • the network device can implement MCG mobility by performing CHO or MCG selective activation, and can implement SCG mobility by performing CPA (or CPC) or SCG selective activation.
  • the combined CHO and CPC may include a CPC configuration included in the CHO, and the combined CHO and CPA may include a CPA configuration included in the CHO.
  • the MCG failure information may be included in the first message and the third message in the form of a radio resource control (RRC) container Container.
  • RRC radio resource control
  • the first message may include at least one of the following: an identity of the terminal device, an identity of the target MN, an identity of one or more cells in the source main cell group MCG, and an identity of one or more cells in the target MCG. , and the identifier of one or more cell groups in the secondary cell group SCG.
  • the identifier of the terminal device may be information used to determine the terminal device, and may be at least one of the following: the identifier of the terminal device in the SN, the identifier of the terminal device in the target MN, and the identifier of the terminal device in the source MN.
  • the identification for example: XnAP ID
  • the identifier of the SN can be the SN number or any other information that can determine the SN.
  • the identification of the target MN may be the number of the target MN or any other information that can determine the target MN.
  • the identity of the source MN may be the number of the source MN or any other information that can determine the source MN.
  • the identification of the cell may be the cell number or any other information that can determine the cell.
  • the first message may also be an RRC transfer TRANSFER message.
  • the optional source MN can respond to the information, such as instructing the terminal device to restore or release the connection.
  • the target master node may send a first message including MCG failure information of the terminal device to the source MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring the reliability of cell group mobility management.
  • Figure 5c is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 501c Receive a second message sent by the source MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • the second message may include at least one of the following: the identity of the terminal device, the identity of the source MN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG, and the identification of one or more cell groups in the secondary cell group SCG.
  • the source MN can respond to the MCG failure information, for example, instruct the terminal device to connect or release the MCG, and will include instructions for instructing the terminal device to connect or release the MCG.
  • the second message of the information is sent to the target MN.
  • the source MN may determine that an MCG failure has occurred in the terminal device based on one or more of the received MCG failure information, the measurement results of the terminal device, and its own current load, which is not limited in this disclosure.
  • the indication information can be an RRC message
  • the RRC message can be any of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, mobility command message from EUTRA, RRC connection release message, and RRC release messages, etc., this disclosure does not limit this.
  • the second message may also be an RRC transfer TRANSFER message.
  • the indication information (that is, the RRC message used to instruct the terminal device to connect or release) may be included in the second message in the form of an RRC container Container.
  • the target MN can receive the second message sent by the source MN containing instruction information for instructing the terminal device to connect or release. Therefore, the terminal device can restore or release the MCG connection according to the instruction information, thereby ensuring that the cell group Reliability of mobility management.
  • Figure 5d is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 501d Send a first message to the source MN, where the first message contains MCG failure information of the terminal device.
  • Step 502d Receive a second message sent by the source MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • steps 502d to 503d please refer to the detailed description of any embodiment of this disclosure, and will not be described again here.
  • the transmission direction of the RRC TRANSFER message can be that the target MN sends it to the source MN, or the source MN sends it to Target MN.
  • the transmission direction of the message can be determined to be sent by the target MN to the source MN.
  • the transmission direction of the message can be determined to be sent by the source MN. Give the target MN.
  • the transmission direction of the same message is applicable to a scenario where the mobility of MCG and SCG is configured at the same time.
  • the target MN after the target MN sends the first message containing the MCG failure information of the terminal device to the source MN, it may receive the second message sent by the source MN containing the instruction information for instructing the terminal device to connect or release. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • Figure 5e is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 501e Receive a third message sent by the secondary node SN, where the third message contains MCG failure information of the terminal device.
  • the third message may include at least one of the following: the identity of the terminal device, the identity of the SN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG, and The identifier of one or more cell groups in the secondary cell group SCG.
  • the secondary node SN may generate a third message based on the received MCG failure information sent by the terminal device, and send the third message to the target master node MN to inform the target master node MN that an MCG failure has occurred in the terminal device.
  • Step 502e Send a first message to the source MN, where the first message contains MCG failure information of the terminal device.
  • Step 503e Receive a second message sent by the source MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • steps 502e to 503e please refer to the detailed description of any embodiment of this disclosure, and will not be described again here.
  • the items contained in the third message and the first message, as well as the values of each item may be the same or different.
  • the first message may include the identification of the terminal device on the target MN interface and the identification of the target MN
  • the third message may include the identification of the terminal device on the SN interface and the identification of the SN, etc. This disclosure does not limit this.
  • any one or more of the first message, the second message, and the third message may be RRC transfer TRANSFER messages.
  • the items contained in the second message, the third message and the first message, as well as the values of each item, may be the same or different, and this disclosure does not limit this.
  • the target MN after receiving the third message containing the MCG failure information of the terminal device sent by the secondary node SN, the target MN can send the first message containing the MCG failure information of the terminal device to the source MN, and then, can receive the first message sent by the source MN.
  • the second message contains instruction information for instructing the terminal device to connect or release. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • FIG. 6 is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure.
  • the method is executed by the target master node MN.
  • the method may include but is not limited to the following steps:
  • Step 601 Send a first message to the source MN, where the first message contains MCG failure information of the terminal device.
  • Step 602 Receive a second message sent by the source MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • steps 601 to 602 please refer to the detailed description of any embodiment of this disclosure, and will not be described again here.
  • Step 603 Send a fourth message to the SN, where the fourth message contains indication information.
  • the target MN may determine the indication information based on the received second message sent by the source MN, and then may generate a fourth message based on the indication information, and send the fourth message to the SN.
  • the SN can determine the indication information and send the indication information to the terminal device to instruct the terminal device to connect or release the MCG, thereby ensuring the reliability of cell group mobility management.
  • the fourth message may be an RRC transfer TRANSFER message.
  • the transmission direction of the fourth message may be sent by the target MN to the SN.
  • the indication information (that is, the RRC message used to instruct the terminal device to connect or release) may be included in the fourth message in the form of an RRC container Container.
  • the fourth message may include at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG. identification, and the identification of one or more cell groups in the secondary cell group SCG.
  • the items contained in the fourth message, the second message, the third message and the first message, as well as the values of each item, may be the same or different, and this disclosure does not limit this.
  • the target MN after the target MN sends the first message containing the MCG failure information of the terminal device to the source MN, it can receive the second message sent by the source MN containing the instruction information for instructing the terminal device to connect or release, and then, it can A fourth message containing indication information is sent to the SN. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • Figure 7a is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure. The method is executed by the source master node MN. As shown in Figure 7a, the method may include but is not limited to the following steps:
  • Step 701a Exchange information related to the failure of the terminal equipment primary cell group MCG with the target master node MN.
  • the terminal device when the network device configures the mobility of MCG and SCG for the terminal device at the same time, the terminal device may succeed in SCG access but fail in MCG access.
  • the terminal device can generate MCG failure information and send the MCG failure information to the target MN through the interaction of network nodes.
  • the target MN can exchange relevant information about the terminal device primary cell group MCG failure with the source master node MN, such as , the source MN may receive the MCG failure information sent by the target MN, and/or the target MN may send indication information instructing the terminal device to connect or release to the target MN.
  • the terminal equipment can release or restore the MCG connection according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • the source master node MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the target MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring the reliability of cell group mobility management.
  • Figure 7b is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure. The method is executed by the source master node MN. As shown in Figure 7b, the method may include but is not limited to the following steps:
  • Step 701b Receive the first message sent by the target MN, where the first message contains MCG failure information of the terminal device.
  • the target master node MN may generate a first message based on the received MCG failure information of the terminal device sent by the SN, and send it to the source MN to synchronize the MCG connection failure of the terminal device to the source MN.
  • the network device can implement simultaneous MCG and SCG mobility by configuring joint CHO and CPA for the terminal device, or configuring joint CHO and CPC, or configuring selective activation of MCG and SCG.
  • the network device can implement MCG mobility by performing CHO or MCG selective activation, and can implement SCG mobility by performing CPA (or CPC) or SCG selective activation.
  • the combined CHO and CPC may include a CPC configuration included in the CHO, and the combined CHO and CPA may include a CPA configuration included in the CHO.
  • the MCG failure information may be included in the first message in the form of a radio resource control (RRC) container Container.
  • RRC radio resource control
  • the first message may include at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG. identification, and the identification of one or more cell groups in the secondary cell group SCG.
  • the identifier of the terminal device may be information used to determine the terminal device, and may be at least one of the following: the identifier of the terminal device in the SN, the identifier of the terminal device in the target MN, and the identifier of the terminal device in the source MN.
  • the identification for example: XnAP ID
  • the identifier of the SN can be the SN number or any other information that can determine the SN.
  • the identification of the target MN may be the number of the target MN or any other information that can determine the target MN.
  • the identity of the source MN may be the number of the source MN or any other information that can determine the source MN.
  • the identification of the cell may be the cell number or any other information that can determine the cell.
  • the first message may also be an RRC transfer TRANSFER message.
  • the source MN can respond to the information, such as instructing the terminal device to release the connection, or restore the connection, etc. This disclosure does not limit this.
  • the source master node can receive the first message containing the MCG failure information of the terminal device sent by the target MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring that the cell group Reliability of mobility management.
  • Figure 7c is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure. The method is executed by the source master node MN. As shown in Figure 7c, the method may include but is not limited to the following steps:
  • Step 701c Send a second message to the target MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • the second message may contain at least one of the following: the identity of the terminal device, the identity of the SN, the identity of the target MN, the identity of the source MN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG.
  • the identifier of one or more cells, and the identifier of one or more cell groups in the secondary cell group SCG are examples of the above identifiers.
  • the source MN may instruct the terminal device to connect or release the MCG based on the MCG failure information, and will include the second instruction information for instructing the terminal device to connect or release the MCG. message, sent to the target MN.
  • the source MN may determine that an MCG failure has occurred in the terminal device based on one or more of the received MCG failure information, the measurement results of the terminal device, and its own current load, which is not limited in this disclosure.
  • the indication information may be an RRC message
  • the RRC message may be any of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, mobility command message from EUTRA, RRC connection release message, and RRC release messages, etc., this disclosure does not limit this.
  • the indication information (that is, the RRC message used to instruct the terminal device to connect or release) may be included in the second message in the form of an RRC container Container.
  • the second message may also be an RRC transfer TRANSFER message.
  • the source MN may send a second message containing instruction information for instructing the terminal device to connect or release to the target MN.
  • the terminal equipment can restore or release the MCG connection according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • Figure 7d is a schematic flowchart of a method for transmitting failure information provided by an embodiment of the present disclosure. The method is executed by the source master node MN. As shown in Figure 7d, the method may include but is not limited to the following steps:
  • Step 701d Receive the first message sent by the target MN, where the first message contains MCG failure information of the terminal device.
  • Step 702d Send a second message to the target MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • steps 701d to 702d please refer to the detailed description of any embodiment of this disclosure, and will not be described again here.
  • the items contained in the second message and the first message, as well as the values of each item may be the same or different.
  • the second message may include the identity of the terminal device on the source MN interface and the identity of the source MN
  • the first message may include the identity of the terminal device on the target MN interface and the identity of the target MN, etc. This disclosure does not make any reference to this. limit.
  • the transmission direction of the RRC TRANSFER message can be that the target MN sends it to the source MN, or the source MN sends it to Target MN.
  • the transmission direction of the message can be determined to be sent by the target MN to the source MN.
  • the transmission direction of the message can be determined to be sent by the source MN. Give the target MN.
  • the transmission direction of the same message is applicable to a scenario where the mobility of MCG and SCG is configured at the same time.
  • the source MN may send a second message containing the instruction information for instructing the terminal device to connect or release to the target MN. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • FIG. 8 is an interactive schematic diagram of a method for transmitting failure information provided by an embodiment of the present disclosure. As shown in Figure 8, the method may include but is not limited to the following steps:
  • Step 801 The secondary node SN receives the primary cell group MCG failure information sent by the terminal device.
  • Step 802 The secondary node SN sends a first message to the target master node MN, where the first message contains MCG failure information.
  • Step 803 The target master node MN sends a second message to the source MN, where the second message contains MCG failure information of the terminal device.
  • Step 804 The source MN sends a third message to the target master node MN, where the third message contains instruction information for instructing the terminal device to connect or release.
  • Step 805 The target master node MN sends a fourth message to the slave node SN, where the fourth message contains instruction information for instructing the terminal device to connect or release.
  • Step 806 The secondary node SN sends a message containing indication information to the terminal device.
  • steps 801 to 806 please refer to the detailed description of any embodiment of this disclosure, and will not be described again here.
  • the SN to which the terminal device successfully accesses forwards it to the connected target MN, and then the target MN forwards it to the source MN.
  • the RRC message is generated by the source MN and forwarded to the target MN, which then forwards it to the successfully accessed SN, and the SN sends it to the terminal device for failure recovery.
  • the terminal device reports the MCG failure message to the source MN through the interaction of each network node.
  • the source MN can instruct the terminal device to connect or release the MCG according to the MCG failure message and through the interaction of each network node, thereby ensuring that the cell Reliability of group mobility management.
  • Figure 9a is an interactive schematic diagram of a failure information transmission method provided by an embodiment of the present disclosure. As shown in Figure 9a, the method may include but is not limited to the following steps:
  • Step 901a The secondary node SN receives the primary cell group MCG failure information sent by the terminal device.
  • Step 902a The secondary node SN sends a first message to the target master node MN, where the first message contains MCG failure information.
  • Step 903a The target master node MN sends a second message to the slave node SN, where the fourth message contains instruction information for instructing the terminal device to connect or release.
  • Step 904a The secondary node SN sends a message containing indication information to the terminal device.
  • steps 901a to 904a please refer to the detailed description of any embodiment of this disclosure, and will not be described again here.
  • the SN to which the terminal device successfully accesses forwards it to the connected target MN.
  • the target MN generates an RRC message and forwards it to the SN, and the SN sends it to the terminal device for failure. recover.
  • the terminal device reports the MCG failure message to the target MN through the interaction of each network node.
  • the target MN can instruct the terminal device to connect or release the MCG according to the MCG failure message and through the interaction of each network node, thereby ensuring that the cell Reliability of group mobility management.
  • Figure 9b is an interactive schematic diagram of a method for transmitting failure information provided by an embodiment of the present disclosure. As shown in Figure 9b, the method may include but is not limited to the following steps:
  • Step 901b After receiving the first message containing the MCG failure information of the terminal device sent by the SN (the target SN to which the terminal device successfully accesses), the target MN may include the MCG failure information in the second message and forward it to the source MN. .
  • Step 902b After receiving the second message containing the MCG failure information of the terminal device sent by the target MN, the source MN may include the corresponding RRC message in the third message and send it to the target MN.
  • Step 903b After receiving the third message containing the MCG failure information of the terminal device sent by the source MN, the target MN may include the corresponding RRC message in the fourth message and forward it to the SN, where the RRC message is used to indicate the terminal device. Release or restore the MCG connection.
  • the optional first message, second message, third message and fourth message can all be RRC TRANSFER.
  • the MCG failure information and the RRC message sent to the UE may be included in the first message, the second message, the third message, and the fourth message in the form of an RRC container.
  • the transmission direction may be the source master node sending it to the target master node or the target master node sending it to the source master node.
  • this transmission direction applies to a specific "mobility management process”.
  • This mobility management process is: performing CHO and CPA (or CPC) at the same time (CHO configuration and CPA/CPC configuration association) or the selection of MCG and SCG Sexual activation.
  • the first message, the second message, the third message, and the fourth message may include: one or more of the ID of the UE in the source MN, the target MN, and the SN (for example: XnAP ID); the source MN , one or more of the identification IDs of the target MN and SN; one or more of the IDs of one or more cells in the source MCG, target MCG, and SCG.
  • the ID of the UE in the source MN, the target MN, and the SN for example: XnAP ID
  • the source MN one or more of the identification IDs of the target MN and SN
  • one or more of the IDs of one or more cells in the source MCG, target MCG, and SCG for example: XnAP ID
  • the RRC TRANSFER sent from the target master node to the source master node for fast MCG recovery carries MCGFailureInformation.
  • the RRC TRANSFER sent from the source master node to the target master node for fast MCG recovery carries the RRC message sent to the UE.
  • the RRC message sent to the UE includes: RRCConnectionReconfiguration message, RRCReconfiguration message, MobilityFromNRCommand message, MobilityFromEUTRACommand message, RRCConnectionRelease message or RRCRelease message.
  • the source MN can also be called the old MN
  • the target MN can also be called the new MN
  • the SN can be the target SN or the new SN.
  • the terminal device reports the MCG failure message to the source MN through the interaction of each network node.
  • the source MN can instruct the terminal device to connect or release the MCG according to the MCG failure message and through the interaction of each network node, thereby ensuring that the cell Reliability of group mobility management.
  • Figure 9c is an interactive schematic diagram of a method for transmitting failure information provided by an embodiment of the present disclosure. As shown in Figure 9c, the method may include but is not limited to the following steps:
  • Step 901c After receiving the first message containing the MCG failure information of the terminal device sent by the SN (the target SN to which the terminal device successfully accesses), the target MN includes the corresponding RRC message in the fourth message and sends it to the SN, where , the RRC message is used to instruct the terminal device to release or restore the MCG connection.
  • the optional first message and fourth message can both be RRC TRANSFER.
  • the MCG failure information and the RRC message sent to the UE may be included in the first message and the fourth message in the form of an RRC container.
  • the first message and the fourth message may include: one or more of the IDs of the UE in the source MN, the target MN, and the SN (for example, XnAP ID); the identification IDs of the source MN, the target MN, and the SN. One or more of the IDs of one or more cells in the source MCG, the target MCG, and the SCG.
  • the RRC TRANSFER sent from the target master node to the source master node for fast MCG recovery carries MCGFailureInformation.
  • the RRC TRANSFER sent from the source master node to the target master node for fast MCG recovery carries the RRC message sent to the UE.
  • the RRC message sent to the UE includes at least one of the following: RRCConnectionReconfiguration message, RRCReconfiguration message, MobilityFromNRCommand message, MobilityFromEUTRACommand message, RRCConnectionRelease message or RRCRelease message.
  • the source MN can also be called the old MN
  • the target MN can also be called the new MN
  • the SN can be the target SN or the new SN.
  • the transmission direction may be the (target) primary node sending it to the (target) secondary node or the (target) secondary node sending it to the (target) primary node. node.
  • this transmission direction applies to a specific "mobility management process”.
  • This mobility management process is: performing CHO and CPA (or CPC) at the same time (CHO configuration and CPA/CPC configuration association) or the selection of MCG and SCG Sexual activation.
  • the terminal device reports the MCG failure message to the target MN through the interaction of each network node.
  • the target MN can instruct the terminal device to connect or release the MCG according to the MCG failure message and through the interaction of each network node, thereby ensuring that the cell Reliability of group mobility management.
  • FIG. 10 is a schematic structural diagram of a communication device 1000 provided by an embodiment of the present disclosure.
  • the communication device 1000 shown in FIG. 10 may include a processing module 1001 and a transceiver module 1002.
  • the transceiving module 1002 may include a sending module and/or a receiving module.
  • the sending module is used to implement the sending function
  • the receiving module is used to implement the receiving function.
  • the transceiving module 1002 may implement the sending function and/or the receiving function.
  • the communication device 1000 may be a secondary node SN, a device in the secondary node SN, or a device that can be used in conjunction with the secondary node SN.
  • the communication device 1000 is on the secondary node SN side, where:
  • the transceiver module 1002 is used to receive the primary cell group MCG failure information sent by the terminal equipment;
  • the above-mentioned transceiving module 1002 is also used to send a first message to the target master node MN, wherein the first message contains the MCG failure information;
  • the above-mentioned transceiving module 1002 is also configured to receive a second message sent by the target MN, wherein the second message contains instruction information used to instruct the terminal device to connect or release;
  • the above-mentioned transceiving module 1002 is also used to send a message containing the indication information to the terminal device.
  • any one or more of the first message and the second message are RRC transfer TRANSFER messages.
  • the first message includes at least one of the following: the identity of the terminal device, the identity of the SN, the identity of one or more cells in the source main cell group MCG, one or more cells in the target MCG.
  • the second message contains at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, one or more cells in the target MCG The identifier, and the identifier of one or more cell groups in the secondary cell group SCG.
  • the identifier of the terminal device is at least one of the following: the identifier of the terminal device in the SN, the identifier of the terminal device in the target MN, and the identifier of the terminal device in the target MN. Identity in the source MN.
  • the indication information is an RRC message
  • the RRC message is any one of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, mobility command message from EUTRA, RRC connection release message, and RRC release message.
  • the MCG failure information is included in the first message in the form of an RRC container Container, and the indication information is included in the second message in the form of an RRC container Container.
  • the terminal device is configured with MCG and SCG mobility, and the mobility of the MCG and SCG includes at least one of the following:
  • the combined CHO and CPC include the CPC configuration included in the CHO, and the combined CHO and CPA include the CPA configuration included in the CHO.
  • the secondary node after receiving the primary cell group MCG failure information sent by the terminal device, the secondary node can send a first message containing the MCG failure information to the target primary node MN, and then, can receive a message sent by the target MN containing the information for instructing the terminal device to perform A second message containing the indication information of connection or release may be sent to the terminal device. Therefore, the terminal device reports the MCG failure message to the target MN through the interaction of each network node, and the target MN can instruct the terminal device to connect or release the MCG according to the MCG failure message and through the interaction of each network node, thereby ensuring that the cell group Reliability of mobility management.
  • the communication device 1000 may be a terminal device, a device in the terminal device, or a device that can be used in conjunction with the terminal device.
  • the communication device 1000 is on the terminal equipment side, where:
  • Transceiver module used to send primary cell group MCG failure information to the secondary node SN;
  • the above-mentioned transceiver module is also configured to receive a message sent by the SN containing instruction information instructing the terminal device to connect or release.
  • the device also includes:
  • the processing module 1001 is configured to respond to the terminal device performing MCG and SCG mobility at the same time. If the MCG fails, MCG failure information is not allowed to be sent.
  • the terminal device is configured with MCG and SCG mobility
  • the MCG and SCG mobility include at least one of the following:
  • the combined CHO and CPC include the CPC configuration included in the CHO, and the combined CHO and CPA include the CPA configuration included in the CHO.
  • the terminal device after the terminal device sends the primary cell group MCG failure information to the secondary node SN, it can receive a message sent by the SN containing instruction information instructing the terminal device to connect or release. Therefore, the terminal equipment can connect or release the MCG according to the instruction information, thereby ensuring the reliability of cell group mobility management.
  • the communication device 1000 may be a target primary cell MN, a device in the target primary cell MN, or a device that can be used in conjunction with the target primary cell MN.
  • the communication device 1000 is on the target primary cell MN side, where:
  • the transceiver module 1002 is configured to exchange information related to the failure of the terminal equipment primary cell group MCG with the secondary node SN.
  • transceiver module 1002 is used for:
  • any one or more of the first message and the second message are RRC transfer TRANSFER messages.
  • the first message includes at least one of the following: the identity of the terminal device, the identity of the SN, the identity of one or more cells in the source main cell group MCG, one or more cells in the target MCG.
  • the second message contains at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, one or more cells in the target MCG The identifier, and the identifier of one or more cell groups in the secondary cell group SCG.
  • the identity of the terminal device is at least one of the following: the identity of the terminal device in the secondary node, the identity of the terminal device in the target MN, the identity of the terminal device in the Identity in the source MN.
  • the indication information is an RRC message
  • the RRC message is any one of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, mobility command message from EUTRA, RRC connection release message, and RRC release message.
  • the MCG failure information is included in the first message in the form of an RRC container Container, and the indication information is included in the second message in the form of an RRC container Container.
  • the terminal device is configured with MCG and SCG mobility, and the mobility of the MCG and SCG includes at least one of the following:
  • the combined CHO and CPC include the CPC configuration included in the CHO, and the combined CHO and CPA include the CPA configuration included in the CHO.
  • the target MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the SN. Therefore, the target master node MN can instruct the terminal device to restore or release the MCG connection, thereby ensuring the reliability of cell group mobility management.
  • the communication device 1000 may be a target primary cell MN, a device in the target primary cell MN, or a device that can be used in conjunction with the target primary cell MN.
  • the communication device 1000 is on the target primary cell MN side, where:
  • the transceiver module 1002 is configured to exchange information related to the failure of the terminal equipment primary cell group MCG with the source master node MN.
  • transceiver module 1002 is used for:
  • the terminal device and/or receive a second message sent by the source MN, where the second message contains instruction information for instructing the terminal device to connect or release.
  • transceiver module 1002 is used for:
  • the first message is sent to the source MN, where the third message contains the MCG failure information.
  • transceiver module 1002 is also used for:
  • any one or more of the first message, the second message, the third message and the fourth message are RRC transfer TRANSFER messages.
  • the first message includes at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, one of the target MCG or the identifiers of multiple cells, and the identifiers of one or more cell groups in the secondary cell group SCG; and/or,
  • the second message includes at least one of the following: the bid document of the terminal equipment, the identity of the source MN, the identity of one or more cells in the source main cell group MCG, one or more cells in the target MCG.
  • the third message includes at least one of the following: the identity of the terminal device, the identity of the SN, the identity of one or more cells in the source main cell group MCG, the identity of one or more cells in the target MCG. Identity, and the identification of one or more cell groups in the secondary cell group SCG; and/or,
  • the fourth message includes at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, one or more cells in the target MCG The identifier, and the identifier of one or more cell groups in the secondary cell group SCG.
  • the identity of the terminal device is at least one of the following: the identity of the terminal device in the secondary node, the identity of the terminal device in the target MN, the identity of the terminal device in the Identity in the source MN.
  • the indication information is an RRC message
  • the RRC message is any one of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, mobility command message from EUTRA, RRC connection release message, and RRC release message.
  • the MCG failure information is included in the first message and the third message in the form of an RRC container Container, and the indication information is included in the second message and the fourth message in the form of an RRC container Container. .
  • the terminal device is configured with MCG and SCG mobility, and the mobility of the MCG and SCG includes at least one of the following:
  • the combined CHO and CPC include the CPC configuration included in the CHO, and the combined CHO and CPA include the CPA configuration included in the CHO.
  • the target MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the source master node MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring the reliability of cell group mobility management.
  • the communication device 1000 may be the source primary cell MN, or may be a device in the source primary cell MN, or may be a device that can be used in conjunction with the source primary cell MN.
  • the communication device 1000 is on the source primary cell MN side, where:
  • the transceiver module 1002 is configured to exchange information related to the failure of the terminal equipment primary cell group MCG with the target master node MN.
  • transceiver module 1002 is used for:
  • any one or more of the first message and the second message are RRC transfer TRANSFER messages.
  • the first message includes at least one of the following: the identity of the terminal device, the identity of the target MN, the identity of one or more cells in the source main cell group MCG, one or more cells in the target MCG.
  • the second message includes at least one of the following: the identity of the terminal device, the identity of the source MN, the identity of one or more cells in the source main cell group MCG, and the identity of one or more cells in the target MCG.
  • the identity of the terminal device is at least one of the following: the identity of the terminal device in the secondary node, the identity of the terminal device in the target MN, the identity of the terminal device in the Identity in the source MN.
  • the indication information is an RRC message
  • the RRC message is any one of the following: RRC connection reconfiguration message, RRC reconfiguration message, mobility command message from NR, mobility command message from EUTRA, RRC connection release message, and RRC release message.
  • the MCG failure information is included in the first message in the form of an RRC container Container, and the indication information is included in the second message in the form of an RRC container Container.
  • the terminal device is configured with MCG and SCG mobility, and the mobility of the MCG and SCG includes at least one of the following:
  • the combined CHO and CPC include the CPC configuration included in the CHO, and the combined CHO and CPA include the CPA configuration included in the CHO.
  • the source master node MN may exchange information related to the failure of the terminal equipment primary cell group MCG with the target MN. Therefore, the source master node can instruct the terminal device to restore or release the MCG connection according to the MCG failure information, thereby ensuring the reliability of cell group mobility management.
  • FIG. 11 is a schematic structural diagram of another communication device 1100 provided by an embodiment of the present disclosure.
  • the communication device 1100 may be a terminal device, a network device, a chip, a chip system, or a processor that supports a terminal device to implement the above method, or a chip, a chip system, or a processor that supports a network device to implement the above method.
  • Devices etc. The device can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 1100 may include one or more processors 1101.
  • the processor 1101 may be a general-purpose processor or a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data.
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.) and execute computer programs. , processing data for computer programs.
  • the communication device 1100 may also include one or more memories 1102, on which a computer program 1104 may be stored.
  • the processor 1101 executes the computer program 1104, so that the communication device 1100 performs the steps described in the above method embodiments. method.
  • the memory 1102 may also store data.
  • the communication device 1100 and the memory 1102 can be provided separately or integrated together.
  • the communication device 1100 may also include a transceiver 1105 and an antenna 1106.
  • the transceiver 1105 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 1105 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 1100 may also include one or more interface circuits 1107.
  • the interface circuit 1107 is used to receive code instructions and transmit them to the processor 1101 .
  • the processor 1101 executes the code instructions to cause the communication device 1100 to perform the method described in the above method embodiment.
  • the communication device 1100 is a secondary node SN: the transceiver 1105 is used to perform step 201, step 202, step 203, step 204, etc. in FIG. 2 .
  • the communication device 1100 is a terminal device: the transceiver 1105 is used to perform steps 301, 302, etc. in Figure 3.
  • the communication device 1100 is the target master node MN: the transceiver 1105 is used to perform step 401a in Figure 4a; step 401b in Figure 4b; step 401c in Figure 4c; step 401d, step 402d in Figure 4d, etc.
  • the communication device 1100 is the target master node MN: the transceiver 1105 is used to perform step 501a in Figure 5a; step 501b in Figure 5b; step 501c in Figure 5c; steps 501d and 502d in Figure 5d; and step 501 in Figure 5c.
  • the communication device 1100 source master node MN the transceiver 1105 is used to perform step 701a in Figure 7a; step 701b in Figure 7b; step 701c in Figure 7c; step 701d, step 702d in Figure 7d, etc.
  • the processor 1101 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 1101 may store a computer program 1103, and the computer program 1103 runs on the processor 1101, causing the communication device 1100 to perform the method described in the above method embodiment.
  • the computer program 1103 may be solidified in the processor 1101, in which case the processor 1101 may be implemented by hardware.
  • the communication device 1100 may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure may be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a terminal device, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 11 .
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • the communication device may be a chip or a chip system
  • the schematic structural diagram of the chip shown in FIG. 12 refer to the schematic structural diagram of the chip shown in FIG. 12 .
  • the chip shown in Figure 12 includes a processor 1201 and an interface 1203.
  • the number of processors 1201 may be one or more, and the number of interfaces 1203 may be multiple.
  • Interface 1203 is used to execute step 201, step 202, step 203, step 204, etc. in Figure 2.
  • Interface 1203 is used to execute step 301, step 302, etc. in Figure 3.
  • the interface 1203 is used to execute step 401a in Figure 4a; step 401b in Figure 4b; step 401c in Figure 4c; step 401d, step 402d in Figure 4d, etc.
  • the interface 1203 is used to execute step 701a in Figure 7a; step 701b in Figure 7b; step 701c in Figure 7c; step 701d, step 702d in Figure 7d, etc.
  • the chip also includes a memory 1203, which is used to store necessary computer programs and data.
  • the present disclosure also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs.
  • the computer program When the computer program is loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present disclosure are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in the present disclosure can also be described as one or more, and the plurality can be two, three, four or more, and the present disclosure is not limited.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D” etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • each table in this disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which is not limited by this disclosure.
  • it is not necessarily required to configure all the correspondences shown in each table.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables. wait.
  • Predefinition in this disclosure may be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

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

Abstract

本公开实施例公开了一种失败信息的传输方法，可应用于通信技术领域，其中，由主节点MN执行的方法包括：与源主节点MN交互终端设备主小区组MCG失败的相关信息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。

Description

一种失败信息的传输方法及装置 技术领域
本公开涉及通信技术领域，尤其涉及一种失败信息的传输方法及装置。
背景技术
双连接(dual connectivity，DC)终端设备，可以接入两个小区组，分别为主小区组(master cell group，MCG)和辅小区组(secondary cell group，SCG)其中，MCG对应网络侧主节点(master node，MN)，SCG对应网络侧辅节点(secondary node，SN)。
在通信系统中，终端设备可以通过执行MCG或SCG的移动性，实现小区组的移动性管理。但是，当终端设备同时进行MCG和SCG的移动性时，可能会发生SCG接入成功，但是MCG失败的现象。在此种情况下，如何可靠地将MCG的失败信息进行上报是目前亟需解决的问题。
发明内容
本公开实施例提供一种失败信息的传输方法及装置。
第一方面，本公开实施例提供一种失败信息的传输方法，该方法由目标主节点MN执行，方法包括：
与源主节点MN交互终端设备主小区组MCG失败的相关信息。
本公开中，目标MN可以与源主节点MN交互终端设备主小区组MCG失败的相关信息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
第二方面，本公开实施例提供一种失败信息的传输方法，该方法由源主节点MN执行，方法包括：
与目标主节点MN交互终端设备主小区组MCG失败的相关信息。
本公开中，源主节点MN可以与目标MN交互终端设备主小区组MCG失败的相关信息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
第三方面，本公开实施例提供一种失败信息的传输方法，该方法由目标主节点MN执行，方法包括：
与辅节点SN交互终端设备主小区组MCG失败的相关信息。
本公开中，目标MN可以与SN交互终端设备主小区组MCG失败的相关信息。由此，目标主节点MN即可指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
第四方面，本公开实施例提供一种通信装置，应用于目标主节点MN侧，包括：
收发模块模块，用于与源主节点MN交互终端设备主小区组MCG失败的相关信息。
第五方面，本公开实施例提供一种通信装置，应用于源主节点MN侧，包括：
收发模块模块，用于与目标主节点MN交互终端设备主小区组MCG失败的相关信息。
第六面，本公开实施例提供一种通信装置，应用于目标主节点MN侧，包括：
收发模块，用于与辅节点SN交互终端设备主小区组MCG失败的相关信息。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的 计算机程序时，执行上述第三方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第十一方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第十二方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第三方面所述的方法。
第十三方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十四方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十五方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第三方面所述的方法。
第十六方面，本公开实施例提供一种失败信息的传输系统，该系统包括第四方面所述的通信装置、第五方面所述的通信装置以及第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置、第八方面所述的通信装置以及第九方面所述的通信装置，或者，第十方面所述的通信装置、第十一方面所述的通信装置以及第十二方面所述的通信装置，或者，该系统包括第十三方面所述的通信装置、第十四方面所述的通信装置以及第十五方面所述的通信装置。
第十七方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第十八方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第二方面所述的方法。
第十九方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第三方面所述的方法。
第二十方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第二十一方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第二十二方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第三方面所述的方法。
第二十三方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十四方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十五方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第三方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十六方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方 面所述的方法。
第二十七方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第二十八方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第三方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1a是本公开实施例提供的一种MCG和SCG移动性同时执行时的信令流程示意图；
图1b是本公开实施例提供的一种通信系统的架构示意图；
图2是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图3是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图4a是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图4b是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图4c是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图4d是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图5a是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图5b是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图5c是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图5d是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图5e是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图6是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图7a是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图7b是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图7c是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图7d是本公开实施例提供的一种失败信息的传输方法的流程示意图；
图8是本公开实施例提供的一种失败信息的传输方法的交互示意图；
图9a是本公开实施例提供的一种失败信息的传输方法的交互示意图；
图9b是本公开实施例提供的一种失败信息的传输方法的交互示意图；
图9c是本公开实施例提供的一种失败信息的传输方法的交互示意图；
图10是本公开实施例提供的一种通信装置的结构示意图；
图11是本公开实施例提供的另一种通信装置的结构示意图；
图12是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于理解，首先介绍本公开涉及的术语。
1、源MN
当前为终端设备服务的MN。
2、目标MN
用于为终端设备准备目标PCell，目标MCG，候选目标PCell，候选目标MCG中的一种或多种的MN.准备候选目标PCell和/或候选目标MCG的目标MN也可以称为候选目标MN。
3、目标MCG
目标MCG为发起MCG改变后可以为终端设备提供网络服务的目标MCG或候选目标MCG，对应于目标MN。
4、主节点
在双连接通信系统中，终端设备可以同时链接两个网络设备，其中，用于主要控制终端设备通信的网络设备称为主节点MN。
5、辅节点
在双连接通信系统中，终端设备可以同时链接两个网络设备，其中，用于辅助终端设备通信的网络设备称为辅节点SN。
6、条件切换(conditional handover，CHO)
终端设备可以根据预配置的条件，选择目标网络设备，并发起切换执行过程，向目标网络设备发起随机接入。终端设备通过执行CHO可以实现主小区组(master cell group，MCG)的移动性。
7、条件主辅小区添加(conditional PSCell addition，CPA)
终端设备可以根据预配置的条件，确定可添加的PSCell。终端设备通过执行CPA可以实现辅小区组(secondary cell group，SCG)的移动性。
8、条件主辅小区变更(conditional PSCell change，CPC)
终端设备可以根据预配置的条件，确定可接入的目标PSCell。终端设备通过执行CPC可以实现SCG的移动性。
9、小区组选择性激活
网络设备可以向终端设备提供预配置的候选的目标小区组或目标小区。后续终端设备可以根据网络设备下发的配置(例如激活消息)或是相应的激活事件将预配置的候选小区组或小区激活或去激活，而不需要重新提供小区组的配置。其中，网络设备下发的配置可以包括以下任意一项：配置ID，激活条件，待激活小区组/小区的配置。或是说，在小区组选择性激活中，激活新的小区或小区组，或者应用新的小区配置或小区组配置后或者接入新的小区或小区组后，终端设备不会删除相应的小区组选择性激活的配置信息。
小区组的选择性激活(selective activation of cell groups)，也可以称为小区组激活。其可以使小区组或小区改变后，相应的配置信息仍然能够执行，无需网络重新配置或者重新初始化相应的小区组激活的配置信息。这可以减少信令开销和小区组改变的中断时长。小区组激活的配置信息可以包括：配置ID以及目标小区的配置或目标小区组的配置。可选的，小区组激活的配置信息还可以包括触发条件(也可以称为执行条件、激活条件)。
在一实施例中，小区组激活是一种移动性管理过程，包括任意一种通过配置小区组激活配置，UE终端设备根据网络发送的信令，或协议规定的准则，或终端设备UE自主等方式激活或去激活相应的小区或小区组，或者应用相应的小区配置或小区组配置后或者接入小区或小区组的移动性管理过程。
在一实施例中，小区组激活是一种移动性管理过程，包括任意一种在执行移动性过程后，不删除或释放相应的部分或全部配置信息的移动性管理过程。其中不删除或释放相应的部分或全部配置信息也可以叫做，保留相应的部分或全部配置信息。
10、基于条件触发的移动性管理：
在R16/R17中，引入了基于条件触发的移动性管理，UE基于网络配置的条件以及相关联的候选小区来实现基于条件触发的移动性管理，UE在满足条件后则触发移动性管理，接入其关联的候选小区。其中网络配置的条件可以是特定的基于测量结果的事件，或是基于位置，基于时间的事件。关联的候选小区可以为候选的主小区，主辅小区，分别对应相应的基于条件触发的移动性管理CHO和CPC/CPA。目前R17中支持MN启动的CHO,MN启动的CPA/CPC,SN启动的CPC。
CHO，CPA/CPC的配置分别包含了相应的配置ID，执行条件以及候选目标小区的配置
但是目前不支持同时配置CHO和CPA/CPC。为了提升鲁棒性，减少对UE吞吐量的影响，后续可以研究CHO和CPC/CPA结合的方案，决定在CHO中包括目标MCG以及用于CPC/CPA的候选SCG。
11、网络设备配置终端设备同时进行MCG和SCG的移动性的配置方法为：
可以通过配置同时进行CHO和CPA(或CPC)，实现同时进行MCG和SCG的移动性的配置，配置同时进行CHO和CPA(或CPC)可能包括如下几种情况：
1)CHO和CPA(或CPC)的配置包含在同一个的条件重配的条目中，关联同一个条件重配标识ID，其中，配置标识可以为条件重配的编号等任一可以确定联合配置的信息。
在一种实现方式中，CHO和CPA(或CPC)可以对应同一个执行条件或不同的执行条件。
在一种实现方式中，CHO和CPA(或CPC)可以对应同一个候选目标配置，比如，可以通过RRCReconfiguration配置目标MCG的配置和目标SCG的配置，或还可以对应不同的候选目标配置。
2)CHO和CPA(或CPC)的配置是独立的条件重配条目，但是CHO的条件重配条目和CPA(或CPC)的条件重配条目存在关联关系。
3)CHO的候选目标小区的配置中包含其关联的CPA(或CPC)的配置，比如，CHO的候选目标小区的配置中包含其关联的的CPA(或CPC)的执行条件和候选PSCell的配置。
或者，可以通过配置MCG和SCG的选择性激活，实现同时进行MCG和SCG的移动性的配置，配置MCG和SCG的选择性激活可能包括如下几种情况：
1)MCG激活和SCG激活的配置包含在同一个小区组选择性激活的条目中，对应同一个激活配置标识ID，其中，激活配置标识可以为激活重配的编号等任一可以确定激活配置的信息。
在一种实现方式中，MCG激活和SCG激活对应同一个激活条件或不同的激活条件(可能会配置激活条件)。
在一种实现方式中，MCG激活和SCG激活可以对应同一个“待激活小区”配置，比如，通过RRCReconfiguration配置目标MCG的配置和目标SCG的配置)，或可以对应不同的“待激活小区”配置。
2).MCG激活和SCG激活的配置是独立的条件重配条目，MCG激活配置的条件重配条目和SCG激活配置的条件重配条目存在关联关系。
3)MCG的“待激活小区”配置中包含其关联的多个SCG“待激活小区”的配置。
12、MCG和SCG移动性同时执行时的信令流程：
源主节点可以向一个或多个目标MN发送用于请求一个或多个目标MN为双连接终端设备准备资源的主小区组MCG改变请求消息，之后，目标MN可以根据MCG改变请求消息，确定目标候选MCG及目标候选SCG，或者，通过与目标SN进行交互，为DC终端设备准备目标候选SCG，然后，目标MN可以向源MN反馈资源准备成功或失败消息，从而实现能够同时改变MCG和SCG或者改变MCG的同时增加SCG。如图1a，图1a为MCG和SCG移动性同时执行时的信令流程示意图。但是MR-DC中如果网络配置了MCG和SCG同时改变，可能同时涉及到多个目标MN和多个目标SN，需要同时改变MCG和SCG或者在改变MCG的同时增加SCG，需要多个MN，SN节点进行信令交互。与单一的SCG的移动性不同，目标SN会与相应的目标MN存在连接，不会与源MN关联。
本公开中，小区组为主小区组(MCG)，及辅小区组(SCG)中的一种或多种。其中MCG包括主小区(Primary Cell，PCell)，辅小区(Secondary Cell，SCell)中的一种或多种。其中，SCG包括主辅小区(Primary Secondary Cell，PSCell)，辅小区(SCell)中的一种或多种。
在本公开中，小区组选择性激活可以包括小区选择性激活或小区激活，例如，PCell激活，PSCell激活，SCell激活中的一种或多种。
在本公开中，小区组也可以是小区，其中，MCG也可以是主小区，SCG也可以是主辅小区。
在本公开中，所述源主节点MN也可以称为老MN，目标MN也可以称为新MN，SN可以为目标SN，新SN，源SN，老SN中的至少一种。为了更好的理解本公开实施例公开的一种失败信息的传输方法，下面首先对本公开实施例适用的通信系统进行描述。
请参见图1b，图1b为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络设备和一个终端设备，图1b所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络设备，两个或两个以上的辅助通信设备，两个或两个以上的终端设备。图1b所示的通信系统以包括一个主节点11、一个终端设备12和一个辅节点13为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本公开实施例中的主节点11和辅节点13是网络侧的一种用于发射或接收信号的实体，其可以分别为终端设备12对应的主节点和辅节点。例如，主节点11和辅节点13可以分别为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对网络设备所采用的具体技术和具体设备形态不做限定。本公开实施例提供的网络设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端设备12是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
通常，终端设备进行MCG或SCG的移动性失败时，终端设备可以通过上报失败信息进行小区组失败恢复。但是，当网络设备为终端设备配置了同时进行MCG和SCG的移动性时，终端设备可能发生SCG接入成功，但是MCG接入失败的情况。在此种情况下，由于终端设备只能将MCG失败信息发送给成功接入的SCG，而成功接入的SCG与源MN没有直接的连接，因此，源MN无法获取到终端设备的MCG失败信息，并且源MN也无法将用于恢复或释放MCG连接的指示信息，通过接入成功的SCG发送给终端设备，从而无法进行MCG失败恢复。
本公开中，当网络设备为终端设备配置了同时进行MCG和SCG的移动性，且终端设备发生SCG接入成功，MCG接入失败的情况下，终端设备可以通过各网络节点的交互，向源主节点MN或目标主节点MN上报MCG失败信息，当源主节点MN或目标主节点MN接收到MCG失败信息后，可以通过各网络节点的交互向终端设备发送指示信息，以指示终端设备恢复MCG的连接或释放MCG的连接，从而保证小区组移动性管理的可靠性。
需要说明的是，本公开中，任一个实施例提供的一种失败信息的传输方法可以单独执行，或是结合其他实施例中的可能的实现方法一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
下面结合附图和具体实施例对本公开所提供的一种失败信息的传输方法及其装置进行详细地介绍。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
取决于语境，如在此所使用的词语“如果”及“响应于”可以被解释成为“在……时”或“当……时”或“响应于确定”。
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的要素。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。
请参见图2，图2是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由辅节点SN执行。如图2所示，该方法可以包括但不限于如下步骤：
在本公开中，SN可以为目标SN也可以为源SN，本发明不做限定
步骤201，接收终端设备发送的主小区组MCG失败信息。
本公开中，当网络设备为终端设备配置了同时进行MCG和SCG的移动性时，终端设备可能发生SCG接入成功，但是MCG接入失败的情况。此时，终端设备可以生成MCG失败信息，并将MCG失败信息发送给辅节点SN，以向SN同步终端设备发生了MCG接入失败。其中，辅节点SN可以是终端设备执行MCG和SCG的移动性时，成功接入的SCG对应的SN。
可选的，网络设备可以通过为终端设备配置联合的CHO和CPA，或者，配置联合的CHO和CPC，或者，配置MCG和SCG的选择性激活，实现同时进行MCG和SCG的移动性。网络设备可以通过执 行CHO或MCG选择性激活实现MCG移动性，可以通过执行CPA(或CPC)或SCG选择性激活实现SCG移动性。
其中，联合的CHO和CPC可以包括CHO中包括CPC配置，联合的CHO和CPA可以包括CHO中包括CPA配置。
步骤202，向目标主节点MN发送第一消息，其中，第一消息中包含MCG失败信息。
本公开中，辅节点SN可以根据接收到的终端设备发送的MCG失败信息，生成第一消息，并向目标主节点MN发送第一消息，以向目标MN同步终端设备发生了MCG失败。
可选的，MCG失败信息可以以无线资源控制(radio resource control，RRC)容器Container的形式包含于第一消息中。
可选的，第一消息还可以包括以下至少一项：终端设备的标识，SN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
其中，终端设备的标识可以为用于确定终端设备的信息，可以为以下至少一项：终端设备在SN中的标识，终端设备在目标MN中的标识，及终端设备在源MN中的标识。比如，终端设备在网络节点(SN、目标MN、源MN)接口上的标识(例如：XnAP ID)。SN的标识可以为SN的编号等任一可以确定SN的信息。目标MN的标识可以为目标MN的编号等任一可以确定目标MN的信息。源MN的标识可以为源MN的编号等任一可以确定源MN的信息。小区的标识可以为小区的编号等任一可以确定小区的信息。
可选的，第一消息还可以为RRC转移TRANSFER消息。
步骤203，接收目标MN发送的第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
其中，第二消息中可以包含以下至少一项：终端设备的标识，目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
此外，第二消息与第一消息中所包含项，以及各项的值可以相同，也可以不同。比如，第二消息中可以包括终端设备在目标MN接口上的标识和目标MN的标识，第一消息中可以包括终端设备在SN接口上的标识和SN的标识等，本公开对此不作限制。
本公开中，目标MN在接收到第一消息后，可以确定终端设备发生了MCG失败，之后，可以根据MCG失败信息，指示终端设备进行连接或释放MCG，并将包含用于指示终端设备进行连接或释放的指示信息的第二消息，发送给SN。
或者，目标MN还可以将MCG失败信息发送给源MN，并接收源MN发送的用于指示终端设备进行连接或释放的指示信息，并根据该指示信息生成第二消息，发送给SN。
可选的，指示信息可以为RRC消息，RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自进化的通用移动通信系统(universal mobile telecommunications system UMTS)陆地无线接入(Evolved-UMTS Terrestrial Radio Access，EUTRA)的移动命令消息，RRC连接释放消息，及RRC释放消息等，本公开对此不作限制。
可选的，指示信息(即用于指示终端设备进行连接或释放的RRC消息)可以以RRC容器Container的形式包含于第二消息中。
可选的，第二消息还可以为RRC转移TRANSFER消息。
此外，第一消息与第二消息对应于同一消息时，比如第一消息与第二消息都为RRC TRANSFER消息时，则RRC TRANSFER消息的传输方向可以为目标MN发送給SN，或者SN发送給目标主节点MN。
示例性的，当该消息用于传输MCG失败信息时，可以确定该消息的传输方向为目标MN发送給SN，当该消息用于传输指示信息时，可以确定该消息的传输方向为SN发送給目标MN。
需要说明的是，示例性的，该同一消息的传输方向适用于同时配置了MCG和SCG的移动性的场景中。
步骤204，向终端设备发送包含指示信息的消息。
本公开中，辅节点SN可以根据接收到的目标MN发送的第二消息，确定指示信息，并可以向终端设备发送包含指示信息的消息。由此，终端设备即可根据该指示信息，进行连接或释放MCG，从而保证小区组移动性管理的可靠性。
本公开中，辅节点SN在接收终端设备发送的主小区组MCG失败信息后，可以向目标主节点MN发送包含MCG失败信息第一消息，之后，可以接收目标MN发送的包含用于指示终端设备进行连接或释放的指示信息的第二消息，然后，可以向终端设备发送包含指示信息的消息。由此，终端设备通过各网络节点的交互，将MCG失败消息上报给目标MN，目标MN即可根据MCG失败消息，通过各网络节点的交互，指示终端设备进行连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图3，图3是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由终端设备执行。如图3所示，该方法可以包括但不限于如下步骤：
步骤301，向辅节点SN发送主小区组MCG失败信息。
本公开中，当网络设备为终端设备配置了同时进行MCG和SCG的移动性时，终端设备可能发生SCG接入成功，但是MCG接入失败的情况。此时，终端设备可以生成MCG失败信息，并将MCG失败信息发送给辅节点SN，以向SN同步终端设备发生了MCG接入失败。其中，辅节点SN可以是终端设备同时执行MCG和SCG的移动性时，成功接入的SCG对应的SN。
可选的，网络设备可以通过为终端设备配置联合的CHO和CPA，或者，配置联合的CHO和CPC，或者，配置MCG和SCG的选择性激活，实现同时进行MCG和SCG的移动性。网络设备可以通过执行CHO或MCG选择性激活实现MCG移动性，可以通过执行CPA(或CPC)或SCG选择性激活实现SCG移动性。
其中，联合的CHO和CPC可以包括CHO中包括CPC配置，联合的CHO和CPA可以包括CHO中包括CPA配置。
步骤302，接收SN发送的包含指示终端设备进行连接或释放的指示信息的消息。
本公开中，辅节点接收到目标主节点MN发送的用于指示终端设备进行连接或释放的指示信息后，可以向终端设备发送包含该指示信息的消息，由此，终端设备即可根据该指示信息，进行连接或释放MCG，从而保证小区组移动性管理的可靠性。其中，指示信息可以为目标主节点MN根据接收到的终端设备的MCG失败信息确定的。
可选的，在终端设备同时进行MCG和SCG移动性，在MCG失败的情况下，也可以不向SN发送MCG失败信息。
在一种实现方式中，在终端设备同时进行MCG和SCG移动性，在MCG失败的情况下，终端设备不允许发送MCG失败信息。
示例性的，基于协议规定，或网络设备指示，或终端设备实现，当终端设备同时进行MCG和SCG移动性，在MCG失败的情况下，终端设备不允许发送MCG失败信息。
在一种实现方式中，在终端设备同时进行MCG和SCG移动性，不支持终端设备发送失败信息，所述失败信息包括MCG失败信息。
在一种实现方式中，在终端设备同时进行MCG和SCG移动性，只支持终端设备发送SCG失败信息。
可选的，在终端设备进行MCG移动性，且未配置SCG移动性的情况下，当MCG失败时，也可以通过上报MCG失败信息进行MCG连接的恢复。
本公开中，终端设备向辅节点SN发送主小区组MCG失败信息后，可以接收SN发送的包含指示终端设备进行连接或释放的指示信息的消息。由此，终端设备可以根据指示信息连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图4a，图4a是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图4a所示，该方法可以包括但不限于如下步骤：
步骤401a，与辅节点SN交互终端设备主小区组MCG失败的相关信息。
公开中，当网络设备为终端设备配置了同时进行MCG和SCG的移动性时，终端设备可能发生SCG接入成功，但是MCG接入失败的情况。此时，终端设备可以生成MCG失败信息，并将MCG失败信息发送给辅节点SN，之后，目标MN可以与SN交互终端设备主小区组MCG失败的相关信息，比如，目标MN可以接收SN发送的MCG失败信息，和/或目标MN可以向SN指示终端设备进行连接或释放的指示信息。由此，终端设备即可根据指示信息释放或恢复MCG连接，从而保证小区组移动性管理的可靠性。
本公开中，目标MN可以与SN交互终端设备主小区组MCG失败的相关信息。由此，目标主节点MN即可指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图4b，图4b是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图4b所示，该方法可以包括但不限于如下步骤：
步骤401b，接收辅节点SN发送的第一消息，其中，第一消息中包含终端设备的MCG失败信息。
本公开中，当网络设备为终端设备配置了同时进行MCG和SCG的移动性时，终端设备可能发生SCG接入成功，但是MCG接入失败的情况。此时，终端设备可以生成MCG失败信息，并将MCG失败信息发送给辅节点SN，以向SN同步终端设备发生了MCG接入失败。之后，辅节点SN可以根据接收到的终端设备发送的MCG失败信息，生成第一消息，并向目标主节点MN发送第一消息，以同步目标主节点终端设备发生了MCG失败。其中，辅节点SN可以是终端设备同时执行MCG和SCG的移动性时，成功接入的SCG对应的SN。
可选的，网络设备可以通过为终端设备配置联合的CHO和CPA，或者，配置联合的CHO和CPC，或者，配置MCG和SCG的选择性激活，实现同时进行MCG和SCG的移动性。网络设备可以通过执行CHO或MCG选择性激活实现MCG移动性，可以通过执行CPA(或CPC)或SCG选择性激活实现SCG移动性。
其中，联合的CHO和CPC可以包括CHO中包括CPC配置，联合的CHO和CPA可以包括CHO中包括CPA配置。
可选的，MCG失败信息可以以无线资源控制(radio resource control，RRC)容器Container的形式包含于第一消息中。
可选的，第一消息可以包括以下至少一项：终端设备的标识，SN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
其中，终端设备的标识可以为用于确定终端设备的信息，可以为以下至少一项：终端设备在SN中的标识，终端设备在目标MN中的标识，及终端设备在源MN中的标识。比如，终端设备在网络节点(SN、目标MN、源MN)接口上的标识(例如：XnAP ID)。SN的标识可以为SN的编号等任一可以确定SN的信息。目标MN的标识可以为目标MN的编号等任一可以确定目标MN的信息。源MN的标识可以为源MN的编号等任一可以确定源MN的信息。小区的标识可以为小区的编号等任一可以确定小区的信息。
可选的，第一消息还可以为RRC转移TRANSFER消息。
可选的，目标MN收到该第一消息后，即可响应该MCG失败信息。比如目标MN可以指示终端设备进行连接，或者释放连接等；或者，目标MN也可以将该MCG失败信息透传给源MN，由源MN对该失败信息进行响应等，本公开对此不做限定。
本公开中，目标MN可以收辅节点SN发送的包含终端设备的MCG失败信息的第一消息，之后，目标主节点MN即可指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图4c，图4c是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图4c所示，该方法可以包括但不限于如下步骤：
步骤401c，向SN发送第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
其中，第二消息中可以包含以下至少一项：终端设备的标识，目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。以上各标识的具体描述可参见本公开任一实施例的详细描述，在此不再赘述。
本公开中，目标MN在确定终端设备发生了MCG失败，之后，可以根据MCG失败信息，指示终端设备进行连接或释放MCG，并将包含用于指示终端设备进行连接或释放的指示信息的第二消息，发送给SN。由此，SN可以将该指示消息发送给终端设备，以指示终端设备进行连接或释放MCG，从而保证小区组移动性管理的可靠性。
可选的，目标MN可以根据接收到的MCG失败信息、终端设备的测量结果及自身当前的负载中的一项或多项，确定终端设备发生了MCG失败，本公开对此不做限定。
可选的，指示信息可以为RRC消息，RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息等，本公开对此不作限制。
可选的，指示信息(即用于指示终端设备进行连接或释放的RRC消息)可以以RRC容器Container 的形式包含于第二消息中。
可选的，第二消息还可以为RRC转移TRANSFER消息。
需要说明的是，示例性的，该同一消息的传输方向适用于同时配置了MCG和SCG的移动性的场景中。
本公开中，目标MN可以向SN发送包含用于指示终端设备进行连接或释放的指示信息的第二消息，之后，终端设备即可根据指示信息恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图4d，图4d是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图4d所示，该方法可以包括但不限于如下步骤：
步骤401d，接收辅节点SN发送的第一消息，其中，第一消息中包含终端设备的MCG失败信息。
步骤402d，向SN发送第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
本公开中，步骤402d-步骤403d的具体描述，可参见本公开任一实施例的详细描述，在此不再赘述。
此外，第二消息与第一消息中所包含项，以及各项的值可以相同，也可以不同。比如，第二消息中可以包括终端设备在目标MN接口上的标识和目标MN的标识，第一消息中可以包括终端设备在SN接口上的标识和SN的标识等，本公开对此不作限制。
第一消息与第二消息对应于同一消息时，比如第一消息与第二消息都为RRC TRANSFER消息时，则RRC TRANSFER消息的传输方向可以为目标MN发送給SN，或者SN发送給目标主节点MN。
示例性的，当该消息用于传输MCG失败信息时，可以确定该消息的传输方向为目标MN发送給SN，当该消息用于传输指示信息时，可以确定该消息的传输方向为SN发送給目标MN。
需要说明的是，示例性的，该同一消息的传输方向适用于同时配置了MCG和SCG的移动性的场景中。
本公开中，目标MN接收辅节点SN发送的包含终端设备的MCG失败信息的第一消息后，可以向SN发送包含用于指示终端设备进行连接或释放的指示信息的第二消息。由此，终端设备可以根据指示信息连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图5a，图5a是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图5a所示，该方法可以包括但不限于如下步骤：
步骤501a，与源主节点MN交互终端设备主小区组MCG失败的相关信息。
本公开中，当网络设备为终端设备配置了同时进行MCG和SCG的移动性时，终端设备可能发生SCG接入成功，但是MCG接入失败的情况。此时，终端设备可以生成MCG失败信息，并将MCG失败信息通过个网络节点的交互发送给目标MN，之后，目标MN可以与源主节点MN交互终端设备主小区组MCG失败的相关信息，比如，目标MN可以将MCG失败信息发送给源MN，和/或目标MN可以接收源MN发送的指示终端设备进行连接或释放的指示信息。由此，终端设备即可根据指示信息释放或恢复MCG连接，从而保证小区组移动性管理的可靠性。
本公开中，目标MN可以与源主节点MN交互终端设备主小区组MCG失败的相关信息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图5b，图5b是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图5b所示，该方法可以包括但不限于如下步骤：
步骤501b，向源MN发送第一消息，其中，第一消息中包含终端设备的MCG失败信息。
本公开中，目标主节点MN可以根据接收到的辅节点SN发送的终端设备的MCG失败信息生成第一消息，并将该第一消息发送给源MN，以向源MN同步终端设备发生了MCG连接失败。
可选的，网络设备可以通过为终端设备配置联合的CHO和CPA，或者，配置联合的CHO和CPC，或者，配置MCG和SCG的选择性激活，实现同时进行MCG和SCG的移动性。网络设备可以通过执行CHO或MCG选择性激活实现MCG移动性，可以通过执行CPA(或CPC)或SCG选择性激活实现SCG移动性。
其中，联合的CHO和CPC可以包括CHO中包括CPC配置，联合的CHO和CPA可以包括CHO中包括CPA配置。
可选的，MCG失败信息可以以无线资源控制(radio resource control，RRC)容器Container的形式 包含于第一消息和第三消息中。
本公开中，第一消息可以包含以下至少一项：终端设备的标识，目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
其中，终端设备的标识可以为用于确定终端设备的信息，可以为以下至少一项：终端设备在SN中的标识，终端设备在目标MN中的标识，及终端设备在源MN中的标识。比如，终端设备在网络节点(SN、目标MN、源MN)接口上的标识(例如：XnAP ID)。SN的标识可以为SN的编号等任一可以确定SN的信息。目标MN的标识可以为目标MN的编号等任一可以确定目标MN的信息。源MN的标识可以为源MN的编号等任一可以确定源MN的信息。小区的标识可以为小区的编号等任一可以确定小区的信息。
可选的，第一消息还可以为RRC转移TRANSFER消息。
可选的源MN在收到终端设备的MCG失败信息后，即可响应该信息，比如指示终端设备进行连接恢复或释放等。
本公开中，目标主节点可以向源MN发送包含终端设备的MCG失败信息第一消息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图5c，图5c是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图5c所示，该方法可以包括但不限于如下步骤：
步骤501c，接收源MN发送的第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
其中，第二消息中可以包含以下至少一项：终端设备的标识，源MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
本公开中，源MN在确定终端设备发生了MCG失败后，可以对该MCG失败信息进行响应，比如，指示终端设备进行连接或释放MCG，并将包含用于指示终端设备进行连接或释放的指示信息的第二消息，发送给目标MN。
可选的，源MN可以根据接收到的MCG失败信息、终端设备的测量结果及自身当前的负载中的一项或多项，确定终端设备发生了MCG失败，本公开对此不做限定。
可选的，指示信息可以为RRC消息，RRC消息可以为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息等，本公开对此不作限制。
可选的，第二消息还可以为RRC转移TRANSFER消息。
可选的，指示信息(即用于指示终端设备进行连接或释放的RRC消息)可以以RRC容器Container的形式包含于第二消息中。
本公开中，目标MN可以接收源MN发送的包含用于指示终端设备进行连接或释放的指示信息的第二消息，由此，终端设备即可根据指示信息恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图5d，图5d是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图5d所示，该方法可以包括但不限于如下步骤：
步骤501d，向源MN发送第一消息，其中，第一消息中包含终端设备的MCG失败信息。
步骤502d，接收源MN发送的第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
本公开中，步骤502d-步骤503d的具体描述，可参见本公开任一实施例的详细描述，在此不再赘述。
此外，第一消息与第二消息对应于同一消息时，比如第一消息与第二消息都为RRC TRANSFER消息时，则RRC TRANSFER消息的传输方向可以为目标MN发送給源MN，或者源MN发送給目标MN。
示例性的，当该消息用于传输MCG失败信息时，可以确定该消息的传输方向为目标MN发送給源MN，当该消息用于传输指示信息时，可以确定该消息的传输方向为源MN发送給目标MN。
需要说明的是，示例性的，该同一消息的传输方向适用于同时配置了MCG和SCG的移动性的场景中。
本公开中，目标MN向源MN发送包含终端设备的MCG失败信息的第一消息后，可以接收源MN发送的包含用于指示终端设备进行连接或释放的指示信息的第二消息。由此，终端设备可以根据指示信息连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图5e，图5e是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图e所示，该方法可以包括但不限于如下步骤：
步骤501e，接收辅节点SN发送的第三消息，其中，第三消息中包含终端设备的MCG失败信息。
其中，第三消息中可以包含以下至少一项：终端设备的标识，SN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。以上各标识的详细解释可参见本公开任一实施例的详细描述，在此不再赘述。
本公开中，辅节点SN可以根据接收到的终端设备发送的MCG失败信息，生成第三消息，并向目标主节点MN发送第三消息，以告知目标主节点MN终端设备发生了MCG失败。
步骤502e，向源MN发送第一消息，其中，第一消息中包含终端设备的MCG失败信息。
步骤503e，接收源MN发送的第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
本公开中，步骤502e-步骤503e的具体描述，可参见本公开任一实施例的详细描述，在此不再赘述。
此外，第三消息与第一消息中所包含项，以及各项的值可以相同，也可以不同。比如，第一消息中可以包括终端设备在目标MN接口上的标识和目标MN的标识，第三消息中可以包括终端设备在SN接口上的标识和SN的标识等，本公开对此不作限制。
可选的，第一消息、第二消息、第三消息中任意一个或多个可以为RRC转移TRANSFER消息。
此外，第二消息、第三消息与第一消息中所包含项，以及各项的值可以相同，也可以不同，本公开对此不作限制。
本公开中，目标MN接收辅节点SN发送的包含终端设备的MCG失败信息的第三消息后，可以向源MN发送包含终端设备的MCG失败信息的第一消息，之后，可以接收源MN发送的包含用于指示终端设备进行连接或释放的指示信息的第二消息。由此，终端设备可以根据指示信息连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图6，图6是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由目标主节点MN执行。如图6所示，该方法可以包括但不限于如下步骤：
步骤601，向源MN发送第一消息，其中，第一消息中包含终端设备的MCG失败信息。
步骤602，接收源MN发送的第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
本公开中，步骤601-步骤602的具体解释，可参见本公开任一实施例的详细描述，在此不再赘述。
步骤603，向SN发送第四消息，其中，第四消息中包含指示信息。
本公开中，目标MN在可以根据接收到的源MN发送的第二消息，确定指示信息，之后可以根据指示信息生成第四消息，并将第四消息发送给SN。由此，SN即可确定指示信息，并将指示信息发送给终端设备，以指示终端设备进行连接或释放MCG，从而保证小区组移动性管理的可靠性。
可选的，第四消息可以为RRC转移TRANSFER消息。第四消息的传输方向可以为目标MN发送給SN。
可选的，指示信息(即用于指示终端设备进行连接或释放的RRC消息)可以以RRC容器Container的形式包含于第四消息中。
可选的，第四消息中可以包含以下至少一项：终端设备的标识，目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
此外，第四消息、第二消息、第三消息与第一消息中所包含项，以及各项的值可以相同，也可以不同，本公开对此不作限制。本公开中，目标MN向源MN发送包含终端设备的MCG失败信息的第一消息后，可以接收源MN发送的包含用于指示终端设备进行连接或释放的指示信息的第二消息，之后，可以向SN发送包含指示信息的第四消息。由此，终端设备可以根据指示信息连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图7a，图7a是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由源主节点MN执行。如图7a所示，该方法可以包括但不限于如下步骤：
步骤701a，与目标主节点MN交互终端设备主小区组MCG失败的相关信息。
本公开中，当网络设备为终端设备配置了同时进行MCG和SCG的移动性时，终端设备可能发生SCG接入成功，但是MCG接入失败的情况。此时，终端设备可以生成MCG失败信息，并将MCG失败信息通过个网络节点的交互发送给目标MN，之后，目标MN可以与源主节点MN交互终端设备主小区组MCG失败的相关信息，比如，源MN可以接收目标MN发送的MCG失败信息，和/或目标MN可以源MN可以向目标MN发送指示终端设备进行连接或释放的指示信息。由此，终端设备即可根据指示信息释放或恢复MCG连接，从而保证小区组移动性管理的可靠性。
本公开中，源主节点MN可以与目标MN交互终端设备主小区组MCG失败的相关信息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图7b，图7b是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由源主节点MN执行。如图7b所示，该方法可以包括但不限于如下步骤：
步骤701b，接收目标MN发送的第一消息，其中，第一消息中包含终端设备的MCG失败信息。
本公开中，目标主节点MN可以根据接收到的SN发送的终端设备的MCG失败信息，生成第一消息，并发送给源MN，以向源MN同步终端设备发生了MCG连接失败。
可选的，网络设备可以通过为终端设备配置联合的CHO和CPA，或者，配置联合的CHO和CPC，或者，配置MCG和SCG的选择性激活，实现同时进行MCG和SCG的移动性。网络设备可以通过执行CHO或MCG选择性激活实现MCG移动性，可以通过执行CPA(或CPC)或SCG选择性激活实现SCG移动性。
其中，联合的CHO和CPC可以包括CHO中包括CPC配置，联合的CHO和CPA可以包括CHO中包括CPA配置。
可选的，MCG失败信息可以以无线资源控制(radio resource control，RRC)容器Container的形式包含于第一消息中。
本公开中，第一消息中可以包含以下至少一项：终端设备的标识，目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
其中，终端设备的标识可以为用于确定终端设备的信息，可以为以下至少一项：终端设备在SN中的标识，终端设备在目标MN中的标识，及终端设备在源MN中的标识。比如，终端设备在网络节点(SN、目标MN、源MN)接口上的标识(例如：XnAP ID)。SN的标识可以为SN的编号等任一可以确定SN的信息。目标MN的标识可以为目标MN的编号等任一可以确定目标MN的信息。源MN的标识可以为源MN的编号等任一可以确定源MN的信息。小区的标识可以为小区的编号等任一可以确定小区的信息。
可选的，第一消息还可以为RRC转移TRANSFER消息。
可选的，源MN在收到终端设备的MCG失败信息后，即可对该信息进行响应，比如指示终端设备释放连接，或者恢复连接等等，本公开对此不做限定。
本公开中，源主节点可以接收目标MN发送的包含终端设备的MCG失败信息的第一消息，由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图7c，图7c是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由源主节点MN执行。如图7c所示，该方法可以包括但不限于如下步骤：
步骤701c，向目标MN发送第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
其中，第二消息中可以包含以下至少一项：终端设备的标识，SN的标识，目标MN的标识，源MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。以上各标识的具体描述，可参见本公开任一实施例的详细描述，在此不再赘述。
本公开中，源MN在确定终端设备发生了MCG失败，之后，可以根据MCG失败信息，指示终端设备进行连接或释放MCG，并将包含用于指示终端设备进行连接或释放的指示信息的第二消息，发送给目标MN。
可选的，源MN可以根据接收到的MCG失败信息、终端设备的测量结果及自身当前的负载中的一项或多项，确定终端设备发生了MCG失败，本公开对此不做限定。
可选的，指示信息可以为RRC消息，RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息等，本公开对此不作限制。
可选的，指示信息(即用于指示终端设备进行连接或释放的RRC消息)可以以RRC容器Container的形式包含于第二消息中。
可选的，第二消息还可以为RRC转移TRANSFER消息。
本公开中，源MN可以向目标MN发送包含用于指示终端设备进行连接或释放的指示信息的第二消息。由此，终端设备即可根据指示信息恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。请参见图7d，图7d是本公开实施例提供的一种失败信息的传输方法的流程示意图，该方法由源主节点MN执行。如图7d所示，该方法可以包括但不限于如下步骤：
步骤701d，接收目标MN发送的第一消息，其中，第一消息中包含终端设备的MCG失败信息。
步骤702d，向目标MN发送第二消息，其中，第二消息中包含用于指示终端设备进行连接或释放的指示信息。
本公开中，步骤701d-步骤702d的具体描述，可参见本公开任一实施例的详细描述，在此不再赘述。
此外，第二消息与第一消息中所包含项，以及各项的值可以相同，也可以不同。比如，第二消息中可以包括终端设备在源MN接口上的标识和源MN的标识，第一消息中可以包括终端设备在目标MN接口上的标识和目标MN的标识等，本公开对此不作限制。
此外，第一消息与第二消息对应于同一消息时，比如第一消息与第二消息都为RRC TRANSFER消息时，则RRC TRANSFER消息的传输方向可以为目标MN发送給源MN，或者源MN发送給目标MN。
示例性的，当该消息用于传输MCG失败信息时，可以确定该消息的传输方向为目标MN发送給源MN，当该消息用于传输指示信息时，可以确定该消息的传输方向为源MN发送給目标MN。
需要说明的是，示例性的，该同一消息的传输方向适用于同时配置了MCG和SCG的移动性的场景中。
本公开中，源MN接收目标MN发送的包含终端设备的MCG失败信息的第一消息后，可以向目标MN发送包含用于指示终端设备进行连接或释放的指示信息的第二消息。由此，终端设备可以根据指示信息连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图8，图8是本公开实施例提供的一种失败信息的传输方法的交互示意图。如图8所示，该方法可以包括但不限于如下步骤：
步骤801，辅节点SN接收终端设备发送的主小区组MCG失败信息。
步骤802，辅节点SN向目标主节点MN发送第一消息，其中，第一消息中包含MCG失败信息。
步骤803，目标主节点MN向源MN发送第二消息，其中，第二消息中包含终端设备的MCG失败信息。
步骤804，源MN向目标主节点MN发送第三消息，其中，第三消息中包含用于指示终端设备进行连接或释放的指示信息。
步骤805，目标主节点MN向辅节点SN发送第四消息，其中，第四消息中包含用于指示终端设备进行连接或释放的指示信息。
步骤806，辅节点SN向终端设备发送包含指示信息的消息。
本公开中，步骤801-步骤806的具体解释，可参见本公开任一实施例的详细描述，在此不再赘述。
示例性的，终端设备成功接入的SN在接收到MCG失败消息后，将其转发给连接的目标MN，再由目标MN转发给源MN。由源MN生成RRC消息，转发给此目标MN，由此目标MN再转发给成功接入的SN，由此SN发送给终端设备用于失败恢复。
本公开中，终端设备通过各网络节点的交互，将MCG失败消息上报给源MN，源MN即可根据MCG失败消息，通过各网络节点的交互，指示终端设备进行连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图9a，图9a是本公开实施例提供的一种失败信息的传输方法的交互示意图。如图9a所示，该方法可以包括但不限于如下步骤：
步骤901a，辅节点SN接收终端设备发送的主小区组MCG失败信息。
步骤902a，辅节点SN向目标主节点MN发送第一消息，其中，第一消息中包含MCG失败信息。
步骤903a，目标主节点MN向辅节点SN发送第二消息，其中，第四消息中包含用于指示终端设备进行连接或释放的指示信息。
步骤904a，辅节点SN向终端设备发送包含指示信息的消息。
本公开中，步骤901a-步骤904a的具体解释，可参见本公开任一实施例的详细描述，在此不再赘述。
示例性的，终端设备成功接入的SN在接收到MCG失败消息后，将其转发给连接的目标MN，由此目标MN生成RRC消息，转发给此SN，由SN发送给终端设备用于失败恢复。
本公开中，终端设备通过各网络节点的交互，将MCG失败消息上报给目标MN，目标MN即可根据MCG失败消息，通过各网络节点的交互，指示终端设备进行连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图9b，图9b是本公开实施例提供的一种失败信息的传输方法的交互示意图。如图9b所示，该方法可以包括但不限于如下步骤：
步骤901b，目标MN在接收到SN(终端设备成功接入的目标SN)发送的包含终端设备的MCG失败信息的第一消息后，可以将此MCG失败信息包含在第二消息中转发给源MN。
步骤902b，源MN在接收到目标MN发送的包含终端设备的MCG失败信息的第二消息后，可以将相应的RRC消息包含在第三消息中发送给目标MN。
步骤903b，目标MN在接收到源MN发送的包含终端设备的MCG失败信息的第三消息后，可以将相应的RRC消息包含在第四消息中转发给SN，其中，RRC消息用于指示终端设备释放或者恢复MCG连接。
可选的第一消息，第二消息，第三消息，第四消息均可以为RRC TRANSFER。
可选的，MCG失败信息，以及发送给UE的RRC消息均可以以RRC容器的形式包含于第一消息，第二消息，第三消息，第四消息中。
可选的，对于传输MCG失败信息的消息或者携带发送给UE的RRC消息的消息，传输方向可以为源主节点发送给目标主节点或者目标主节点发送给源主节点。
可选的，此传输方向适用于特定的“移动性管理过程”，此移动性管理过程为：同时进行CHO和CPA(或CPC)(CHO配置和CPA/CPC配置关联)或者MCG和SCG的选择性激活。
可选的，第一消息，第二消息，第三消息，第四消息中可以包括：UE在源MN，目标MN，SN的ID(例如：XnAP ID)中的一种或多种；源MN，目标MN，SN的标识ID中的一种或多种；源MCG，目标MCG，SCG中的一个或多个小区的ID中的一种或多种。
可选的，从目标主节点发送给源主节点的用于快速MCG恢复的RRC TRANSFER中携带MCGFailureInformation。和/或，从源主节点发送给目标主节点的用于快速MCG恢复的RRC TRANSFER中携带发送给UE的RRC消息。
可选的，所述发送给UE的RRC消息包括：RRCConnectionReconfiguration message,RRCReconfiguration message,MobilityFromNRCommand message,MobilityFromEUTRACommand message,RRCConnectionRelease message or RRCRelease message。
可选的，源MN也可以称为老MN，目标MN也可以称为新MN，SN可以为目标SN，或新SN。
本公开中，终端设备通过各网络节点的交互，将MCG失败消息上报给源MN，源MN即可根据MCG失败消息，通过各网络节点的交互，指示终端设备进行连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图9c，图9c是本公开实施例提供的一种失败信息的传输方法的交互示意图。如图9c所示，该方法可以包括但不限于如下步骤：
步骤901c，目标MN在接收到SN(终端设备成功接入的目标SN)发送的包含终端设备的MCG失败信息的第一消息后，将相应的RRC消息包含在第四消息中发送给SN，其中，RRC消息用于指示终端设备释放或者恢复MCG连接。
可选的第一消息，第四消息均可以为RRC TRANSFER。
可选的，MCG失败信息，以及发送给UE的RRC消息均可以以RRC容器的形式包含于第一消息，第四消息中。
可选的，第一消息，第四消息中可以包括：UE在源MN，目标MN，SN的ID(例如：XnAP ID) 中的一种或多种；源MN，目标MN，SN的标识ID中的一种或多种；源MCG，目标MCG，SCG中的一个或多个小区的ID中的一种或多种。
可选的，从目标主节点发送给源主节点的用于快速MCG恢复的RRC TRANSFER中携带MCGFailureInformation。和/或，从源主节点发送给目标主节点的用于快速MCG恢复的RRC TRANSFER中携带发送给UE的RRC消息。
可选的，所述发送给UE的RRC消息包括以下至少一个：RRCConnectionReconfiguration message,RRCReconfiguration message,MobilityFromNRCommand message,MobilityFromEUTRACommand message,RRCConnectionRelease message or RRCRelease message。
可选的，源MN也可以称为老MN，目标MN也可以称为新MN，SN可以为目标SN，或新SN。
可选的，对于传输MCG失败信息的消息或者携带发送给UE的RRC消息的消息，传输方向可以为(目标)主节点发送给(目标)辅节点或者(目标)辅节点发送给(目标)主节点。
可选的，此传输方向适用于特定的“移动性管理过程”，此移动性管理过程为：同时进行CHO和CPA(或CPC)(CHO配置和CPA/CPC配置关联)或者MCG和SCG的选择性激活。
本公开中，终端设备通过各网络节点的交互，将MCG失败消息上报给目标MN，目标MN即可根据MCG失败消息，通过各网络节点的交互，指示终端设备进行连接或者释放MCG，从而保证小区组移动性管理的可靠性。
请参见图10，为本公开实施例提供的一种通信装置1000的结构示意图。图10所示的通信装置1000可包括处理模块1001和收发模块1002。收发模块1002可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块1002可以实现发送功能和/或接收功能。
可以理解的是，通信装置1000可以是辅节点SN，也可以是辅节点SN中的装置，还可以是能够与辅节点SN匹配使用的装置。
通信装置1000在辅节点SN侧，其中：
收发模块1002，用于接收终端设备发送的主小区组MCG失败信息；
上述收发模块1002，还用于向目标主节点MN发送第一消息，其中，所述第一消息中包含所述MCG失败信息；
上述收发模块1002，还用于接收所述目标MN发送的第二消息，其中，所述第二消息中包含用于指示所述终端设备进行连接或释放的指示信息；
上述收发模块1002，还用于向所述终端设备发送包含所述指示信息的消息。
可选的，所述第一消息及所述第二消息中任意一个或多个，为RRC转移TRANSFER消息。
可选的，所述第一消息包含以下至少一项：所述终端设备的标识，所述SN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；和/或，
所述第二消息中包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
可选的，所述终端设备的标识，为以下至少一项：所述终端设备在所述SN中的标识，所述终端设备在所述目标MN中的标识，及所述终端设备在所述源MN中的标识。
可选的，所述指示信息为RRC消息，所述RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息。
可选的，所述MCG失败信息以RRC容器Container的形式包含于所述第一消息中，所述指示信息以RRC容器Container的形式包含于所述第二消息中。
可选的，所述终端设备配置了MCG和SCG的移动性，所述MCG和SCG的移动性包括以下至少之一：
联合的CHO和CPA，或者，联合的CHO和CPC，或者，MCG和SCG的选择性激活。
其中联合的CHO和CPC包括，CHO中包括CPC配置，联合的CHO和CPA，包括CHO中包括CPA配置。
本公开中，辅节点在接收终端设备发送的主小区组MCG失败信息后，可以向目标主节点MN发送包含MCG失败信息第一消息，之后，可以接收目标MN发送的包含用于指示终端设备进行连接或释放 的指示信息的第二消息，然后，可以向终端设备发送包含指示信息的消息。由此，终端设备通过各网络节点的交互，将MCG失败消息上报给目标MN，目标MN即可根据MCG失败消息，通过各网络节点的交互，指示终端设备进行连接或者释放MCG，从而保证小区组移动性管理的可靠性。
可以理解的是，通信装置1000可以是终端设备，也可以是终端设备中的装置，还可以是能够与终端设备匹配使用的装置。
通信装置1000在终端设备侧，其中：
收发模块，用于向辅节点SN发送主小区组MCG失败信息；
上述收发模块，还用于接收所述SN发送的包含指示所述终端设备进行连接或释放的指示信息的消息。
可选的，所述装置还包括：
处理模块1001，用于响应于所述终端设备同时进行MCG和SCG移动性，若MCG失败，不允许发送MCG失败信息。
可选的，终端设备配置了MCG和SCG的移动性，所述MCG和SCG的移动性包括以下至少之一：
联合的CHO和CPA，或者，联合的CHO和CPC，或者，MCG和SCG的选择性激活。
其中联合的CHO和CPC包括，CHO中包括CPC配置，联合的CHO和CPA，包括CHO中包括CPA配置。
本公开中，终端设备向辅节点SN发送主小区组MCG失败信息后，可以接收SN发送的包含指示终端设备进行连接或释放的指示信息的消息。由此，终端设备可以根据指示信息连接或者释放MCG，从而保证小区组移动性管理的可靠性。
可以理解的是，通信装置1000可以是目标主小区MN，也可以是目标主小区MN中的装置，还可以是能够与目标主小区MN匹配使用的装置。
通信装置1000在目标主小区MN侧，其中：
收发模块1002，用于与辅节点SN交互终端设备主小区组MCG失败的相关信息。
可选的，上述收发模块1002，用于：
接收辅节点SN发送的第一消息，其中，所述第一消息中包含终端设备的MCG失败信息；
和/或
向所述SN发送第二消息，其中，所述第二消息中包含用于指示所述终端设备进行连接或释放的指示信息。
可选的，所述第一消息及所述第二消息中任意一个或多个，为RRC转移TRANSFER消息。
可选的，所述第一消息包含以下至少一项：所述终端设备的标识，所述SN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；和/或，
所述第二消息中包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
可选的，所述终端设备的标识，为以下至少一项：所述终端设备在所述辅节点中的标识，所述终端设备在所述目标MN中的标识，所述终端设备在所述源MN中的标识。
可选的，所述指示信息为RRC消息，所述RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息。
可选的，所述MCG失败信息以RRC容器Container的形式包含于所述第一消息中，所述指示信息以RRC容器Container的形式包含于所述第二消息中。
可选的，所述终端设备配置了MCG和SCG的移动性，所述MCG和SCG的移动性包括以下至少之一：
联合的CHO和CPA，或者，联合的CHO和CPC，或者，MCG和SCG的选择性激活。
其中联合的CHO和CPC包括，CHO中包括CPC配置，联合的CHO和CPA，包括CHO中包括CPA配置。
本公开中，目标MN可以与SN交互终端设备主小区组MCG失败的相关信息。由此，目标主节点MN即可指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
可以理解的是，通信装置1000可以是目标主小区MN，也可以是目标主小区MN中的装置，还可以是能够与目标主小区MN匹配使用的装置。
通信装置1000在目标主小区MN侧，其中：
收发模块1002，用于与源主节点MN交互终端设备主小区组MCG失败的相关信息。
可选的，上述收发模块1002，用于：
向源MN发送第一消息，其中，所述第一消息中包含终端设备的MCG失败信息；
和/或接收所述源MN发送的第二消息，其中，所述第二消息中包含用于指示所述终端设备进行连接或释放的指示信息。
可选的，上述收发模块1002，用于：
响应于接收到辅节点SN发送的第三消息，向所述源MN发送所述第一消息，其中，所述第三消息中包含所述MCG失败信息。
可选的，上述收发模块1002，还用于：
向所述SN发送第四消息，其中，所述第四消息中包含所述指示信息。
可选的，所述第一消息、所述第二消息、所述第三消息及所述第四消息中任意一个或多个，为RRC转移TRANSFER消息。
可选的，所述第一消息中包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；和/或，
所述第二消息中包含以下至少一项：所述终端设备的标书，所述源MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；和/或，
所述第三消息中包含以下至少一项：所述终端设备的标识，所述SN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；和/或，
所述第四消息中包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
可选的，所述终端设备的标识，为以下至少一项：所述终端设备在所述辅节点中的标识，所述终端设备在所述目标MN中的标识，所述终端设备在所述源MN中的标识。
可选的，所述指示信息为RRC消息，所述RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息。
可选的，所述MCG失败信息以RRC容器Container的形式包含于所述第一消息和第三消息中，所述指示信息以RRC容器Container的形式包含于所述第二消息和第四消息中。
可选的，所述终端设备配置了MCG和SCG的移动性，所述MCG和SCG的移动性包括以下至少之一：
联合的CHO和CPA，或者，联合的CHO和CPC，或者，MCG和SCG的选择性激活。
其中联合的CHO和CPC包括，CHO中包括CPC配置，联合的CHO和CPA，包括CHO中包括CPA配置。
本公开中，目标MN可以与源主节点MN交互终端设备主小区组MCG失败的相关信息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
可以理解的是，通信装置1000可以是源主小区MN，也可以是源主小区MN中的装置，还可以是能够与源主小区MN匹配使用的装置。
通信装置1000在源主小区MN侧，其中：
收发模块1002，用于与目标主节点MN交互终端设备主小区组MCG失败的相关信息。
可选的，上述收发模块1002，用于：
接收目标MN发送的第一消息，其中，所述第一消息中包含终端设备的MCG失败信息；
和/或
向所述目标MN发送第二消息，其中，所述第二消息中包含用于指示所述终端设备进行连接或释放的指示信息。
可选的，所述第一消息及所述第二消息中任意一个或多个，为RRC转移TRANSFER消息。
可选的，所述第一消息包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；和/或，
所述第二消息中包含以下至少一项：所述终端设备的标识，所述源MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
可选的，所述终端设备的标识，为以下至少一项：所述终端设备在所述辅节点中的标识，所述终端设备在所述目标MN中的标识，所述终端设备在所述源MN中的标识。
可选的，所述指示信息为RRC消息，所述RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息。
可选的，所述MCG失败信息以RRC容器Container的形式包含于所述第一消息中，所述指示信息以RRC容器Container的形式包含于所述第二消息中。
可选的，所述终端设备配置了MCG和SCG的移动性，所述MCG和SCG的移动性包括以下至少之一：
联合的CHO和CPA，或者，联合的CHO和CPC，或者，MCG和SCG的选择性激活。
其中联合的CHO和CPC包括，CHO中包括CPC配置，联合的CHO和CPA，包括CHO中包括CPA配置。
本公开中，源主节点MN可以与目标MN交互终端设备主小区组MCG失败的相关信息。由此，源主节点即可根据MCG失败信息指示终端设备恢复或释放MCG连接，从而保证小区组移动性管理的可靠性。
请参见图11，图11是本公开实施例提供的另一种通信装置1100的结构示意图。通信装置1100可以是终端设备，还可以是网络设备，还可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器，还可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1100可以包括一个或多个处理器1101。处理器1101可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1100中还可以包括一个或多个存储器1102，其上可以存有计算机程序1104，处理器1101执行所述计算机程序1104，以使得通信装置1100执行上述方法实施例中描述的方法。可选的，所述存储器1102中还可以存储有数据。通信装置1100和存储器1102可以单独设置，也可以集成在一起。
可选的，通信装置1100还可以包括收发器1105、天线1106。收发器1105可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1105可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1100中还可以包括一个或多个接口电路1107。接口电路1107用于接收代码指令并传输至处理器1101。处理器1101运行所述代码指令以使通信装置1100执行上述方法实施例中描述的方法。
通信装置1100为辅节点SN：收发器1105用于执行图2中的步骤201、步骤202、步骤203、步骤204等。
通信装置1100为终端设备：收发器1105用于执行图3中的步骤301、步骤302等。
通信装置1100为目标主节点MN：收发器1105用于执行图4a中的步骤401a；图4b中的步骤401b；图4c中的步骤401c；图4d中的步骤401d、步骤402d等。
通信装置1100为目标主节点MN：收发器1105用于执行图5a中的步骤501a；图5b中的步骤501b；图5c中的步骤501c；图5d中的步骤501d、步骤502d；图5c中的步骤501c、步骤502c、步骤503c； 图6中的步骤601、步骤602、步骤603等。
通信装置1100源主节点MN：收发器1105用于执行图7a中的步骤701a；图7b中的步骤701b；图7c中的步骤701c；图7d中的步骤701d、步骤702d等。
在一种实现方式中，处理器1101中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1101可以存有计算机程序1103，计算机程序1103在处理器1101上运行，可使得通信装置1100执行上述方法实施例中描述的方法。计算机程序1103可能固化在处理器1101中，该种情况下，处理器1101可能由硬件实现。
在一种实现方式中，通信装置1100可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是终端设备，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图11的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图12所示的芯片的结构示意图。图12所示的芯片包括处理器1201和接口1203。其中，处理器1201的数量可以是一个或多个，接口1203的数量可以是多个。
对于芯片用于实现本公开实施例中辅节点SN的功能的情况：
接口1203，用于执行图2中的步骤201、步骤202、步骤203、步骤204等。
对于芯片用于实现本公开实施例中终端设备的功能的情况：
接口1203，用于执行图3中的步骤301、步骤302等。
对于芯片用于实现本公开实施例中目标主节点MN的功能的情况：
接口1203，用于执行图4a中的步骤401a；图4b中的步骤401b；图4c中的步骤401c；图4d中的步骤401d、步骤402d等。
对于芯片用于实现本公开实施例中目标主节点MN的功能的情况：
接口1203，用于执行图5a中的步骤501a；图5b中的步骤501b；图5c中的步骤501c；图5d中的步骤501d、步骤502d；图5c中的步骤501c、步骤502c、步骤503c；图6中的步骤601、步骤602、步骤603等。
对于芯片用于实现本公开实施例中源主节点MN的功能的情况：
接口1203，用于执行图7a中的步骤701a；图7b中的步骤701b；图7c中的步骤701c；图7d中的步骤701d、步骤702d等。
可选的，芯片还包括存储器1203，存储器1203用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件 来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (29)

  1. 一种失败信息的传输方法，其特征在于，由目标主节点MN执行，所述方法包括：
    与源主节点MN交互终端设备主小区组MCG失败的相关信息。
  2. [根据细则91更正 01.06.2022]
    如权利要求1所述的方法，其特征在于，所述与源MN交互终端设备主小区组MCG失败的相关信息，包括：
    向源MN发送第一消息，其中，所述第一消息中包含终端设备的MCG失败信息；
    和/或
    接收所述源MN发送的第二消息，其中，所述第二消息中包含用于指示所述终端设备进行连接或释放的指示信息。
  3. 如权利要求2所述的方法，其特征在于，所述向源MN发送第一消息，包括：
    响应于接收到辅节点SN发送的第三消息，向所述源MN发送所述第一消息，其中，所述第三消息中包含所述MCG失败信息。
  4. 如权利要求2所述的方法，其特征在于，在所述接收所述源MN发送的第二消息之后，还包括：
    向所述SN发送第四消息，其中，所述第四消息中包含所述指示信息。
  5. 如权利要求4所述的方法，其特征在于，所述第一消息、所述第二消息、所述第三消息及所述第四消息中任意一个或多个，为RRC转移TRANSFER消息。
  6. 如权利要求5所述的方法，其特征在于，
    所述第一消息中包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；
    所述第二消息中包含以下至少一项：所述终端设备的标书，所述源MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；
    所述第三消息中包含以下至少一项：所述终端设备的标识，所述SN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；
    所述第四消息中包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
  7. 如权利要求6所述的方法，其特征在于，所述终端设备的标识，为以下至少一项：所述终端设备在所述辅节点中的标识，所述终端设备在所述目标MN中的标识，所述终端设备在所述源MN中的标识。
  8. 如权利要求2-7任一所述的方法，其特征在于，所述指示信息为RRC消息，所述RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息。
  9. 如权利要求8所述的方法，其特征在于，所述MCG失败信息以RRC容器Container的形式包含于所述第一消息和第三消息中，所述指示信息以RRC容器Container的形式包含于所述第二消息和第四消息中。
  10. [根据细则91更正 01.06.2022]
    如权利要求2-7任一所述的方法，其特征在于，所述终端设备配置了MCG和SCG的移动性，所述MCG和SCG的移动性包括以下至少之一：
    联合的CHO和CPA，或者，联合的CHO和CPC，或者，MCG和SCG的选择性激活。
    其中联合的CHO和CPC包括，CHO中包括CPC配置，联合的CHO和CPA，包括CHO中包括CPA配置。
  11. 一种失败信息的传输方法，其特征在于，由源主节点MN执行，所述方法包括：
    与目标主节点MN交互终端设备主小区组MCG失败的相关信息。
  12. 如权利要求11所述的方法，其特征在于，所述与目标主节点MN交互终端设备主小区组MCG失败的相关信息，包括：
    接收目标MN发送的第一消息，其中，所述第一消息中包含终端设备的MCG失败信息；
    和/或
    向所述目标MN发送第二消息，其中，所述第二消息中包含用于指示所述终端设备进行连接或释放的指示信息。
  13. 如权利要求12所述的方法，其特征在于，所述第一消息及所述第二消息中任意一个或多个，为RRC转移TRANSFER消息。
  14. [根据细则91更正 01.06.2022]
    如权利要求12所述的方法，其特征在于，
    所述第一消息包含以下至少一项：所述终端设备的标识，所述目标MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识；
    所述第二消息中包含以下至少一项：所述终端设备的标识，所述源MN的标识，源主小区组MCG中的一个或多个小区的标识，目标MCG中的一个或多个小区的标识，及辅小区组SCG中的一个或多个小区组的标识。
  15. 如权利要求14所述的方法，其特征在于，所述终端设备的标识，为以下至少一项：所述终端设备在所述辅节点中的标识，所述终端设备在所述目标MN中的标识，所述终端设备在所述源MN中的标识。
  16. 如权利要求12-15任一所述的方法，其特征在于，所述指示信息为RRC消息，所述RRC消息为以下任一项：RRC连接重配消息，RRC重配消息，来自NR的移动命令消息，来自EUTRA的移动命令消息，RRC连接释放消息，及RRC释放消息。
  17. 如权利要求12-15任一所述的方法，其特征在于，所述MCG失败信息以RRC容器Container的形式包含于所述第一消息中，所述指示信息以RRC容器Container的形式包含于所述第二消息中。
  18. 如权利要求12-17任一所述的方法，其特征在于，所述终端设备配置了MCG和SCG的移动性，所述MCG和SCG的移动性包括以下至少之一：
    联合的CHO和CPA，或者，联合的CHO和CPC，或者，MCG和SCG的选择性激活。
    其中联合的CHO和CPC包括，CHO中包括CPC配置，联合的CHO和CPA，包括CHO中包括CPA配置。
  19. 一种失败信息的传输方法，其特征在于，由目标主节点MN执行，所述方法包括：
    与辅节点SN交互终端设备主小区组MCG失败的相关信息。
  20. 如权利要求19所述的方法，其特征在于，所述与辅节点SN交互终端设备主小区组MCG失败的相关信息，包括：
    接收辅节点SN发送的第一消息，其中，所述第一消息中包含终端设备的MCG失败信息；
    和/或
    向所述SN发送第二消息，其中，所述第二消息中包含用于指示所述终端设备进行连接或释放的指示信息。
  21. 一种通信装置，其特征在于，所述装置应用于目标主节点MN，所述装置包括：
    收发模块，用于与源主节点MN交互终端设备主小区组MCG失败的相关信息。
  22. 一种通信装置，其特征在于，所述装置应用于源主节点MN，所述装置包括：
    收发模块，用于与目标主节点MN交互终端设备主小区组MCG失败的相关信息。
  23. 一种通信装置，其特征在于，所述装置应用于目标主节点MN，所述装置包括：
    收发模块，用于与辅节点SN交互终端设备主小区组MCG失败的相关信息。
  24. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至10中任一项所述的方法。
  25. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求11至18中任一项所述的方法。
  26. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求19至20中任一项所述的方法。
  27. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至10中任一项所述的方法被实现。
  28. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求11至18中任一项所述的方法被实现。
  29. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求19至20中任一项所述的方法被实现。
PCT/CN2022/096493 2022-05-31 2022-05-31 一种失败信息的传输方法及装置 WO2023230934A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280001909.1A CN117501744A (zh) 2022-05-31 2022-05-31 一种失败信息的传输方法及装置
PCT/CN2022/096493 WO2023230934A1 (zh) 2022-05-31 2022-05-31 一种失败信息的传输方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/096493 WO2023230934A1 (zh) 2022-05-31 2022-05-31 一种失败信息的传输方法及装置

Publications (1)

Publication Number Publication Date
WO2023230934A1 true WO2023230934A1 (zh) 2023-12-07

Family

ID=89026724

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/096493 WO2023230934A1 (zh) 2022-05-31 2022-05-31 一种失败信息的传输方法及装置

Country Status (2)

Country Link
CN (1) CN117501744A (zh)
WO (1) WO2023230934A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831254A (zh) * 2018-08-08 2020-02-21 维沃移动通信有限公司 连接失败恢复的方法和设备
WO2020227870A1 (zh) * 2019-05-10 2020-11-19 Oppo广东移动通信有限公司 一种切换方法及装置、通信设备
CN114125966A (zh) * 2019-01-25 2022-03-01 中兴通讯股份有限公司 用于上报主小区组失败的方法和装置
CN114365531A (zh) * 2019-07-29 2022-04-15 日本电气株式会社 主节点、辅节点及其方法
CN114451063A (zh) * 2019-09-30 2022-05-06 华为技术有限公司 通信方法和通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831254A (zh) * 2018-08-08 2020-02-21 维沃移动通信有限公司 连接失败恢复的方法和设备
CN114125966A (zh) * 2019-01-25 2022-03-01 中兴通讯股份有限公司 用于上报主小区组失败的方法和装置
WO2020227870A1 (zh) * 2019-05-10 2020-11-19 Oppo广东移动通信有限公司 一种切换方法及装置、通信设备
CN114365531A (zh) * 2019-07-29 2022-04-15 日本电气株式会社 主节点、辅节点及其方法
CN114451063A (zh) * 2019-09-30 2022-05-06 华为技术有限公司 通信方法和通信装置

Also Published As

Publication number Publication date
CN117501744A (zh) 2024-02-02

Similar Documents

Publication Publication Date Title
WO2023201754A1 (zh) 一种终端设备的移动性管理方法及装置
WO2023201756A1 (zh) 一种用于基于条件的移动性的信息的处理方法及装置
WO2023230934A1 (zh) 一种失败信息的传输方法及装置
WO2023193271A1 (zh) 一种双连接中终端设备小区组的更新方法及装置
WO2023230935A1 (zh) 一种小区组失败的恢复方法及装置
WO2023193275A1 (zh) 一种cpc配置或cpa配置的取消方法及其装置
WO2023193273A1 (zh) 一种控制源辅节点释放的方法及装置
WO2023236061A1 (zh) 一种失败恢复方法及其装置
WO2023236060A1 (zh) 一种失败恢复方法及其装置
WO2024011431A1 (zh) 原因指示方法、装置、设备及存储介质
WO2024065128A1 (zh) 一种控制终端设备连接的方法及其装置
WO2023193274A1 (zh) 一种配置信息传输方法及其装置
WO2024060143A1 (zh) 一种上报方法/装置/设备及存储介质
WO2024011432A1 (zh) 一种信息传输方法及其装置
WO2024011435A1 (zh) 一种失败处理方法及其装置
WO2023193272A1 (zh) 一种双连接终端设备小区组的更新方法及装置
WO2024031272A1 (zh) 一种上报方法、装置、设备及存储介质
WO2024000205A1 (zh) 传输控制方法及其装置
WO2024011639A1 (zh) 一种路径切换方法、装置、设备及存储介质
WO2023201755A1 (zh) 一种移动性管理的配置方法及装置
WO2023220941A1 (zh) 一种数据前转信息的传输方法及其装置
WO2024011545A1 (zh) 切换方法及装置
WO2024000198A1 (zh) 连接控制方法、装置、设备及存储介质
WO2023240419A1 (zh) 一种接入控制的方法及装置
WO2024060234A1 (zh) 信息上报方法和装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280001909.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22944268

Country of ref document: EP

Kind code of ref document: A1