WO2022152220A1

WO2022152220A1 - Processing method, apparatus and system for connection failure information

Info

Publication number: WO2022152220A1
Application number: PCT/CN2022/071857
Authority: WO
Inventors: 耿婷婷; 曾宇; 吴烨丹; 胡星星
Original assignee: 华为技术有限公司
Priority date: 2021-01-14
Filing date: 2022-01-13
Publication date: 2022-07-21
Also published as: CN114765791A

Abstract

Disclosed in the present application are a communication method, apparatus and system. The method comprises: after a handover process is started, if a first connection failure is detected, recording first connection failure information corresponding to the first connection failure, and starting a timer; and then, after the timer stops or times out, sending indication information indicating that connection failure information is stored, wherein the connection failure information at least comprises the first connection failure information. Whether the indication information indicating that the connection failure information is stored can be sent to a network device is determined according to a running condition of the timer, so that a terminal device can provide complete failure information in a one-time mobility process to provide a correct reference for mobility optimization of the network device.

Description

Method, device and system for processing connection failure information

This application is required to be submitted to the State Intellectual Property Office on January 14, 2021, the application number is 202110049289.6, and the application name is "Method, Device and System for Processing Connection Failure Information", and submitted to the State Intellectual Property Office on December 10, 2021 , the priority of the Chinese patent application with the application number of 202111509893.9 and the application title of "Method, Device and System for Processing Connection Failure Information", the entire contents of which are incorporated in this application by reference.

technical field

The present application relates to the field of mobile communication technologies, and in particular, to a communication method, apparatus and system.

Background technique

At present, in addition to the normal handover (legacy handover) process (also called the process), there are dual active protocol stack (dual active protocol stack, DAPS) switching and conditional handover (conditional handover, CHO). However, in a DAPS handover process, a conditional handover process, or a normal handover but with a CHO configuration (for example, after the terminal device receives the CHO configuration and before the CHO is triggered or executed, the UE receives a normal handover command, but the previously received CHO configuration is still valid), the end device may detect more than one connection failure. At present, the latest connection (or link) failure information is stored and reported in the radio link failure (radio link failure, RLF) report (report) of the terminal device. However, the inventor of the present application found that the current RLF report There is irrationality in the processing method, which makes the robustness of the mobility strategy insufficient.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a communication method, device and system, which can make the processing of connection failure information more reasonable, so that it can be used to formulate a reasonable mobility strategy and improve the mobility performance of a terminal device.

In a first aspect, a communication method is provided, or it can also be called a connection failure information processing method. It can be understood that the method of the first aspect can be performed by a first apparatus, and the first apparatus can be a terminal device or a communication device capable of supporting the functions required by the terminal device to implement the method, such as a chip or a circuit or a chip system.

Exemplarily, after starting the handover process, the method may include: detecting a first connection failure, recording first connection failure information corresponding to the first connection failure, and starting a timer; after the timer stops or times out , sending indication information indicating that connection failure information is stored, wherein the connection failure information at least includes first connection failure information. While the timer is still running (not stopped or timed out), no information is sent indicating that the connection failure information is stored.

The timer may be the second timer described in the detailed description. The duration of the second timer may be preset, set by the terminal device, or configured by the network device. In the above-mentioned embodiment, it is determined whether the indication information that the connection failure information is stored can be sent to the network device according to the operation of the second timer, so that the terminal device can provide complete failure information in a mobility process, and perform the operation for the network device. Mobility optimization provides the right reference.

In some possible implementations, during the running of the timer, a second connection failure may occur, then when the second connection failure is detected, the operation of the timer can be stopped, and the corresponding second connection failure can be recorded. The second connection failure message.

In some possible implementations, if the target cell selected by the terminal device after performing cell selection is not a CHO cell; or the terminal device cannot successfully access the DAPS target cell configured in the DAPS HO, or if the target cell selected by the terminal device after performing cell selection The cell is a CHO cell, but HOF occurs in the CHO cell, or if the terminal device successfully establishes a connection with the CHO cell after performing cell selection or is handed over to another cell after the DAPS HO target cell successfully accesses, or if the terminal device switches from The connected state enters the non-connected state, which will also cause the timer to stop running. By considering the above scenario of stopping the second timer, the operation mechanism of the second timer can be made more complete.

In some possible implementations, there may be various ways of sending the indication information indicating that the connection failure information is stored, for example, it may be indicated by the first indication information that the connection failure information is stored (in this way, the network device does not know how many connections there are. failure information), or, it can be indicated by the second indication information that there are at least two connection failure information stored (in this way, the network device can know how many connection failure information is stored), or the indication information is that the first connection fails The information and the second connection failure information respectively correspond to multiple pieces of information (for example, in the third indication information and the fourth indication information, in this manner, the network device can know how many connection failure information is stored). Optionally, the third indication information and the fourth indication information may be sent to the network device according to the time sequence in which the connection failure occurs. For example, the first report may be sent to the network device after the network device requests the first report according to the third indication information. Send the fourth indication message at the time.

In some possible implementations, when the first connection failure information and the second connection failure information are stored, the method of sending the connection failure information may be: sending a first report, where the first report includes the first connection failure information and second connection failure information; or send a first report and a second report, where the first report includes the first connection failure information, and the second report includes the second connection failure information. Optionally, the first report and the second report may be sent at the same time, or the first report and the second report may be sent sequentially according to the chronological order of failures.

In some possible ways, it is also possible to indicate to the network device that the timing of processing the first report and the second report is the same, that is, to indicate to the network device to process the first report and the second report at the same time, so that the connection failure information can be processed. It is more reasonable and flexible, so that the target network device can receive complete connection failure information in time, so as to carry out reasonable mobility management.

In a second aspect, a communication method is provided, or it can also be called a connection failure information processing method. It can be understood that the method of the second aspect can be performed by a second device, which can be a terminal device or a communication device capable of supporting the functions required by the terminal device to implement the method, such as a chip or a circuit or a chip system. This method can be implemented in the CHO scenario. The method may include: detecting a first connection failure, recording first connection failure information corresponding to the first connection failure, and in the case of continuing to execute CHO and the second connection failure is not HOF, starting a timer, and in the After the timer stops or times out, an indication message indicating that the connection failure information is stored is sent.

In some possible manners, the running mechanism of the timer may refer to the second timer of the first aspect.

In some possible implementation manners, if the second connection failure is HOF, the timer is not started, and the second connection failure information corresponding to the second connection failure is recorded.

In some possible implementation manners, for the sending of the indication information indicating that the connection failure information is stored and the manner of sending the connection failure information, reference may be made to the description of the first aspect.

In some possible implementation manners, if the target cell is not a CHO cell after the first connection failure, the timer is not started, and indication information indicating that the first connection failure information is stored is sent.

In a third aspect, a communication method is provided, or it can also be called a connection failure information processing method. It can be understood that the method of the third aspect can be performed by a third apparatus, and the third apparatus can be a terminal device or a communication device capable of supporting the functions required by the terminal device to implement the method, such as a chip or a circuit or a chip system. This method can be implemented in the DAPS HO scenario. The method may include: detecting a first connection failure, recording first connection failure information corresponding to the first connection failure, and starting the timing when the handover of the DAPS target cell is continued and the second connection failure is not HOF After the timer stops or times out, it sends the indication information indicating that the connection failure information is stored.

In some possible ways, it is also possible to indicate to the network device that the timing of processing the first report and the second report is the same, that is, to indicate to the network device to process the first report and the second report at the same time, so that the connection failure information can be processed. more reasonable and flexible.

Through the method of the second aspect or the third aspect, the probability of the terminal device starting the second timer can be reduced. For example, after a connection failure occurs and the connection with the CHO or DAPS HO target cell is successfully established, the terminal device starts the second timer. The second timer is not started in other scenarios, thereby reducing the implementation complexity of the terminal device and reducing unnecessary energy consumption of the terminal device.

In a fourth aspect, a communication method is provided, or it can also be called a connection failure information processing method. It can be understood that the method of the fourth aspect may be performed by a fourth apparatus, and the fourth apparatus may be a network device or a communication device capable of supporting the functions required by the network device to implement the method, such as a chip or a circuit or a chip system. The method can be implemented independently, or can be implemented in combination with any one of the first to third aspects. The method may include: receiving information indicating that the first connection failure information is stored from the terminal device, and requesting the terminal device to obtain connection failure information according to the access type of the terminal device in the access network device, where the connection failure information At least the first connection failure information is included.

In some possible implementations, the access type is conditional handover CHO or dual-activation protocol stack handover DAPS HO, then after the first time period arrives, the terminal device may be requested to obtain connection failure information.

In some possible implementations, if the access type does not belong to conditional handover CHO or does not belong to dual activation protocol stack handover DAPS HO, the connection failure information may be directly requested from the terminal device without waiting for the first duration.

In some possible implementation manners, the above-mentioned first duration may be determined according to information received from the source network device, or the first duration may be preset, or the first duration may be determined according to time information indicated by the terminal device. of.

In some possible implementation manners, the above-mentioned connection failure information is carried in the first report, then after receiving the first report, the first report may be processed, for example, forwarded to the target network device, including: sending the first report to the target network device. A report, and indicating the manner of receiving the first report, wherein the manner of receiving the first report includes conditional switching or dual-active protocol stack switching.

In the embodiment of the present application, through the behavior of the network device, the network device can be prevented from requesting incomplete connection failure information from the terminal device, so that incorrect mobility parameter adjustment can be avoided according to the incomplete connection failure information, and the mobility is improved. Robustness of the strategy.

In a fifth aspect, a communication method is provided, or it can also be called a connection failure information processing method. It can be understood that the method of the fifth aspect can be performed by a fourth device, and the fifth device can be a network device or a communication device capable of supporting the functions required by the network device to implement the method, such as a chip or a circuit or a chip system. The method can be implemented independently, or can be implemented in combination with any one of the first to third aspects. The method may include: indicating to the first target network device or the third target network device a manner of receiving the first report and/or the second report, wherein the first target network device is the target network device corresponding to the first report, and the first target network device is the target network device corresponding to the first report. The third target network device is the target network device corresponding to the second report. For example, the receiving network device indicates that the above-mentioned report is received in the DAPS HO or CHO scenario. Optionally, the first target network device and the third target network device may be the same or different network devices. In the above manner, the target network device can be made aware of the scene in which the first report and/or the second report occurs, or the manner in which the receiving network device receives the first report and/or the second report, so that it can be used as a reference for mobility optimization, Improve the robustness of mobility strategies. In a sixth aspect, a communication method is also provided, or it can also be called a connection failure information processing method. The method may be implemented by a terminal device or a component (eg, a chip or a circuit) available for the terminal device. The method may include: detecting a first connection failure, recording first connection failure information corresponding to the first connection failure; if a second connection failure is detected, and the terminal device according to whether the cell corresponding to the second connection failure is a terminal Determine whether the cell where the device performs CHO execution is a cell related to CHO execution or whether it is a cell that performs CHO recovery, and determines the processing method for the first connection failure information. For example, if it is determined that the cell corresponding to the second connection failure is a cell where the terminal device performs CHO execution, a cell related to CHO execution, or a cell for performing CHO recovery, record the second connection failure information and do not delete the currently stored a connection failure information; or, when it is determined that the cell corresponding to the second connection failure is not a cell where the terminal equipment performs CHO execution or is not a cell related to CHO execution or is not a cell for CHO recovery, delete the first connection failure information and Record the second connection failure information. Optionally, the method may further include: sending the recorded connection failure information. Through this method, the terminal device can process the connection failure information according to whether the cell where the new connection failure occurs is the cell where the terminal device performs CHO execution, or whether it is a cell related to CHO execution or whether it is a cell for performing CHO recovery, The implementation complexity of the terminal device can be reduced, and the unnecessary energy consumption of the terminal device can be reduced.

In a seventh aspect, a communication device is provided, and the communication device has a function of implementing the actions or steps in the method of the first aspect. The communication means may be a terminal device or a component (eg a chip or a circuit) usable in a terminal device. The functions can be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the communication device includes: a detection unit, a processing unit, and a transceiver unit. Optionally, a storage unit may also be included, and the storage unit may be used to store instructions and/or data. These modules/units can perform the corresponding functions in the method examples of the first aspect. For details, please refer to the detailed descriptions in the method examples, which will not be repeated here.

In an eighth aspect, a communication device is provided, and the communication device has a function of implementing the acts or steps in the method of the second aspect. The communication means may be a terminal device or a component (eg a chip or a circuit) usable in a terminal device. The functions can be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. These modules/units can perform the corresponding functions in the method examples of the second aspect. For details, please refer to the detailed descriptions in the method examples, which will not be repeated here.

In a ninth aspect, a communication device is provided, and the communication device has the function of implementing the actions or steps in the method of the third aspect. The communication means may be a terminal device or a component (eg a chip or a circuit) usable in a terminal device. The functions can be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. These modules/units can perform the corresponding functions in the method examples of the third aspect. For details, please refer to the detailed descriptions in the method examples, which will not be repeated here.

According to a tenth aspect, a communication device is provided, and the communication device has a function of implementing the acts or steps in the method of the fourth aspect. The communication means may be a network device or a component (e.g. a chip or circuit) usable with a network device. The functions can be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. These modules/units can perform the corresponding functions in the method examples of the fourth aspect. For details, please refer to the detailed descriptions in the method examples, which will not be repeated here.

In an eleventh aspect, a communication device is provided, and the communication device has a function of implementing the acts or steps in the method of the fifth aspect. The communication apparatus may be a network device or a component (eg, a chip or circuit) usable in a network device. The functions can be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. These modules/units can perform the corresponding functions in the method examples of the fifth aspect. For details, please refer to the detailed descriptions in the method examples, which will not be repeated here.

A twelfth aspect provides a communication device, the communication device having the function of implementing the acts or steps in the method of the sixth aspect. The communication means may be a terminal device or a component (eg a chip or a circuit) usable in a terminal device. The functions can be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. These modules/units can perform the corresponding functions in the method examples of the sixth aspect. For details, please refer to the detailed descriptions in the method examples, which will not be repeated here.

In a thirteenth aspect, a communication device is provided, and the communication device may be a communication device implementing any one of the communication methods in the first to sixth aspects above. The communication device includes a processor and a memory. Wherein, the memory is used to store computer programs or instructions or data, and the processor is coupled to the memory, and when the processor reads the computer program or instructions or data, the communication device executes the method of any aspect. Optionally, the communication device may further include a communication interface.

Exemplarily, the communication interface may be a transceiver in a communication device. The transceiver may be used for the communication device to communicate with other devices.

In a fourteenth aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor for implementing any one of the methods in the first aspect to the sixth aspect. In one possible design, the system-on-a-chip further includes a memory for storing program instructions and/or data. The chip system can be composed of chips, and can also include chips and other discrete devices.

In a fifteenth aspect, an embodiment of the present application provides a communication system, where the system includes one or more of the communication devices of the seventh aspect - the thirteenth aspect.

A sixteenth aspect provides a computer program product, the computer program product comprising: computer program code, when the computer program code is executed, causes any of the methods in the above aspects to be performed.

In a seventeenth aspect, the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, any method in the above-mentioned aspects is implemented.

Description of drawings

FIG. 1 is a schematic structural diagram of a communication system to which an embodiment of the application is applied;

2 is an example diagram of a possible scenario in which connection failure occurs in the CHO flow process of the embodiment of the present application;

3 is a flowchart of an example of a communication method provided by an embodiment of the present application;

FIG. 4 is a flowchart of an example of a communication method provided by an embodiment of the present application;

5 is a flowchart of an example of a communication method provided by an embodiment of the present application;

6 is a flowchart of an example of a communication method provided by an embodiment of the present application;

6A is a flowchart of an example of a communication method provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application described below can be applied to the network architecture shown in FIG. 1 , wherein FIG. 1 is only an example of a communication system, and the communication system may include at least one terminal device and at least one network device. , FIG. 1 includes one terminal device and two network devices as an example, the terminal device 1 may switch from the network device 1 to the network device 2 . It can be understood that the number of terminal devices and network devices in FIG. 1 is only an example, and there may be more terminal devices and network devices in the communication system, and any network device can provide services for the terminal devices within the coverage.

The terminal device is a device with wireless transceiver function, which can be a fixed device, a mobile device, a handheld device, a wearable device, a vehicle-mounted device, or a device built into the above-mentioned device (for example, a communication module or a chip system, etc.). The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios. Also sometimes referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal Equipment, wireless terminals in industrial control, wireless terminals in internet of things (IoT) systems, wireless terminals in self-driving, wireless terminals in remote medical , wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone , Session initiation protocol (session initiation protocol, SIP) telephone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant,

PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, in-vehicle devices, in-vehicle communication devices, in-vehicle communication processing chips, wearable devices, terminal equipment in 5G networks or future evolution of public Terminal equipment in a land mobile communication network (public land mobile network, PLMN). It should be understood that the present application does not limit the specific form of the terminal device.

The network device may be an access network device, and the access network device may also be called a radio access network (RAN) device. A device for wireless terminal communication can also be regarded as a device that provides a wireless communication function for the terminal device. Access network equipment includes, but is not limited to, the next generation base station (generation nodeB, gNB), evolved node B (evolved node B, eNB), baseband unit (baseband unit, BBU) in 5G, transmitting and receiving points (transmitting and receiving), for example, but not limited to: point, TRP), transmitting point (transmitting point, TP), the base station in the future mobile communication system or the access point in the WiFi system, etc. The access network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (DU) in a cloud radio access network (cloud radio access network, CRAN) scenario, or a network The device may be a relay station, a vehicle-mounted device, and a network device in a future evolved PLMN network, and the like.

CUs and DUs can be physically separate or deployed together. Multiple DUs can share one CU. A DU can also be connected to multiple CUs. The CU and the DU can be connected through an interface, such as an F1 interface. CU and DU can be divided according to the protocol layer of the wireless network. For example, one of the possible division methods is: the CU is used to execute the radio resource control (Radio Resouce Control, RRC) layer, the service data adaptation protocol (service data adaptation protocol, SDAP) layer and the packet data convergence layer protocol (packet data convergence layer protocol). Protocol, PDCP) layer function, and DU is used to perform radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer, physical (physical) layer and other functions. It can be understood that the division of CU and DU processing functions according to this protocol layer is only an example, and may also be divided in other ways. For example, a CU or DU may be divided into functions with more protocol layers. For example, a CU or DU can also be divided into partial processing functions with a protocol layer. In one design, some functions of the RLC layer and functions of the protocol layers above the RLC layer are placed in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are placed in the DU. In another design, the functions of the CU or DU may also be divided according to service types or other system requirements. For example, according to the delay, the functions whose processing time needs to meet the delay requirements are set in the DU, and the functions that do not need to meet the delay requirements are set in the CU. The network architecture shown in the figure above can be applied to a 5G communication system, which can also share one or more components or resources with an LTE system. In another design, the CU may also have one or more functions of the core network. One or more CUs can be set centrally or separately. For example, the CU can be set on the network side to facilitate centralized management. The DU can have multiple radio functions, or the radio functions can be set farther away.

The functions of the CU can be implemented by one entity or by different entities. For example, the functions of the CU can be further segmented, for example, the control plane (CP) and the user plane (UP) can be separated, that is, the CU control plane (CU-CP) and the CU user plane (CU -UP). For example, the CU-CP and the CU-UP may be implemented by different functional entities, and the CU-CP and the CU-UP may be coupled with the DU to jointly complete the functions of the access network device.

Terminal equipment can communicate with access network equipment of different technologies. For example, terminal equipment can communicate with access network equipment that supports long term evolution (LTE), and can also communicate with access network equipment that supports 5G. It can communicate with LTE-enabled access network devices and 5G-enabled access network devices at the same time. The embodiments of the present application are not limited.

The examples of this application first briefly introduce CHO and DAPS HO.

1. DAPS HO

After the terminal device receives a handover message (such as a handover command or an RRC reconfiguration message) from the source network device, it maintains data transmission with the source network device, that is, the terminal device maintains the user plane protocol stack corresponding to the source network device. The corresponding user plane protocol stack does not perform layer 2 restoration/re-establishment, and the terminal device establishes a user plane protocol stack corresponding to the target network device for random access and data transmission with the target network device. Before the terminal device releases the connection with the source network device, the terminal device maintains two sets of security keys (or security contexts) and two sets of header decompression contexts (or two sets of header compression contexts). The network device is also the target network device, and uses the corresponding key/header decompression context to process the received data packet. After the terminal device completes the access to the target network device, before receiving the release message sent by the target network device to release the connection between the terminal device and the source network device, the terminal device continues to perform data transmission (uplink and / or downlink data transmission); when the terminal device receives a release message sent by the target network device for releasing the connection between the terminal device and the source network device, the terminal device releases its connection with the source network device. Optionally, for the process or signaling of DAPS HO, please refer to the description in chapter 9.2.3.2 of 3GPP TS 38.300 V16.3.0. Exemplarily, the scenario or process of detecting connection failure in DAPS HO may include: before the terminal device successfully completes random access with the target network device, the terminal device continues to perform wireless chaining on the connection between the terminal device and the source network device. Road failure (radio link failure, RLF) monitoring (or detection); in the process of random access between the terminal device and the target network device, the terminal device may detect a handover failure (HOF); After the random access of the target network device, the terminal device can monitor the wireless link connected between the terminal device and the target network device to determine whether any wireless link fails. In this embodiment of the present application, for the convenience of description, the command or message used to indicate the DAPS HO may also be referred to as the DAPS HO command. The cell belonging to the source network equipment accessed by the terminal equipment is called the source cell, and the cell belonging to the target network equipment accessed by the terminal equipment is called the target cell. The information of the target cell is configured through the DAPS HO command. It can also be referred to as a DAPS target cell.

2. CHO

The CHO configuration information sent by the source network device to the terminal device includes information of one or more candidate cells configured by the source network device for the terminal device. The information of the candidate cell may include information used to indicate identification information of the candidate cell, one or more corresponding handover trigger conditions (or execution conditions) and configuration information of the candidate cell. The information used to indicate the identity information of the candidate cell may be the CHO configuration identity or the CHO candidate cell information. The cell information may be the cell global identifier (CGI), physical cell identifier (PCI) and frequency, cell identifier (cell ID), non-public network identifier (non-public network) of the cell. identifier, NPN ID), non-terrestrial network identifier (non-terrestrial network identifier, NTN ID) or at least one of other cell identifiers. The CGI may include a public land mobile network (PLMN ID) and a cell ID. In this embodiment of the present application, the candidate cell in the CHO configuration information may be referred to as a CHO cell for short.

After receiving the configuration information of the CHO, the terminal device determines whether each CHO candidate cell satisfies the handover trigger condition according to the configuration information, and this process can be understood as a normal CHO. If the CHO candidate cell that satisfies the handover trigger condition is taken as the candidate target cell, the source cell is handed over to the target cell.

If the terminal device receives a handover command without CHO configuration (that is, the handover command does not carry CHO configuration information) before any CHO execution condition is satisfied, it can also be converted into a normal handover (normal HO or legacy HO). The normal handover command executes the handover process. It can be understood that, at this time, the terminal device has an available CHO configuration, and the handover type corresponding to this scenario can also be called CHO. In the embodiment of the present application, each scenario in which the terminal device receives the CHO configuration information and the CHO configuration information is not cleared may be referred to as the terminal device has the available CHO configuration, for example, it may include: normal CHO or if any CHO execution condition is used Before it is satisfied, the terminal device has received a handover command without CHO configuration. In this embodiment of the present application, for convenience of description, a command or message having CHO configuration information may also be referred to as a CHO command, and the CHO command may be, for example, an RRC reconfiguration message. In this embodiment of the present application, the handover type corresponding to any scenario with available CHO configuration may be referred to as CHO.

When the terminal device has an available CHO configuration, the terminal device detects that the connection fails. If the appropriate cell selected by the terminal device is a CHO candidate cell, the terminal device can try a CHO execution, which can also be called CHO recovery (CHO recovery). ; If the target cell selected by the terminal equipment is not a CHO candidate cell, the terminal equipment performs the re-establishment process; if the terminal equipment does not find a suitable cell within a period of time, the terminal equipment enters an idle state. It is understandable that if the terminal device attempts to perform CHO once in the CHO process (that is, the terminal device performs CHO recovery), the terminal device detects the connection failure again, regardless of whether the appropriate cell selected by the terminal device is the target cell in the CHO candidate cells. , the terminal device no longer attempts to perform CHO (or CHO recovery), and optionally, the terminal device may perform a re-establishment process. It can be understood that the embodiment of the present application is described by taking the terminal device that detects the connection failure for the first time in the CHO process as an example, and can try CHO execution again (that is, the terminal device performs one CHO recovery) as an example. In the CHO process After the terminal device detects the first connection failure, it can try N CHO executions (or CHO recovery), where N is preset to limit the CHO executions that can be attempted after the first connection failure is detected in the CHO process ( or CHO recovery) the maximum number of times, N is greater than or equal to 1.

It can be understood that, in this embodiment of the present application, messages or commands used to implement handover configuration or handover instruction may also be collectively referred to as handover messages or handover commands.

Figure 2 exemplarily shows a possible scenario in which at least two connection failures occur in the CHO process. As shown in Figure 2, after the source cell triggers the conditional handover, the terminal device first attempts to handover to the target cell B (T- cell B), after the T-cell B fails to connect, perform cell selection, and select the target cell C (T-cell C) in the CHO candidate cell, and the terminal equipment tries to switch to T-cell C (that is, the terminal equipment Attempt to perform CHO recovery with T-cell C), and a connection failure also occurs in the target cell T-cell C, and this CHO process ends. The above connection failures may include failures caused by HOF, RLF or timer expiration. Here, T-cell B can be called the first target cell in the CHO procedure. It can be understood that, for the legacy HO process with CHO configuration, the scenario shown in Figure 2 may also occur, that is, the terminal device performs handover to the target cell cell B (target cell indicated by legacy HO) according to legacy HO. After a connection failure occurs, the cell selection is performed and the target cell T-cell C in the CHO candidate cell is selected. A connection failure also occurs in the target cell T-cell C, and this CHO process ends. . In addition, there are multiple failures in other CHO scenarios. Take the terminal device performing at most one CHO attempt after detecting the first connection failure as an example: the terminal device receives the CHO configuration, does not trigger CHO handover, and detects that the connection between the terminal device and the source network device fails; the terminal device determines the execution cell Select and select the target cell B (T-cell B) in the CHO candidate cell, the terminal equipment performs CHO to T-cell B (that is, the terminal equipment attempts to perform CHO recovery with T-cell B), and the terminal equipment can detect the terminal The connection between the device and T-cell B failed.

For the DAPS HO process, in a DAPS HO process, there may be more than one connection failure. For example, after the terminal device receives the DAPS HO command in the source cell, the terminal device detects that the connection with the source cell fails, for example, RLF, the terminal equipment continues to perform DAPS HO with the target cell, and the terminal equipment detects that the connection between the terminal equipment and the target cell fails, such as HOF or RLF. For another example, after the terminal device receives the DAPS HO command in the source cell, the terminal device detects that the connection with the target cell fails, for example, HOF, the terminal device returns to the source cell, and tries to perform connection recovery with the source cell, The terminal device detects that the connection between the terminal device and the source cell has failed.

In this embodiment of the present application, the process before the terminal device initiates the handover to successfully access the target cell or transitions to other non-connected states may be referred to as a handover process (or a handover process). Understand CHO, DAPS HO, normal handover (can be called normal HO or legacy HO), etc. as different handover types. For the CHO scenario, the timing when the base station of the source network device sends the CHO configuration information can be regarded as the handover initiation. For the DAPS HO scenario, the timing when the source network device sends the DAPS HO command to the terminal device can be regarded as the handover initiation. For normal handover, The timing at which the source network device sends the source-sent switching command to the terminal device can be considered as starting the switching.

It can be understood that the above-mentioned one-time handover process may also be referred to as a one-time mobility process. During the mobility process, at least one connection failure may occur, and for the connection failure that occurs, the terminal device may record connection failure information.

As an example, the connection failure information may include at least one of the following information:

1) Failed primary cell identifier (failedPCellId): the terminal device detects the RLF or the primary cell information of which the first timer has expired (expired), or the target primary cell information of the HOF. The timer may be, for example, a timer started after the terminal device sends the measurement report. If the terminal device has not received the handover command after the first timer expires, it may be considered that a connection failure occurs, and the first timer may be, for example, T312.

Optionally, the connection failure information may also not include the failed primary cell identifier (failedPCellId), but include the failed cell identifier (failedCellId). Wherein, the failed cell identifier is the information of the cell where the terminal device detects a link failure or the timer expires, or the information of the target cell where the handover fails, which is not limited in this embodiment of the present application.

2) Connection failure type (connectionFailureType).

As an example, the connection failure type may be RLF or HOF or timer expiration. Connection failure types can also be referred to simply as failure types.

3) The previous primary cell identifier (previousPCellId): the previous primary cell information that the terminal device received the handover command last time.

Optionally, the connection failure information may not include the previous primary cell identifier (previousPcellId), but may include the previous cell identifier (previousCellId). Wherein, the previous cell identifier is the previous cell information on which the terminal device received the handover command last time, which is not limited in this embodiment of the present application.

4) Reestablishment Cell Identifier (reestablishmentCellId): cell information that is attempted to be re-established after the connection fails.

5) Connection failure time (timeConnFailure): the length of time from when the last (or most recent) handover command (or reconfiguration message) is received to the connection failure.

6) Time after failure (timeSinceFailure): The length of time to start recording when the connection fails. Generally refers to the length of time from the connection failure to the reporting of the failure report.

7) Reason for connection failure (rlf-Cause): Among them, the reasons for connection failure can include HOF, RLF, reconfiguration synchronization failure, NR switching failure to other systems, integrity check failure (integrity check failure) or RRC connection re-connection. Configuration failed.

8) Location information (locationInfo): information about the location where the terminal device fails to connect.

9) Random access information (ra-InformationCommon): information that the terminal device performs random access in the cell.

9) Measurement result: it may be a measurement result of a cell and/or a beam, and the measurement result may include a measurement result of a serving cell and/or a neighboring cell.

10) Receive time information (timeCHOcfgExe) from CHO configuration to trigger normal CHO execution (ie, CHO execution condition trigger)

The connection failure information in this embodiment of the present application may also be referred to as link failure information.

In this embodiment of the present application, in a mobility process, if the number of connection failures is greater than one (for example, M times, where M is an integer greater than 1), the terminal device may report connection failure information in two ways.

Mode (1): include failure information of M connection failures in a report (eg RLF report);

Mode (2): M times of connection failure information respectively correspond to M reports.

It can be understood that the above methods (1) and (2) are described by taking the terminal equipment reporting part or all of the connection failure information as an example in the RLF report, and the embodiment of the present application does not limit the terminal equipment to store the carrier or report of the connection failure information. form.

In order to solve the problem of how to reasonably handle the connection failure information when the number of times of connection failure is M during a mobility process, the embodiment of the present application provides a communication method. It can be understood that the communication method It can also be called a connection failure information processing method. In this communication method, after starting the switching process, the terminal device detects the first connection failure (first connection failure), records the first connection failure information corresponding to the first connection failure and stores the first connection failure information, and the terminal device Instead of immediately indicating to the network device that the connection failure information is stored, a timer is started, and after the timer stops or times out, indication information indicating that the connection failure information is stored is sent again. For the operation of the timer, reference may be made to the detailed description of the following embodiments.

As shown in FIG. 3, taking M=2 as an example, the communication method includes:

S301, the terminal device detects that the connection fails.

It can be understood that, in this embodiment, the connection failure may be referred to as the first connection failure. The terminal device detects a connection failure, which may be: the terminal device receives the CHO configuration, the CHO execution condition is not triggered, and the terminal device detects a connection failure between the terminal device and the source cell, such as a failure triggered by RLF or timer expiration; or When the terminal device receives the CHO configuration, triggers the CHO execution condition or receives a normal handover command, the terminal device detects that the connection to the target cell fails, such as HOF or RLF; or after the terminal device receives the DAPS HO command, it detects the terminal device The connection with the source cell fails, such as RLF; or after the terminal device receives the DAPS HO command, it detects that the connection between the terminal device and the target cell fails, such as HOF.

After the handover procedure is started, and before the handover procedure is ended, a connection failure of the terminal device in the source cell or the target cell may occur. If the terminal device determines that the connection failure is detected, S302 may be executed. The connection failure detected in S301 may be referred to as the first connection failure.

It can be understood that, if the terminal device does not detect the connection failure, it means that the terminal device can normally complete the handover process, and the process of this embodiment of the present application may not be executed.

In this embodiment of the present application, the cell where the terminal is located when the first connection failure occurs may be referred to as the first cell.

S302, the terminal device records connection failure information.

Correspondingly, the connection failure information corresponding to the first connection failure recorded in this step may be referred to as the first connection failure information, and may also be referred to as the first connection failure information.

When the terminal device detects a connection failure, the terminal device records and saves the connection failure information this time.

In some possible implementation manners, subsequently, when the terminal device reports the first connection failure information, the first connection failure information may be reported in the first report (for example, the first RLF report).

S303, the terminal device starts a second timer.

Wherein, the second timer is used for the terminal device to determine whether it can send indication information indicating that it stores the connection failure information to the network device. This embodiment of the present application does not limit the duration of the second timer. It can be understood that the duration information of the second timer may be configured by the network device, for example, the network device to which the first cell belongs may send the duration information of the second timer to the terminal device through a system message or a handover message. Optionally, the network device to which the first cell belongs may receive duration information of the second timer from the target network device, such as receiving duration information of the second timer in a handover confirmation message sent by the target network device. Alternatively, the duration of the second timer may also be configured by the source network device, or may also be set by the terminal device.

It can be understood that, S303 may be executed after S301 or S302, or may be executed synchronously with S301 or S302. That is to say, the second timer may be started when or after the terminal device detects the connection failure, or the timer may be started when or after the terminal device records the connection failure information.

After S303, S304 may be performed. It can be understood that, in an actual scenario, S304 does not necessarily occur.

S304, during the running of the second timer, the terminal device determines to detect connection failure again.

During the running of the second timer, after detecting the failure of the first connection, the terminal device continues to try to access at least one other cell (the second cell). For example, the selected suitable cell is the CHO candidate cell, and the terminal device can try CHO execution (or called CHO recovery); or continue to attempt handover with the target cell of DAPS HO; or after the terminal device detects the HOF with the target cell of DAPS HO, it tries to return to the source cell for connection recovery.

It can be understood that, on the basis of the first connection failure, a connection failure may occur again, and in this embodiment of the present application, a connection failure that occurs again may be referred to as a second connection failure. If the terminal device detects the connection failure again, execute S305. If the terminal device does not detect the connection failure again during the running of the second timer, it means that the terminal device can access normally. Then, when the second timer expires, S306 may be performed.

S305, the second timer is stopped, and the terminal device records the connection failure information of the second connection failure.

When the terminal device detects that the number of connection failures reaches M, the terminal device stops the second timer. Taking M=2 as an example, when the terminal device detects that the second connection fails, the terminal device stops the second timer. In addition, the terminal device records connection failure information (second connection failure information) corresponding to the second connection failure. It can be understood that the recording of the second connection failure information and the stopping of the second timer may be performed simultaneously or sequentially (the sequence of recording the second connection failure information and stopping the second timer is not limited).

Optionally, the terminal device may also record the running duration information of the second timer, where the recorded running duration information of the second timer may be used as a part of the connection failure information.

Optionally, the terminal device may report the second connection failure information through the first report, or may report the second connection failure information through a report (second report) different from the first report.

It can be understood that the detection of the second connection failure by the terminal device is one of the scenarios in which the second timer is stopped. In other scenarios, the terminal device can also stop the second timer. For example, the terminal device performs cell selection and then selects The target cell is not a CHO cell; or the terminal equipment fails to successfully access the DAPS target cell configured in the DAPS HO; or the terminal equipment selects a CHO cell after performing cell selection, but HOF occurs in the CHO cell; or the terminal equipment After the cell selection is performed, the connection is successfully established with the CHO cell or after the DAPS HO target cell is successfully accessed, it is switched to other cells; or the terminal device enters the disconnected state from the connected state. It can be understood that the above only uses the connection failure detected again as an example to illustrate the record of the connection failure information. For any of the above cases, when a connection failure occurs, the connection failure can also be reported through the above methods (1) or (2). information. In addition, in any case of stopping the second timer, S306 may continue to be executed after the second timer is stopped.

S306, the terminal device sends indication information, where the indication information indicates that the terminal device stores connection failure information or indicates that the terminal device stores the first connection failure information and the second connection failure information.

The terminal device may send indication information to the network device (which may be referred to as the receiving network device) after the second timer stops or expires. This embodiment of the present application describes the specific sending of the indication information after the second timer stops or expires. Timing is not limited. The receiving network device here may be the same or different network device as the source network device/the network device that detects the connection failure, which is not limited in this embodiment of the present application.

In some possible implementations, the indication information may be first indication information, that is, the first indication information indicates that the terminal device stores connection failure information (the connection failure information includes at least the first connection failure information); or, the indication information It may be a piece of information (second indication information), that is, the second indication information indicates that the terminal device stores at least two connection failure information, or the indication information may be respectively corresponding to the first connection failure information and the second connection failure information Multiple pieces of information (for example, the third indication information and the fourth indication information), that is, the third indication information (for example, rlf-Info 1Available) corresponding to the first connection failure information indicates that the terminal device stores the first connection failure information, which is the same as the second connection failure information. The fourth indication information (for example, rlf-Info 2Available) information corresponding to the connection failure information indicates that the terminal device stores the second connection failure information, or the second indication information indicates that the terminal device stores M pieces of connection failure information. Optionally, the third indication information and the fourth indication information may be sent at the same timing or at different timings, for example, the third indication information and the fourth indication information may be sent to the network device in a chronological order in which the corresponding connection failure occurs. It can be understood that, for the manner indicated by the second indication information and the third and fourth indication information, the network device can learn how many connection failure information is stored in the terminal device.

It should be noted that, in the case where the connection failure information occurs only once in a mobility process, the terminal device may also indicate to the network device that it stores the connection failure information through the first indication information.

Optionally, when the second timer is still running (that is, the second timer has not been stopped or expired), even if the terminal device has stored the first connection failure information, the terminal device may not send the stored information to the network device. Indication of the connection failure message.

Optionally, S307 may also be executed after S306.

S307, the receiving network device requests the terminal device to acquire connection failure information according to the above-mentioned indication information.

In a possible implementation manner, the receiving network device may request the terminal device to obtain the first connection failure information or request to obtain the first connection failure information and the second connection failure information.

In other words, the receiving network device will send a message for requesting the first report or requesting the first report and the second report to the terminal device.

After the receiving network device receives the above-mentioned indication information, it can be learned that the terminal device stores the connection failure information, so that the terminal device can be requested to send a report corresponding to the connection failure information. Correspondingly, the terminal device will send the first report and/or the second report to the receiving network device according to the request of the receiving network device.

In a possible implementation manner, in the case that the indication information is the first indication information, the receiving network device requests the terminal device to obtain the first connection failure information (the first report).

In a possible implementation manner, for the case where the indication information is the second indication information, the receiving network device requests the terminal device to obtain the first connection failure information (the first report) and the second connection failure information (the second report) or A first report is requested from the terminal device. Optionally, the terminal device may send the first report and the second report at the same time, or may send the first report and the second report successively in the chronological order of failure occurrence. Not limited.

In a possible implementation manner, for the case where the indication information is the third indication information and the fourth indication information, the receiving network device requests the terminal device to obtain the first connection failure information (the first report) and the second connection failure information ( The second report) can be the following A or B:

A: If both the third indication information and the fourth indication information are sent to the network device before the receiving network device makes a request (for example, the third indication information and the fourth indication information are sent to the receiving network device at the same time), then the receiving network device can The first connection failure information (first report) and the second connection failure information (second report) are requested from the terminal device. Optionally, the terminal device may send the first report and the second report at the same time, or may send the first report and the second report successively in the chronological order of failure occurrence. Not limited.

B: If both the third indication information and the fourth indication information are not sent to the network device before the receiving network device makes a request (for example, the third indication information is sent to the receiving network device first), then the receiving network device can first send the The first message is used to request the terminal device for the first connection failure information (first report). In addition to sending the first report to the receiving network device, the terminal device can also send fourth indication information to the receiving network device. The fourth indication information further requests the terminal device for second connection failure information (second report) through a second message. In a possible implementation manner, the terminal device may carry the fourth indication information in a user equipment information response (UE information response) message.

It can be understood that, for mode B, there may be a situation that the receiving network device successfully receives the first report but fails to receive the second report. For example, after the terminal device sends the first report to the receiving network device, the connection between the terminal device and the receiving network device is disconnected. For example, the terminal device detects that the connection with the receiving network device fails, or the terminal device performs CHO to other cells. Or the terminal device receives a normal handover command or a connection release command sent by the receiving network device. In this case, the terminal device may save the first connection failure information after sending the first report. When the terminal device determines that the first report and the second report are successfully sent to the receiving network device, the terminal device deletes the stored first connection failure information and the first report. Two connection failure information. In a possible implementation manner, if the receiving network device determines that the terminal device stores the first connection failure information and the second connection failure information, and determines that it has not received the first report and the second report, the receiving network device may delete the For the received first report or second report, correspondingly, the receiving network device does not perform S308.

Optionally, after S307, S308 may also be performed.

S308, the receiving network device processes the received report.

As mentioned above, according to the method (1), the receiving network device may process the first report; according to the method (2), the receiving network device may process the first report and the second report respectively, and the first report The way of processing the first report and the second report is similar, but the timing of processing the first report and the second report may be the same or different.

It can be understood that, for the same situation when the first report and the second report are processed, the protocol may stipulate that the receiving network device processes the first report and the second report at the same time (for example, the processing may be forwarding, for details, please refer to The description of the following embodiments), or it may be that the receiving network device simultaneously processes the first report and the second report according to the instruction (fifth instruction information) of the terminal device. For example, the fifth indication information instructs the receiving network device to process both the first report and the second report, or instructs the receiving network device to process the first report and the second report at the same time, or indicates that the first report and the second report belong to A mobility process.

The following takes the processing of the first report by the receiving network device as an example to illustrate how the receiving network device processes the received report. It can be understood that the processing of the second report is similar to the first report.

The receiving network device may determine a target network device to forward the first report according to the received connection failure information (a first target network device, different connection failure information in the first report may correspond to different first target network devices). As an example, if the connection failure type in the first report is HOF, the receiving network device may determine, according to the "previous primary cell identifier", that the network device to which the corresponding cell belongs is the first target network device. Optionally, Further, corresponding processing may be performed by the first target network device according to the first report, thereby improving mobility robustness. If the connection failure type in the first report is RLF or the first timer expires, the receiving network device may determine that the network device to which the corresponding cell belongs is the first target network device according to the "failure primary cell identifier". , and further corresponding processing can be performed by the first target network device according to the first report, so that the mobility robustness can be improved. Optionally, if the first target network device can further determine whether the first report needs to be forwarded to the network device (may be referred to as the second target network device) to which the cell corresponding to the "previous primary cell identifier" belongs, if so, the first The target network device may send the first report to the network device to which the cell corresponding to the "previous primary cell identity" belongs. For example, the first target network device determines that the first time when the terminal device performs handover to the detected connection failure with the failed primary cell is less than or equal to a certain threshold. The network device to which the cell belongs sends the first report. It can be understood that, when the first target network device and the receiving network device are the same network device, forwarding may not be performed, but the receiving network device performs corresponding processing according to the first report, or the first target network device and the first target network device may not perform forwarding. If the two target network devices are the same network device, forwarding may not be performed, but the first target network device performs corresponding processing according to the first report, thereby improving mobility robustness.

It should be noted that the target network device (first target network device) corresponding to the first report and the target network device (third target network device) corresponding to the second report may be the same or different network devices. Optionally, the receiving network device may also indicate to the first target network device or the third target network device the manner or scenario of receiving the first report and/or the second report, for example, the indication is received in a DAPS HO or CHO scenario. to the above report. It can be understood that the way in which the receiving network device determines that the first report and/or the second report is received may be determined according to the way in which the terminal device accesses the receiving network device. For example, the terminal device performs CHO configuration to access the receiving network device. , the manner in which the receiving network device determines to receive the first report and/or the second report may be CHO; or, for example, if the terminal device performs DAPS HO configuration to access the receiving network device, the receiving network device determines that the first report is received. And/or the manner of the second report may be DAPS HO. In some possible implementations, the receiving network device may indicate to the target network device the manner in which it received the above-mentioned report in the failure indication message or the radio link failure indication information, that is to say, in the failure indication message or the radio link failure indication information. Included in is information indicating the manner in which the first report and/or the second report was received. By indicating the manner or scenario of receiving the first report and/or the second report, the target network device can be made aware of the scenario in which the first report and/or the second report occurs, or that the receiving network device receives the first report and/or the first report and/or the second report. The second way of reporting can be used as a reference for mobility optimization. It can be understood that the manner in which the receiving network device indicates to the first target network device or the third target network device that the first report and/or the second report is received may be decoupled from the previous embodiments, that is to say, the first target network device is not limited. The report and/or the second report are stored in the manner of the foregoing embodiments, for example, the first report and/or the second report may be acquired without using the second timer.

This embodiment of the present application does not limit the process and manner of processing the first report and/or the second report by the network device, for example, it may be to adjust the mobility parameters according to the information in the first report and/or the second report, and/or For example, the first target network device determines, according to the connection failure time, whether to send the first report and/or the second report to the network device to which the cell corresponding to the previous primary cell identifier belongs.

Optionally, for the situation that the receiving network device may successfully receive the first report but fails to receive the second report in the way B, the receiving network device may also forward the first report to the target network device. The device sends sixth indication information, where the sixth indication information may indicate that the first report is an incomplete report, and/or indicates that the first report only includes failure information corresponding to the first connection failure, and/or indicates that the first report is an incomplete report. A report is also associated with a second report, and/or, indicates that the second report was not received successfully. Through the above sixth indication information, the target network device can confirm that the received first report information is incomplete, then the target network device may not adjust the mobility parameters based on the first report, or wait for the second report to be received according to the first report. A report and a second report carry out the adjustment of mobility parameters.

In some possible implementation manners, if the target network device is the CU, the method in this embodiment of the present application further includes: the CU sends part or all of the information of the first report/second report to the DU.

In the above-mentioned embodiment, it is determined whether the indication information that the connection failure information is stored can be sent to the network device according to the operation of the second timer, so that the terminal device can provide complete failure information in a mobility process, and perform the operation for the network device. Mobility optimization provides the right reference.

It can be understood that, in the above-mentioned embodiment shown in FIG. 3 , the second timer is started after the first connection failure is detected, and further, the timing or scenario of starting the second timer can also be distinguished, for example, in CHO Or in the DAPS HO process, it is determined whether to start the second timer according to the failure type of the connection failure that occurs again, and the CHO and DAPS HO processes are respectively described in the embodiments of FIG. 4 and FIG. 5 below.

As shown in FIG. 4 , an embodiment of the present application provides a communication method for a CHO scenario. It can be understood that the communication method may also be called a connection failure information processing method. The method can include:

S401, the terminal device detects that the first connection fails.

The terminal device detects a connection failure in the first cell. For this step, reference may be made to the relevant description applicable to the CHO scenario in S301.

S402, the terminal device records connection failure information.

The connection failure information is the first connection failure information. Further, for this step, reference may be made to the relevant description at S302, which will not be repeated here.

Optionally, the subsequent terminal device may report the first connection failure information through the first report.

S403, the terminal device performs cell selection, and determines a target cell, so as to determine whether to continue to perform CHO.

After detecting the failure of the first connection, the terminal device will perform cell selection, and continue to try to access at least one other cell. In this embodiment of the present application, the selected cell for access attempt may be referred to as a target cell. If the target cell is a non-CHO cell, S409 may be executed. If the target cell is a CHO cell, the terminal device may perform CHO, that is, perform S404.

S404, the terminal device continues to execute CHO, and detects whether HOF occurs in the CHO cell.

In the process of the terminal equipment continuing to perform CHO, if the terminal equipment detects the HOF between the terminal equipment and the CHO cell, S405 may be performed; if the terminal equipment and the target cell successfully establish a connection, S406 may be performed.

S405, the terminal device records the connection failure information corresponding to the HOF.

The connection failure information corresponding to the HOF is the reoccurring connection failure information (second connection failure information).

Optionally, the subsequent second connection failure information may be reported in the manner (1) or (2) described in the foregoing embodiment. For details, reference may be made to the relevant description of the foregoing embodiment and the second connection failure information. S409 may be executed after S405.

S406, the terminal device starts a second timer.

For the description of the second timer, reference may be made to the related description at S303.

Optionally, after S406, S407 may be performed.

S407, during the running of the second timer, the terminal device determines whether the connection failure is detected again.

If the terminal device detects that the second connection fails during the running of the second timer, S408 may be executed.

If the terminal device does not detect the connection failure again during the running of the second timer, it means that the terminal device can access normally. Then, when the second timer expires, S409 may be executed.

S408, the second timer is stopped, and the terminal device records the connection failure information of the second connection failure.

When the terminal device detects that the second connection fails, the terminal device stops the second timer. In addition, the terminal device records connection failure information (second connection failure information) corresponding to the second connection failure. For the operation mechanism of the second timer, further reference may be made to the related description of the embodiment in FIG. 3 . Similarly, for other scenarios in which the second timer is stopped, reference may also be made to the relevant description of the embodiment in FIG. 3 , which will not be repeated here.

For any scenario where the second timer is stopped, the terminal device may continue to perform S409.

S409, the terminal device sends indication information, where the indication information indicates that the terminal device stores connection failure information or that the terminal device stores the first connection failure information and the second connection failure information.

Regarding the sending of the indication information, reference may be made to the relevant description at S306, which will not be repeated here.

Optionally, after S409, S410 may also be performed.

S410, the receiving network device requests the terminal device for the first report or requests the first report and the second report according to the above-mentioned indication information.

S411, the receiving network device processes the received report.

It can be understood that S410 and S411 are similar to S307 and S308 respectively, and the relevant descriptions of the foregoing embodiments can be further referred to, and details are not repeated here.

As shown in FIG. 5 , an embodiment of the present application also provides a communication method for a DAPS HO scenario. It can be understood that this communication method may also be called a connection failure information processing method. The method can include:

S501, before the terminal device successfully performs the handover to the DAPS target cell, it detects a connection failure.

The connection failure may be referred to as the first connection failure. For the first connection failure, further reference may be made to the relevant description applicable to the DAPS HO scenario in S301, which will not be repeated here.

S502, the terminal device records connection failure information.

S503, the terminal equipment continues to perform handover to the DAPS target cell, and judges whether HOF is detected.

After detecting the failure of the first connection, the terminal device can continue to perform the handover to the DAPS target cell, that is to say, continue to perform the DAPS HO procedure. In the process of continuing to perform the handover process, if the terminal device detects the HOF, S504 may be performed, and if the terminal device successfully establishes a connection with the DAPS target cell, S505 may be performed.

S504, the terminal device records the connection failure information corresponding to the HOF.

The connection failure information corresponding to the HOF is the reoccurring connection failure information (second connection failure information). Related descriptions of the second connection failure information in the foregoing embodiments. After S504, S508 may be performed.

S505, the terminal device starts a second timer.

Optionally, after S505, S506 may be performed.

S506, during the running of the second timer, the terminal device determines that the connection failure is detected again.

If the terminal device detects that the second connection fails during the running of the second timer, S507 may be performed.

If the terminal device does not detect the connection failure again during the running of the second timer, it means that the terminal device can access normally. Then, when the second timer expires, S508 may be performed.

S507, the second timer is stopped, and the terminal device records the connection failure information of the second connection failure.

When the terminal device detects that the second connection fails, the terminal device stops the second timer. In addition, the terminal device records connection failure information (second connection failure information) corresponding to the second connection failure. For the operation mechanism of the second timer, further reference may be made to the related description of the embodiment in FIG. 3 .

Similarly, for other scenarios in which the second timer is stopped, reference may also be made to the relevant description of the embodiment in FIG. 3 , which will not be repeated here.

For any scenario where the second timer is stopped, the terminal device may continue to perform S508. S508: The terminal device sends indication information, where the indication information indicates that the terminal device stores connection failure information or that the terminal device stores the first connection failure information and the second connection failure information.

Optionally, after S508, S509 may also be executed.

S509, the receiving network device requests the terminal device for the first report or requests the first report and the second report according to the above-mentioned indication information.

S510, the receiving network device processes the received report.

It can be understood that S509 and S510 are respectively similar to S307 and S308, and the relevant descriptions of the foregoing embodiments may be further referred to, and details are not repeated here.

In some possible implementation manners, for the embodiments shown in FIG. 4 and FIG. 5 , the terminal device may select different ways to process the connection failure information according to different scenarios. Correspondingly, the network device will also process the connection failure information according to the received connection failure information. to be processed. With the embodiment shown in FIG. 4 or FIG. 5 , the probability of the terminal equipment starting the second timer can be reduced. For example, after a connection failure occurs and the connection with the CHO or DAPS HO target cell is successfully established, the terminal equipment starts the second timer. The second timer is not started in other scenarios, thereby reducing the implementation complexity of the terminal device and reducing unnecessary energy consumption of the terminal device.

It should be noted that, in the above-mentioned embodiment of FIG. 3-5, the maximum number of connection failures in one mobility process is 2 for illustration, and the case where the maximum number of connection failures is greater than 2 is similar, except that the terminal device records and sends the data. More connection failure information, and the second timer stops running at the Mth connection failure. Optionally, in any of the above-mentioned embodiments of FIG. 3 to FIG. 5 , after the second timer stops or expires, if the terminal device detects a new connection failure, then the terminal device can delete the currently stored connection failure information and record it. For the connection failure information corresponding to the new connection failure, the new connection failure may be regarded as the first connection failure and the subsequent steps of detecting the first connection failure as in the previous embodiments are performed.

In the above-mentioned embodiment of FIG. 3-FIG. 5, by setting a timer in the terminal device to realize the recording and reporting of connection failure information for multiple times, it is also possible to realize multiple times in a mobility process (for example, the first handover process) through the behavior of the network device. Recording and reporting of connection failure information, as shown in FIG. 6 , an embodiment of the present application further provides a communication method, and it can be understood that the communication method may also be called a connection failure information processing method. Optionally, the method may be implemented independently, or may be combined with the manner in which the terminal device stores the first report in any of the embodiments in FIGS. 3-5 , and the method may include:

S601, the terminal device detects that the connection fails.

Wherein, S601 is similar to S301, and reference may be made to the relevant description in the embodiment of FIG. 3, which will not be repeated here.

S602, the terminal device records connection failure information.

Correspondingly, the connection failure information recorded in this step may be referred to as the first connection failure information, and may also be referred to as the first connection failure information.

In some possible implementation manners, the terminal device may report the first connection failure information through the first report. In the case of subsequent connection failures, the connection failure information in the same mobility process may be reported through the first report or other reports.

S603: The terminal device sends indication information indicating that the first connection failure information is stored to the network device.

After the terminal device successfully establishes a connection to the current serving cell (accessing the network device), it can send indication information indicating that it stores the first connection failure information to the network device (receiving network device) to which the current serving cell belongs.

Optionally, if there is a second timer running on the side of the terminal device as in the previous embodiment, the terminal device may send to the network device, in addition to the indication information indicating that the first connection failure information is stored, to the network device to indicate that the second timer is stored. Information that the timer is running, and/or, the terminal device may send the current running duration information of the second timer to the network device. If the terminal device just sends the second timer duration information (current running duration and/or remaining duration) to the network device, it may be understood that the terminal device implicitly indicates to the network device that the second timer is running.

S604, the receiving network device determines the access type.

It can be understood that this step may also be referred to as the receiving network device determining (identifying) a handover type or an access method for the terminal device to access the receiving network device.

If the receiving network device determines that the access type is CHO or DAPS HO, S605 may be executed; for example, if the terminal device performs CHO configuration to access the receiving network device, the receiving network device determines that the access type of the terminal device accessing the receiving network device is CHO; or, for example, the terminal device performs DAPS HO configuration to access the receiving network device, and the receiving network device determines that the access type of the terminal device accessing the receiving network device is DAPS HO.

If the receiving network device determines that the access type does not belong to CHO or does not belong to DAPS HO, that is, non-CHO or non-DAPS HO (for example, the access mode of re-establishment, or the access mode of connection establishment), S606 may be performed.

It should be noted that S604 may be an optional step. If the terminal device sends the information indicating that the second timer is running and/or the current running duration information of the second timer to the network device, S604 may not be performed. Alternatively, the network device may determine the subsequent processing not by the access type, but by whether the information indicating that the second timer is running and/or the current running duration information of the second timer is received, for example, if the network device After receiving the information indicating that the second timer is running and/or the current running duration information of the second timer, S605 may be executed, if the network device receives the information indicating that the second timer is running and/or the current running duration of the second timer information about the running time, S606 can be executed.

S605: After the first time period arrives, the receiving network device requests the terminal device to obtain connection failure information.

The first duration may be preset, may be sent by the source network device to the receiving network device, or may be determined by the receiving network device according to the duration information of the second timer received from the terminal device. This application implements The example does not limit the time length and determination method of the first duration. That is to say, when the receiving network device determines that the access type is CHO or DAPS HO, it continues to wait for the first time period, and then requests the terminal device to obtain the connection failure information.

In addition, a third timer may be set, and the running duration of the third timer is the first duration. After the third timer expires, the receiving network device may request the terminal device to obtain connection failure information. The third timer may start to run after receiving the indication information indicating that the connection failure information is stored.

Optionally, if before the first time period arrives, the terminal device disconnects the connection with the receiving network device, then S606 and subsequent steps may not be performed, and the terminal device may send data to other networks different from the receiving network device. The device sends the indication information indicating that the connection failure information is stored and sends the connection failure information. This embodiment of the present application does not limit the terminal device to send the indication information indicating that the connection failure information is stored and the connection failure information to other network devices.

S606: Receive a request from the network device to the terminal device to obtain connection failure information.

After the receiving network device requests the terminal device to obtain the connection failure information, the terminal device may send the connection failure information to the receiving network device through the first report.

Optionally, after S605 or S606, S607 may be executed.

S607, the receiving network device processes the received report.

For the processing manner of the received report by the receiving network device, reference may be made to the relevant description at S308, and details are not repeated here.

It should be noted that, in the embodiments shown in FIG. 3 to FIG. 6 above, the interaction between the receiving network device and the target network device may be direct interaction or indirect interaction. The receiving network device can directly (through the interface between the base station and the base station, such as X2, Xn interface) or indirectly (through the interface between the base station and the core network device, such as the S1 or NG interface) to send the above-mentioned first report/second report to the target network device Some or all of the information reported. For example, the above information can be sent through at least one of the following messages: a failure indication (FAILURE INDICATION, RLF INDICATION) message of the X2/Xn interface, a handover report (HANDOVER REPORT) message, or an uplink RAN configuration transmission (UPLIKN RAN CONFIGURATION TRANSFER) message, downlink RAN configuration transfer (DOWNLIKN RAN CONFIGURATION TRANSFER) message, base station configuration transfer (eNB CONFIGURATION TRANSFER) message, core network equipment configuration transfer (MME CONFIGURATION TRANSFER) message.

As shown in FIG. 6A , another communication method for a CHO scenario provided by an embodiment of the present application, it can be understood that this communication method may also be called a connection failure information processing method. The method can include:

S601A, the terminal device detects that the first connection fails.

S602A, the terminal device records connection failure information.

In a possible implementation manner, the terminal device records the first connection failure information in a report variable, which may be, for example, varRLF-report.

S603A, the terminal device performs cell selection, and determines a target cell, so as to determine whether to continue to perform CHO.

After detecting the failure of the first connection, the terminal device will perform cell selection, and continue to try to access at least one other cell. In this embodiment of the present application, the selected cell for access attempt may be referred to as a target cell. If the target cell is a non-CHO cell, S608A may be executed. If the target cell is a CHO cell, the terminal device may perform CHO, that is, perform S604A.

S604A, the terminal device continues to execute CHO, and detects that a connection failure (second connection failure) occurs in the CHO cell.

S605A, the terminal device determines whether the cell corresponding to the second connection failure is a cell where the terminal device performs CHO execution, a cell related to CHO execution, or a cell for performing CHO recovery.

If the terminal device detects that the second connection fails, and the terminal device determines that the cell corresponding to the second connection failure is a cell where the terminal device performs CHO execution, a cell related to CHO execution, or a cell for CHO recovery, 606A can be performed;

If the terminal device detects that the second connection fails, and the terminal device determines that the cell corresponding to the second connection failure is not a cell where the terminal device performs CHO execution or is not a cell related to CHO execution or is not a cell for CHO recovery, 607A may be executed.

S606A, the terminal device records the second connection failure information.

The terminal device records the second connection failure information, and the terminal device does not delete the currently stored first connection failure information, that is, the terminal device records and saves the first connection failure information and the second connection failure information. This embodiment of the present application does not limit the manner in which the terminal device records and saves the first connection failure information and the second connection failure information. In a possible implementation manner, the first connection failure information and the second connection failure information may be recorded in the same report variable, which may be, for example, varRLF-report. Optionally, after S606A, S608A can also be executed.

S607A, the terminal device deletes the first connection failure information, and the terminal device records the second connection failure information.

It can be understood that this step can be understood as updating the first connection failure information. For example, the terminal device deletes or clears the first connection failure information in varRLF-report, and records the second connection failure information in the

varRLF-report.

In a possible implementation manner, the terminal device may use the second connection failure information as the first connection failure information and continue to perform the subsequent steps of detecting the first connection failure in this embodiment. Optionally, after S607A, S608A can also be executed.

S608A, the terminal device sends the recorded connection failure information to the network device (receiving network device).

For the manner in which the terminal device sends the connection failure information to the network device, reference may be made to the relevant descriptions of the foregoing embodiments.

For example, when the first connection failure information and the second connection failure information are stored, reference may be made to other descriptions in the embodiments of the present application for the manner in which the terminal device sends the connection failure information, which will not be repeated here. It may be: sending a first report, where the first report includes first connection failure information and second connection failure information; or sending a first report and a second report, where the first report includes first connection failure information, and the second The report includes second connection failure information. Optionally, the first report and the second report may be sent at the same time, or the first report and the second report may be sent sequentially according to the time sequence of failures. For example, the terminal device may send the first connection failure information and the second connection failure information to the network device through the first report.

S609A, the receiving network device processes the received report.

For this step, reference may be made to the relevant description at S308, which will not be repeated here.

In this embodiment of the present application, the terminal device can perform connection failure information according to whether the cell where the new connection failure occurs is the cell where the terminal device performs CHO execution, or whether it is a cell related to CHO execution, or whether it is a cell that performs CHO recovery. The processing can reduce the implementation complexity of the terminal device and reduce unnecessary energy consumption of the terminal device.

The apparatus for implementing the above method in the embodiments of the present application will be described below with reference to the accompanying drawings. Therefore, the above content can be used in subsequent embodiments, and repeated content will not be repeated. In order to implement the functions in the methods provided by the above embodiments of the present application, each network element or device may include a hardware structure and/or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module . Whether one of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

FIG. 7 is a schematic block diagram of a communication apparatus 700 according to an embodiment of the present application. The communication apparatus 700 may correspondingly implement the functions or steps implemented by the terminal device in the method embodiments shown in FIG. 3 to FIG. 6A. The communication apparatus 700 may be a terminal device or a component (for example, a chip or a circuit, etc.) applicable to the terminal device, or the communication apparatus 700 may be a chip system. In this embodiment of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

In some possible implementations, the communication apparatus may include a detection unit 710 , a processing unit 720 and a transceiver unit 730 .

Exemplarily, when used to implement the method of the embodiment shown in FIG. 3:

The detection unit 710 can be used to detect the first connection failure and record the first connection failure information corresponding to the first connection failure; the processing unit 720 can be used to start the second timer, and the sending unit is used to stop the second timer. Or after the timeout, the indication information storing the connection failure information is sent to the network device.

In some possible implementations, the detection unit 710 is further configured to detect the second connection failure and record the second connection failure information corresponding to the second connection failure during the running of the timer, and the processing unit 720 detects the second connection failure in the detection unit. On failure, stop the operation of the second timer.

In some possible implementation manners, the transceiver unit 730 is further configured to send the first report to the network device or send the first report and the second report to the network device according to the message received from the network device for requesting to obtain connection failure information.

In some possible implementations, the processing unit 720 may also be configured to stop the operation of the second timer in any of the following cases: the target cell selected after the terminal device performs cell selection is not the candidate cell configured in the CHO configuration information, or The terminal device cannot successfully access the DAPS target cell configured in the DAPS HO, or the target cell selected by the terminal device after performing cell selection is the candidate cell configured in the CHO configuration information, but the candidate cell configured in the CHO configuration information has been handed over. Failure, or the terminal device establishes a connection with the candidate cell configured in the CHO configuration information after performing cell selection, or is switched to another cell after the DAPS HO target cell is successfully accessed, or the terminal device enters the disconnected state from the connected state.

In some possible implementations, the transceiver unit 730 does not send the information indicating that the connection failure information is stored when the timer is still running (not stopped or timed out).

In some possible manners, the transceiver unit 730 may further indicate to the network device that the timing of processing the first report and the second report is the same, that is, to indicate to the network device to process the first report and the second report at the same time.

Exemplarily, when used to implement the method of the embodiment shown in FIG. 4:

The detection unit 710 can be used to detect the first connection failure, record the first connection failure information corresponding to the first connection failure, and the processing unit 720 can be used to continue to execute CHO, and the second connection failure is not HOF. , start the timer, and the transceiver unit 730 may be configured to send the indication information indicating that the connection failure information is stored after the timer stops or times out.

In some possible implementations, if the second connection failure is HOF, the processor 720 does not start the timer, and the detection unit 710 records the second connection failure information corresponding to the second connection failure.

In some possible implementations, if the target cell is not a CHO cell after the first connection fails, the processing unit 720 does not start the timer, and the transceiver unit 730 may be configured to send indication information indicating that the first connection failure information is stored.

Exemplarily, when used to implement the method of the embodiment shown in FIG. 5:

The detection unit 710 is configured to detect the first connection failure and record the first connection failure information corresponding to the first connection failure, the processing unit 720 is configured to continue to perform the handover of the DAPS target cell, and the second connection failure is not HOF In this case, a timer is started, and the transceiver unit 730 sends indication information indicating that the connection failure information is stored after the timer stops or times out.

In some possible implementation manners, if the second connection failure is HOF, the processing unit 720 does not start the timer, and the detection unit 710 is configured to record the second connection failure information corresponding to the second connection failure.

Exemplarily, when used to implement the method of the embodiment shown in FIG. 6A:

The detection unit 710 can be used to detect the first connection failure and record the first connection failure information corresponding to the first connection failure; the processing unit 720 can be used for the terminal device to perform cell selection, and determine the target cell, so as to determine whether to continue the execution CHO; the detection unit 710 detects that the second connection failure occurs in the CHO cell, and the processing unit 720 is used to determine whether the cell corresponding to the second connection failure is a cell where the terminal equipment performs CHO execution or is a cell related to CHO execution or is In a cell for CHO recovery, if the processing unit 720 determines that the cell corresponding to the second connection failure is a cell where the terminal equipment performs CHO execution, or a cell related to CHO execution, or a cell for CHO recovery, the second connection failure information is recorded and not. Delete the currently stored first connection failure information, if the processing unit 720 determines that the cell corresponding to the second connection failure is not a cell where the terminal equipment performs CHO execution or is not a cell related to CHO execution or is not a cell for CHO recovery, record the second connection failure information and delete the currently stored first connection failure information. Optionally, the transceiver unit 730 may also be configured to send the recorded connection failure information.

It should be understood that the detection unit 710 and the processing unit 720 in this embodiment of the present application may be implemented by at least one processor or a processor-related circuit component, and the transceiver unit 730 may be implemented by a transceiver or a transceiver-related circuit component or a communication interface. In addition, the foregoing units may be separated or integrated, which is not limited in this embodiment of the present application.

Optionally, the communication device 700 may further include a storage unit 740, the storage unit 740 may be used to store instructions or data, and the processing unit 720 may execute or read the instructions or data stored in the storage unit, so that the communication device implement the corresponding operation. Optionally, the storage unit 740 may be implemented by at least one memory.

It can be understood that, regarding the coupling between the units of the communication apparatus 700 and the specific implementation, reference may be made to the descriptions in the method embodiments, and details are not repeated here.

As shown in FIG. 8 , the communication apparatus 800 provided by the embodiment of the present application can implement the functions of the network device in the methods provided by the embodiments of FIG. 3 to FIG. 6A of the present application. The communication apparatus 800 may be a network device; or the communication apparatus 800 may also be an apparatus capable of supporting the network device to implement the corresponding functions in the methods provided in the embodiments of the present application; or the communication apparatus 800 may be a chip system. In this embodiment of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

The communication apparatus 800 may include a transceiving unit 810 and a processing unit 820 . Exemplarily, the transceiver unit 810 may be configured to receive information indicating that the first connection failure information is stored from the terminal device, the processing unit 820 may be configured to determine the access type of the terminal device accessing the network device, and the transceiver unit 810 may use to request the terminal device to obtain connection failure information according to the access type.

In some possible implementations, when the access type is conditional switching CHO or dual-activation protocol stack switching DAPS HO, then the transceiver unit 810 may request the terminal device to obtain connection failure information after the first time period arrives, and the processing unit 820 The first duration can be controlled by a timer.

In some possible implementations, when the access type does not belong to the conditional handover CHO or does not belong to the dual activation protocol stack handover DAPS HO, the transceiver unit 810 may directly request the connection failure information from the terminal device without waiting for the first duration.

The processing unit 820 in this embodiment of the present application may be implemented by at least one processor or a processor-related circuit component, and the transceiver unit 810 may be implemented by a transceiver or a transceiver-related circuit component or a communication interface. In addition, the foregoing units may be separated or integrated, which is not limited in this embodiment of the present application.

Optionally, the communication device 800 may further include a storage unit 830, the storage unit 1030 may be used to store instructions or data, and the processing unit 820 may execute or read the instructions or data stored in the storage unit, so that the communication device implement the corresponding operation. Optionally, the storage unit 830 may be implemented by at least one memory.

It can be understood that, regarding the coupling between the units of the communication apparatus 800 and the specific implementation, reference may be made to the descriptions in the method embodiments, and details are not repeated here.

In a possible implementation manner, the transceiver unit 810 may be configured to indicate the manner in which the first report and/or the second report is received to the first target network device or the third target network device, wherein the first target network device is the first target network device. The first report corresponds to the target network device, and the third target network device is the target network device corresponding to the second report. For example, the transceiver unit 810 indicates that the above-mentioned report is received in a DAPS HO or CHO scenario.

As shown in FIG. 9 , an embodiment of the present application further provides a communication apparatus 900, which may be used to implement or support the communication apparatus 900 to implement the functions of a network device or a terminal device in the methods provided by various embodiments of the present application. The communication device 900 includes at least one processor 910 and at least one memory 920 for storing program instructions and/or data. Memory 920 is coupled to processor 910 . The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. Processor 910 may cooperate with memory 920 . The processor 910 may execute program instructions and/or data stored in the memory 920 to cause the communication device 900 to implement the corresponding method. Optionally, at least one of the at least one memory may be included in the processor.

The communication apparatus 900 may also include a communication interface 930 for communicating with other devices through a transmission medium, so that the devices used in the communication apparatus 900 may communicate with other devices.

The specific connection medium between the communication interface 930 , the processor 910 , and the memory 920 is not limited in the embodiments of the present application. Exemplarily, in the embodiment of the present application, the memory 920, the processor 910, and the communication interface 930 are connected through a bus 940 in FIG. 9, and the bus is represented by a thick line in FIG. A schematic illustration is provided, which is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.

In this embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which may be implemented or executed The methods, steps, and logical block diagrams disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

In this embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random Access memory (random-access memory, RAM). Memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory in this embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and/or data.

The embodiments of the present application further provide a communication system, which is used to implement all or part of the steps of the foregoing method embodiments. For example, the communication system may include the above-mentioned terminal equipment. Optionally, the communication system may further include at least one network device.

Embodiments of the present application further provide a computer-readable storage medium, including instructions, which, when executed on a computer, cause the methods performed by the terminal device in the embodiments shown in FIG. 3 to FIG. 6A to be executed.

Embodiments of the present application further provide a computer-readable storage medium, including instructions, which, when executed on a computer, cause the method performed by the network device in the embodiment shown in FIG. 3 to FIG. 6A to be executed.

Embodiments of the present application also provide a computer program product, including instructions, which, when executed on a computer, cause the method performed by the network device or the terminal device in the embodiments shown in FIG. 3 to FIG. 6A to be executed.

It should be understood that the terms "system" and "network" in the embodiments of the present application may be used interchangeably. "At least one" means one or more, and "plurality" means two or more. "And/or", which describes the association relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, which can indicate: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural. The character "/" generally indicates that the associated objects are an "or" relationship. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a) of a, b or c may represent: a, b, c, a-b, a-c, b-c or a-b-c, wherein a, b, c may be single or multiple.

And, unless stated to the contrary, ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are not used to limit the order, sequence, priority, or importance of multiple objects. For example, the first timer and the second timer, just to distinguish the role.

It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, and may also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), ready-made Field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory mentioned in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (direct rambus RAM, DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, the memory (storage module) is integrated in the processor.

It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions described in accordance with the embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Drive (SSD)), and the like.

The above are only specific implementations of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes within the technical scope disclosed in the embodiments of the present application. Or alternatives, all should be covered within the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims

A method for processing connection failure information, characterized in that the method comprises:

Detecting a first connection failure, recording first connection failure information corresponding to the first connection failure, and starting a timer;

After the timer stops or times out, indication information indicating that connection failure information is stored is sent, wherein the connection failure information includes at least first connection failure information.
The method of claim 1, further comprising:

During the running of the timer, a second connection failure is detected;

Stop the timer, and record second connection failure information corresponding to the second connection failure.
The method according to claim 2, wherein the sending the indication information indicating that the connection failure information is stored comprises:

The indication information indicates that connection failure information is stored, or the indication information indicates that at least two connection failure information is stored, or the indication information includes information indicating that the first connection failure information is stored and indicating that the second connection failure information is stored. Information about the connection failure message.
The method according to claim 2 or 3, further comprising:

A first report is sent to the network device according to a message received from the network device for requesting to obtain connection failure information, where the first report includes first connection failure information and second connection failure information.
The method of claim 3, further comprising:

The first report and the second report are sent to the network device according to the message received from the network device requesting to obtain the connection failure information.
The method according to claim 5, wherein sending the first report and the second report to the network device according to a message received from the network device for requesting to obtain connection failure information, comprising:

receiving, from the network device, a first message requesting to obtain first connection failure information;

sending the first report and the information indicating that the second connection failure information is stored to the network device;

receiving, from the network device, a second message requesting to obtain the second connection failure information;

The second report is sent to the network device.
The method according to any one of claims 1-6, wherein the first connection failure occurs in a conditional switching CHO process or a DAPS HO process of the dual activation protocol stack switching.
The method according to claim 7, wherein the timer is stopped in any one of the following situations:

The target cell selected by the terminal device after performing cell selection is not the candidate cell configured in the CHO configuration information, or the terminal device cannot successfully access the DAPS target cell configured in the DAPS HO, or the target cell selected by the terminal device after performing cell selection is CHO The candidate cell configured in the configuration information, but the candidate cell configured in the CHO configuration information fails to handover, or the terminal device establishes a connection with the candidate cell configured in the CHO configuration information after performing cell selection, or successfully accesses the DAPS HO target cell After that, it is handed over to another cell, or the terminal device enters the disconnected state from the connected state.
A method for processing connection failure information, comprising:

receiving information indicating that the first connection failure information is stored from the terminal device;

determining the access type of the terminal device;

The terminal device is requested to acquire connection failure information according to the access type, where the connection failure information includes at least first connection failure information.
The method according to claim 9, wherein the requesting to the terminal device for obtaining connection failure information according to the access type comprises:

Determine that the access type is conditional handover CHO or dual activation protocol stack handover DAPS HO;

After the first time period arrives, request the terminal device to obtain the connection failure information.
The method according to claim 9 or 10, wherein the requesting the connection failure information from the terminal device according to the access type comprises:

Determine that the access type does not belong to conditional handover CHO or does not belong to dual activation protocol stack handover DAPS HO;

Request the connection failure information from the terminal device.
The method according to claim 10, wherein the first duration is determined according to information received from the source network device, or the first duration is preset, or the first duration is determined according to the terminal The time information indicated by the device is determined.
The method according to any one of claims 9-12, wherein the connection failure information is carried in the first report, and the method further comprises:

The first report is sent to the target network device, and a manner of receiving the first report is indicated, wherein the manner of receiving the first report includes conditional switching or dual-active protocol stack switching.
A communication device, characterized by being used for implementing the method according to any one of claims 1-8.
A communication device, characterized by being used for implementing the method according to any one of claims 9-13.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, which, when executed, causes the method according to any one of claims 1 to 13 to be executed .
A computer program product, characterized in that the computer program product comprises instructions which, when executed, cause the method of any one of claims 1-13 to be implemented.