WO2023217078A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2023217078A1
WO2023217078A1 PCT/CN2023/092731 CN2023092731W WO2023217078A1 WO 2023217078 A1 WO2023217078 A1 WO 2023217078A1 CN 2023092731 W CN2023092731 W CN 2023092731W WO 2023217078 A1 WO2023217078 A1 WO 2023217078A1
Authority
WO
WIPO (PCT)
Prior art keywords
mcg
scg
rlf
network device
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/092731
Other languages
English (en)
French (fr)
Inventor
王凡凡
耿婷婷
胡星星
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to KR1020247040273A priority Critical patent/KR20250005463A/ko
Priority to EP23802848.4A priority patent/EP4510689A4/en
Publication of WO2023217078A1 publication Critical patent/WO2023217078A1/zh
Priority to US18/941,983 priority patent/US20250071593A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • 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/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • 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
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00692—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO]

Definitions

  • the present application relates to the field of communication technology, and in particular, to a communication method and device.
  • the terminal device can communicate with at least two access network devices at the same time, for example, with a primary base station and one or more secondary base stations. Connection, where the master base station manages the master cell group (MCG), and the secondary base station manages the secondary cell group (SCG).
  • MCG master cell group
  • SCG secondary cell group
  • the terminal device can obtain the communication services of the master base station through the cells in the MCG, and, The communication services of the secondary base station can be obtained through the cells in the SCG.
  • the terminal device when the terminal device detects that a wireless link failure (RLF) occurs in the MCG, it can try to restore the terminal through the fast MCG link recovery (fast MCG link recovery) process.
  • RLF wireless link failure
  • the network device cannot obtain relevant parameters of the fast MCG link recovery process in time, the network device cannot perform mobility optimization for the MCG link recovery process, affecting the communication quality of dual connections or multiple connections.
  • This application provides a communication method and device to enable terminal equipment to report an RLF report related to whether the link recovery for MCG is successful, thereby improving the effect of mobility optimization of network equipment based on RLF reports.
  • this application provides a communication method, which may include: a terminal device communicating with a first network device and a second network device respectively; after the terminal device determines that RLF occurs in the first MCG, A first RLF report is sent, where the first RLF report is related to whether link recovery for the first MCG is successful.
  • the first network device manages a first MCG
  • the second network device manages a first SCG
  • the first SCG is configured with an MCG link recovery function.
  • the third network device may be the first network device or the second network device. Wherein, when an RLF occurs in the first SCG managed by the second network device, the third network device may be the second network device.
  • the terminal device can report to the network device an RLF report related to whether the link recovery for the MCG is successful, thereby improving the effect of the network device's mobility optimization based on the RLF report.
  • the network device can respond to the MCG link recovery Optimize the relevant network parameters to improve the success rate of subsequent MCG re-establishment of connections, thereby enhancing the continuity and reliability of dual-connection or multi-connection communication by terminal equipment and improving communication quality.
  • the first RLF report may include the link recovery failure reason.
  • the subsequent network device can analyze the reason for the link recovery failure of the first MCG based on the first RLF report, and then adjust relevant network parameters.
  • the link recovery failure reason may include one or more of the following: the first SCG is added, the first SCG is changed, or the transmission of the first SCG is suspended.
  • the subsequent network device can analyze the reason for the link recovery failure of the first MCG based on the first RLF report, and then adjust relevant network parameters.
  • the terminal device determines not to perform link recovery for the first MCG based on the first SCG being added or changed, or the transmission of the first SCG being suspended, so that , determining that link recovery for the first MCG is unsuccessful.
  • the terminal device determines that the link recovery for the first MCG was unsuccessful based on the failure of sending the RLF information of the first MCG to the second network device. In this way, the terminal device can locate the reason why the link recovery for the first MCG is unsuccessful, and then record the relevant reason information in the RLF report, so that the network device can perform cause analysis.
  • the terminal device after the terminal device sends the RLF information of the first MCG to the second network device through the first SCG, the terminal device does not receive the RLF information based on the first preset time period. In response to the RLF information of the first MCG, it is determined that the link recovery for the first MCG was unsuccessful. In this way, the terminal device can locate the reason why the link recovery for the first MCG is unsuccessful, and then record the relevant reason information in the RLF report, so that the network device can perform cause analysis.
  • the first RLF report may include one or more of the following: a link recovery failure reason, and whether the RLF information of the first MCG was successfully sent to the second through the first SCG.
  • Instruction information of the network device first time information or RLF information of the first SCG, wherein the first time information indicates a first running time of the first timer, and the first running time is greater than or equal to the The preset duration of the first timer, the first running time is from the time the terminal device sends the RLF information of the first MCG to the second network device through the first SCG to initiating radio resource control (radio). resource control, RRC) reconstruction process duration.
  • radio resource control radio resource control
  • the RLF report can be enhanced based on the scenario where the terminal device fails to initiate the MCG link recovery process, so that the network device can optimize the MCG link recovery process and thereby optimize related network parameters.
  • the configuration parameters of the first SCG can be optimized.
  • the subsequent first SCG can reduce the occurrence of RLF, so that the terminal device can successfully communicate with the second network device. communication.
  • the link recovery failure reason may include one or more of the following: link recovery failure for the first MCG caused by beam recovery failure after the beam failure of the first SCG; Random access for the first SCG fails or radio link control RLC retransmission for the first SCG reaches the maximum number of times. In this way, the specific reasons for link recovery failure can be clarified, so that network optimization can be accurately performed.
  • the RLF information of the first SCG may include one or more of the following: identification information of the first SCG, the reason why the RLF occurs in the first SCG, or the change of the first SCG fails. s reason.
  • the first SCG where the problem occurs can be clarified, so that the network device can optimize the configuration parameters of the first SCG. Since the first SCG is used to send the RLF information of the first MCG, after the configuration parameters of the first SCG are optimized, the configuration parameters of the first SCG can be optimized. Subsequently, the first SCG reduces the occurrence of RLF, thereby enabling the terminal device to successfully communicate with the second network device.
  • the terminal device when the link to the first MCG is restored successfully, can also determine whether the switch from the first MCG to the second MCG is successful; and then the terminal device determines whether the link is successfully switched from the first MCG to the second MCG.
  • the first MCG is successfully switched to the second MCG, and the first RLF report is determined.
  • the content of the first RLF report can be determined in combination with the actual handover situation of the terminal device, so that the network device can optimize the subsequent handover process and improve the handover success rate.
  • the first RLF report may include the RLF information of the first MCG, and the second MCG's RLF information. Handover failure information or RLF information of the second MCG.
  • the RLF report can be enhanced so that the network device can optimize the subsequent processes of the MCG link recovery process. For example, the terminal can be adjusted The MCG that the device needs to switch to, etc., means that the terminal device can switch from the first MCG to another more suitable MCG other than the second MCG, thereby improving the switching success rate.
  • the terminal device may determine that the switch from the first MCG to the second MCG has not been successful through the following method: the terminal device determines that the terminal device has not successfully switched to the second MCG based on the , an RLF occurs in the second MCG within the second preset time period, and it is determined that the switch from the first MCG to the second MCG is unsuccessful. In this way, in a short period of time after the terminal device switches to the second MCG, if an RLF occurs in the second MCG and the terminal device cannot communicate through the second MCG, the terminal device can continue to reselect the MCG.
  • the first RLF may report RLF information including the first MCG, and one or more of the following: The identification information or second time information of the second MCG, the second time information indicates the second running time of the first timer, the second running time is less than the preset duration of the first timer, the The second running time is the time period for the terminal device to receive the response message sent by the second network device after sending the RLF information of the first MCG to the second network device through the first SCG.
  • the RLF report is enhanced, so that the network device can optimize related parameters for handover from the first MCG to the second MCG based on the RLF report. This allows the terminal equipment to switch from the first MCG to the second MCG quickly, thereby reducing the MCG service interruption time.
  • the present application provides a communication method.
  • the method may include: after the third network device receives the first RLF report from the terminal device, adjust the network parameters related to the first RLF report according to the first RLF report. .
  • the first RLF report is related to whether link recovery for the first MCG is successful after the first primary cell group MCG sends the RLF; the terminal device communicates with the first network device and the second network device respectively, wherein, The first network device manages a first primary cell group MCG, the second network device manages a first secondary cell group SCG, and the first SCG is configured with an MCG link recovery function.
  • the third network device may be the first network device or the second network device. Wherein, when an RLF occurs in the first SCG managed by the second network device, the third network device may be the second network device.
  • the terminal device can report to the network device an RLF report related to whether the link recovery for the MCG is successful, thereby improving the effect of the network device's mobility optimization based on the RLF report.
  • the network device can respond to the MCG link recovery Optimize the relevant network parameters to improve the success rate of subsequent MCG re-establishment of connections, thereby enhancing the continuity and reliability of dual-connection communication by terminal equipment and improving communication quality.
  • the first RLF report may include the link recovery failure reason.
  • the network device can analyze the reason for the link recovery failure of the first MCG based on the first RLF report, and then adjust relevant network parameters.
  • the link recovery failure reason may include one or more of the following: the first SCG is added, the first SCG is changed, or the transmission of the first SCG is suspended.
  • the network device can analyze the reason for the link recovery failure of the first MCG based on the first RLF report, and then adjust relevant network parameters.
  • the first RLF report may include one or more of the following: the link recovery failure reason, the RLF of the first MCG Is the information successfully passed? Instruction information, first time information or RLF information of the first SCG sent to the second network device through the first SCG, wherein the first time information indicates the first running time of the first timer , the first running time is greater than or equal to the preset duration of the first timer, and the first running time is when the terminal device sends the first SCG to the second network device.
  • the RLF report can be enhanced based on the scenario where the terminal device fails to initiate the MCG link recovery process, so that the network device can optimize the MCG link recovery process and thereby optimize related network parameters.
  • the configuration parameters of the first SCG can be optimized.
  • the subsequent first SCG can reduce the occurrence of RLF, so that the terminal device can successfully communicate with the second network device. communication.
  • the link recovery failure reason may include one or more of the following: link recovery failure for the first MCG caused by beam recovery failure after the beam failure of the first SCG; Random access for the first SCG fails or radio link control RLC retransmission for the first SCG reaches the maximum number of times. In this way, the specific reasons for link recovery failure can be clarified, so that network optimization can be accurately performed.
  • the RLF information of the first SCG may include one or more of the following: identification information of the first SCG, the reason why the RLF occurs in the first SCG, or the change of the first SCG fails. s reason.
  • the first SCG where the problem occurs can be clarified, so that the network device can optimize the configuration parameters of the first SCG. Since the first SCG is used to send the RLF information of the first MCG, after the configuration parameters of the first SCG are optimized, the configuration parameters of the first SCG can be optimized. Subsequently, the first SCG reduces the occurrence of RLF, thereby enabling the terminal device to successfully communicate with the second network device.
  • the first RLF report is also related to whether the terminal device successfully switches from the first MCG to the second MCG. In this way, when the link recovery for the first MCG is successful, the content of the first RLF report can be determined in combination with the actual handover situation of the terminal device, so that the network device can optimize the subsequent handover process and improve the handover success rate.
  • the first RLF report may include the RLF information of the first MCG, and the handover of the second MCG fails. information or the RLF information of the second MCG.
  • the RLF report can be enhanced so that the third network device can optimize the subsequent process of the MCG link recovery process. For example, Adjusting the MCG that the terminal device needs to switch to, etc., means switching the terminal device from the first MCG to another more suitable MCG other than the second MCG, thereby improving the switching success rate.
  • the first RLF report may include the RLF information of the first MCG, and one or more of the following: The identification information or second time information of the second MCG, the second time information indicates the second running time of the first timer, the second running time is less than the preset duration of the first timer, the The second running time is the time period for the terminal device to receive the response message sent by the second network device after sending the RLF information of the first MCG to the second network device through the first SCG.
  • the RLF report is enhanced, so that the network device can optimize related parameters for handover from the first MCG to the second MCG based on the RLF report. This allows the terminal equipment to switch from the first MCG to the second MCG quickly, thereby reducing the MCG service interruption time.
  • the present application also provides a communication device, which may be a terminal device.
  • the communication device has the function of implementing the method in the above-mentioned first aspect or each possible design example of the first aspect.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more Modules corresponding to the above functions.
  • the structure of the communication device includes a transceiver unit and a processing unit. These units can perform the corresponding functions in the above-mentioned first aspect or each possible design example of the first aspect. For details, see the method examples. Detailed description will not be repeated here.
  • the structure of the communication device includes a transceiver and a processor, and optionally a memory.
  • the transceiver is used to send and receive information or data, and to communicate with other devices in the communication system.
  • the processor is configured to support the communication device to perform corresponding functions in the above-mentioned first aspect or each possible design example of the first aspect.
  • the memory is coupled to the processor and holds program instructions and data necessary for the communications device.
  • this application also provides a communication device, which may be a third network device.
  • the communication device has the function of implementing the method in the above-mentioned second aspect or each possible design example of the second aspect.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the communication device includes a transceiver unit and a processing unit. These units can perform the corresponding functions in the above second aspect or each possible design example of the second aspect. For details, see the method examples. Detailed description will not be repeated here.
  • the structure of the communication device includes a transceiver and a processor, and optionally a memory.
  • the transceiver is used to send and receive information or data, and to communicate with other devices in the communication system.
  • the processor is configured to support the communication device to perform corresponding functions in the above second aspect or each possible design example of the second aspect.
  • the memory is coupled to the processor and holds program instructions and data necessary for the communications device.
  • embodiments of the present application provide a communication system, which may include the above-mentioned terminal device, a first network device, a second network device, a third network device, and the like.
  • embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores program instructions. When the program instructions are run on a computer, they cause the computer to execute the first aspect of the embodiments of the application and its contents. Any possible design, or the method described in the second aspect and any possible design thereof.
  • computer-readable storage media can be any available media that can be accessed by a computer.
  • computer-readable media may include non-transitory computer-readable media, random-access memory (random-access memory, RAM), read-only memory (read-only memory, ROM), electrically erasable memory
  • RAM random-access memory
  • ROM read-only memory
  • programmable read-only memory electrically EPROM, EEPROM
  • CD-ROM or other optical disk storage magnetic disk storage media or other magnetic storage devices, or can be used to carry or store the desired program code in the form of instructions or data structures and can Any other media accessed by a computer.
  • embodiments of the present application provide a computer program product that includes computer program code or instructions.
  • the computer program code or instructions are run on a computer, the first aspect or any of the possible designs of the first aspect are enabled. , or the method described in the above second aspect or any possible design of the second aspect is executed.
  • the present application also provides a chip, including a processor, the processor being coupled to a memory and configured to read and execute program instructions stored in the memory, so that the chip implements the above-mentioned first aspect Or any possible design of the first aspect, or the method described in the above second aspect or any possible design of the second aspect.
  • Figure 1 is a schematic diagram of the architecture of a communication system provided by this application.
  • Figure 2 is a schematic diagram of a protocol stack of a base station provided by this application.
  • Figure 3 is a schematic flow chart of a communication method provided by this application.
  • Figure 4 is a schematic flow chart of an example of a communication method provided by this application.
  • Figure 5 is a schematic flowchart of another example of a communication method provided by this application.
  • Figure 6 is a schematic flow chart of another example of a communication method provided by this application.
  • Figure 7 is a schematic flow chart of another example of a communication method provided by this application.
  • Figure 8 is a schematic flowchart of another example of a communication method provided by this application.
  • Figure 9 is a schematic structural diagram of a communication device provided by this application.
  • Figure 10 is a structural diagram of a communication device provided by this application.
  • Embodiments of the present application provide a communication method and device to enable the terminal device to report an RLF report related to whether the link recovery for the MCG is successful, thereby improving the effect of mobility optimization of the network device based on the RLF report.
  • the method and the device described in this application are based on the same technical concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repeated parts will not be repeated.
  • the protocol described in this application may refer to a communication protocol or specification, such as the 3GPP communication protocol.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean determining B only based on A.
  • B can also be determined based on A and/or other information.
  • transmission refers to two-way transmission, including the actions of sending and/or receiving.
  • transmission in the embodiments of this application includes the sending of data, the receiving of data, or the sending and receiving of data.
  • the data transmission here includes uplink and/or downlink data transmission.
  • Data may include information and/or signals, uplink data transmission means uplink information and/or uplink signal transmission, and downlink data transmission means downlink information and/or downlink signal transmission.
  • DC Dual-connectivity
  • MC multi-connectivity
  • Dual connection or multi-connection that is, the terminal device can have communication connections with at least two access network devices at the same time, that is, it supports at least two access network devices to provide data transmission services for one terminal device at the same time.
  • one access network device is a main base station, and the main base station (may be referred to as the main station) may also be called a master node (MN).
  • MN master node
  • Other access network equipment is a secondary base station, and a secondary base station (which may be referred to as a secondary station) may also be called a secondary node (SN).
  • the MN may be responsible for interacting with the terminal device in radio resource control messages and with the core network control plane entity.
  • multiple serving cells managed by the MN form the main A cell group (master cell group, MCG) includes a primary cell (primary cell, PCell) and optionally one or more secondary cells (secondary cell, SCell).
  • MCG master cell group
  • SCell secondary cell
  • Multiple serving cells managed by the SN form a secondary cell group (SCG), including a primary secondary cell (PScell) and optionally one or more SCells.
  • SCG secondary cell group
  • PScell primary secondary cell
  • SCell secondary cell
  • SCell secondary cell group
  • the terminal device When the terminal device detects that RLF occurs in MCG, even if SCG is still communicating with the terminal device normally, the terminal device will initiate RRC reconstruction for MCG and release the SCG configuration. However, RRC reconstruction will cause long-term data interruption, such as 90 to 130 milliseconds. (ms) of data interruption.
  • the occurrence of RLF in the MCG can be understood as the occurrence of RLF in one or more cells in the MCG, including the PCell.
  • the occurrence of RLF in MCG can also be understood as the connection failure between the terminal device and MCG.
  • the fast MCG link recovery process can be used. If the terminal device detects that RLF occurs in the MCG, the terminal device can indicate the link failure information of the MCG to the MN through the SN and attempt to perform link recovery of the MCG, that is, the terminal device attempts to restore the connection between the terminal device and the MCG.
  • the SCG supports the rapid recovery of the MCG, that is, the terminal device can transmit relevant information for the rapid recovery of the MCG to the MN through the SN, such as link failure information indicating the MCG.
  • the terminal device reports MCG link failure information (MCG failure information) to SCG by splitting signaling radio bearer 1 (SRB1) or SRB3, and starts the T316 timer (timer). If in T316 Within the timer duration, if the terminal device receives a handover or RRC release (RRCRelease) message, the fast MCG link recovery is successful, otherwise the terminal device initiates the RRC reconstruction process.
  • MCG failure information MCG link failure information
  • SRB1 signaling radio bearer 1
  • RRCRelease RRC release
  • the T316 timer is started when the terminal device sends MCG link failure information, and when the terminal device receives the RRC release (RRCRelease) message and the RRC reconfiguration (including synchronous reconfiguration) of the primary cell (RRC reconfiguration with reconfiguration with Sync for the PCell), Mobility From NR Command, or initiating the re-establishment procedure, T316 stops.
  • split SRB refers to the offloading of SRB1/SRB2, that is: in the dual connection scenario, SRB1 and SRB2 are established between the terminal equipment and the main base station.
  • split SR B is introduced mechanism, that is, if the link quality between the terminal equipment and the main base station deteriorates, the S RB1/SRB2 between the terminal equipment and the main base station can also be assisted in transmission through the secondary base station, that is, the main base station will transfer part of the information
  • the traffic is then offloaded to the secondary base station, and the secondary base station further sends it to the terminal equipment.
  • SRB3 is a signaling channel established directly between the SN and the terminal device, and can be used for interactive signaling between the SN and the terminal device.
  • the establishment and release of SRB3 is completed in the SN addition and change process; SRB3 reconfiguration is completed in the SN modification process.
  • SCG is released, SRB3 is released.
  • Split SRB is configured by the MN during the SN addition and change process, and the SN configuration part is provided by the SN.
  • the terminal device can be configured with split SRB1, split SRB2 and SRB3 at the same time.
  • the SCG branches of SRB3 and split SRB can be configured independently.
  • At least one (species, item) refers to one (species, item) or multiple (species, item), and multiple (species, item) refers to two (species, item) , item) or more than two (species, item).
  • At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of single or plural items.
  • at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, c Can be single or multiple.
  • Figure 1 shows the architecture of a possible communication system to which the communication method provided by the embodiment of the present application is applicable.
  • the communication system is a dual-connection system.
  • the architecture of the communication system may include at least one terminal device and at least two network devices.
  • Figure 1 shows only one terminal device and two network devices as an example.
  • the terminal device and two network devices shown in Figure 1 The devices (MN and SN) establish DC communication.
  • the network device may be a device with a wireless transceiver function or a chip that can be disposed on the network device.
  • the network device may be an access network device such as a base station.
  • the network equipment can be various types of base stations, such as evolved base stations (evolved NodeB, eNodeB), next generation base stations (next generation NodeB, gNB) in the fifth generation (5th generation, 5G) mobile communication system, sixth generation ( 6th generation, 6G) next-generation base stations in mobile communication systems, base stations in future mobile communication systems, etc.
  • the network device may be a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an access point in a wireless fidelity (Wi-Fi) system ( Access point, AP), integrated access and backhaul (IAB), wireless relay node, wireless backhaul node, transmission point (transmission and reception point, TRP or transmission point, TP), etc., can also be used It is a network node with base station function, such as baseband unit (BBU), etc.
  • BBU baseband unit
  • base stations can include centralized units (centralized units, CU) and distributed units (distributed units, DU).
  • the gNB may also include a radio unit (RU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB.
  • CU can be divided into CU control plane (CU-(control panel, CP)) and CU user plane (CU-(user panel, UP)).
  • CU-CP is responsible for the control plane function, which mainly includes the functions of radio resource control (RRC) and packet data convergence protocol (PDCP)-C.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the control plane CU-CP of the CU may also include a further segmentation architecture, that is, the existing CU-CP is further segmented into CU-CP1 and CU-CP2.
  • CU-CP1 includes various radio resource management functions
  • CU-CP2 only includes RRC functions and PDCP-C functions (ie, the basic functions of control plane signaling at the PDCP layer).
  • CU-UP is responsible for user plane functions, mainly including service data adaptation protocol (service data adaptation protocol, SDAP) and PDCP-U functions.
  • CU-CP and CU-UP are connected through the E1 interface.
  • CU-CP represents that CU is connected to the core network through the Ng interface and connected to the DU through F1-C (control plane).
  • CU-UP is connected to DU through F1-U (user plane).
  • PDCP-C is also in CU-UP.
  • the CU implements the functions of the RRC, PDCP, and SDAP layers.
  • DU implements the functions of radio link control (RLC), media access control (media access control, MAC) and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the network device may be a CU node, a DU node, or a device including a CU node and a DU node.
  • the CU can be divided into network equipment in the access network RAN, or the CU can be divided into network equipment in the core network CN, without limitation.
  • multiple DUs may share one CU.
  • one DU can also be connected to multiple CUs.
  • CU and DU can be connected through the F1 interface.
  • One DU can manage one or more cells, and each cell has a corresponding cell identity.
  • the CU and the DU may also be physically separated.
  • CU and DU can be considered as two separate nodes.
  • the network device may be a CU.
  • the terminal equipment may also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment , user agent or user device.
  • the terminal device is a remote terminal device and needs to be provided with a relay service.
  • the terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, or an augmented reality (AR) terminal.
  • Equipment wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation security ( Wireless terminals in transportation safety, wireless terminals in smart cities, smart wearable devices (smart glasses, smart watches, smart headphones, etc.), wireless terminals in smart homes, etc., can also be Chips or chip modules (or chip systems) that can be installed on the above devices.
  • the embodiments of this application do not limit application scenarios.
  • terminal equipment with wireless transceiver functions and chips that can be installed in the aforementioned terminal equipment are collectively referred to as terminal equipment.
  • the technical solution provided by this application is explained below by taking an example of using a UE as a terminal device.
  • the communication system shown in Figure 1 above can be the fourth generation (The 4th Generation, 4G) communication system, the fifth generation (The 5th Generation, 5G) communication system, the future sixth generation communication system and evolution.
  • 4G The 4th Generation, 4G
  • 5G The 5th Generation
  • 5G the future sixth generation communication system and evolution.
  • Other communication systems, etc., this application does not limit this.
  • Step 1 MN requests SN to support fast MCG link recovery through split SRB1 or SRB3.
  • SRB3 is only used when split SRB1 is not configured.
  • Step 2 The MN sends the fast recovery configuration (fast recovery configuration) containing the T316 timer information to the UE.
  • Step 3 The UE detects that RLF occurs in the MCG and saves the MCG link failure information in the RLF report.
  • the connection failure type recorded in the RLF report is RLF.
  • Step 4 If the SCG transmission is not suspended and the SN is not changing or adding PScell, the UE sends MCG link failure information to the SN and starts the T316 timer.
  • the MCG link failure information may include the following information: MCG/SCG available measurement results, MCG link failure types, and non-serving cell available measurement results.
  • Step 5a Before the T316 timer times out, the UE receives the recovery response message sent by the SN, such as the handover (Handover) message or the RRC release (RRCRelease) message, and the UE performs handover or reselection according to the recovery response message; otherwise, perform step 5b .
  • the recovery response message sent by the SN such as the handover (Handover) message or the RRC release (RRCRelease) message
  • the UE performs handover or reselection according to the recovery response message; otherwise, perform step 5b .
  • the MCG connection when the UE performs handover according to the recovery response message, if a handover failure (HOF) occurs, the MCG connection will fail.
  • the MCG connection fails due to HOF the UE can record that the connection failure type is HOF in the RLF report. That is to say, in this application, in the RLF report, the type of RLF occurring in the MCG (that is, the connection failure type of the MCG) may include RLF or HOF.
  • the UE Before the T316 timer times out, if the UE receives the recovery response message from the SN, the fast MCG link recovery is successful, and the UE clears the RLF report recorded in step 3. The UE performs handover or reselection according to the recovery response to change the cell. If the cell change fails or fails soon after accessing the cell, the MCG connection failure occurs again (RLF/HOF). Re-record the RLF report of the second MCG connection failure information.
  • Step 5b UE initiates RRC reestablishment.
  • the UE After the T316 timer times out, if the UE does not receive the recovery response message from the SN, the fast MCG link recovery fails, and the RLF report recorded in step 3 is retained. After the RRC is reestablished, the UE sends the RLF report to the accessed MN.
  • the RLF report can include at least one of the following information:
  • FailedPcellID The UE detects the cell information that sends RLF, or the target cell information that fails to handover;
  • connectionFailureType RLF or HOF or timer expiration (the timer is a timer started after the UE sends the measurement report, such as T312);
  • Previous primary cell identifier the source cell information of the last time the UE received a handover command
  • Reestablishment Cell Id (reestablishmentCellId): cell information that initiates re-establishment after connection failure;
  • Connection failure time (timeConnFailure): the time from the last time the HO command is received to the connection failure;
  • Failure start time (timeSinceFailure): The length of time when the connection fails to start recording, generally refers to the time from the connection failure to the RLF-report.
  • RLF reason (rlf-Cause): reasons for wireless link failure or handover failure, such as T310 timer timeout, random access problem (randomAccessProblem), beam failure recovery failure (beamFailureRecoveryFailure), listen before failure (listen before) talk failure, lbtFailure), too many RLC retransmission failures, etc.
  • the above-mentioned cell information may include cell global identity (CGI), and/or physical cell identity (physical cell identity, PCI) and frequency (frequency).
  • CGI cell global identity
  • PCI physical cell identity
  • frequency frequency
  • the RLF report can also carry the cell quality of each cell, such as the cell quality of the failed cell and/or neighboring cells when MCG link failure is detected.
  • the cell information may also include cell measurement results.
  • the UE when the MCG connection fails, the UE will record the RLF report; when the MCG connection fails again, the UE clears the previously recorded RLF report and records the latest RLF report.
  • MRO mobility robustness optimization
  • the existing MRO mechanism can analyze the RLF report fed back by the UE and adjust network parameters related to the RLF report to optimize mobility for the UE.
  • the current RLF report recorded by UE does not consider scenarios such as fast MCG link recovery failure or fast MCG link recovery failure after success. Therefore, when network equipment optimizes network parameters based on the current RLF report recorded by UE, the mobility optimization effect is not good. .
  • the embodiment of this application proposes a communication method so that the RLF report determined by the UE can be related to whether the link recovery for MCG is successful.
  • the RLF report can cover scenarios such as fast MCG link recovery failure or fast MCG link recovery failure after success. Parameters, so that network equipment can accurately adjust the parameters involved in these scenarios in a targeted manner, improve the mobility optimization effect, and then improve the success rate of subsequent MCG re-establishment of connections, thereby enhancing the terminal equipment to perform dual or multi-connection Communication continuity and reliability, improve communication quality.
  • the communication method provided by the embodiment of the present application is suitable for the communication system as shown in Figure 1.
  • the specific process of this method may include:
  • Step 301 The UE communicates with the first network device and the second network device respectively.
  • the UE performs dual-connectivity communication with the first network device and the second network device, and can obtain communication services from the first network device and the second network device respectively.
  • the first network device manages the first MCG
  • the second network device manages the first SCG. That is to say, the first network device is the MN of the UE, and the second network device is the SN of the UE.
  • the first SCG is configured with an MCG link recovery function, that is, the first SCG supports MCG fast recovery.
  • the first SCG supporting MCG fast recovery can be understood to mean that the second network device to which the first SCG belongs supports MCG fast recovery, that is, the UE transmits data to the first network through the second network device to which the first SCG belongs. Device sends information for MCG quick recovery. In this application, it is only explained that the first SCG supports MCG fast recovery.
  • the first network device sends request information to the second network device, where the request information is used to request that the first SCG managed by the second network device supports MCG fast recovery,
  • the second network device replies the response information of the request information to the first network device.
  • the first SCG is configured with the MCG link recovery function, so that when RLF occurs in the first MCG, the UE can perform link recovery of the first MCG through the first SCG.
  • the request information may request the first SCG to support MCG fast recovery through split SRB1 or SRB3.
  • the first network device may configure a first timer for the UE, so that when the UE determines that RLF occurs in the first MCG, the first SCG sends a request to the second timer through the first SCG. After the network device sends the RLF information of the first MCG, it determines whether the link for the first MCG is restored by whether it receives the response message sent by the second network device within the preset time period of the first timer. success.
  • the first timer may be a T316 timer or the like.
  • Step 302 The UE determines that RLF occurs in the first MCG.
  • the UE determines that RLF occurs in the first MCG, it may be understood that the connection between the UE and the first MCG fails. In the case where RLF occurs in the first MCG, the UE cannot communicate with the first network device through the first MCG.
  • Step 303 The UE sends a first RLF report to the third network device, where the first RLF report is related to whether link recovery for the first MCG is successful.
  • the content of the first RLF report is different.
  • the content of the first RLF report is explained below for different situations:
  • the first RLF report may include the link recovery failure reason.
  • the link recovery failure reason may include one or more of the following: the first SCG is added, the first SCG is changed, or the transmission of the first SCG is suspended. (SCG transmission suspended). That is to say, the above-mentioned link recovery failure reason causes link recovery for the first MCG to be unsuccessful.
  • the addition or change of the first SCG may mean that the primary and secondary cells are being added or changed (Pscell change or addition ongoing).
  • the link recovery failure reason may be in an enumeration format, such as Pscell change or addition ongoing, suspended SCG transmission.
  • the UE is added or changed based on the first SCG, or the first SCG
  • the transmission is suspended and it is determined that link recovery for the first MCG is not performed.
  • the first SCG link is unstable, causing the UE to be unable to pass the first SCG.
  • the SCG communicates with the second network device, so the UE will not perform link recovery for the first MCG. Therefore, since the link recovery for the first MCG is not performed, it can be considered that the link recovery for the first MCG is unsuccessful.
  • the first RLF report may also include, for example, at least one of the seven items included in the above-described RLF report, which will not be described again here.
  • the UE determines that link recovery for the first MCG is unsuccessful based on the failure to send the RLF information of the first MCG to the second network device.
  • the first RLF report may include one or more of the following: the reason for the link recovery failure, whether the RLF information of the first MCG was successfully sent to the second network through the first SCG Instruction information of the device, first time information or RLF information of the first SCG, wherein the first time information indicates a first running time of the first timer, and the first running time is greater than or equal to the first running time.
  • a preset duration of a timer, and the first running time is the duration from when the UE sends the RLF information of the first MCG to the second network device through the first SCG until the RRC reestablishment process is initiated.
  • the first timer is the first timer configured for the UE by the first network device described in step 301.
  • the first timer involved in the following description has the same meaning as the first timer in step 301, and will not be explained one by one.
  • the link recovery failure reason is related to a problem in the connection between the UE and the first SCG, resulting in the UE being unable to send the RLF information of the first MCG to the UE through the first SCG.
  • the second network device may be caused by RLF occurring in the first SCG.
  • the link recovery failure reason may include one or more of the following: Beam failure of the first SCG Link recovery failure for the first MCG caused by failure of rear beam recovery (beamFailureRecoveryFailure), random access failure for the first SCG (randomAccessProblem), or wireless link control (radio) for the first SCG link control, RLC) retransmits to the maximum number of times (rlc-MaxNumRetx). It can also be understood that the failure of beam recovery after the beam failure of the first SCG, the failure of random access for the first SCG, or the maximum number of radio link control retransmissions for the first SCG causes the An RLF occurs in the first SCG, causing link recovery failure in the first MCG.
  • the UE after the beam failure of the first SCG, the UE will initiate a beam recovery request process for the beam failure of the first SCG.
  • the successful recovery of the beam indicates that the beam recovery is successful. , if the beam does not recover, it means that the beam recovery failed.
  • the failure of beam recovery after the beam failure of the first SCG means that after the beam failure of the first SCG, the beam is not recovered after the UE initiates a beam recovery request process for the beam failure of the first SCG.
  • the RLF information of the first SCG may include one or more of the following: identification information of the first SCG, the reason why RLF occurs in the first SCG, or the reason why the first SCG fails to change ( rlf-Cause) etc.
  • the identification information of the first SCG may include identification information of the secondary primary cell in which the UE detects the RLF or identification information of the secondary primary cell whose change failed (failedPSCellId).
  • the reason why the RLF occurs in the first SCG is any one of the reasons described above that causes the RLF to occur in the first SCG, such as a random access failure for the first SCG.
  • the indication information of whether the RLF information of the first MCG is successfully sent to the second network device through the first SCG may indicate that the RLF information of the first MCG is not successfully passed through the first SCG.
  • whether the RLF information of the first MCG is successfully sent to the second network device through the first SCG may be indicated by sending success identification information, for example, by sending the value of the success identification information. Indicates true or false (true or false) to indicate whether the RLF information of the first MCG is successfully sent, that is, "true" indicates that the RLF information is successfully sent, and "false" indicates that it is not successfully sent.
  • the value of the success identification information is "false".
  • the success identification information may include a bit. A value of "1" for this bit may indicate that the value of the success identification information is "true”, and a value of "0" for this bit may indicate that the The value of the successful identification information is "false”.
  • Case a3 The UE sends the RLF information of the first MCG to the second network device through the first SCG; the UE is based on not receiving the RLF information for the first MCG within the first preset time period.
  • the response message of the RLF information is to determine that the link recovery for the first MCG was unsuccessful.
  • the content of the first RLF report is similar to the content of the first RLF report described in the above case a2, and can be referred to each other, and the description will not be repeated here.
  • the first preset duration may be the preset duration of the first timer.
  • the indication information of whether the RLF information of the first MCG included in the first RLF report is successfully sent to the second network device through the first SCG can indicate that the The RLF information of the first MCG is successfully sent to the second network device through the first SCG.
  • the indication information is the aforementioned success identification information, in this case a3, the success identification information takes a value of true.
  • the first RLF report may also include, for example, at least one of the seven items that may be included in the RLF report introduced above, and the description will not be repeated here.
  • the above situations a1-a3 are scenarios when the link recovery for the first MCG is unsuccessful.
  • the UE also determines whether the link recovery from the first MCG is successful. Switching to the second MCG, that is, whether the UE's MN handover is successful, or whether the UE is successful in switching from the first network device to the target network device (ie, the target MN), where the second MCG is the target network MCG managed by the device; furthermore, the UE may determine the content of the first RLF report based on whether the handover from the first MCG to the second MCG is successful.
  • the switching command may be any one of the following: a command to switch from NR (MobilityFromNRCommand), a command to switch from evolved universal terrestrial radio access (EUTRA) (MobilityFromEUTRACommand), or synchronous reconfiguration. (Reconfiguration with sync).
  • a handover failure occurs when the UE switches from the first MCG to the second MCG, it means that the UE fails to switch from the first MCG to the second MCG.
  • the UE determines that the handover from the first MCG to the second MCG is unsuccessful, which may include: the UE determines that after the UE hands over to the second MCG, the second If an RLF occurs in the second MCG within a preset time period, it is determined that the switch from the first MCG to the second MCG was unsuccessful. That is, if an RLF failure occurs in the second MCG soon after the UE switches to the second MCG, it means that the UE fails to switch from the first MCG to the second MCG successfully.
  • the occurrence of RLF in the second MCG can be understood as a loss of connection between the UE and the second MCG. defeat.
  • the RLF report may be as shown in the following case a4 and case a5:
  • the first RLF report may include the RLF information of the first MCG and the handover failure information of the second MCG. Or the RLF information of the second MCG.
  • the content of the first RLF report may include information related to the first RLF occurrence of MCG (also called the first failure) and the last RLF occurrence of MCG (also known as the second failure) related information.
  • the occurrence of RLF in the first MCG refers to the occurrence of RLF in the first MCG.
  • the occurrence of RLF in the last MCG refers to the handover failure when switching from the first MCG to the second MCG or the occurrence of RLF in the second MCG. .
  • the content of the first RLF report may include one or more of the following: (1) first failedCellId: that is, the identity of the cell that failed for the first time, such as the identity A1 of the Pcell of the first MCG; (2) first connectionFailureType: That is, the connection failure type of the first failure, for example, the connection failure type is RLF; (3) first previousCellId: that is, the source cell identifier of the last handover command received by the UE when the first failure occurred; (4) last failedCellId: that is, the last The identity of the cell that failed once, such as the identity of the Pcell of the second MCG A2; (5) last connectionFailureType: the connection failure type of the last failure, for example, the connection failure type is HOF or RLF; (6) last previousCellId: the last failure When the UE last received the source cell identity of the handover command, for example, the identity B1 of the PScell of the first SCG.
  • first failedCellId that is, the identity of
  • the above items (1)-(3) belong to the RLF information of the first MCG
  • the items (4)-(6) belong to the handover failure information of the second MCG or the RLF information of the second MCG.
  • A1, B1, and A2 are only examples of cell identifiers and are not intended to limit this application.
  • the UE may not clear the RLF report recorded when RLF occurred in the previous first MCG.
  • the first RLF report may also include second time information, the second time information indicates the second running time of the first timer, and the second running time is less than the first timer.
  • the second running time is the time after the UE sends the RLF information of the first MCG to the second network device through the first SCG and receives the response message sent by the second network device. duration.
  • the second running time being less than the preset duration of the first timer means that the first timer is stopped before the first timer times out after being started.
  • the first RLF report may include the RLF information of the first MCG and one or more of the following: the second MCG MCG identification information or second time information.
  • the second time information please refer to the description of the second time information in case a4.
  • the RLF information of the first MCG please refer to the foregoing description and will not be described again here.
  • the identification information of the second MCG is recorded in the first RLF in the following manner:
  • Method 1 Multiplex the reestablishment cell identifier (reestablishmentCellId) field and/or add a new reestablishment cell identifier field (reestablishmentCellIdtype) to indicate the recorded cell identifier of the reestablished cell or the handover target cell or the reselection cell, for example, the cell identifier A2 of the handover target cell.
  • reestablishmentCellId reestablishmentCellId
  • reestablishmentCellIdtype a new reestablishment cell identifier field
  • Method 2 Add a new handover target cell field and/or a reselection cell field to record the cell identity. For example, add a new handover target cell field to record the cell identity A2 of the handover target cell.
  • the UE may not clear the RLF report recorded when RLF occurred in the previous first MCG.
  • the first RLF report in the above five situations can cover parameters related to the first MCG link recovery in various scenarios such as fast MCG link recovery failure or fast MCG link recovery success and then failure, so that subsequent Enable network equipment to accurately adjust network parameters related to MCG link recovery to improve mobility optimization effects, including: improving the success rate of subsequent MCG link recovery, or improving the success rate of UE changing from the first MCG to other MCGs.
  • the network device can analyze the link failure cause based on the first RLF report and determine that the link recovery failure of the first MCG is not because the related parameters configured for the link recovery of the first MCG are unreasonable. Parameter optimization does not need to be performed.
  • the network device can optimize the configuration parameters of the first SCG so that the subsequent first SCG reduces the occurrence of RLF, so that the UE can successfully communicate with the second network device to which the first SCG belongs.
  • the network device can adjust the MCG that the UE needs to switch to, that is, switch the UE from the first MCG to another more appropriate MCG other than the second MCG, thereby improving the handover success rate.
  • the network device can optimize the relevant parameters when the first MCG is switched to the second MCG, so that the UE switches from the first MCG to the second MCG faster to reduce MCG service interruption time.
  • Step 304 The third network device adjusts network parameters related to the first RLF report according to the first RLF report.
  • step 303 For the relevant description of adjusting the network parameters related to the first RLF report, please refer to the relevant description in step 303, which will not be described again here.
  • the third network device can send the adjusted network parameters to other network devices through the interface between network devices, so that the adjusted network parameters can be used when restoring the MCG link between other network devices and the UE. Improve the success rate of MCG link recovery.
  • the third network device as the target main base station in the UE handover process, can send the adjusted network parameters to the source main base station.
  • the UE may initiate RRC reestablishment to access the network device, and then the UE sends the first RLF report to the third network device.
  • the UE may switch or reselect the network device to access the network device, and then the UE sends the first RLF report to the third network device.
  • the third network device may be the first network device, or may be a network device other than the first network device.
  • the UE switches from the first network device to the third network device, that is, the third network device
  • the device is the target network device in the handover scenario, which is not limited in this application. It should be noted that when an RLF occurs in the first SCG managed by the second network device, the third network device may also be the second network device.
  • the third network device receives the first RLF report from the UE.
  • the third network device may receive the first RLF report from the UE through other network devices.
  • the other network devices are the The network device currently accessed by the UE. That is to say, the UE first sends the first RLF report to other network devices (ie, the network device currently accessed by the UE), and then the other network devices forward the first RLF report to the third network device.
  • the third network device is not the network device currently accessed by the UE.
  • the third network device may be a network device currently accessed by the UE.
  • the third network device may directly receive the first RLF report from the UE.
  • the third network device may adjust network parameters related to the first RLF report according to the first RLF report.
  • the first network device directly obtains the first RLF report from the UE; or, when the UE has switched from the first network device to another network device, the first network device can obtain the first RLF report from the other network device.
  • the network device obtains the first RLF report.
  • the third network device may adjust the network parameters related to the first RLF report according to the first RLF report, and use the adjusted The network parameters The relevant information is sent to the first network device and/or the second network device.
  • the UE can report an RLF report related to whether the link recovery for the MCG is successful, thereby improving the mobility optimization effect, thereby improving the success rate of subsequent MCG re-establishment connections, thereby enhancing the terminal equipment's performance
  • the continuity and reliability of dual-connection or multi-connection communication improve communication quality.
  • the UE and the first network device are used as the source MN (source MN, S-MN), that is, the S-MN manages the first MCG, the second network device is the SN, that is, the SN manages the first SCG, and the third
  • the network device is the target MN (target MN, T-MN), and the first timer is the T316 timer as an example for explanation.
  • Figure 4 shows an example of a communication method.
  • the RLF report adds a new record of the reason for link recovery failure.
  • the specific process of this example may include:
  • Step 401 The S-MN sends request information to the SN, which requests the SN to support MCG fast recovery through split SRB1 or SRB3.
  • Step 402 The S-MN configures the T316 timer for the UE.
  • Step 403 The UE determines that RLF occurs in the first MCG and detects that the first SCG is added or changed, or the transmission of the first SCG is suspended, then the UE determines not to perform link recovery for the first MCG. .
  • the UE cannot initiate fast MCG link recovery procedure.
  • the UE if the UE detects that RLF occurs in the first MCG, the UE needs to indicate the RLF information of the first MCG to the S-MN through the first SCG when initiating the fast MCG link recovery procedure. In the case of step 403, the first SCG and the UE The transmission has been interrupted. When the UE senses this situation, it does not initiate the fast MCG link recovery procedure.
  • Step 404 The UE initiates the RRC reestablishment process and accesses the T-MN.
  • Step 405 The UE sends the first RLF report to the T-MN.
  • the T-MN may then send the first RLF report to the S-MN, so that the S-MN adjusts relevant network parameters based on the first RLF report.
  • the first RLF report please refer to the first RLF report in case a1 in the embodiment shown in 3 above, which will not be described again here.
  • the RLF report is enhanced based on this scenario so that the network device can analyze the cause of the fast MCG link recovery failure. It can be known that the fast MCG link recovery failure is not for fast MCG. It is caused by unreasonable configuration parameters of link recovery, but it is caused by unreasonable configuration of mobility-related parameters of SCG.
  • Figure 5 shows another example of a communication method.
  • RLF occurs in the first MCG
  • the UE initiates a link recovery process for the first MCG (that is, initiating a fast MCG A failure occurs in link recovery procedure
  • the RLF report adds process information that records link recovery failure.
  • the specific process of this example may include:
  • Step 501 The S-MN sends request information to the SN, which requests the SN to support MCG fast recovery through split SRB1 or SRB3.
  • Step 502 The S-MN configures the T316 timer for the UE.
  • Step 503 After determining that RLF occurs in the first MCG, the UE initiates a link recovery process for the first MCG, but the UE fails to send the RLF information of the first MCG to the SN through the first SCG.
  • the reason why the UE fails to send the RLF information of the first MCG to the SN through the first SCG may be that RLF occurs in the first SCG, or the UE fails to randomly access the first SCG when the first SCG is deactivated.
  • Step 504 The UE initiates the RRC reestablishment process and accesses the T-MN.
  • Step 505 The UE sends the first RLF report to the T-MN.
  • the T-MN may then send the first RLF report to the S-MN, so that the S-MN adjusts relevant network parameters based on the first RLF report.
  • first RLF report please refer to the first RLF report in case a2 in the embodiment shown in 3 above, which will not be described again here.
  • the RLF report is enhanced based on this scenario so that the network device can optimize the fast MCG link recovery process.
  • the configuration parameters of the SCG can be optimized. Since the SCG is used Sending the RLF information of the first MCG and optimizing the configuration parameters of the SCG can reduce the occurrence of RLF in subsequent SCGs, thereby enabling the UE to successfully communicate with the SN.
  • Figure 6 shows another example of a communication method.
  • RLF occurs in the first MCG
  • the UE initiates a link recovery process for the first MCG (that is, initiating a fast MCG A failure occurs in link recovery procedure
  • the RLF report adds process information that records link recovery failure.
  • the specific process of this example may include:
  • Step 601 The S-MN sends request information to the SN, which requests the SN to support MCG fast recovery through split SRB1 or SRB3.
  • Step 602 The S-MN configures the T316 timer for the UE.
  • Step 603 After determining that RLF occurs in the first MCG, the UE initiates a link recovery process for the first MCG, and the UE sends the RLF information of the first MCG to the SN through the first SCG.
  • Step 604 The UE determines that a response message for the RLF information of the first MCG has not been received.
  • RLF occurs in the first SCG, causing the UE to not receive a response message to the RLF information of the first MCG within the preset duration of the T316 timer.
  • Step 605 The UE initiates the RRC reestablishment process and accesses the T-MN.
  • Step 606 The UE sends the first RLF report to the T-MN.
  • the T-MN may then send the first RLF report to the S-MN, so that the S-MN adjusts relevant network parameters based on the first RLF report.
  • the first RLF report please refer to the first RLF report in case a3 in the embodiment shown in 3 above, which will not be described again here.
  • the RLF report is enhanced based on this scenario so that the network device can optimize the fast MCG link recovery process.
  • the configuration parameters of the SCG can be optimized. Since the SCG uses After sending the RLF information of the first MCG and optimizing the configuration parameters of the SCG, the occurrence of RLF in subsequent SCGs can be reduced, so that the UE can successfully communicate with the SN described in the SCG.
  • Figure 7 shows another example of a communication method.
  • RLF occurs in the first MCG
  • the UE successfully initiates the link recovery process for the first MCG that is, initiating the fast MCG link recovery procedure is successful
  • the UE occurs RLF at the second MCG
  • the RLF report newly records the second MCG connection failure information.
  • the second MCG is not an MCG managed by the T-MN.
  • the second MCG is an MCG managed by the MN that the UE needs to switch to when the link recovery procedure for the first MCG is successful.
  • the UE accesses the T-MN through the RRC reestablishment process.
  • the specific process of this example may include:
  • Step 701 The S-MN sends request information to the SN, which requests the SN to support MCG fast recovery through split SRB1 or SRB3.
  • Step 702 The S-MN configures the T316 timer for the UE.
  • Step 703 After determining that RLF occurs in the first MCG, the UE initiates a link recovery process for the first MCG, and the UE sends the RLF information of the first MCG to the SN through the first SCG.
  • Step 704 The UE receives a response message for the RLF information of the first MCG from the SN through the first SCG, instructing the UE to switch from the first MCG to the second MCG.
  • the response message to the RLF information of the first MCG may be a switching command.
  • Step 705 The UE determines that the handover from the first MCG to the second MCG was unsuccessful.
  • the UE fails to switch from the first MCG to the second MCG, please refer to the situation in which the UE fails to switch from the first MCG to the second MCG in the embodiment shown in FIG. 3. No further details will be given here.
  • Step 706 The UE initiates the RRC reestablishment process and accesses the T-MN.
  • Step 707 The UE sends the first RLF report to the T-MN.
  • the T-MN may then send the first RLF report to the S-MN, so that the S-MN adjusts relevant network parameters based on the first RLF report.
  • the RLF report is enhanced based on this scenario so that the network device can optimize the subsequent processes of the fast MCG link recovery process, such as The MCG that the UE needs to switch to can be adjusted, that is, the terminal device can switch from the first MCG to another more suitable MCG other than the second MCG, thereby improving the handover success rate.
  • Figure 8 shows an example of yet another communication method.
  • RLF occurs in the first MCG, and the UE successfully initiates the link recovery process for the first MCG (that is, initiating fast MCG link recovery procedure is successful), RLF reports the relevant information of the second MCG after the new record is switched.
  • the specific process of this example may include:
  • Step 801 The S-MN sends request information to the SN.
  • the request information requests the SN to support MCG fast recovery through split SRB1 or SRB3.
  • Step 802 The S-MN configures the T316 timer for the UE.
  • Step 803 After determining that RLF occurs in the first MCG, the UE initiates a link recovery process for the first MCG, and the UE sends the RLF information of the first MCG to the SN through the first SCG.
  • Step 804 The UE receives a response message for the RLF information of the first MCG from the SN through the first SCG, instructing the UE to switch from the first MCG to the second MCG.
  • the response message to the RLF information of the first MCG may be a handover command (MobilityFromNRCommand, MobilityFromEUTRACommand, Reconfiguration with sync), or it may also be an RRC release message.
  • Step 805 The UE determines that the handover from the first MCG to the second MCG is successful.
  • Step 806 The UE sends the first RLF report to the T-MN through the second MCG.
  • the T-MN is the MN managing the second MCG.
  • the T-MN may then send the first RLF report to the S-MN, so that the S-MN adjusts relevant network parameters based on the first RLF report.
  • first RLF report please refer to the first RLF report in case a5 in the embodiment shown in 3 above, which will not be described again here.
  • the RLF report is enhanced based on this scenario so that the network device can optimize the fast MCG link recovery process.
  • the network device can be based on The RLF report optimizes relevant parameters for switching from the first MCG to the second MCG, allowing the UE to switch from the first MCG to the second MCG faster and reducing the MCG service interruption time.
  • the communication device 900 may include a transceiver unit 901 and a processing unit 902 .
  • the transceiver unit 901 is used for the communication device 900 to receive information (message or data) or send information (message or data), and the processing unit 902 is used to control and manage the actions of the communication device 900 .
  • the processing unit 902 can also control the steps performed by the transceiver unit 901.
  • the communication device 900 may be the network device (such as the first network device, the second network device or the third network device, etc.) in the above embodiment, a processor or chip in the network device, or A chip system, or a functional module, etc.; or, the communication device 900 can specifically be the terminal equipment (such as UE) in the above embodiment, the processor of the terminal equipment, or a chip, or a chip system, or a functional module. Modules etc.
  • the communication device 900 when used to implement the functions of the terminal equipment (such as UE) in the embodiments described in Figures 3 to 8, it may include: the transceiver unit 901 may be used to communicate with the first A network device communicates with a second network device, wherein the first network device manages a first primary cell group MCG, the second network device manages a first secondary cell group SCG, and the first SCG is configured with an MCG chain road recovery function; the processing unit 902 may be used to determine that a wireless link failure RLF occurs in the first MCG; the transceiver unit 901 may also be used to send a first RLF report to the third network device, the first RLF The report relates to whether link recovery for the first MCG was successful.
  • the transceiver unit 901 may be used to communicate with the first A network device communicates with a second network device, wherein the first network device manages a first primary cell group MCG, the second network device manages a first secondary cell group SCG, and the first SCG is configured with an
  • the first RLF report when the link recovery for the first MCG is unsuccessful, the first RLF report includes the link recovery failure reason.
  • the link recovery failure reason may include one or more of the following: the first SCG is added, the first SCG is changed, or the transmission of the first SCG is suspended.
  • the processing unit 902 may also be configured to determine not to perform link recovery for the first MCG based on the first SCG being added or changed, or the transmission of the first SCG being suspended. .
  • the processing unit 902 may also be configured to determine link recovery for the first MCG based on a failure to send the RLF information of the first MCG to the second network device. Unsuccessful.
  • the transceiver unit 901 may also be configured to send the RLF information of the first MCG to the second network device through the first SCG; the processing unit 902 may also Used to determine that link recovery for the first MCG is unsuccessful based on the fact that the transceiver unit 901 does not receive a response message for the RLF information for the first MCG within a first preset time period.
  • the first RLF report may include one or more of the following: a link recovery failure reason, whether the RLF information of the first MCG was successfully sent to the second network device through the first SCG.
  • Indication information first time information or RLF information of the first SCG, wherein the first time information indicates a first running time of the first timer, and the first running time is greater than or equal to the first timing
  • the preset duration of the device the first operation
  • the travel time is the time from when the terminal device sends the RLF information of the first MCG to the second network device through the first SCG until the RRC reestablishment process is initiated.
  • the link recovery failure reason includes one or more of the following: link recovery failure for the first MCG caused by beam recovery failure after the beam failure of the first SCG, link recovery failure for the first MCG.
  • the RLF information of the first SCG includes one or more of the following: identification information of the first SCG, the reason why the RLF occurs in the first SCG, or the reason why the change of the first SCG fails.
  • the processing unit 902 may also be used to determine whether the switch from the first MCG to the second MCG is successful; and based on whether the switch from the first MCG to the second MCG is successful; The first MCG is successfully switched to the second MCG, and the first RLF report is determined.
  • the first RLF report when the handover from the first MCG to the second MCG is unsuccessful, includes the RLF information of the first MCG and the handover failure information of the second MCG. Or the RLF information of the second MCG.
  • the processing unit 902 determines that the switch from the first MCG to the second MCG has not been successful, it may be configured to: based on the second MCG after the terminal device switches to the second MCG, If an RLF occurs in the second MCG within a preset time period, it is determined that the switch from the first MCG to the second MCG was unsuccessful.
  • the first RLF report when switching from the first MCG to the second MCG is successful, includes the RLF information of the first MCG and one or more of the following: the first MCG Two MCG identification information or second time information, the second time information indicates the second running time of the first timer, the second running time is less than the preset duration of the first timer, the second The running time is the time period for the terminal device to receive the response message sent by the second network device after sending the RLF information of the first MCG to the second network device through the first SCG.
  • the communication device 900 when used to implement the functions of the third network device in the embodiments described in FIGS. 3-8, it may include: the transceiver unit 901 may be used to receive the third network device from the terminal device.
  • An RLF report the first RLF report is related to whether the link recovery for the first MCG is successful after the first primary cell group MCG sends the RLF;
  • the processing unit 902 may be configured to perform the following operations according to the first RLF report: Adjust network parameters related to the first RLF report.
  • the terminal device communicates with a first network device and a second network device respectively, wherein the first network device manages a first primary cell group MCG, and the second network device manages a first secondary cell group SCG, so The first SCG is configured with the MCG link recovery function.
  • the first RLF report when the link recovery for the first MCG is unsuccessful, the first RLF report includes the link recovery failure reason.
  • the link recovery failure reason includes one or more of the following: the first SCG is added, the first SCG is changed, or the transmission of the first SCG is suspended.
  • the first RLF report when the link recovery for the first MCG is unsuccessful, includes one or more of the following: the link recovery failure reason, the first Whether the RLF information of the MCG is successfully sent to the second network device through the first SCG, the first time information or the RLF information of the first SCG, wherein the first time information indicates the first timing
  • the first running time of the timer is greater than or equal to the preset duration of the first timer, and the first running time is when the terminal device sends a signal to the second network through the first SCG. The time period from when the device sends the RLF information of the first MCG to initiating the RRC reestablishment process.
  • the link recovery failure reason includes one or more of the following: link recovery failure for the first MCG caused by beam recovery failure after the beam failure of the first SCG, link recovery failure for the first MCG.
  • the RLF information of the first SCG includes one or more of the following: identification information of the first SCG, the reason why the RLF occurs in the first SCG, or the reason why the change of the first SCG fails.
  • the first RLF report is also related to whether the terminal device successfully switches from the first MCG to the second MCG.
  • the first RLF report when the handover from the first MCG to the second MCG is unsuccessful, includes the RLF information of the first MCG, and the handover failure information of the second MCG or the Describe the RLF information of the second MCG.
  • the first RLF report when switching from the first MCG to the second MCG is successful, includes the RLF information of the first MCG and one or more of the following: the first MCG.
  • Two MCG identification information or second time information the second time information indicates the second running time of the first timer, the second running time is less than the preset duration of the first timer, the second The running time is the time period for the terminal device to receive the response message sent by the second network device after sending the RLF information of the first MCG to the second network device through the first SCG.
  • each functional unit in the embodiment of the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of the application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .
  • the communication device 1000 may include a transceiver 1001 and a processor 1002 .
  • the communication device 1000 may also include a memory 1003.
  • the memory 1003 may be disposed inside the communication device 1000 or may be disposed outside the communication device 1000 .
  • the processor 1002 can control the transceiver 1001 to receive and send information, messages or data, etc.
  • the processor 1002 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor 1002 may further include a hardware chip.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL) or any combination thereof.
  • the transceiver 1001, the processor 1002 and the memory 1003 are connected to each other.
  • the transceiver 1001, the processor 1002 and the memory 1003 are connected to each other through a bus 1004;
  • the bus 1004 can be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard Structure (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI peripheral component interconnect standard
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in Figure 10, but it does not mean that there is only one bus or one type of bus.
  • the memory 1003 is used to store programs, etc.
  • the program may include program code including computer operating instructions.
  • the memory 1003 may include RAM, and may also include non-volatile memory (non-volatile memory), such as one or more disk memories.
  • the processor 1002 executes the application program stored in the memory 1003 to implement the above functions, thereby realizing the functions of the communication device 1000 .
  • the communication device 1000 may be the network device (the first network device, the second network device, or the third network device) in the above embodiment; it may also be the terminal device in the above embodiment.
  • the transceiver 1001 can implement the functions of the terminal equipment in the embodiments shown in FIGS. 3-8. Transceiver operations performed; the processor 1002 can implement other operations other than the transceiver operations performed by the terminal device in the embodiments shown in FIGS. 3 to 8 .
  • the relevant descriptions please refer to the relevant descriptions in the above-mentioned embodiments shown in FIGS. 3 to 8 , and will not be introduced in detail here.
  • the transceiver 1001 can implement the functions of the third network device in the embodiment shown in FIGS. 3-8.
  • Transceiver operations performed by the third network device; the processor 1002 may implement other operations other than the transceiver operations performed by the third network device in the embodiments shown in FIGS. 3 to 8 .
  • the relevant descriptions in the above-mentioned embodiments shown in FIGS. 3 to 8 please refer to the relevant descriptions in the above-mentioned embodiments shown in FIGS. 3 to 8 , and will not be introduced in detail here.
  • embodiments of the present application provide a communication system, which may include the terminal device, a first network device, a second network device, a third network device, etc. involved in the above embodiments.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium is used to store a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.
  • Embodiments of the present application also provide a computer program product.
  • the computer program product is used to store a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.
  • An embodiment of the present application also provides a chip, including a processor, which is coupled to a memory and configured to call a program in the memory so that the chip implements the communication method provided by the above method embodiment.
  • An embodiment of the present application also provides a chip, which is coupled to a memory, and is used to implement the communication method provided by the above method embodiment.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • the terminal and/or the network device may perform some or all of the steps in the embodiment of the present application. These steps or operations are only examples. In the embodiment of the present application, other operations or operations may also be performed. A variation of the operation. In addition, various steps may be performed in a different order than those presented in the embodiments of the present application, and it may not be necessary to perform all operations in the embodiments of the present application.

Landscapes

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

Abstract

本申请提供一种通信方法及装置，用以实现终端设备上报与针对MCG的链路恢复是否成功相关的RLF报告。终端设备分别与第一网络设备以及第二网络设备通信，所述第一网络设备管理第一MCG，所述第二网络设备管理第一SCG，所述第一SCG被配置了MCG链路恢复功能；所述终端设备确定所述第一MCG发生无线链路失败RLF后，向第三网络设备发送第一RLF报告，所述第一RLF报告与针对所述第一MCG的链路恢复是否成功相关。这样终端设备可以上报与针对MCG的链路恢复是否成功相关的RLF报告，从而提升网络设备基于RLF报告进行移动性优化的效果。

Description

通信方法及装置
相关申请的交叉引用
本申请要求在2022年05月11日提交中国专利局、申请号为202210510815.9、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
双连接(dual-connectivity，DC)或多连接(multi-connectivity，MC)通信中，终端设备可以同时与至少两个接入网设备，例如，与一个主基站以及一个或多个辅基站存在通信连接，其中，主基站管理主小区组(master cell group，MCG)，辅基站管理辅小区组(se condary cell group，SCG)，终端设备可以通过MCG中的小区获取主基站的通信服务，以及，可以通过SCG中的小区获取辅基站的通信服务。
在上述双连接或多连接通信场景中，当终端设备检测到MCG发生无线链路失败(rad io link failure，RLF)时，可以通过快速MCG链路恢复(fast MCG link recovery)流程，尝试恢复终端设备与MCG之间的连接。
然而，如果网络设备不能及时获取快速MCG链路恢复流程的相关参数，则网络设备无法针对MCG链路恢复流程进行移动性优化，影响双连接或多连接的通信质量。
发明内容
本申请提供一种通信方法及装置，用以实现终端设备上报与针对MCG的链路恢复是否成功相关的RLF报告，从而提升网络设备基于RLF报告进行移动性优化的效果。
第一方面，本申请提供了一种通信方法，该方法可以包括：终端设备分别与第一网络设备以及第二网络设备通信；所述终端设备确定第一MCG发生RLF后，向第三网络设备发送第一RLF报告，所述第一RLF报告与针对所述第一MCG的链路恢复是否成功相关。其中，所述第一网络设备管理第一MCG，所述第二网络设备管理第一SCG，所述第一SC G被配置了MCG链路恢复功能。
其中，第三网络设备可以是第一网络设备或者第二网络设备。其中，当第二网络设备管理的第一SCG发生RLF后，第三网络设备可以是第二网络设备。
通过上述方法，终端设备可以向网络设备上报与针对MCG的链路恢复是否成功相关的RLF报告，从而提升网络设备基于RLF报告进行移动性优化的效果，具体地，网络设备可以针对MCG链路恢复的相关网络参数进行优化，提高后续MCG重新建立连接的成功率，从而，增强终端设备进行双连接或多连接通信的连续性与可靠性，提高通信质量。
在一个可能的设计中，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告可以包括链路恢复失败原因。这样后续网络设备可以基于所述第一RLF报告分析第一M CG的链路恢复失败的原因，进而调整相关网络参数。
在一个可能的设计中，所述链路恢复失败原因可以包括以下一项或多项：所述第一SCG被添加、所述第一SCG被变更或所述第一SCG的传输被挂起。这样后续网络设备可以基于所述第一RLF报告分析第一MCG的链路恢复失败的原因，进而调整相关网络参数。
在一个可能的设计中，所述终端设备基于所述第一SCG被添加或被变更，或者，所述第一SCG的传输被挂起确定不进行针对所述第一MCG的链路恢复，从而，确定针对所述第一MCG的链路恢复未成功。
在一个可能的设计中，所述终端设备基于向所述第二网络设备发送所述第一MCG的RLF信息失败，确定针对所述第一MCG的链路恢复未成功。这样终端设备可以定位到未成针对所述第一MCG的链路恢复未成功的原因，进而在RLF报告中记录相关原因信息，以使网络设备进行原因分析。
在一个可能的设计中，所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后，所述终端设备基于在第一预设时长内没有接收到针对所述第一MCG的RLF信息的响应消息，则确定针对所述第一MCG的链路恢复未成功。这样终端设备可以定位到未成针对所述第一MCG的链路恢复未成功的原因，进而在RLF报告中记录相关原因信息，以使网络设备进行原因分析。
在一个可能的设计中，所述第一RLF报告可以包括以下一项或多项：链路恢复失败原因、所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息、第一时间信息或所述第一SCG的RLF信息，其中，所述第一时间信息指示第一定时器的第一运行时间，所述第一运行时间大于或者等于所述第一定时器的预设时长，所述第一运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后到发起无线资源控制(radio resource control，RRC)重建流程的时长。这样，可以基于终端设备发起MCG链路恢复过程中失败的场景，对RLF报告进行增强，以使网络设备可以优化MCG链路恢复流程，从而优化相关网络参数，例如可以优化第一SCG的配置参数，由于该第一SCG用于发送第一MCG的RLF信息，对该第一SCG的配置参数优化后，可以使后续第一SCG减少发生RLF的情况，从而可以使终端设备与第二网络设备成功通信。
在一个可能的设计中，所述链路恢复失败原因可以包括以下一项或多项：所述第一SCG的波束失败后波束恢复的失败导致的针对所述第一MCG的链路恢复失败、针对所述第一SCG的随机接入失败或针对所述第一SCG的无线链路控制RLC重传达到最大次数。这样可以明确链路恢复失败的具体原因，从而准确进行网络优化。
在一个可能的设计中，所述第一SCG的RLF信息可以包括以下一项或多项：所述第一SCG的标识信息、所述第一SCG发生RLF的原因或所述第一SCG变更失败的原因。这样可以明确发生问题的第一SCG，从而网络设备可以优化第一SCG的配置参数，由于该第一SCG用于发送第一MCG的RLF信息，对该第一SCG的配置参数优化后，可以使后续第一SCG减少发生RLF的情况，从而可以使终端设备与第二网络设备成功通信。
在一个可能的设计中，当针对所述第一MCG的链路恢复成功时，所述终端设备还可以确定是否从所述第一MCG成功切换到第二MCG；进而所述终端设备根据是否从所述第一MCG成功切换到所述第二MCG，确定所述第一RLF报告。这样，在针对所述第一MCG的链路恢复成功的情况下，可以结合终端设备的实际切换情况来确定第一RLF报告的内容，以使网络设备优化后续切换流程，提高切换成功率。
在一个可能的设计中，当从所述第一MCG未成功切换到所述第二MCG时，所述第一RLF报告可以包括所述第一MCG的RLF信息，以及，所述第二MCG的切换失败信息或所述第二MCG的RLF信息。这样，可以基于终端设备发起MCG链路恢复流程成功后，在第二MCG发生RLF失败的场景，对RLF报告进行增强，以使网络设备可以优化MCG链路恢复流程的后续流程，例如可以调整终端设备需要切换到的MCG等，也即令终端设备可以从第一MCG切换到第二MCG以外的其他更适合的MCG，提高切换成功率。
在一个可能的设计中，所述终端设备可以通过如下方法确定从所述第一MCG未成功切换到所述第二MCG：所述终端设备基于当所述终端设备切换到所述第二MCG后，在第二预设时长内所述第二MCG发生RLF，确定未成功从所述第一MCG切换到所述第二MCG。这样，在终端设备切换到第二MCG后很短时间内，第二MCG发生RLF导致终端设备无法通过第二MCG通信的情况下，使终端设备可以继续重选MCG。
在一个可能的设计中，当从所述第一MCG成功切换到所述第二MCG时，所述第一RLF可以报告包括所述第一MCG的RLF信息，以及以下一项或多项：所述第二MCG的标识信息或第二时间信息，所述第二时间信息指示第一定时器的第二运行时间，所述第二运行时间小于所述第一定时器的预设时长，所述第二运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后收到所述第二网络设备发送的响应消息的时长。这样，基于终端设备发起MCG链路恢复过程成功后，在第二MCG连接的场景，对RLF报告进行增强，可以使网络设备基于RLF报告进行第一MCG切换到第二MCG的相关参数的优化，令终端设备从第一MCG较快地切换到第二MCG，减少MCG服务中断时间。
第二方面，本申请提供了一种通信方法，该方法可以包括：第三网络设备从终端设备接收第一RLF报告后，根据所述第一RLF报告调整所述第一RLF报告相关的网络参数。所述第一RLF报告与在第一主小区组MCG发送RLF后针对所述第一MCG的链路恢复是否成功相关；所述终端设备分别与第一网络设备以及第二网络设备通信，其中，所述第一网络设备管理第一主小区组MCG，所述第二网络设备管理第一辅小区组SCG，所述第一SCG被配置了MCG链路恢复功能。其中，第三网络设备可以是第一网络设备或者第二网络设备。其中，当第二网络设备管理的第一SCG发生RLF后，第三网络设备可以是第二网络设备。
通过上述方法，终端设备可以向网络设备上报与针对MCG的链路恢复是否成功相关的RLF报告，从而提升网络设备基于RLF报告进行移动性优化的效果，具体地，网络设备可以针对MCG链路恢复的相关网络参数进行优化，提高后续MCG重新建立连接的成功率，从而，增强终端设备进行双连接通信的连续性与可靠性，提高通信质量。
在一个可能的设计中，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告可以包括链路恢复失败原因。这样网络设备可以基于所述第一RLF报告分析第一MCG的链路恢复失败的原因，进而调整相关网络参数。
在一个可能的设计中，所述链路恢复失败原因可以包括以下一项或多项：所述第一SCG被添加、所述第一SCG被变更或所述第一SCG的传输被挂起。这样网络设备可以基于所述第一RLF报告分析第一MCG的链路恢复失败的原因，进而调整相关网络参数。
在一个可能的设计中，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告可以包括以下一项或多项：链路恢复失败原因、所述第一MCG的RLF信息是否成功通 过所述第一SCG发送给所述第二网络设备的指示信息、第一时间信息或所述第一SCG的RLF信息，其中，所述第一时间信息指示第一定时器的第一运行时间，所述第一运行时间大于或者等于所述第一定时器的预设时长，所述第一运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后到发起RRC重建流程的时长。这样，可以基于终端设备发起MCG链路恢复过程中失败的场景，对RLF报告进行增强，以使网络设备可以优化MCG链路恢复流程，从而优化相关网络参数，例如可以优化第一SCG的配置参数，由于该第一SCG用于发送第一MCG的RLF信息，对该第一SCG的配置参数优化后，可以使后续第一SCG减少发生RLF的情况，从而可以使终端设备与第二网络设备成功通信。
在一个可能的设计中，所述链路恢复失败原因可以包括以下一项或多项：所述第一SCG的波束失败后波束恢复的失败导致的针对所述第一MCG的链路恢复失败、针对所述第一SCG的随机接入失败或针对所述第一SCG的无线链路控制RLC重传达到最大次数。这样可以明确链路恢复失败的具体原因，从而准确进行网络优化。
在一个可能的设计中，所述第一SCG的RLF信息可以包括以下一项或多项：所述第一SCG的标识信息、所述第一SCG发生RLF的原因或所述第一SCG变更失败的原因。这样可以明确发生问题的第一SCG，从而网络设备可以优化第一SCG的配置参数，由于该第一SCG用于发送第一MCG的RLF信息，对该第一SCG的配置参数优化后，可以使后续第一SCG减少发生RLF的情况，从而可以使终端设备与第二网络设备成功通信。
在一个可能的设计中，当针对所述第一MCG的链路恢复成功时，所述第一RLF报告还与所述终端设备是否从所述第一MCG成功切换到第二MCG相关。这样，在针对所述第一MCG的链路恢复成功的情况下，可以结合终端设备的实际切换情况来确定第一RLF报告的内容，以使网络设备优化后续切换流程，提高切换成功率。
在一个可能的设计中，当从所述第一MCG未成功切换到所述第二MCG时，所述第一RLF报告可以包括所述第一MCG的RLF信息，以及，第二MCG的切换失败信息或所述第二MCG的RLF信息。这样，可以基于终端设备发起MCG链路恢复流程成功后，在第二MCG发生RLF失败的场景，对RLF报告进行增强，以使第三网络设备可以优化MCG链路恢复流程的后续流程，例如可以调整终端设备需要切换到的MCG等，也即令终端设备从第一MCG切换到第二MCG以外的其他更适合的MCG，提高切换成功率。
在一个可能的设计中，当从所述第一MCG成功切换到所述第二MCG时，所述第一RLF报告可以包括所述第一MCG的RLF信息，以及以下一项或多项：所述第二MCG的标识信息或第二时间信息，所述第二时间信息指示第一定时器的第二运行时间，所述第二运行时间小于所述第一定时器的预设时长，所述第二运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后收到所述第二网络设备发送的响应消息的时长。这样，基于终端设备发起MCG链路恢复过程成功后，在第二MCG连接的场景，对RLF报告进行增强，可以使网络设备基于RLF报告进行第一MCG切换到第二MCG的相关参数的优化，令终端设备从第一MCG较快地切换到第二MCG，减少MCG服务中断时间。
第三方面，本申请还提供了一种通信装置，所述通信装置可以是终端设备，该通信装置具有实现上述第一方面或第一方面的各个可能的设计示例中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个 与上述功能相对应的模块。
在一个可能的设计中，所述通信装置的结构中包括收发单元和处理单元，这些单元可以执行上述第一方面或第一方面的各个可能的设计示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述通信装置的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发信息或数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述通信装置执行上述第一方面或第一方面的各个可能的设计示例中的相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第四方面，本申请还提供了一种通信装置，所述通信装置可以是第三网络设备，该通信装置具有实现上述第二方面或第二方面的各个可能的设计示例中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述通信装置的结构中包括收发单元和处理单元，这些单元可以执行上述第二方面或第二方面的各个可能的设计示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述通信装置的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发信息或数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述通信装置执行上述第二方面或第二方面的各个可能的设计示例中的相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第五方面，本申请实施例提供了一种通信系统，可以包括上述提及的终端设备、第一网络设备、第二网络设备和第三网络设备等。
第六方面，本申请实施例提供的一种计算机可读存储介质，该计算机可读存储介质存储有程序指令，当程序指令在计算机上运行时，使得计算机执行本申请实施例第一方面及其任一可能的设计中，或第二方面及其任一可能的设计中所述的方法。示例性的，计算机可读存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括非瞬态计算机可读介质、随机存取存储器(random-access memory，RAM)、只读存储器(read-only memory，ROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。
第七方面，本申请实施例提供一种计算机程序产品，包括计算机程序代码或指令的，当计算机程序代码或指令在计算机上运行时，使得上述第一方面或第一方面任一种可能的设计中，或者上述第二方面或第二方面任一种可能的设计中所述的方法被执行。
第八方面，本申请还提供了一种芯片，包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以使所述芯片实现上述第一方面或第一方面任一种可能的设计中，或者上述第二方面或第二方面任一种可能的设计中所述的方法。
上述第三方面至第八方面中的各个方面以及各个方面可能达到的技术效果请参照上述针对第一方面或第一方面中的各种可能方案，或者第二方面或第二方面中的各种可能方 案可以达到的技术效果说明，这里不再重复赘述。
附图说明
图1为本申请提供的一种通信系统的架构示意图；
图2为本申请提供的一种基站的协议栈的示意图；
图3为本申请提供的一种通信方法的流程示意图；
图4为本申请提供的一种通信方法的示例的流程示意图；
图5为本申请提供的又一种通信方法的示例的流程示意图；
图6为本申请提供的又一种通信方法的示例的流程示意图；
图7为本申请提供的又一种通信方法的示例的流程示意图；
图8为本申请提供的又一种通信方法的示例的流程示意图；
图9为本申请提供的一种通信装置的结构示意图；
图10为本申请提供的一种通信装置的结构图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种通信方法及装置，以实现终端设备上报与针对MCG的链路恢复是否成功相关的RLF报告，从而提升网络设备基于RLF报告进行移动性优化的效果。其中，本申请所述方法和装置基于同一技术构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
本申请中所述的协议可以是指通信协议或者说规范，例如3GPP通信协议。
应理解，在本申请实施例中，“与A对应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本申请实施例中出现的“传输”(transmit/transmission)如无特别说明，是指双向传输，包含发送和/或接收的动作。具体地，本申请实施例中的“传输”包含数据的发送，数据的接收，或者数据的发送和数据的接收。或者说，这里的数据传输包括上行和/或下行数据传输。数据可以包括信息和/或信号，上行数据传输即上行信息和/或上行信号传输，下行数据传输即下行信息和/或下行信号传输。
以下，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
(1)双连接(dual-connectivity，DC)，或多连接(multi-connectivity，MC)
双连接或多连接，即终端设备可以同时与至少两个接入网设备存在通信连接，也即支持至少两个接入网设备同时为一个终端设备提供数据传输服务。其中，一个接入网设备为主基站，主基站(可以简称主站)也可以称为主节点(master node，MN)。其他接入网设备为辅基站，辅基站(可以简称辅站)也可以称为辅节点(secondary node，SN)。MN可以负责与该终端设备交互无线资源控制消息以及负责和核心网控制面实体交互。由于终端设备在一个接入网设备下可以同时接收多个小区的服务，MN管理的多个服务小区组成主 小区组(master cell group，MCG)，包括一个主小区(primary cell，PCell)和可选的一个或多个辅小区(secondary cell，SCell)。SN管理的多个服务小区组成辅小区组(second ary cell group，SCG)，包括一个主辅小区(primary secondary cell，PScell)的和可选的一个或多个SCell。在一些场景中，MN也可以称为MCG，SN也可以称为SCG。
(2)快速MCG链路恢复(fast MCG link recovery)
当终端设备检测到MCG发生RLF时，即使SCG仍在正常与终端设备通信，终端设备将针对MCG发起RRC重建并释放SCG配置，而RRC重建会带来长时间的数据中断，例如90～130毫秒(ms)的数据中断。其中，本申请中，MCG发生RLF可以理解为MCG中包括PCell在内的一个或多个小区发生RLF。MCG发生RLF也可以理解为终端设备和MCG之间的连接失败。
为了避免RRC重建，可以采用fast MCG link recovery流程。如果终端设备检测到M CG发生RLF，终端设备可以通过SN向MN指示MCG的链路失败信息，尝试进行MCG的链路恢复，即终端设备尝试恢复该终端设备与MCG之间的连接。在上述过程中，SCG支持MCG的快速恢复，即终端设备可以通过SN向MN传输用于MCG快速恢复的相关信息，例如指示MCG的链路失败信息。
例如，终端设备通过分裂(split)信令无线承载1(signaling radio bearer，SRB1)或SRB3向SCG上报MCG的链路失败信息(MCG failure information)，并启动T316定时器(timer)，若在T316定时器定时时长内，终端设备收到切换(handover)或者RRC释放(RRCRelease)消息，则fast MCG link recovery成功，否则终端设备发起RRC重建流程。
其中，T316定时器在终端设备发送MCG的链路失败信息时启动，在终端设备收到R RC释放(RRCRelease)消息、主小区的RRC重配置(包含同步重配置)(RRC reconfigu ration with reconfiguration with Sync for the PCell)、从NR切换的命令(Mobility From NR Command)或者启动RRC重建流程(initiating the re-establishment procedure)时，T316停止。
其中，split SRB指的是对SRB1/SRB2的分流，即：对于双连接场景下，终端设备和主基站之间建立SRB1和SRB2，为了保证SRB1/SRB2传输的可靠性，就引入了split SR B的机制，即如果终端设备和主基站之间的链路质量变差，则终端设备和主基站之间的S RB1/SRB2还可以通过辅基站来协助传输，也就是说，主基站将部分信令分流到辅基站上，由辅基站进一步发送给终端设备。
SRB3是SN和终端设备之间直接建立的信令通道，可以用于SN与终端设备交互信令。SRB3的建立和释放在SN添加和变更流程中完成；SRB3重配置在SN修改流程中完成。当SCG释放时，SRB3被释放。
Split SRB由MN在SN添加和变更流程中配置，SN配置部分由SN提供。终端设备可以同时配置split SRB1、split SRB2和SRB3。SRB3和split SRB的SCG分支可以独立配置。
(3)在本申请中的描述中，“至少一个(种、项)”是指一个(种、项)或者多个(种、项)，多个(种、项)是指两个(种、项)或者两个(种、项)以上。“以下至少一项”或其类似表达，是指的这些项中的任意组合，包括单项或复数项的任意组合。例如，a,b,或c中的至少一项，可以表示：a，b，c，a和b，a和c，b和c，或，a和b和c，其中，a,b,c可以是单个，也可以是多个。
本申请的描述中“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A、B可以是单数或者复数。“/”表示“或”，例如a/b表示a或b。
需要说明的是，随着技术的不断发展，本申请实施例的术语有可能发生变化，但都在本申请的保护范围之内。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的通信方法及装置进行详细说明。
图1示出了本申请实施例提供的通信方法适用的一种可能的通信系统的架构，所述通信系统为双连接系统。所述通信系统的架构中可以包括至少一个终端设备和至少两个网络设备，图1中仅以一个终端设备和两个网络设备进行示例示出，图1中所示的终端设备和两个网络设备(MN和SN)建立DC通信。
其中，网络设备可以为具有无线收发功能的设备或可设置于该网络设备的芯片，该网络设备可以是基站等接入网设备。例如，网络设备可以是各类基站，例如演进型基站(evolved NodeB，eNodeB)、第五代(5th generation，5G)移动通信系统中的下一代基站(next generation NodeB，gNB)、第六代(6th generation，6G)移动通信系统中的下一代基站、未来移动通信系统中的基站等。此外，网络设备可以是家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，无线保真(wireless fidelity，Wi-Fi)系统中的接入点(access point，AP)、接入回传一体化(integrated access and backhaul，IAB)、无线中继节点、无线回传节点、传输点(transmission and reception point，TRP或者transmission point，TP)等，还可以为具有基站功能的网络节点，如基带单元(BBU)等。
在一些部署中，如图2所示，基站(如gNB)可以包括集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)。gNB还可以包括射频单元(radio unit，RU)。CU实现gNB的部分功能，DU实现gNB的部分功能。一种示例中，如图2中的(a)所示，CU可以划分为CU控制面(CU-(control panel，CP))和CU用户面(CU-(user panel，UP))。其中CU-CP负责控制面功能，主要包含无线资源控制(radio resource control，RRC)和分组数据汇聚层协议(packet data convergence protocol，PDCP)-C的功能。CU的控制面CU-CP还可以包括一种进一步切分的架构，即把现有的CU-CP进一步切分为CU-CP1和CU-CP2。其中CU-CP1包括各种无线资源管理功能，CU-CP2仅包括RRC功能和PDCP-C功能(即控制面信令在PDCP层的基本功能)。CU-UP负责用户面功能，主要包含服务数据适配协议(service data adaptation protocol，SDAP)和PDCP-U功能。其中CU-CP和CU-UP通过E1接口连接。CU-CP代表CU通过Ng接口和核心网连接，通过F1-C(控制面)和DU连接。CU-UP通过F1-U(用户面)和DU连接。当然还有一种可能的实现是PDCP-C也在CU-UP。另一种示例中，如图2中的(b)所示，CU实现RRC、PDCP、SDAP层的功能。如图2所示，DU实现无线链路控制(radio link control，RLC)、媒体接入控制(media access control，MAC)和物理(physical，PHY)层的功能。可以理解的是，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的设备。此外，CU可以划分为接入网RAN中的网络设备，也可以将CU划分为核心网CN中的网络设备，对此不作限定。
示例性的，多个DU可以共用一个CU。在RAN共享的场景下，一个DU也可以连接多个CU。CU和DU之间可以通过F1接口相连。一个DU可以管理一个或者多个小区，每个小区都有对应的小区标识。
在一些实施例中，除基站由CU和DU组成的情况，也即除CU和DU部署在一起的请情况外，CU和DU在物理上也可以是分离的。也就是说CU和DU可以认为是单独的两个节点。在此种情况下，所述网络设备可以是CU。
所述终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请实施例中，所述终端设备为远端(remote)终端设备，需要被提供中继(relay)服务。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智能穿戴设备(智能眼镜、智能手表、智能耳机等)、智慧家庭(smart home)中的无线终端等等，也可以是能够设置于以上设备的芯片或芯片模组(或芯片系统)等。本申请的实施例对应用场景不做限定。本申请中将具有无线收发功能的终端设备及可设置于前述终端设备的芯片统称为终端设备。以下将UE作为终端设备的举例对本申请提供的技术方案进行说明。
需要说明的是，上述图1所示的通信系统可以是第四代(The 4th Generation，4G)通信系统、第五代(The 5th Generation，5G)通信系统、未来的第六代通信系统和演进的其他通信系统等等，本申请对此不作限定。
Fast MCG link Recovery流程的具体步骤可以如下：
步骤1：MN请求SN支持通过split SRB1或SRB3进行fast MCG link recovery。
其中，SRB3仅在未配置split SRB1时被使用。
步骤2：MN向UE发送包含T316定时器的信息的快速恢复配置(fast recovery configuration)。
步骤3：UE检测到MCG发生RLF，并将MCG链路失败信息保存在RLF报告中。
在MCG第一次发生RLF时，RLF报告中记录连接失败类型是RLF。
步骤4：如果SCG的传输没有被挂起(suspended)，并且SN没有正在进行PScell的变更或增加，UE向SN发送MCG链路失败信息，并启动T316定时器。
其中，MCG链路失败信息可以包括以下信息：MCG/SCG可用测量结果、MCG链路故障类型和非服务小区可用测量结果。
步骤5a：在T316定时器超时前，UE收到SN发送的恢复响应消息，如切换(Handover)消息或RRC释放(RRCRelease)消息，则UE根据恢复响应消息执行切换或者重选；否则执行步骤5b。
其中，UE根据恢复响应消息执行切换时，若发生切换失败(handover failure，HOF)会导致MCG连接失败。由于HOF导致MCG连接失败时，UE可以在RLF报告中记录连接失败类型是HOF。也就是说，在本申请中，RLF报告中，MCG发生RLF的类型(即MCG的连接失败类型)可以包括RLF或者HOF。
在T316定时器超时前，UE收到SN的恢复响应消息，则fast MCG link recovery成功，则UE清除步骤3中记录的RLF报告。UE按照恢复响应执行切换或者重选来进行小区变更，如果小区变更失败或者接入小区后很快失败，则MCG再次发生了连接失败(RLF/HOF)， 重新记录第二次MCG连接失败信息的RLF报告。
步骤5b：UE发起RRC重建。
在T316定时器超时后，UE未收到SN的恢复响应消息，则fast MCG link recovery失败，步骤3中记录的RLF报告保留，UE在RRC重建后，将RLF报告发送给接入的MN。
目前，RLF报告中可以包括如下至少一种信息：
1)失败的主小区标识(failedPcellID)：UE检测到发送RLF的小区信息，或者切换失败的目标小区信息；
2)连接失败类型(connectionFailureType)：RLF或者HOF或者定时器到期(定时器为UE发送测量报告后启动的定时器，比如T312)；
3)先前的主小区标识(previousPCellId)：UE上一次收到切换命令的源小区信息；
4)重建小区标识(reestablishmentCellId)：连接失败后发起重建立的小区信息；
5)连接失败时间(timeConnFailure)：最后一次收到HO命令到连接失败的时间；
6)失败开始时间(timeSinceFailure)：连接失败时开始记录的时间长度，一般指连接失败到上报RLF-report的时间。
7)RLF原因(rlf-Cause)：无线链路失败或者切换失败的原因，如T310定时器超时，随机接入问题(randomAccessProblem)，波束失败恢复失败(beamFailureRecoveryFailure)，先听后说失败(listen before talk failure，lbtFailure)，RLC重传失败过多等。
需要说明的是，上述涉及的小区信息可以包括小区全球标识(cell global identity，CGI)，和/或，物理小区标识(physical cell identity，PCI)与频率(frequency)。此外RLF报告中还可以携带各小区的小区质量，比如检测到MCG链路失败时的失败小区和/或邻区的小区质量。可选的，小区信息还可以包括小区的测量结果。
目前当MCG发生了连接失败，UE会记录RLF报告；当MCG再次发生连接失败，UE清空之前记录的RLF报告，记录最新的RLF报告。
为了减小因网络参数设置不合理而导致的同频切换、异频切换、异系统切换等切换中的切换过早、切换过晚以及乒乓切换等问题，目前，通信系统支持移动鲁棒性优化(mobility robustness optimization，MRO)机制，MRO是网络自优化的一个重要机制，UE发生与移动性相关的异常情况(例如切换失败、在目标小区的无线链路失败等)时，向网络上报发生移动性相关的异常参数，网络设备可以根据UE上报的相关参数进行自主分析、优化网络参数。例如，现有MRO机制可以基于UE反馈的RLF报告进行分析，调整RLF报告相关的网络参数，以针对UE进行移动性优化。然而，目前UE记录的RLF报告没有考虑fast MCG link recovery失败或者fast MCG link recovery成功后又失败等场景，因此，网络设备基于目前UE记录的RLF报告进行网络参数优化时，移动性优化效果不佳。
本申请实施例提出一种通信方法，以使UE确定的RLF报告可以与针对MCG的链路恢复是否成功相关，RLF报告可以涵盖fast MCG link recovery失败或者fast MCG link recovery成功后又失败等场景的参数，从而可以使网络设备可以有针对性地对这些场景涉及的参数进行准确调整，提升移动性优化效果，进而提高后续MCG重新建立连接的成功率，从而，增强终端设备进行双连接或多连接通信的连续性与可靠性，提高通信质量。
基于以上描述，本申请实施例提供的一种通信方法，适用于如图1所示的通信系统。参阅图3所示，该方法的具体流程可以包括：
步骤301：UE分别与第一网络设备以及第二网络设备通信。
具体地，UE与第一网络设备以及第二网络设备进行双连接通信，可以分别从第一网络设备以及第二网络设备获取通信服务。其中，第一网络设备管理第一MCG，所述第二网络设备管理第一SCG。也就是说，第一网络设备是该UE的MN，第二网络设备是该UE的SN。所述第一SCG被配置了MCG链路恢复功能，也即所述第一SCG支持进行MCG快速恢复。
需要说明的是，在本申请中第一SCG支持进行MCG快速恢复可以理解为第一SCG所属的第二网络设备支持MCG快速恢复，即UE通过第一SCG所属的第二网络设备向第一网络设备发送信息以进行MCG快速恢复。在本申请中，仅以第一SCG支持进行MCG快速恢复来说明。
在一种可选的实施方式中，所述第一网络设备向所述第二网络设备发送请求信息，该请求信息用于请求所述第二网络设备管理的第一SCG支持进行MCG快速恢复，所述第二网络设备向所述第一网络设备回复该请求信息的响应信息。这样，所述第一SCG被配置了MCG链路恢复功能，以使在第一MCG发生RLF时UE可以通过第一SCG进行第一MCG的链路恢复。
可选的，所述请求信息可以请求所述第一SCG支持通过split SRB1或SRB3进行MCG快速恢复。
在一种可选的实施方式中，所述第一网络设备可以为所述UE配置第一定时器，以使UE在确定第一MCG发生RLF时，通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后，通过是否在所述第一定时器的预设时长内收到所述第二网络设备发送的响应消息来判断针对第一MCG的链路恢复是否成功。
可选的，所述第一定时器可以为T316定时器等。
步骤302：所述UE确定所述第一MCG发生RLF。
其中，所述UE确定所述第一MCG发生RLF可以理解为所述UE和所述第一MCG之间的连接失败。在所述第一MCG发生RLF的情况下，所述UE不能通过所述第一MCG与所述第一网络设备通信。
步骤303：所述UE向第三网络设备发送第一RLF报告，所述第一RLF报告与针对所述第一MCG的链路恢复是否成功相关。
在不同的情况下，所述第一RLF报告的内容不同。示例性的，下面针对不同情况对第一RLF报告的内容进行说明：
情况a1、当由于UE不进行针对所述第一MCG的链路恢复导致的针对所述第一MCG的链路恢复未成功时，所述第一RLF报告可以包括链路恢复失败原因。
可选的，在情况a1中，所述链路恢复失败原因可以包括以下一项或多项：所述第一SCG被添加、所述第一SCG被变更或所述第一SCG的传输被挂起(SCG transmission suspended)。也就是说，上述链路恢复失败原因导致了针对所述第一MCG的链路恢复未成功。
可选的，所述第一SCG被添加或被变更可以指主辅小区正在被添加或被变更(Pscell change or addition ongoing)。
示例性的，所述链路恢复失败原因可以采用枚举格式，例如Pscell change or addition ongoing，suspended SCG transmission。
在该情况a1中，所述UE基于所述第一SCG被添加或被变更，或者，所述第一SCG 的传输被挂起确定不进行针对所述第一MCG的链路恢复。在这种情况下，由于所述第一SCG被添加或被变更，或者，所述第一SCG的传输被挂起时，第一SCG链路不稳定，导致所述UE不能通过所述第一SCG与所述第二网络设备通信，因此所述UE将不进行针对所述第一MCG的链路恢复。由此，由于未进行针对所述第一MCG的链路恢复，则可以认为针对所述第一MCG的链路恢复未成功。
在该情况a1中，所述第一RLF报告中除了上述链路恢复失败原因外，还可以包括例如上述介绍的RLF报告中包括的七项内容中的至少一项，此处不再重复描述。
情况a2、所述UE基于向所述第二网络设备发送所述第一MCG的RLF信息失败，确定针对所述第一MCG的链路恢复未成功。该情况a2下，所述第一RLF的报告可以包括以下一项或多项：链路恢复失败原因、所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息、第一时间信息或所述第一SCG的RLF信息，其中，所述第一时间信息指示第一定时器的第一运行时间，所述第一运行时间大于或者等于所述第一定时器的预设时长，所述第一运行时间为所述UE通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后到发起RRC重建流程的时长。
其中，所述第一定时器为步骤301中描述的所述第一网络设备为所述UE配置的第一定时器。在后面的描述中涉及的第一定时器与步骤301中的第一定时器含义相同，不再一一说明。
可选的，所述链路恢复失败原因与所述UE和所述第一SCG的连接出现问题相关，从而导致所述UE不能将所述第一MCG的RLF信息通过所述第一SCG发送给所述第二网络设备。例如，所述链路恢复失败原因可能是因为所述第一SCG发生RLF的原因导致的，例如，所述链路恢复失败原因可以包括以下一项或多项：所述第一SCG的波束失败后波束恢复的失败(beamFailureRecoveryFailure)导致的针对所述第一MCG的链路恢复失败、针对所述第一SCG的随机接入失败(randomAccessProblem)或针对所述第一SCG的无线链路控制(radio link control，RLC)重传达到最大次数(rlc-MaxNumRetx)。也可以理解为，所述第一SCG的波束失败后波束恢复的失败、针对所述第一SCG的随机接入失败或针对所述第一SCG的无线链路控制重传达到最大次数导致所述第一SCG发生RLF，进而导致第一MCG链路恢复失败。
其中，基于波束失败恢复(beam failure recovery，BFR)技术，所述第一SCG的波束失败后，UE针对所述第一SCG的波束失败会发起波束恢复请求流程，波束成功恢复则表示波束恢复成功，波束未恢复则表示波束恢复失败。所述第一SCG的波束失败后波束恢复的失败，是指所述第一SCG的波束失败后，UE针对所述第一SCG的波束失败发起波束恢复请求流程后，波束未恢复。
示例性的，所述第一SCG的RLF信息可以包括以下一项或多项：所述第一SCG的标识信息、所述第一SCG发生RLF的原因或所述第一SCG变更失败的原因(rlf-Cause)等。例如，所述第一SCG的标识信息可以包括所述UE检测到RLF的辅主小区的标识信息或变更失败的辅主小区的标识信息(failedPSCellId)。可选的，所述第一SCG发生RLF的原因为上述描述的任意一项导致所述第一SCG发生RLF的原因，例如针对第一SCG的随机接入失败。
在该情况a2中，所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息，可以指示所述第一MCG的RLF信息未成功通过所述第一SCG 发送给所述第二网络设备。可选的，所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息可以通过发送成功标识信息来指示，例如可以通过发送成功标识信息的取值表示真或假(true or false)，来指示是否成功发送了所述第一MCG的RLF信息，即“真”指示成功发送，“假”指示未成功发送。即在该情况a2中，成功标识信息取值为“假”。例如，所述成功标识的信息可以包括一个比特，该比特的取值为“1”可以表示所述成功标识信息的取值为“真”，该比特的取值为“0”可以表示所述成功标识信息的取值为“假”。
情况a3、所述UE通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息；所述UE基于在第一预设时长内没有接收到针对所述第一MCG的RLF信息的响应消息，即确定针对所述第一MCG的链路恢复未成功。该情况a3下，所述第一RLF的报告的内容与上述情况a2中描述的第一RLF报告的内容类似，可以相互参见，此处不再重复描述。
其中，所述第一预设时长可以为所述第一定时器的预设时长。
需要说明的是，与情况a2不同的是，第一RLF报告中包括的所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息，可以指示所述第一MCG的RLF信息成功通过所述第一SCG发送给所述第二网络设备。示例性的，若该指示信息是前述成功标识信息，在该情况a3中，成功标识信息取值为真。
示例性的，在上述情况a2和情况a3中，所述第一RLF报告中还可以包括例如上述介绍的RLF报告中可以包括的七项内容中的至少一项，此处不再重复描述。
上述情况a1-a3是当针对所述第一MCG的链路恢复未成功时的场景，当针对所述第一MCG的链路恢复成功时，所述UE还确定是否从所述第一MCG成功切换到第二MCG，也即所述UE进行MN切换是否切换成功，或者说，UE从所述第一网络设备切换到目标网络设备(即目标MN)是否成功，其中第二MCG是该目标网络设备管理的MCG；进而，所述UE可以根据是否从所述第一MCG成功切换到所述第二MCG，确定所述第一RLF报告的内容。
可选的，当所述UE在所述第一定时器的预设时长内收到所述第二网络设备发送的响应消息确定针对第一MCG的链路恢复成功。例如，在所述第一定时器的预设时长内，当所述UE通过所述第一SCG从所述第二网络设备接收到切换命令或者RRC释放消息时，则表示针对所述第一MCG的链路恢复成功。可选的，所述切换命令可以是以下任意一项：从NR切换的命令(MobilityFromNRCommand)、从演进通用陆地无线接入(evolved universal terrestrial radio access，EUTRA)切换的命令(MobilityFromEUTRACommand)、同步重配置(Reconfiguration with sync)。
一种可选的示例，当所述UE从所述第一MCG切换到所述第二MCG时发生切换失败，则表示所述UE从所述第一MCG未成功切换到所述第二MCG。
一种可选的示例，所述UE确定从所述第一MCG未成功切换到所述第二MCG，可以包括：所述UE基于当所述UE切换到所述第二MCG后，在第二预设时长内所述第二MCG发生RLF，确定未成功从所述第一MCG切换到所述第二MCG。即，所述UE切换到所述第二MCG后很快第二MCG发生RLF失败，则表示所述UE从所述第一MCG未成功切换到所述第二MCG。
其中，所述第二MCG发生RLF可以理解为所述UE和所述第二MCG之间的连接失 败。
示例性的，基于UE是否从所述第一MCG成功切换到所述第二MCG，所述RLF报告可以为以下情况a4和情况a5所示：
情况a4、当UE未成功从所述第一MCG切换到所述第二MCG时，所述第一RLF报告可以包括所述第一MCG的RLF信息，以及，所述第二MCG的切换失败信息或所述第二MCG的RLF信息。
例如，在该情况a4中，所述第一RLF报告的内容可以包括第一次(first)MCG发生RLF(也可以称为第一次失败)的相关信息和最后一次(last)MCG发生RLF(也可称为第二次失败)的相关信息。其中，第一次MCG发生RLF是指所述第一MCG发生RLF，最后一次MCG发生RLF是指从所述第一MCG切换到所述第二MCG时的切换失败或所述第二MCG发生RLF。例如，所述第一RLF报告的内容可以包括以下一项或多项：(1)first failedCellId：即第一次失败的小区标识，例如第一MCG的Pcell的标识A1；(2)first connectionFailureType：即第一次失败的连接失败类型，例如连接失败类型为RLF；(3)first previousCellId：即第一次失败时，UE上一次收到切换命令的源小区标识；(4)last failedCellId：即最后一次失败的小区标识，例如第二MCG的Pcell的标识A2；(5)last connectionFailureType：即最后一次失败的连接失败类型，例如连接失败类型为HOF或RLF；(6)last previousCellId：即最后一次失败时，UE上一次收到切换命令的源小区标识，例如第一SCG的PScell的标识B1。
其中，上述第(1)-(3)项属于所述第一MCG的RLF信息，第(4)-(6)项属于所述第二MCG的切换失败信息或所述第二MCG的RLF信息。其中的A1、B1、A2仅为小区标识的举例，不作为对本申请的限定。
在该情况a4中，在UE可以不清除之前第一MCG发生RLF时记录的RLF报告。
可选的，所述第一RLF报告中还可以包括第二时间信息，所述第二时间信息指示第一定时器的第二运行时间，所述第二运行时间小于所述第一定时器的预设时长，所述第二运行时间为所述UE通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后收到所述第二网络设备发送的响应消息的时长。其中，所述第二运行时间小于所述第一定时器的预设时长表示所述第一定时器启动后在所述第一定时器超时前停止。
情况a5、当UE从所述第一MCG成功切换到所述第二MCG时，所述第一RLF报告可以包括所述第一MCG的RLF信息，以及以下一项或多项：所述第二MCG的标识信息或第二时间信息，所述第二时间信息可以参见情况a4中关于第二时间信息的描述。其中，第一MCG的RLF信息可以参见前述描述，此处不再赘述。
可选的，所述第二MCG的标识信息的记录在所述第一RLF中的方式可以如下：
方式1：复用重建小区标识(reestablishmentCellId)字段和/或新增重建小区标识字段(reestablishmentCellIdtype)指示记录的重建小区或切换目标小区或重选小区的小区标识，例如切换目标小区的小区标识A2。
方式2：新增切换目标小区字段和/或重选小区字段来记录小区标识，例如新增切换目标小区字段记录切换目标小区的小区标识A2。
在该情况a5中，在UE可以不清除之前第一MCG发生RLF时记录的RLF报告。
上述五种情况下的第一RLF报告可以涵盖fast MCG link recovery失败或者fast MCG link recovery成功后又失败等多种场景中和第一MCG链路恢复相关的参数，从而后续可以 使网络设备对MCG链路恢复相关的网络参数进行准确调整，提升移动性优化效果，包括：提高后续MCG链路恢复的成功率，或者提高UE从第一MCG变更到其他MCG的成功率。例如，在上述情况a1中网络设备可以基于第一RLF报告进行链路失败原因分析后可以确定第一MCG的链路恢复失败并不是因为针对一MCG的链路恢复配置的相关参数不合理，此时可以不进行参数优化。又例如，在上述情况a2和a3中网络设备可以优化第一SCG的配置参数，以使后续第一SCG减少发生RLF的情况，从而可以使UE与第一SCG所属的第二网络设备成功通信。又例如，在上述情况a4中，网络设备可以调整UE需要切换到的MCG，也即令UE从第一MCG切换到第二MCG以外的其他更合适的MCG，提高切换成功率。又例如，在上述情况a5中，网络设备基于第一RLF报告可以进行第一MCG切换到第二MCG时的相关参数的优化，令UE从第一MCG较快地切换到第二MCG，以减少MCG服务中断时间。
步骤304：所述第三网络设备根据所述第一RLF报告调整所述第一RLF报告相关的网络参数。
其中，调整所述第一RLF报告相关的网络参数的相关描述可以参见步骤303中的相关描述，此处不再赘述。
可选地，第三网络设备可以将调整后的网络参数通过网络设备之间的接口发送给其他网络设备，使得其他网络设备与UE之间进行MCG链路恢复时可以使用经过调整的网络参数，提高MCG链路恢复的成功率。例如，第三网络设备作为UE切换过程中的目标主基站，可以将调整后的网络参数发送给源主基站。
在一种可选的实施方式中，在上述情况a1-a4下，UE可以发起RRC重建，以接入网络设备，进而UE向第三网络设备发送第一RLF报告。
在另一种可选的实施方式中，在上述情况a3下，UE可以切换或者重选网络设备，以接入网络设备，进而UE向第三网络设备发送第一RLF报告。
其中，所述第三网络设备可以是所述第一网络设备，也可以是所述第一网络设备以外的网络设备，例如，UE从第一网络设备切换到第三网络设备，即第三网络设备是切换场景中的目标网络设备，本申请对此不作限定。需要说明的是，当第二网络设备管理的第一SCG发生RLF后，第三网络设备也可以是第二网络设备。
可选的，所述第三网络设备从UE接收所述第一RLF报告，可以是所述第三网络设备通过其他网络设备从所述UE接收所述第一RLF报告，其他网络设备为所述UE当前接入的网络设备。也就是说，所述UE先将所述第一RLF报告发送给其他网络设备(即UE当前接入的网络设备)，然后其他网络设备将第一RLF报告转发给所述第三网络设备。在这种情况下，第三网络设备不是所述UE当前接入的网络设备。
可选的，所述第三网络设备可以是所述UE当前接入的网络设备，此时所述第三网络设备可以直接从所述UE接收所述第一RLF报告。
示例性的，当所述第三网络设备为所述第一网络设备时，所述第三网络设备可以根据所述第一RLF报告调整所述第一RLF报告相关的网络参数。此时当所述仍然接入第一网络设备时，第一网络设备直接从UE获得第一RLF报告；或者，当UE已经从第一网络设备切换到其他网络设备，第一网络设备可以从其他网络设备获得所述第一RLF报告。
示例性地，所述第三网络设备不为所述第一网络设备时，所述第三网络设备可以根据所述第一RLF报告调整所述第一RLF报告相关的网络参数，并将调整的所述网络参数的 相关信息发送给所述第一网络设备和/或所述第二网络设备。
采用本申请实施例提供的方法，UE可以上报与针对MCG的链路恢复是否成功相关的RLF报告，从而提升移动性优化效果，进而提高后续MCG重新建立连接的成功率，从而，增强终端设备进行双连接或多连接通信的连续性与可靠性，提高通信质量。
基于以上实施例，下面通过具体的示例对本申请实施例提供的通信方法进行详细说明。在以下的事例中，以UE、第一网络设备为源MN(source MN，S-MN)，即S-MN管理第一MCG，第二网络设备为SN，即SN管理第一SCG，第三网络设备为目标MN(target MN，T-MN)，第一定时器为T316定时器为例进行说明。
图4示出了一种通信方法的示例，在该示例中，UE在被配置T316定时器后，第一MCG发生RLF，UE未发起针对第一MCG的链路恢复流程(即未发起fast MCG link recovery procedure)，RLF报告新增记录链路恢复失败原因。示例性的，该示例的具体流程可以包括：
步骤401：S-MN向SN发送请求信息，该请求信息请求SN支持通过split SRB1或SRB3进行MCG快速恢复。
步骤402：S-MN为UE配置T316定时器。
步骤403：UE确定第一MCG发生RLF，且检测到第一SCG被添加或被变更，或者所述第一SCG的传输被挂起，则UE确定不进行针对所述第一MCG的链路恢复。
也即，UE无法发起fast MCG link recovery procedure。
具体的，如果UE检测到第一MCG发生RLF，UE发起fast MCG link recovery procedure需要通过第一SCG向S-MN指示第一MCG的RLF信息，在步骤403的情况下，第一SCG与UE的传输已经中断，UE感知到这种情况时，则不发起fast MCG link recovery procedure。
步骤404：UE发起RRC重建流程，接入T-MN。
步骤405：UE向T-MN发送第一RLF报告。
可选的，之后T-MN可以将所述第一RLF报告发送给S-MN，以使S-MN基于所述第一RLF报告调整相关网络参数。
其中，所述第一RLF报告可以参见上述如3所示的实施例中情况a1中的第一RLF报告，此处不再赘述。
上述示例考虑了UE未发起fastMCG link recovery procedure的场景，因此基于该场景对RLF报告进行增强，以使网络设备对fast MCG link recovery失败原因进行分析，可以得知fast MCG link recovery失败并非针对fast MCG link recovery的配置参数不合理导致的，而是SCG的移动性相关参数配置不合理导致的。
图5示出了又一种通信方法的示例，在该示例中，UE在被配置T316定时器后，第一MCG发生RLF，UE发起针对第一MCG的链路恢复流程中(即发起fast MCG link recovery procedure)中发生失败，RLF报告新增记录链路恢复失败的过程信息。示例性的，该示例的具体流程可以包括：
步骤501：S-MN向SN发送请求信息，该请求信息请求SN支持通过split SRB1或SRB3进行MCG快速恢复。
步骤502：S-MN为UE配置T316定时器。
步骤503：UE确定第一MCG发生RLF后，发起针对第一MCG的链路恢复的流程，但UE通过第一SCG向SN发送第一MCG的RLF信息失败。
可选的，UE通过第一SCG向SN发送第一MCG的RLF信息失败的原因可能是第一SCG发生RLF，或者在第一SCG去激活时，UE随机接入第一SCG失败。
步骤504：UE发起RRC重建流程，接入T-MN。
步骤505：UE向T-MN发送第一RLF报告。
可选的，之后T-MN可以将所述第一RLF报告发送给S-MN，以使S-MN基于所述第一RLF报告调整相关网络参数。
其中，所述第一RLF报告可以参见上述如3所示的实施例中情况a2中的第一RLF报告，此处不再赘述。
上述示例考虑了UE发起fastMCG link recovery procedure中失败的场景，因此基于该场景对RLF报告进行增强，以使网络设备可以优化fast MCG link recovery流程，例如可以优化SCG的配置参数，由于该SCG用于发送第一MCG的RLF信息，对该SCG的配置参数优化后，可以使后续SCG减少发生RLF的情况，从而可以使UE与SN成功通信。
图6示出了又一种通信方法的示例，在该示例中，UE在被配置T316定时器后，第一MCG发生RLF，UE发起针对第一MCG的链路恢复流程中(即发起fast MCG link recovery procedure)中发生失败，RLF报告新增记录链路恢复失败的过程信息。示例性的，该示例的具体流程可以包括：
步骤601：S-MN向SN发送请求信息，该请求信息请求SN支持通过split SRB1或SRB3进行MCG快速恢复。
步骤602：S-MN为UE配置T316定时器。
步骤603：UE确定第一MCG发生RLF后，发起针对第一MCG的链路恢复的流程，UE通过第一SCG向SN发送第一MCG的RLF信息。
步骤604：UE确定未收到针对所述第一MCG的RLF信息的响应消息。
其中，SN在收到该第一MCG的RLF信息后，第一SCG发生RLF，导致UE在T316定时器的预设时长内未收到针对所述第一MCG的RLF信息的响应消息。
步骤605：UE发起RRC重建流程，接入T-MN。
步骤606：UE向T-MN发送第一RLF报告。
可选的，之后T-MN可以将所述第一RLF报告发送给S-MN，以使S-MN基于所述第一RLF报告调整相关网络参数。
其中，所述第一RLF报告可以参见上述如3所示的实施例中情况a3中的第一RLF报告，此处不再赘述。
上述示例考虑了UE发起fast MCG link recovery procedure中失败的场景，因此基于该场景对RLF报告进行增强，以使网络设备可以优化fast MCG link recovery流程，例如可以优化SCG的配置参数，由于该SCG用于发送第一MCG的RLF信息，对该SCG的配置参数优化后，可以使后续SCG减少发生RLF的情况，从而可以使UE与SCG所述的SN成功通信。
图7示出了又一种通信方法的示例，在该示例中，UE在被配置T316定时器后，第一MCG发生RLF，UE发起针对第一MCG的链路恢复流程成功(即发起fast MCG link recovery procedure成功)，但是UE在第二MCG发生RLF，RLF报告新增记录第二MCG连接失败信息。在该示例中，第二MCG不是T-MN管理的MCG，第二MCG是在针对第一MCG的链路恢复流程成功时，UE需要切换到的MN管理的MCG。而在该示例中，由 于UE未成功切换到第二MCG，进而UE通过RRC重建流程接入T-MN。示例性的，该示例的具体流程可以包括：
步骤701：S-MN向SN发送请求信息，该请求信息请求SN支持通过split SRB1或SRB3进行MCG快速恢复。
步骤702：S-MN为UE配置T316定时器。
步骤703：UE确定第一MCG发生RLF后，发起针对第一MCG的链路恢复的流程，UE通过第一SCG向SN发送第一MCG的RLF信息。
步骤704：UE通过第一SCG从SN接收到针对所述第一MCG的RLF信息的响应消息，指示UE从第一MCG切换到第二MCG。
例如，针对所述第一MCG的RLF信息的响应消息可以是切换命令。
步骤705：UE确定从第一MCG未成功切换到所述第二MCG。
示例性的，UE从第一MCG未成功切换到所述第二MCG具体可以参见图3所示的实施例中涉及的UE从所述第一MCG未成功切换到所述第二MCG的情况，此处不再赘述。
步骤706：UE发起RRC重建流程，接入T-MN。
步骤707：UE向T-MN发送第一RLF报告。
可选的，之后T-MN可以将所述第一RLF报告发送给S-MN，以使S-MN基于所述第一RLF报告调整相关网络参数。
其中，所述第一RLF报告可以参见上述如3所示的实施例中情况a4中的第一RLF报告，此处不再赘述。
上述示例考虑了UE发起fast MCG link recovery procedure成功后，在第二MCG发生RLF失败的场景，因此基于该场景对RLF报告进行增强，以使网络设备可以优化fast MCG link recovery流程的后续流程，例如可以调整UE需要切换到的MCG，也即令终端设备可以从第一MCG切换到第二MCG以外的其他更合适的MCG，提高切换成功率。
图8示出了又一种通信方法的示例，在该示例中，UE在被配置T316定时器后，第一MCG发生RLF，UE发起针对第一MCG的链路恢复流程成功(即发起fast MCG link recovery procedure成功)，RLF报告新增记录切换后第二MCG的相关信息。示例性的，该示例的具体流程可以包括：
步骤801：S-MN向SN发送请求信息，该请求信息请求SN支持通过split SRB1或SRB3进行MCG快速恢复。
步骤802：S-MN为UE配置T316定时器。
步骤803：UE确定第一MCG发生RLF后，发起针对第一MCG的链路恢复的流程，UE通过第一SCG向SN发送第一MCG的RLF信息。
步骤804：UE通过第一SCG从SN接收到针对所述第一MCG的RLF信息的响应消息，指示UE从第一MCG切换到第二MCG。
例如，针对所述第一MCG的RLF信息的响应消息可以是切换命令(MobilityFromNRCommand、MobilityFromEUTRACommand、Reconfiguration with sync)，或者也可以是RRC释放消息。
步骤805：UE确定从第一MCG成功切换到所述第二MCG。
步骤806：UE通过第二MCG向T-MN发送第一RLF报告。
在该示例中，T-MN是管理所述第二MCG的MN。
可选的，之后T-MN可以将所述第一RLF报告发送给S-MN，以使S-MN基于所述第一RLF报告调整相关网络参数。
其中，所述第一RLF报告可以参见上述如3所示的实施例中情况a5中的第一RLF报告，此处不再赘述。
上述示例考虑了UE发起fast MCG link recovery过程成功后，并切换到第二MCG的场景，因此基于该场景对RLF报告进行增强，以使网络设备可以优化fast MCG link recovery流程，例如网络设备可以基于RLF报告进行第一MCG切换到第二MCG的相关参数的优化，令UE从第一MCG较快地切换到第二MCG，减少MCG服务中断时间。
基于以上实施例，本申请实施例还提供了一种通信装置，参阅图9所示，通信装置900可以包括收发单元901和处理单元902。其中，所述收发单元901用于所述通信装置900接收信息(消息或数据)或发送信息(消息或数据)，所述处理单元902用于对所述通信装置900的动作进行控制管理。所述处理单元902还可以控制所述收发单元901执行的步骤。
示例性地，该通信装置900具体可以是上述实施例中的网络设备(例如第一网络设备、第二网络设备或第三网络设备等)、所述网络设备中的处理器，或者芯片，或者芯片系统，或者是一个功能模块等；或者，该通信装置900具体可以是上述实施例中的终端设备(例如UE)、所述终端设备的处理器，或者芯片，或者芯片系统，或者是一个功能模块等。
在一个实施例中，所述通信装置900用于实现上述图3-图8所述的实施例中终端设备(例如UE)的功能时，可以包括：所述收发单元901可以用于分别与第一网络设备以及第二网络设备通信，其中，所述第一网络设备管理第一主小区组MCG，所述第二网络设备管理第一辅小区组SCG，所述第一SCG被配置了MCG链路恢复功能；所述处理单元902可以用于确定所述第一MCG发生无线链路失败RLF；所述收发单元901还可以用于向第三网络设备发送第一RLF报告，所述第一RLF报告与针对所述第一MCG的链路恢复是否成功相关。
在一种可选的实施方式中，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告包括链路恢复失败原因。
示例性的，所述链路恢复失败原因可以包括以下一项或多项：所述第一SCG被添加、所述第一SCG被变更或所述第一SCG的传输被挂起。
可选的，所述处理单元902还可以用于基于所述第一SCG被添加或被变更，或者，所述第一SCG的传输被挂起确定不进行针对所述第一MCG的链路恢复。
在另一种可选的实施方式中，所述处理单元902还可以用于基于向所述第二网络设备发送所述第一MCG的RLF信息失败，确定针对所述第一MCG的链路恢复未成功。
在又一种可选的实施方式中，所述收发单元901还可以用于通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息；所述处理单元902还可以用于基于所述收发单元901在第一预设时长内没有接收到针对所述第一MCG的RLF信息的响应消息，确定针对所述第一MCG的链路恢复未成功。
示例性的，所述第一RLF报告可以包括以下一项或多项：链路恢复失败原因、所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息、第一时间信息或所述第一SCG的RLF信息，其中，所述第一时间信息指示第一定时器的第一运行时间，所述第一运行时间大于或者等于所述第一定时器的预设时长，所述第一运 行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后到发起RRC重建流程的时长。
可选的，所述链路恢复失败原因包括以下一项或多项：所述第一SCG的波束失败后波束恢复的失败导致的针对所述第一MCG的链路恢复失败、针对所述第一SCG的随机接入失败或针对所述第一SCG的无线链路控制RLC重传达到最大次数。
可选的，所述第一SCG的RLF信息包括以下一项或多项：所述第一SCG的标识信息、所述第一SCG发生RLF的原因或所述第一SCG变更失败的原因。
在一种可能的方式中，当针对所述第一MCG的链路恢复成功时，所述处理单元902还可以用于确定是否从所述第一MCG成功切换到第二MCG；以及根据是否从所述第一MCG成功切换到所述第二MCG，确定所述第一RLF报告。
一种示例中，当从所述第一MCG未成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及，所述第二MCG的切换失败信息或所述第二MCG的RLF信息。
可选的，所述处理单元902在确定从所述第一MCG未成功切换到所述第二MCG时，可以用于：基于当所述终端设备切换到所述第二MCG后，在第二预设时长内所述第二MCG发生RLF，确定未成功从所述第一MCG切换到所述第二MCG。
另一种示例中，当从所述第一MCG成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及以下一项或多项：所述第二MCG的标识信息或第二时间信息，所述第二时间信息指示第一定时器的第二运行时间，所述第二运行时间小于所述第一定时器的预设时长，所述第二运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后收到所述第二网络设备发送的响应消息的时长。
在一个实施例中，所述通信装置900用于实现上述图3-图8所述的实施例中第三网络设备的功能时，可以包括：所述收发单元901可以用于从终端设备接收第一RLF报告，所述第一RLF报告与在第一主小区组MCG发送RLF后针对所述第一MCG的链路恢复是否成功相关；所述处理单元902可以用于根据所述第一RLF报告调整所述第一RLF报告相关的网络参数。其中，所述终端设备分别与第一网络设备以及第二网络设备通信，其中，所述第一网络设备管理第一主小区组MCG，所述第二网络设备管理第一辅小区组SCG，所述第一SCG被配置了MCG链路恢复功能。
在一种可选的实施方式中，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告包括链路恢复失败原因。
示例性的，所述链路恢复失败原因包括以下一项或多项：所述第一SCG被添加、所述第一SCG被变更或所述第一SCG的传输被挂起。
在另一种可选的实施方式中，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告包括以下一项或多项：链路恢复失败原因、所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息、第一时间信息或所述第一SCG的RLF信息，其中，所述第一时间信息指示第一定时器的第一运行时间，所述第一运行时间大于或者等于所述第一定时器的预设时长，所述第一运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后到发起RRC重建流程的时长。
可选的，所述链路恢复失败原因包括以下一项或多项：所述第一SCG的波束失败后波束恢复的失败导致的针对所述第一MCG的链路恢复失败、针对所述第一SCG的随机接入失败或针对所述第一SCG的无线链路控制RLC重传达到最大次数。
可选的，所述第一SCG的RLF信息包括以下一项或多项：所述第一SCG的标识信息、所述第一SCG发生RLF的原因或所述第一SCG变更失败的原因。
在一种可能的方式中，当针对所述第一MCG的链路恢复成功时，所述第一RLF报告还与所述终端设备是否从所述第一MCG成功切换到第二MCG相关。
一种示例中，当从所述第一MCG未成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及，第二MCG的切换失败信息或所述第二MCG的RLF信息。
又一种示例中，当从所述第一MCG成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及以下一项或多项：所述第二MCG的标识信息或第二时间信息，所述第二时间信息指示第一定时器的第二运行时间，所述第二运行时间小于所述第一定时器的预设时长，所述第二运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后收到所述第二网络设备发送的响应消息的时长。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例还提供了一种通信装置，参阅图10所示，通信装置1000可以包括收发器1001和处理器1002。可选的，所述通信装置1000中还可以包括存储器1003。其中，所述存储器1003可以设置于所述通信装置1000内部，还可以设置于所述通信装置1000外部。其中，所述处理器1002可以控制所述收发器1001接收和发送信息、消息或数据等。
具体地，所述处理器1002可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器1002还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
其中，所述收发器1001、所述处理器1002和所述存储器1003之间相互连接。可选的，所述收发器1001、所述处理器1002和所述存储器1003通过总线1004相互连接；所述总线1004可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一种可选的实施方式中，所述存储器1003，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1003可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器1002执行所述存储器1003所存放的应用程序，实现上述功能，从而实现通信装置1000的功能。
示例性地，该通信装置1000可以是上述实施例中的网络设备(第一网络设备、第二网络设备或第三网络设备)；还可以是上述实施例中的终端设备。
在一个实施例中，所述通信装置1000在实现图3-图8所示的实施例中终端设备的功能时，收发器1001可以实现图3-图8所示的实施例中的由终端设备执行的收发操作；处理器1002可以实现图3-图8所示的实施例中由终端设备执行的除收发操作以外的其他操作。具体的相关具体描述可以参见上述图3-图8所示的实施例中的相关描述，此处不再详细介绍。
在一个实施例中，所述通信装置1000在实现图3-图8所示的实施例中第三网络设备的功能时，收发器1001可以实现图3-图8所示的实施例中的由第三网络设备执行的收发操作；处理器1002可以实现图3-图8所示的实施例中由第三网络设备执行的除收发操作以外的其他操作。具体的相关具体描述可以参见上述图3-图8所示的实施例中的相关描述，此处不再详细介绍。
基于以上实施例，本申请实施例提供了一种通信系统，该通信系统可以包括上述实施例涉及的终端设备、第一网络设备、第二网络设备和第三网络设备等。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的通信方法。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的通信方法。
本申请实施例还提供一种芯片，包括处理器，所述处理器与存储器耦合，用于调用所述存储器中的程序使得所述芯片实现上述方法实施例提供的通信方法。
本申请实施例还提供一种芯片，所述芯片与存储器耦合，所述芯片用于实现上述方法实施例提供的通信方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或 方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
本申请的各个实施例中的内容可以相互参考，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的，本申请实施例中，终端和/或网络设备可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例中，还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。

Claims (33)

  1. 一种通信方法，其特征在于，包括：
    终端设备分别与第一网络设备以及第二网络设备通信，其中，所述第一网络设备管理第一主小区组MCG，所述第二网络设备管理第一辅小区组SCG，所述第一SCG被配置了MCG链路恢复功能；
    所述终端设备确定所述第一MCG发生无线链路失败RLF；
    所述终端设备向第三网络设备发送第一RLF报告，所述第一RLF报告与针对所述第一MCG的链路恢复是否成功相关。
  2. 如权利要求1所述的方法，其特征在于，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告包括链路恢复失败原因。
  3. 如权利要求2所述的方法，其特征在于，所述链路恢复失败原因包括以下一项或多项：所述第一SCG被添加、所述第一SCG被变更或所述第一SCG的传输被挂起。
  4. 如权利要求2或3所述的方法，其特征在于，所述方法还包括：所述终端设备基于所述第一SCG被添加或被变更，或者，所述第一SCG的传输被挂起确定不进行针对所述第一MCG的链路恢复。
  5. 如权利要求1所述的方法，其特征在于，所述方法还包括：所述终端设备基于向所述第二网络设备发送所述第一MCG的RLF信息失败，确定针对所述第一MCG的链路恢复未成功。
  6. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息；
    所述终端设备基于在第一预设时长内没有接收到针对所述第一MCG的RLF信息的响应消息，确定针对所述第一MCG的链路恢复未成功。
  7. 如权利要求5或6所述的方法，其特征在于，所述第一RLF报告包括以下一项或多项：链路恢复失败原因、所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息、第一时间信息或所述第一SCG的RLF信息，其中，所述第一时间信息指示第一定时器的第一运行时间，所述第一运行时间大于或者等于所述第一定时器的预设时长，所述第一运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后到发起无线资源控制RRC重建流程的时长。
  8. 如权利要求7所述的方法，其特征在于，所述链路恢复失败原因包括以下一项或多项：所述第一SCG的波束失败后波束恢复的失败导致的针对所述第一MCG的链路恢复失败、针对所述第一SCG的随机接入失败或针对所述第一SCG的无线链路控制RLC重传达到最大次数。
  9. 如权利要求7所述的方法，其特征在于，所述第一SCG的RLF信息包括以下一项或多项：所述第一SCG的标识信息、所述第一SCG发生RLF的原因或所述第一SCG变更失败的原因。
  10. 如权利要求1所述的方法，其特征在于，当针对所述第一MCG的链路恢复成功时，所述方法还包括：
    所述终端设备确定是否从所述第一MCG成功切换到第二MCG；
    所述终端设备根据是否从所述第一MCG成功切换到所述第二MCG，确定所述第一RLF报告。
  11. 如权利要求10所述的方法，其特征在于，当从所述第一MCG未成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及，所述第二MCG的切换失败信息或所述第二MCG的RLF信息。
  12. 如权利要求10或11所述的方法，其特征在于，所述终端设备确定从所述第一MCG未成功切换到所述第二MCG，包括：
    所述终端设备基于当所述终端设备切换到所述第二MCG后，在第二预设时长内所述第二MCG发生RLF，确定未成功从所述第一MCG切换到所述第二MCG。
  13. 如权利要求10所述的方法，其特征在于，当从所述第一MCG成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及以下一项或多项：所述第二MCG的标识信息或第二时间信息，所述第二时间信息指示第一定时器的第二运行时间，所述第二运行时间小于所述第一定时器的预设时长，所述第二运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后收到所述第二网络设备发送的响应消息的时长。
  14. 如权利要求1-13任一项所述的方法，其特征在于，所述第三网络设备是所述第一网络设备或所述第二网络设备。
  15. 如权利要求1-13任一项所述的方法，其特征在于，当所述第二网络设备管理的所述第一SCG发生RLF后，所述第三网络设备是所述第二网络设备。
  16. 一种通信方法，其特征在于，包括：
    第三网络设备从终端设备接收第一RLF报告，所述第一RLF报告与在第一主小区组MCG发送RLF后针对所述第一MCG的链路恢复是否成功相关；其中，所述终端设备分别与第一网络设备以及第二网络设备通信，其中，所述第一网络设备管理第一主小区组MCG，所述第二网络设备管理第一辅小区组SCG，所述第一SCG被配置了MCG链路恢复功能；
    所述第三网络设备根据所述第一RLF报告调整所述第一RLF报告相关的网络参数。
  17. 如权利要求16所述的方法，其特征在于，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告包括链路恢复失败原因。
  18. 如权利要求17所述的方法，其特征在于，所述链路恢复失败原因包括以下一项或多项：所述第一SCG被添加、所述第一SCG被变更或所述第一SCG的传输被挂起。
  19. 如权利要求16所述的方法，其特征在于，当针对所述第一MCG的链路恢复未成功时，所述第一RLF报告包括以下一项或多项：链路恢复失败原因、所述第一MCG的RLF信息是否成功通过所述第一SCG发送给所述第二网络设备的指示信息、第一时间信息或所述第一SCG的RLF信息，其中，所述第一时间信息指示第一定时器的第一运行时间，所述第一运行时间大于或者等于所述第一定时器的预设时长，所述第一运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后到发起无线资源控制RRC重建流程的时长。
  20. 如权利要求19所述的方法，其特征在于，所述链路恢复失败原因包括以下一项或多项：所述第一SCG的波束失败后波束恢复的失败导致的针对所述第一MCG的链路恢复失败、针对所述第一SCG的随机接入失败或针对所述第一SCG的无线链路控制RLC重传 达到最大次数。
  21. 如权利要求19所述的方法，其特征在于，所述第一SCG的RLF信息包括以下一项或多项：所述第一SCG的标识信息、所述第一SCG发生RLF的原因或所述第一SCG变更失败的原因。
  22. 如权利要求16所述的方法，其特征在于，当针对所述第一MCG的链路恢复成功时，所述第一RLF报告还与所述终端设备是否从所述第一MCG成功切换到第二MCG相关。
  23. 如权利要求22所述的方法，其特征在于，当从所述第一MCG未成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及，第二MCG的切换失败信息或所述第二MCG的RLF信息。
  24. 如权利要求22所述的方法，其特征在于，当从所述第一MCG成功切换到所述第二MCG时，所述第一RLF报告包括所述第一MCG的RLF信息，以及以下一项或多项：所述第二MCG的标识信息或第二时间信息，所述第二时间信息指示第一定时器的第二运行时间，所述第二运行时间小于所述第一定时器的预设时长，所述第二运行时间为所述终端设备通过所述第一SCG向所述第二网络设备发送所述第一MCG的RLF信息后收到所述第二网络设备发送的响应消息的时长。
  25. 如权利要求16-24任一项所述的方法，其特征在于，所述第三网络设备是所述第一网络设备或所述第二网络设备。
  26. 如权利要求16-24任一项所述的方法，其特征在于，当所述第二网络设备管理的所述第一SCG发生RLF后，所述第三网络设备是所述第二网络设备。
  27. 一种通信装置，其特征在于，包括用于执行如权利要求1-15任一项所述的方法的单元或模块。
  28. 一种通信装置，其特征在于，包括用于执行如权利要求16-26任一项所述的方法的单元或模块。
  29. 一种通信装置，其特征在于，包括处理器和收发器，其中：
    所述收发器，用于收发数据或信息；
    所述处理器，与存储器耦合，用于调用所述存储器中的计算机指令，以通过所述收发器执行如权利要求1-15任一项所述的方法。
  30. 一种通信装置，其特征在于，包括处理器和收发器，其中：
    所述收发器，用于收发数据或信息；
    所述处理器，与存储器耦合，用于调用所述存储器中的计算机指令，以通过所述收发器执行如权利要求16-26任一项所述的方法。
  31. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时以执行如权利要求1-15中任一项所述的方法，或者执行如权利要求16-26中任一项所述的方法。
  32. 一种计算机程序产品，其特征在于，包含指令，当所述指令在计算机上运行时，使得如权利要求1-15中任一项所述的方法，或如权利要求16-26中任一项所述的方法被执行。
  33. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如权利要求1-15中任一项所述的方法，或者实现如述权利要求16-26中任一项所述的方法。
PCT/CN2023/092731 2022-05-11 2023-05-08 通信方法及装置 Ceased WO2023217078A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020247040273A KR20250005463A (ko) 2022-05-11 2023-05-08 통신 방법 및 장치
EP23802848.4A EP4510689A4 (en) 2022-05-11 2023-05-08 COMMUNICATION METHOD AND APPARATUS
US18/941,983 US20250071593A1 (en) 2022-05-11 2024-11-08 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210510815.9 2022-05-11
CN202210510815.9A CN117098176A (zh) 2022-05-11 2022-05-11 通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/941,983 Continuation US20250071593A1 (en) 2022-05-11 2024-11-08 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2023217078A1 true WO2023217078A1 (zh) 2023-11-16

Family

ID=88729764

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/092731 Ceased WO2023217078A1 (zh) 2022-05-11 2023-05-08 通信方法及装置

Country Status (5)

Country Link
US (1) US20250071593A1 (zh)
EP (1) EP4510689A4 (zh)
KR (1) KR20250005463A (zh)
CN (1) CN117098176A (zh)
WO (1) WO2023217078A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3975617B1 (en) * 2013-01-18 2025-04-30 Telefonaktiebolaget LM Ericsson (publ) Adapting a mobile network
CN120186663A (zh) * 2023-12-19 2025-06-20 夏普株式会社 信息报告方法以及用户设备
US12520264B2 (en) * 2025-04-18 2026-01-06 Mentats Co., Ltd. Method for supporting faster service recovery and user equipment thereof

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3497967A1 (en) * 2016-08-12 2019-06-19 Sony Corporation Communications devices, infrastructure equipment and methods
WO2020221179A1 (zh) * 2019-04-29 2020-11-05 华为技术有限公司 通信方法和通信装置
CN112399503A (zh) * 2019-08-16 2021-02-23 华为技术有限公司 链路失败报告传输的方法和装置
WO2021190608A1 (zh) * 2020-03-26 2021-09-30 夏普株式会社 无线链路失败报告方法以及用户设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4199638A4 (en) * 2020-10-08 2024-02-21 Samsung Electronics Co., Ltd. METHOD AND DEVICE FOR MANAGING A CONNECTION IN WIRELESS COMMUNICATIONS
WO2022077183A1 (en) * 2020-10-12 2022-04-21 Lenovo (Beijing) Limited Methods and apparatuses for a mro mechanism for a fast mcg link recovery procedure and an unbalanced ul and dl coverage scenario

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3497967A1 (en) * 2016-08-12 2019-06-19 Sony Corporation Communications devices, infrastructure equipment and methods
WO2020221179A1 (zh) * 2019-04-29 2020-11-05 华为技术有限公司 通信方法和通信装置
CN112399503A (zh) * 2019-08-16 2021-02-23 华为技术有限公司 链路失败报告传输的方法和装置
WO2021190608A1 (zh) * 2020-03-26 2021-09-30 夏普株式会社 无线链路失败报告方法以及用户设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Fast MCG recovery", 3GPP TSG-RAN WG2 MEETING #109-E R2-2002137, 11 March 2020 (2020-03-11), XP051864669 *
HUAWEI, HISILICON: "Fast MCG recovery via SCG", 3GPP TSG-RAN WG2 MEETING#105 R2-1901617, 15 February 2019 (2019-02-15), XP051602972 *
See also references of EP4510689A4 *

Also Published As

Publication number Publication date
EP4510689A4 (en) 2025-08-13
CN117098176A (zh) 2023-11-21
EP4510689A1 (en) 2025-02-19
KR20250005463A (ko) 2025-01-09
US20250071593A1 (en) 2025-02-27

Similar Documents

Publication Publication Date Title
EP3905833B1 (en) Access control for a terminal device in dual connectivity
US11470517B2 (en) Two-step addition of a primary-secondary cell, PSCell, in a multi-connected handover
JP7652397B2 (ja) モビリティ最適化方法および関連する装置
US20200396656A1 (en) Method and apparatus for handover
WO2023217078A1 (zh) 通信方法及装置
US20230171648A1 (en) Method Network Optimization in Handover Failure Scenarios
WO2018059299A1 (zh) 小区切换的方法、装置及系统和计算机存储介质
JP7842235B2 (ja) 通信方法および装置
WO2021227881A1 (zh) 无线链路失败恢复方法及对应的用户设备
KR20150055535A (ko) 단말이 복수의 기지국에 이중으로 연결될 수 있는 네트워크 환경에서의 통신 방법 및 장치
EP3932144A1 (en) Handover during secondary cell group failure
CN116438845A (zh) 通信方法和通信装置
WO2023011165A1 (zh) 一种通信方法及装置
US12501325B2 (en) Method and apparatus for determining daps handover failure type
JP7669484B2 (ja) Ｍｒｏ臨界シーンの判定方法、装置及び機器
WO2022222893A1 (zh) 通信方法及装置
US20240236719A9 (en) Multi-connectivity communication method and apparatus
CN117479239A (zh) 一种通信方法及装置
WO2024093931A1 (zh) 一种通信方法及装置
WO2023011612A1 (zh) 移动性管理的方法及通信装置
WO2023078340A1 (zh) 一种无线通信链路失败处理方法及装置
EP4608007A1 (en) Communication method, communication apparatus, computer-readable storage medium, and computer program product
JP7800730B2 (ja) 障害情報の送信方法、受信方法、装置及びシステム
WO2025156394A1 (zh) 报告记录方法、报告接收方法以及装置
WO2025160913A1 (zh) 小区改变的执行和配置方法以及装置

Legal Events

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

Ref document number: 23802848

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023802848

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023802848

Country of ref document: EP

Effective date: 20241112

WWE Wipo information: entry into national phase

Ref document number: 202447091855

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20247040273

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020247040273

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE