Communication methods, apparatuses and systems

Abstract

The application discloses a communication method, device and system. In the method, in the case that multiple connection failures occur in a first switching process, a processing mode of connection failure information is determined according to a switching type of the first switching process, so that the terminal device can reasonably report the connection failure information, and then the network device can obtain more helpful connection failure information, and further use the connection failure information to formulate a reasonable mobility strategy and improve the mobility performance of the terminal device.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of mobile communication, and in particular to a communication method, device and system. BACKGROUND

[0002] Currently, in addition to the normal handover (legacy handover) process, there are dual active protocol stack (DAPS) handover and conditional handover (CHO). However, in a DAPS handover process, a CHO process, or a normal handover process with CHO configuration (for example, after the terminal device receives the CHO configuration, the UE receives the normal handover command, but the previously received CHO configuration is still valid), the terminal device may detect more than one connection failure. Currently, the terminal device records and reports the latest connection (or link) failure information in the radio link failure (RLF) report. However, the present inventors have found that the current RLF report processing method is not reasonable, thereby reducing the robustness of the mobility strategy. SUMMARY

[0003] The embodiments of the present application provide a communication method, device and system, which can make the processing of connection failure information more reasonable, thereby enabling the formulation of a reasonable mobility strategy and improving the mobility performance of the terminal device.

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

[0005] For example, the method can include detecting a first connection failure and recording first connection failure information corresponding to the first connection failure, detecting a second connection failure occurring after the first connection failure, and determining that the first connection failure and the second connection failure belong to a first handover process; determining a processing method for connection failure information according to a handover type of the first handover process, wherein the handover type includes conditional handover or dual active protocol stack handover.

[0006] Optionally, the method can further include sending the connection failure information to a network device.

[0007] In some possible implementation manners, if the switching type of the first switching procedure is dual active protocol stack switching, all or part of the information in the first connection failure information can be updated by the second connection failure information.

[0008] In some possible implementation manners, if the switching type of the first switching procedure is dual active protocol stack switching, and the second connection failure includes a first connection failure in the target cell, all or part of the information in the first connection failure information can be updated by the first connection failure in the target cell.

[0009] In some possible implementation manners, if the switching type of the first switching procedure is dual active protocol stack switching, and the first connection failure occurs in the target cell, the first connection failure information can not be updated or replaced by subsequent connection failure information.

[0010] In some possible implementation manners, if the switching type of the first switching procedure is conditional switching, the first connection failure information is retained, that is, the recorded first connection failure information is not updated or replaced.

[0011] Optionally, all or part of the information in the first connection failure information includes at least one of the following: a connection failure type, a failed primary cell identifier, a connection failure time, a time after the failure, a connection failure reason, location information, random access information, measurement results, and time information of receiving a CHO configuration to trigger CHO execution.

[0012] By the above method, the terminal device can reasonably report the connection failure information, and the network device can obtain more helpful connection failure information, which is further used to formulate a reasonable mobility strategy and improve the mobility performance of the terminal device.

[0013] In a second aspect, a communication method, or a connection failure information processing method, is provided. It can be understood that the method of the second aspect can be executed by a second device, which can be a terminal device or a communication device, such as a chip or a circuit or a chip system, capable of supporting functions required by the terminal device to implement the method. The method can not limit the number of connection failure information recorded by the terminal device, that is, the terminal device records and saves at least one connection failure information in a switching procedure. The method includes detecting at least one connection failure, which belongs to a first switching procedure, and recording and saving connection failure information corresponding to each connection failure. The method can further include sending the connection failure information to a network device.

[0014] In a third aspect, a communication method, or also called a connection failure information processing method, is provided. It can be understood that the method of the third aspect can be executed by a third device, which can be a network device or a communication device, such as a chip or a circuit or a chip system, capable of supporting the network device to implement the functions required by the method. The method can include: receiving, from a terminal device, connection failure information of at least one connection failure, the at least one connection failure belonging to a first handover procedure; and determining a first cell according to a number of connection failure information of the first handover procedure in the received connection failure information.

[0015] Optionally, the method can further include: sending the received connection failure information to a network device to which the first cell belongs. In some possible implementation manners, the network device to which the first cell belongs and the network device that receives the connection failure information are the same network device, and thus the step of sending the received connection failure information to the network device to which the first cell belongs can not be executed.

[0016] In some possible implementation manners, if the number of connection failure information in the first handover procedure is 1, the first cell can be further determined according to a failure type of the connection failure information. For example, when the failure type is a handover failure, a cell corresponding to a previous primary cell identifier can be determined as the first cell; for another example, when the failure type is a conditional handover or a timer timeout, a cell corresponding to a failure primary cell identifier can be determined as the first cell.

[0017] In some possible implementation manners, when the number of connection failure information in the first handover procedure is greater than 1 (i.e., at least two connection failures occur), the first cell can be further determined according to a handover type of the first handover procedure, the handover type including a conditional handover or a dual active protocol stack handover. For example, if the handover type is a conditional handover, the first cell is determined according to a failure type corresponding to a first connection failure; for another example, if the handover type is a dual active protocol stack handover, the first cell is determined according to a failure type of a connection failure of a first target cell. The manner of determining the first cell according to the failure type is similar to that when the number of connection failure information is 1.

[0018] The method of the above second aspect or third aspect can make the terminal device report relatively comprehensive connection failure information, so that a serving network device can obtain more helpful information of connection failure, and further use the information to formulate a reasonable mobility strategy, and improve the mobility performance of the terminal device.

[0019] In a fourth aspect, a communication method, or also called a timing method in CHO, is provided. It can be understood that the method of the fourth aspect can be performed by a fourth device, which can be a terminal device or a communication device, such as a chip or a circuit or a chip system, capable of supporting the terminal device to implement the functions required by the method. The method can include: receiving conditional handover (CHO) configuration information, and starting a timer, wherein the timer includes a first timer and / or a second timer, the first timer is used to implement timing of triggering CHO execution based on the received CHO configuration, and the second timer is used to calculate or record a time from a last time of receiving a handover message to a connection failure; before the terminal device reaches an execution condition corresponding to the CHO configuration information, or before the terminal device performs time synchronization with a target cell, determining a processing manner of the timer according to whether a new handover message is received, wherein the new handover message includes a handover message carrying new CHO configuration information, a normal handover command, or a dual active protocol stack handover command. It can be understood that the restart time of the first timer and the second timer is similar, but the time information recording or stopping time of the timer can be different, and the first timer and the second timer can be implemented by one or more timers.

[0020] In some possible implementation manners, the timer is restarted in a case where the new handover message is received.

[0021] In some possible implementation manners, the first timer and / or the second timer can be cell-granular.

[0022] If the new handover message is received, and the new handover message is a handover message carrying new CHO configuration information, the new CHO configuration information includes information for updating configuration information of all or part of candidate cells in previous CHO configuration information, the first timer and / or the second timer corresponding to all or part of the updated candidate cells are restarted; if the new handover message is received, and the new handover message is a handover message carrying new CHO configuration information, the new CHO configuration information includes information indicating to delete configuration information of all or part of candidate cells in previous CHO configuration information, the first timer and / or the second timer corresponding to all or part of the candidate cells indicated to be deleted are deleted; if the new handover message is received, and the new handover message is a handover message carrying new CHO configuration information, the new CHO configuration information includes information indicating to add configuration information of a new candidate cell, the first timer and / or the second timer corresponding to the new candidate cell are added; if the new handover message is received, and the new handover message is a normal handover command or a dual active protocol stack handover command, the first timer and / or the second timer corresponding to all candidate cells are stopped.

[0023] In some possible implementation manners, the detecting whether a new handover message is received is not performed after the target cell is time-synchronized.

[0024] Optionally, the method of the fourth aspect can further include determining that a connection failure occurs in the target cell, and a running time length of the second timer is a time of the latest connection failure after the handover message is received. The connection failure includes a first connection failure after the conditional handover (CHO) configuration information is received and / or at least one connection failure after the first connection failure. That is, the time information of the latest connection failure after the handover message is received or multiple connection failures can be recorded.

[0025] By using the method, the time length information in the CHO process can be more accurately reflected, so that the network device can make a correct judgment on the mobility problem based on the information and determine a reasonable mobility strategy adjustment.

[0026] It can be understood that the method of the first aspect to the method of the fourth aspect can be implemented individually, or any one of the method of the first aspect to the third aspect can be combined with the method of the fourth aspect.

[0027] In a fifth aspect, a communication apparatus is provided, which has a function of implementing the behaviors or steps in the method of the first aspect. The communication apparatus can be a terminal device or a component (for example, a chip or a circuit) that can be used for a terminal device. The function 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 one possible design, the communication apparatus includes a detection unit and a processing unit. The detection unit can be used to detect a first connection failure and record a first connection failure time corresponding to the first connection failure, and detect a second connection failure occurring after the first connection failure. The processing unit can be used to determine a processing manner of the connection failure information according to a handover type of the first handover procedure. Optionally, the communication apparatus can further include a transceiver unit, which is used to send the connection failure information to a network device. Optionally, the transceiver unit can also be used to receive a handover message from the network device. Optionally, the communication apparatus can further include a storage unit, which can be used to store instructions and / or data. The modules / units can perform the corresponding functions in the method examples of the first aspect, and details are described in the method examples, which are not described herein.

[0028] In a sixth aspect, a communication apparatus is provided, which has the function of implementing the behaviors or steps in the method of the second aspect. The communication apparatus can be a terminal device or a component (e.g., a chip or circuit) for a terminal device. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the communication apparatus includes a detection unit and a processing unit. The detection unit can be configured to detect at least one connection failure, which belongs to the first handover procedure. The processing unit can be configured to record and save connection failure information corresponding to each connection failure. Optionally, the communication apparatus can further include a transceiver unit, configured to send the connection failure information to a network device. Optionally, the transceiver unit can also be configured to receive a handover message from the network device. Optionally, the communication apparatus can further include a storage unit, configured to store instructions and / or data. The modules / units can perform the corresponding functions in the method examples of the second aspect, and details are not described herein again.

[0029] In a seventh aspect, a communication apparatus is provided, which has the function of implementing the behaviors or steps in the method of the third aspect. The communication apparatus can be a network device or a component (e.g., a chip or circuit) for a network device. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the communication apparatus includes a transceiver unit and a processing unit. The transceiver unit is configured to receive, from a terminal device, connection failure information of at least one connection failure, which belongs to the first handover procedure. The processing unit is configured to determine a first cell according to the number of connection failure information in the first handover procedure in the received connection failure information. Optionally, the transceiver unit can also be configured to send the received connection failure information to a network device to which the first cell belongs. Optionally, the communication apparatus can further include a storage unit, configured to store instructions and / or data. The modules / units can perform the corresponding functions in the method examples of the third aspect, and details are not described herein again.

[0030] In an eighth aspect, a communication apparatus is provided. The communication apparatus has the functions of implementing the steps or behaviors in the method of the fourth aspect. The communication apparatus can be a terminal device or a component (e.g., a chip or circuit) for 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 functions described above. In one possible design, the communication apparatus includes a transceiver and a processing unit. The transceiver is configured to receive the conditional handover (CHO) configuration information. The processing unit starts a timer after the transceiver receives the CHO configuration information. The processing unit is configured to determine a processing manner of the timer according to whether a new handover message is received before the terminal device meets an execution condition corresponding to the CHO configuration information, or before the terminal device performs time synchronization with a target cell. Optionally, the communication apparatus can further include a storage unit configured to store instructions and / or data. The modules / units can perform the corresponding functions in the method examples of the fourth aspect. For details, refer to the descriptions of the method examples, which are not repeated here.

[0031] In a ninth aspect, a communication apparatus is provided. The communication apparatus can be a communication apparatus implementing any one of the methods of the first aspect to the fourth aspect. The communication apparatus includes a processor and a memory. The memory is configured to store computer programs or instructions or data. The processor is coupled to the memory. When the processor reads the computer programs or instructions or data, the processor causes the communication apparatus to perform the method of any one of the aspects. Optionally, the communication apparatus can further include a communication interface.

[0032] For example, the communication interface can be a transceiver in the communication apparatus. The transceiver can be configured to communicate with other devices.

[0033] In a tenth aspect, a chip system is provided. The chip system includes a processor configured to implement any one of the methods of the first aspect to the fourth aspect. In one possible design, the chip system further includes a memory configured to store program instructions and / or data. The chip system can be composed of a chip, or can include a chip and other discrete devices.

[0034] In an eleventh aspect, a communication system is provided. The system includes one or more of the communication apparatuses of the fifth aspect to the eighth aspect.

[0035] In a twelfth aspect, a computer program product is provided. The computer program product includes computer program codes. When the computer program codes are executed, any one of the methods of the aspects described above is performed.

[0036] In a thirteenth aspect, the present application provides a computer readable storage medium, which stores a computer program, when the computer program is executed, causes any method in the above aspects to be implemented. BRIEF DESCRIPTION OF DRAWINGS

[0037] Figure 1 An architecture diagram of a communication system for the embodiments of the present application;

[0038] Figure 2 An example diagram of a possible scenario of connection failure in the CHO procedure of the embodiments of the present application;

[0039] Figure 3 A flowchart of an example of the communication method provided by the embodiments of the present application;

[0040] Figure 4 A flowchart of an example of the communication method provided by the embodiments of the present application;

[0041] Figure 5 A flowchart of an example of the communication method provided by the embodiments of the present application;

[0042] Figure 6 An example of timing provided by the embodiments of the present application;

[0043] Figure 7 A flowchart of an example of the communication method provided by the embodiments of the present application;

[0044] Figure 8 An example of timing provided by the embodiments of the present application;

[0045] Figure 9 A structure diagram of the communication device provided by the embodiments of the present application;

[0046] Figure 10 A structure diagram of the communication device provided by the embodiments of the present application;

[0047] Figure 11 A structure diagram of the communication device provided by the embodiments of the present application;

[0048] Figure 12 A structure diagram of the communication device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0049] 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 part of the embodiments of the present application, not 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 labor fall within the scope of protection of the present application.

[0050] The technical solutions of the embodiments of the application described below can be applied to a network architecture as shown in the figure, wherein, Figure 1 Figure 1 This is only an example of a communication system, which can include at least one terminal device and at least one network device, Figure 1 For example, including 1 terminal device and 2 network devices, terminal device 1 can be handed over from network device 1 to network device 2. It can be understood that, Figure 1 The number of terminal devices in and is only an example, and there can be more terminal devices and network devices in the communication system, and any network device can provide services for terminal devices within the coverage range.

[0051] ​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 (for example, a communication module or a chip system) built in the above devices. The terminal device is used to connect people, things, machines, etc., and can be widely used in various scenes. It can also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in an internet of things (IoT) system, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a vehicle-mounted communication device, a vehicle-mounted communication processing chip, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN), etc. It should be understood that the specific form of the terminal device is not limited in the present application.

[0052] The network device can be an access network device, which can also be referred to as a radio access network (RAN) device, and refers to a device in the access network that communicates over the air interface through one or more sectors with wireless terminals, and can also be considered as a device that provides a wireless communication function for a terminal device. The access network device includes, for example, but is not limited to: a next generation nodeB (gNB) in 5G, an evolved node B (eNB), a baseband unit (BBU), a transmitting and receiving point (TRP), a transmitting point (TP), a base station in a future mobile communication system, or an access point in a WiFi system, etc. The access network device can also be a wireless controller in a cloud radio access network (CRAN) scenario, a centralized unit (CU), and / or a distributed unit (DU), or the network device can be a relay station, a vehicle-mounted device, and a network device in a future evolved PLMN network, etc.

[0053] The CU and the DU can be physically separated or deployed together. Multiple DUs can share one CU. One DU can also connect to multiple CUs. The CU and the DU can be connected through an interface, for example, an F1 interface. The CU and the DU can be divided according to protocol layers of a wireless network. For example, in one possible division, the CU can be configured to perform functions of a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, and a packet data convergence protocol (PDCP) layer, and the DU can be configured to perform functions of a radio link control (RLC) layer, a media access control (MAC) layer, and a physical layer. It can be understood that the division of the CU and the DU according to the protocol layers is merely an example, and the CU and the DU can also be divided in other manners. For example, the CU or the DU can be divided into more protocol layers. For example, the CU or the DU can also be divided into partial processing functions of the protocol layers. In one design, partial functions of the RLC layer and functions of protocol layers above the RLC layer are arranged in the CU, and remaining functions of the RLC layer and functions of protocol layers below the RLC layer are arranged in the DU. In another design, the functions of the CU or the DU can also be divided according to service types or other system requirements. For example, according to a delay requirement, functions that need to meet the delay requirement are arranged in the DU, and functions that do not need to meet the delay requirement are arranged in the CU. The network architecture shown in the above figure can be applied to a 5G communication system, and one or more components or resources of the network architecture can also be shared with an LTE system. In another design, the CU can also have one or more functions of a core network. One or more CUs can be arranged centrally or separately. For example, the CU can be arranged at a network side for centralized management. The DU can have multiple radio frequency functions, or the radio frequency functions can be arranged remotely.

[0054] 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 divided, for example, a control panel (CP) and a user panel (UP) are separated, that is, a CU control panel (CU-CP) and a CU user panel (CU-UP). For example, the CU-CP and the CU-UP can be implemented by different functional entities, and the CU-CP and the CU-UP can be coupled with the DU to jointly complete functions of an access network device.

[0055] The terminal device can communicate with access network devices of different technologies, for example, the terminal device can communicate with an access network device supporting long term evolution (LTE), can also communicate with an access network device supporting 5G, and can also communicate with both an access network device supporting LTE and an access network device supporting 5G at the same time. Embodiments of the present application are not limited.

[0056] Embodiments of the present application first briefly introduce CHO and DAPS HO.

[0057] I. DAPS HO

[0058] After the terminal device receives the handover message (e.g., handover command or RRC reconfiguration message) from the source network device, the terminal device maintains data transmission with the source network device, i.e., the terminal device maintains the user plane protocol stack corresponding to the source network device, does not perform layer 2 recovery / reestablishment on the user plane protocol stack corresponding to the source network device, and 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), and processes the received data packets according to whether the data packets are from the source network device or the target network device using the corresponding keys / header decompression contexts. After the terminal device completes access to the target network device, the terminal device continues data transmission (uplink and / or downlink data transmission) with the source 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; and the terminal device releases the connection with the source network device after receiving the release message sent by the target network device to release the connection between the terminal device and the source network device. Optionally, the process or signaling related to DAPS HO can be further referred to the description in 3GPP TS 38.300 V16.3.0 9.2.3.2. For example, in the DAPS HO, the scenario or process for detecting connection failure can include: before the terminal device successfully completes random access to the target network device, the terminal device continues to monitor (or detect) radio link failure (RLF) of the connection between the terminal device and the source network device; during the random access of the terminal device to the target network device, the terminal device can detect handover failure (HOF); and after the terminal device successfully completes random access to the target network device, the terminal device can monitor the radio link of the connection between the terminal device and the target network device to determine whether there is a radio link failure. In the embodiments of the present application, for ease of description, the command or message used to indicate DAPS HO can also be referred to as DAPS HO command. The cell accessed by the terminal device and belonging to the source network device is referred to as the source cell, and the cell accessed by the terminal device and belonging to the target network device is referred to as the target cell.

[0059] II. CHO

[0060] 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 can include information for indicating identification information of the candidate cell, and corresponding one or more handover triggering conditions (or also called execution conditions) and configuration information of the candidate cell. The information for indicating the identification information of the candidate cell can be CHO configuration identification or CHO candidate cell information. The cell information can be at least one of a cell global identifier (CGI), a physical cell identifier (PCI) and a frequency, a cell identifier (cell ID), a non-public network identifier (NPN ID), a non-terrestrial network identifier (NTN ID), or other cell identifiers. The CGI can include a public land mobile network (PLMN ID) and a cell ID.

[0061] After receiving the configuration information of the CHO, the terminal device determines whether each CHO candidate cell meets the handover triggering condition according to the configuration information, which can be understood as a normal CHO. If the CHO candidate cell meeting the handover triggering condition is used as a candidate target cell, the terminal device is switched from the source cell to the target cell.

[0062] 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 met, it can also be converted into a normal handover (normal HO or legacy HO), and the terminal device performs a handover process according to the normal handover command. It can be understood that at this time, the terminal device has available CHO configuration, and the handover type corresponding to this scenario can be called CHO. In the embodiments of the present application, each scenario in which the terminal device receives CHO configuration information and the CHO configuration information is not cleared can be called as the terminal device having available CHO configuration, for example, it can include a normal CHO or if the terminal device receives a handover command without CHO configuration before any CHO execution condition is met. In the embodiments of the present application, for convenience of description, the command or message with CHO configuration information can also be called CHO command, for example, the CHO command can be an RRC reconfiguration message.

[0063] When the terminal device has available CHO configuration, the terminal device detects connection failure, if the suitable cell selected by the terminal device is a CHO candidate cell, the terminal device can attempt CHO execution once; if the target cell selected by the terminal device is not a CHO candidate cell, the terminal device performs a re-establishment procedure; if the terminal device does not find a suitable cell within a period of time, the terminal device enters an idle state. It can be understood that if the terminal device attempts CHO execution once in the CHO procedure, and the terminal device detects connection failure again, regardless of whether the suitable cell selected by the terminal device is a target cell in the CHO candidate cell, the terminal device no longer attempts CHO execution, and optionally, the terminal device can perform a re-establishment procedure. It can be understood that the embodiments of the present application take the terminal device attempting CHO execution once after detecting connection failure for the first time in the CHO procedure as an example for illustration, and the terminal device can attempt CHO execution N times after detecting connection failure for the first time in the CHO procedure, N is a preset maximum number of times of CHO execution that can be attempted after detecting connection failure for the first time in the CHO procedure, and N is greater than or equal to 1.

[0064] It can be understood that in the embodiments of the present application, the message or command used to implement the handover configuration or the handover indication can also be collectively referred to as a handover message or a handover command.

[0065] Figure 2 An exemplary scenario in which connection failure occurs in the CHO procedure is given as follows: Figure 2 As shown in the figure, after the terminal device triggers a handover in the source cell, the terminal device first attempts to hand over to target cell B (T-cell B), connection failure occurs in T-cell B, the terminal device performs cell selection and selects a target cell C (T-cell C) in the CHO candidate cell, the terminal device attempts to hand over to T-cell C again, and connection failure also occurs in the target cell T-cell C, and the CHO procedure ends. The above connection failure can include HOF, RLF or failure caused by expiration of a timer. Here, T-cell B can be referred to as the first target cell in the CHO procedure. If the prior art is followed, the RLF report finally recorded by the terminal device for this CHO procedure is connection failure information occurring in T-cell C, however, the inventors of the present application have found that for CHO, the first target cell is the first cell selected by the terminal device for access based on factors such as coverage, and the successful access to the first cell is more important to the terminal device, and therefore the connection failure information occurring in T-cell B is more meaningful for adjustment of the mobility strategy. It can be understood that for the legacy HO procedure with CHO configuration, the scenario as shown in Figure 2The illustrated scenario. In addition, there are also multiple failures in other CHO scenarios. For example, the terminal device performs CHO attempt at most once after detecting the first connection failure: the terminal device receives CHO configuration, does not trigger CHO handover, and detects connection failure between the terminal device and the source network device; the terminal device determines to perform cell selection, and selects a target cell B (T-cell B) in the CHO candidate cell, the terminal device performs CHO to T-cell B, and the terminal device can detect connection failure between the terminal device and T-cell B.

[0066] For the DAPS HO procedure, there can also be more than one connection failure in one DAPS HO procedure, for example, the terminal device receives a DAPS HO command in the source cell, detects connection failure (e.g., RLF) between the terminal device and the source cell, and continues to perform DAPS HO between the terminal device and the target cell. The terminal device detects connection failure (e.g., HOF or RLF) between the terminal device and the target cell.

[0067] In the embodiments of the present application, the procedure from the start of switching by the terminal device to the successful access to the target cell or the transition to other non-connected state can be referred to as one-time switching procedure (or one-time switching process). CHO, DAPS HO, normal switching (which can be referred to as normal HO or legacy HO) and the like are understood as different switching types. For the CHO scenario, the occasion when the source network device base station sends the CHO configuration information can be considered as the start of switching, for the DAPS HO scenario, the occasion when the source network device sends the DAPS HO command to the terminal device can be considered as the start of switching, and for the normal switching, the occasion when the source network device sends the switching command to the terminal device can be considered as the start of switching.

[0068] To solve the problem of how to reasonably record the RLF report in the case of more than one connection failure in one-time switching procedure (first switching procedure), the present application provides a communication method, which can also be called a connection failure information processing method. As shown in Figure 3 The communication method comprises:

[0069] S301, the terminal device detects a connection failure.

[0070] It can be understood that in the embodiment, the connection failure can be referred to as a first connection failure. The terminal device detecting the connection failure can be that the terminal device receives a CHO configuration, a CHO execution condition is not triggered, the terminal device detects a connection failure between the terminal device and a source cell, such as RLF or a failure triggered by expiration of a timer; or the terminal device receives a CHO configuration, a CHO execution condition is triggered or a normal handover command is received, and the terminal device detects a connection failure between the terminal device and a target cell, such as HOF or RLF; or the terminal device receives a DAPS HO command and detects a connection failure between the terminal device and the source cell, such as RLF.

[0071] After starting the handover procedure and before ending the handover procedure, a connection failure of the terminal device in the source cell or the target cell can occur. If the terminal device determines that the connection failure is detected, S302 can be performed. The connection failure detected in S301 can be referred to as a first connection failure. If the terminal device does not detect the connection failure, it means that the terminal device can normally complete the handover procedure.

[0072] S302, the terminal device records connection failure information.

[0073] Correspondingly, the connection failure information recorded in this step can be referred to as first connection failure information, or first connection failure information.

[0074] In the case that the terminal device detects the connection failure, the terminal device records and saves the connection failure information.

[0075] As an example, the connection failure information can include at least one of the following information:

[0076] 1) failedPCellId: the information of a primary cell in which the terminal device detects RLF or expiration of a first timer, or the information of a target primary cell in which HOF occurs. The first timer can be a timer started by the terminal device after sending a measurement report. If the terminal device has not received a handover command after the timer expires, it can be considered that a connection failure occurs, such as T312

[0077] Optionally, the failedPCellId can not be included in the failure information, but a failedCellId can be included. The failedCellId is the information of a cell in which the terminal device detects a link failure or expiration of a first timer, or the information of a target cell in which a handover failure occurs, which is not limited in the embodiment of the application.

[0078] 2) connectionFailureType.

[0079] As an example, the connection failure type can be RLF or HOF or expiry of a first timer. The connection failure type can also be referred to as failure type.

[0080] 3) previous PCell ID (previousPCellId): information of a previous PCell where the terminal device last received a handover command.

[0081] Optionally, the failure report can not include the previous PCell ID (previousPCellId) but include a previous cell ID (previousCellId). The previous cell ID is information of a previous cell where the terminal device last received a handover command, which is not limited in the embodiments of the present application.

[0082] 4) reestablishment cell ID (reestablishmentCellId): information of a cell where reestablishment is attempted after connection failure.

[0083] 5) connection failure time (timeConnFailure): length of time from when a handover command (or reconfiguration message) is last (or most recently) received to connection failure.

[0084] 6) time since failure (timeSinceFailure): length of time recorded since connection failure. Generally refers to length of time from connection failure to reporting of the failure report.

[0085] 7) connection failure cause (rlf-Cause): the connection failure cause can include HOF, RLF, reconfiguration synchronization failure, NR handover failure to other system, integrity check failure, or RRC connection reconfiguration failure.

[0086] 8) location information (locationInfo): information of a location where the terminal device experiences connection failure.

[0087] 9) random access information (ra-InformationCommon): information of random access performed by the terminal device in the cell.

[0088] 9) measurement result: measurement result of a cell and / or beam, which can include measurement result of a serving cell and / or neighbor cell.

[0089] 10) time information of receiving CHO configuration to triggering CHO execution (timeCHOcfgExe)

[0090] The connection failure information in the embodiments of the present application can also be referred to as link failure information.

[0091] S303, the terminal device determines that the connection failure is detected again.

[0092] After detecting the first connection failure, the terminal device continues to attempt to access in other at least one cell, such as a selected suitable cell as a CHO candidate cell, and the terminal device can attempt CHO execution; or continue to attempt handover between the target cell of DAPS HO.

[0093] It can be understood that, on the basis of the first connection failure, at least one connection failure may occur again, which can be referred to as a second connection failure in the embodiments of the present application. If the terminal device detects the connection failure again, S304 is executed. If the terminal device does not detect the connection failure again, it means that the terminal device can normally access.

[0094] S304, the terminal device determines the processing mode of the connection failure information according to the handover type.

[0095] It should be noted that the embodiments of the present application are described by determining the processing mode of the connection failure information according to the handover type, which can be replaced, and can also be referred to as determining the processing mode of the connection failure information according to whether there is an available CHO configuration.

[0096] It can be understood that, if the terminal device has an available CHO configuration, the terminal device can determine that the handover type is CHO. If the terminal device receives a DAPS HO command, the terminal device can determine that the handover type is DAPS HO. Wherein, the terminal device has an available CHO configuration includes a scenario in which the terminal device only receives a CHO configuration, and a scenario in which the terminal device receives a CHO configuration before the CHO execution condition is met. The terminal device receives a normal handover command.

[0097] The terminal device can determine the handover type of the first handover process when the terminal device detects the connection failure again, i.e., the terminal device detects the second or more connection failures, and determine the processing mode of the recorded connection failure information according to the result of the determination.

[0098] If the terminal device determines that the handover type is DAPS HO, the processing mode of the connection failure information of the terminal device can be the following mode A or B.

[0099] Mode A: the terminal device updates (or replaces) all or part of the information based on the previous connection failure information, that is, the terminal device uses the re-connection failure information to update (replace) all or part of the connection failure information recorded currently. It can be understood that the re-connection failure may occur more than once. According to this mode, no matter how many times the re-connection failure occurs, the last connection failure information is used to replace all or part of the previous connection failure information. It can be understood that the terminal device saves the last connection failure information. Or,

[0100] Mode B: in the case of DAPS HO, the terminal device can also process the connection failure information as follows: the terminal device finally retains (saves) the first connection failure information in the target cell. Mode B includes: (1) the first connection failure occurs in the source cell, and at least one of the subsequent re-connection failures occurs in the target cell. The terminal device updates or replaces all or part of the previous connection failure information (for example, the connection failure information in the source cell) with the first connection failure information in the target cell. Optionally, the subsequent connection information in the target cell other than the first time can not be monitored or used to update the first connection failure information in the target cell; (2) the first connection failure occurs in the target cell. After recording the first connection failure information, the terminal device can not update or replace the first connection failure information with the subsequent connection failure information. Optionally, the subsequent connection information in the target cell other than the first time can not be monitored or used to update the first connection failure information in the target cell. The above-mentioned mode B can also be understood as that when the handover type is DAPS HO, the terminal device further determines the processing of the connection failure information according to whether the first connection failure occurs in the source cell. For example, when the handover type is DAPS HO, the terminal device detects the first connection failure and records the first connection failure information. The terminal device detects the connection failure (or the second connection failure) between the terminal device and the first target cell (i.e., the first target cell that the terminal device attempts to connect to). If the terminal device determines that the first connection failure occurs in the source cell, the terminal device can update or replace all or part of the connection failure information in the first connection failure information with the second connection failure information. If the first connection failure occurs in the first target cell, the terminal device retains the first connection failure information.

[0101] For example, the above-mentioned all or part of the connection failure information that can be updated or replaced can include at least one of the following: connection failure type, failed primary cell identifier, connection failure time, time after failure, connection failure reason, location information, random access information, measurement result, time information from receiving CHO configuration to triggering CHO execution.

[0102] If the terminal device judges that the switching type is CHO, the terminal device can process the connection failure information in the following way: the terminal device keeps the first recorded connection failure information, that is, the terminal device does not update the recorded first connection failure information. It can be understood that the reoccurring connection failure can occur more than once. According to the way, no matter how many times the reoccurring connection failure occurs, the first connection failure information is kept (or saved). Alternatively, the terminal device can not record the connection failure information occurring later. For example, when the switching type is CHO, the terminal device detects the first connection failure, the terminal device records the first connection failure information, and the second connection failure occurs again, the terminal device does not update the first connection failure information with the second connection failure information.

[0103] It can be understood that for normal switching, the connection failure information is generally included in one switching procedure.

[0104] Alternatively, after the terminal device processes the connection failure information according to S304, the communication method of the embodiment of the application can further include the following steps.

[0105] S305, the terminal device sends an RLF report.

[0106] When the terminal device completes access to the current network device, the terminal device can send all or part of the currently stored connection failure information to the currently accessed network device in the form of an RLF report. The serving network device here can be the network device to which the target cell in the reestablishment or connection establishment procedure belongs, or the network device to which the target cell in the switching procedure belongs, or other network devices having a wireless resource connection with the terminal device. In the embodiment of the application, the network device receiving the RLF report can be referred to as a receiving network device. The receiving network device can process different according to the content of the RLF report, that is, perform S306.

[0107] It can be understood that the embodiment of the application sends part or all of the currently stored connection failure information to the currently accessed network device in the form of an RLF report, which is only an example, and does not limit the report form of the stored connection failure information sent by the terminal device.

[0108] S306, the receiving network device processes according to the content of the received RLF report.

[0109] The receiving network device can determine the first target network device forwarding the RLF report according to the received connection failure information. As an example, if the connection failure type in the RLF report is HOF, the receiving network device can determine the network device to which the cell corresponding to the "previous primary cell identifier" belongs as the first target network device, and optionally, the first target network device can further perform corresponding processing according to the RLF report, thereby improving the mobility robustness.

[0110] If the connection failure type in the RLF report is RLF or the first timer expires, the receiving network device can determine the network device to which the cell corresponding to the "failure primary cell identifier" belongs as the first target network device, and optionally, the first target network device can further perform corresponding processing according to the RLF report, thereby improving the mobility robustness. Optionally, the first target network device can further determine whether the RLF report needs to be forwarded to the network device to which the cell corresponding to the "previous primary cell identifier" belongs (which can be referred to as the second target network device), and if so, the first target network device can send the RLF report to the network device to which the cell corresponding to the "previous primary cell identifier" belongs. For example, the first target network device determines that the first time at which the terminal device performs handover to the cell detecting the connection failure between the failure primary cell is less than or equal to a certain threshold, and the first target network device can send the RLF report to the network device to which the cell corresponding to the "previous primary cell identifier" belongs.

[0111] It can be understood that when the first target network device and the receiving network device are the same network device, the forwarding can not be performed, and the receiving network device can perform corresponding processing according to the RLF report, or the first target network device and the second target network device are the same network device, the forwarding can not be performed, and the first target network device can perform corresponding processing according to the RLF report, thereby improving the mobility robustness.

[0112] The embodiments of the present application do not limit the processing process and manner of the network device to the RLF report, for example, it can be to adjust the mobility parameter according to the information in the RLF report and / or perform operations such as determining whether the first target network device sends the RLF report to the network device to which the cell corresponding to the "previous primary cell identifier" belongs according to the connection failure time.

[0113] The communication method of the embodiments of the present application determines the processing manner of the connection failure information according to the switching type, so that the terminal device can reasonably report the connection failure information, and the network device can obtain more helpful connection failure information to further formulate a reasonable mobility strategy and improve the mobility performance of the terminal device.

[0114] The embodiments of the present application also provide a communication method (which can be understood as a connection failure information processing method), which can not limit the number of connection failure information recorded by the terminal device, that is, the terminal device records and saves at least one connection failure information in a switching process, as shown in the following Figure 4 The method can include the following steps.

[0115] S401, the terminal device detects at least one connection failure and records the information of the at least one connection failure.

[0116] For the scenario of the embodiments of the present application, the terminal device detects at least one connection failure in a switching process (switching process A), and the scenario in which the terminal device detects more than or equal to two connection failures can refer to the related description of the embodiments shown in the following Figure 3

[0117] Unlike the prior art which only records the information of the last connection failure, in the embodiments of the present application, the terminal device records and saves the connection failure information of each connection failure in a switching process. The content of the connection failure information can refer to the related description of the previous embodiments, which will not be described here.

[0118] S402, the terminal device sends the saved connection failure information to the serving network device.

[0119] When the terminal device completes access to the serving network device, it will send all or part of the saved connection failure information to the serving network device. For example, the terminal device can send all or part of the connection failure information to the serving network device in the form of RLF report, and the RLF report includes the recorded connection failure information of at least one connection failure. Optionally, the connection failure information of the at least one connection failure can be arranged in the RLF report in the time order (ascending or descending) of the occurrence of the connection failure. It can be understood that the embodiments of the present application send part or all of the currently stored connection failure information to the currently accessed network device in the form of RLF report, which is only an example and does not limit the report form of the stored connection failure information sent by the terminal device.

[0120] ​Correspondingly, the serving network device receives the connection failure information sent by the terminal device, and performs S403. It can be understood that the connection failure information sent by the terminal device can include at least one connection failure information in the handover process A. For multiple connection failure information, it can be sent to the serving network device through one message or multiple messages.

[0121] S403, the serving network device determines the first cell according to the number of connection failure information in the handover process A in the received connection failure information.

[0122] The first cell is the object to which the serving network device determines to forward the connection failure information.

[0123] Optionally, the serving network device can determine the connection failure information belonging to the handover process A in the received connection failure information, and determine the first cell according to at least the number of connection failure information belonging to the handover process A. It can be understood that the number of connection failure information corresponding to one connection failure is 1, and the number of connection failure information corresponds to the number of connection failures in one handover process. For example, three connection failures occur in one handover process, and the number of connection failure information is 3.

[0124] When the first cell is determined, the serving network device can further determine a network device corresponding to the first cell (or a network device to which the first cell belongs), which can be referred to as a first target network device in embodiments of the present application. The serving network device can also be referred to as a receiving network device. The first target network device and the receiving network device can be different network devices, or can be the same network device. If the first target network device and the receiving network device are the same network device, the forwarding process can not be performed, and the first network device (or the serving network device) can perform corresponding processing on the connection failure information. If the first target network device and the serving network device are different network devices, the serving network device can forward the connection failure information (or RLF report) to the first target network device for corresponding processing. When the serving network device determines that the number of connection failure information received in this handover process is 1, the serving network device can further determine what the failure type is. Different failure types can result in different first cells. For example, when the connection failure type is HOF, the receiving network device can determine the cell corresponding to the previous primary cell identifier as the first cell, and the network device to which the first cell belongs is the first target network device. Optionally, the first target network device can further perform corresponding processing according to the RLF report, thereby improving the mobility robustness. When the connection failure type is RLF or the first timer expires, the receiving network device can determine the cell corresponding to the failure primary cell identifier as the first cell, and the network device to which the first cell belongs is the first target network device. Optionally, the first target network device can further perform corresponding processing according to the RLF report, thereby improving the mobility robustness. Optionally, the first target network device can send the RLF report to the second target network device, and the second target network device can further perform corresponding processing according to the RLF report, thereby improving the mobility robustness.

[0125] When the serving network device determines that the number of received connection failure information is greater than 1, the serving network device can further determine the first cell in combination with the handover type corresponding to this handover. For example, if the handover type corresponding to this handover is CHO, the first cell can be determined according to the failure type corresponding to the first connection failure information. The specific way of determining the first cell according to the failure type is similar to the way described above when the number of failure types is 1. If the handover type corresponding to this handover is DAPS HO, the serving network device can determine the first cell according to the failure type of the connection failure of the first target cell. The specific way of determining the first cell according to the failure type is similar to the way described above when the number of connection failure information is 1.

[0126] In the embodiments of the present application, the terminal device reports relatively comprehensive connection failure information, so that the service network device can obtain more helpful connection failure information, and further use it to formulate a reasonable mobility strategy to improve the mobility performance of the terminal device. In addition, the embodiments of the present application do not limit the manner in which the first target network device processes the RLF report.

[0127] It should be noted that the above various embodiments of the present application do not limit how to determine or how to distinguish whether multiple connection failures belong to one handover process.

[0128] In the CHO process, some time information needs to be recorded or calculated, which can be achieved by at least one timer. The embodiments of the present application also provide a communication method, which starts the at least one timer after receiving the CHO configuration information, and then determines the processing manner of the at least one timer according to whether a new handover message is received before the terminal device does not meet the execution condition corresponding to the last received CHO command or before the terminal device is not time-synchronized with the target cell. The following embodiments are used as examples to illustrate. Figures 5-8

[0129] As shown in Figure 5 , a communication method is provided, which is suitable for CHO scenarios and controls the timing of the CHO process, so it can also be called a timing method in CHO. The method comprises:

[0130] S501, the terminal device receives CHO configuration information.

[0131] In some possible implementation manners, the terminal device can receive the CHO configuration information from the network device, and the CHO configuration information can be sent by the network device to the terminal device through a handover message such as an RRC reconfiguration message. The message carrying the CHO configuration information can also be called the last received CHO command. The CHO execution condition included in the CHO configuration information can also be called the execution condition corresponding to the last received CHO command.

[0132] S502, the terminal device starts the timer.

[0133] ​The timer can include a first timer and / or a second timer. The first timer is used to implement the timing of receiving the CHO configuration to triggering the CHO execution, that is, to calculate or record the time length from the last time of receiving the handover message to triggering the CHO execution by the timer. Alternatively, the second timer is used to calculate or record the time length from the last time of receiving the handover message to the connection failure (the first connection failure and / or any connection failure after the first connection failure). The terminal device starts the first timer and / or the second timer after receiving the CHO configuration information, and starts timing from “0”. It can be understood that the starting time of the first timer and the second timer can be the same, but the stopping time can be different. Alternatively, the first timer and the second timer can have a corresponding maximum running time limit respectively, and the present application does not limit the time length and setting method of the maximum running time.

[0134] In addition, the first timer and the second timer can be implemented by one timer, which only saves different time information at different time points to calculate or record different time information. Alternatively, the first timer and the second timer can be different timers.

[0135] S503, before the terminal device reaches the execution condition corresponding to the last received CHO command, or before the terminal device is time-synchronized with the target cell, the terminal device detects whether a new handover message is received.

[0136] The new handover message can be one of a handover message carrying new CHO configuration information (also referred to as a new CHO command), a normal handover command, and a DAPS handover command. The new CHO configuration information can include information for updating all or part of the configuration information of the candidate cells in the previous CHO configuration information, and / or information indicating to delete all or part of the configuration information of the candidate cells in the previous CHO configuration information, and / or information indicating to add configuration information of a new candidate cell, and the present application does not limit the embodiments.

[0137] After the terminal device receives the CHO configuration information, it determines whether each candidate cell meets the execution condition according to the CHO configuration information. If a candidate cell meets the execution condition, the terminal device can attempt to start handover to the target cell (start CHO) by taking the candidate cell as the target cell. Before the terminal device reaches the execution condition corresponding to the last received CHO command, or before the terminal device is time-synchronized with the target cell, the terminal device can detect (monitor or determine) whether a new handover message is received. If the terminal device detects a new handover message, S504 is performed.

[0138] In addition, if the terminal device does not detect a new handover message before the terminal device reaches the execution condition corresponding to the last received CHO command, or before the terminal device performs time synchronization with the target cell, the terminal device can continue to detect after the terminal device does not reach the execution condition corresponding to the last received CHO command, or before the terminal device performs time synchronization with the target cell. If the terminal device has not detected a new handover message all the time before the terminal device reaches the execution condition corresponding to the last received CHO command, or before the terminal device performs time synchronization with the target cell, the timer continues to run. Alternatively, if the terminal device has performed time synchronization with the target cell, the terminal device can not detect whether a new handover message is received after the time synchronization with the target cell, but perform S505 and subsequent steps.

[0139] S504, the terminal device restarts the timer.

[0140] If the terminal device detects a new handover message before the terminal device reaches the execution condition corresponding to the last received CHO command or performs time synchronization with the target cell, the first timer and / or the second timer are restarted, that is, S502 and subsequent steps are performed again.

[0141] Alternatively, after S503 or S504, the terminal device can perform steps S505 and S506, or perform step S506, for example, when the terminal device performs normal handover or CHO execution is not triggered, the terminal device can only perform step S506.

[0142] S505, the terminal device determines to trigger CHO execution (CHO triggering).

[0143] If the terminal device determines to trigger CHO execution (i.e. meets the CHO triggering condition and performs CHO), or the terminal device determines to complete time synchronization with the target cell, at this time, the running time (timing value) of the first timer is the value of "the time length from the last received handover message to the triggering of CHO execution". Alternatively, the terminal device can stop the first timer. Alternatively, the terminal device can continue to run the first timer. Alternatively, the terminal device can continue to perform step S506.

[0144] S506, the terminal device determines that a connection failure occurs.

[0145] After performing CHO, if the terminal device determines that a connection failure occurs, at this time, the running time (timing value) of the second timer is the value of the last received handover message to the connection failure. It can be understood that the connection failure here can be the first connection failure, or any connection failure, for example, the second connection failure.

[0146] The terminal device can record the running time length information of the second timer when the first connection failure occurs. After the first connection failure occurs, the second timer can be stopped or continue running. When the subsequent connection failure occurs, the terminal device obtains the running time length information of the second timer at this time, and then the terminal device can calculate or record the time length information of the subsequent connection failure. It can be understood that it is also possible that no connection failure occurs after the CHO is performed. In this case, the running time length information of the second timer can not be recorded.

[0147] Then, in the case where no new handover message is received, the time period from S501 to S506 is the value of the second timer, and in the case where a new handover message is received, the time period from S504 to S506 is the value of the second timer.

[0148] Optionally, the method can further include S507.

[0149] S507, the terminal device sends the connection failure information to the serving network device.

[0150] After the terminal device accesses the serving network device, the terminal device sends the connection failure information to the serving network device for subsequent processing. As described above, the connection failure information includes the time length information from the last time the handover message is received to the CHO execution triggering and / or the time length information from the last time the handover message is received to the connection failure. The embodiments of the present application do not limit and specifically describe the processing of the serving network device after receiving the connection failure information, for example, the description of the foregoing embodiments can be referred to.

[0151] In the case where the terminal device receives the handover message, the terminal device can perform the CHO execution, and then the terminal device can send the connection failure information to the serving network device. Figure 6For a specific example, when the terminal device receives CHO configuration 1 (candidate cells are cell 2, cell 3 and cell 4) at cell 1 at time t1, and starts the timer at this time. At time t2, the terminal device does not meet the execution condition corresponding to the last received CHO command, or before time synchronization with the target cell, it receives the updated CHO configuration 2 (update the configuration of cell 2, delete or release the configuration information of cell 3, and add the configuration information of cell 5) sent by the network device. According to the method of the embodiment of the present application, the terminal device will restart the timer at time t2. Assuming that the terminal device starts to trigger handover to Cell4 at time t3, and connection failure (such as HOF or RLF) occurs in cell 4 at time t4, the timer duration can include [t2, t3] and / or [t2, t4] information. It can be seen that since CHO configuration 2 is the latest handover configuration of the network device, the terminal device will also perform handover according to this configuration, and therefore the method of the embodiment of the present application can more accurately reflect the time length information in the CHO process, so that the network device can make correct judgment on the mobility problem based on the information, and determine a reasonable mobility strategy adjustment.

[0152] The above Figures 5-6 The embodiments shown above can be independently implemented, or can be combined with the above Figure 3 Or Figure 4 The embodiments are combined to be implemented, for example Figure 3 Or Figure 4 The timeCHOcfgExe and / or timeConnFailure in the connection failure information in the embodiments shown above can be implemented according to Figures 5-6 The embodiments shown above can be implemented.

[0153] In addition, the timing control of the CHO process can also be implemented according to the cell level (the granularity is the cell), such as Figure 7 The embodiment of the present application also provides a communication method (which can also be referred to as a timing method in CHO), comprising:

[0154] S701, the terminal device receives CHO configuration information.

[0155] S702, the terminal device starts the timer.

[0156] The description of S701 and S702 can be referred to Figure 5The related description of the illustrated embodiments is not repeated here. The difference is that, in the embodiments of the present application, the timer is cell-level, that is, the candidate cell in the CHO configuration information corresponds to the timer. Taking the first timer and / or the second timer as an example, one candidate cell can correspond to one timer (one-to-one relationship between the candidate cell and the timer), or multiple candidate cells can correspond to one timer (many-to-one relationship between the candidate cell and the timer). The time length of the timer corresponding to each candidate cell can be the same or different. In the embodiments of the present application, the timer corresponding to the cell can also be referred to as the timer of the cell.

[0157] S703, before the terminal device reaches the execution condition corresponding to the last received CHO command or before the terminal device performs time synchronization with the target cell, the terminal device detects whether a new handover message is received.

[0158] Before the terminal device reaches the execution condition corresponding to the last received CHO command or before the terminal device performs time synchronization with the target cell, the terminal device can detect whether a new handover message is received. If the terminal device detects a new handover message, S704 is performed. If the terminal device does not detect a new handover message, the terminal device can continue to detect before the terminal device reaches the execution condition corresponding to the last received CHO command or before the terminal device performs time synchronization with the target cell. If no new handover message is detected before the terminal device reaches the execution condition corresponding to the last received CHO command or before the terminal device performs time synchronization with the target cell, the timer corresponding to each candidate cell continues to run. Alternatively, if the terminal device has performed time synchronization with the target cell, the terminal device can not detect whether a new handover message is received after the time synchronization with the target cell, but perform S705 and subsequent steps.

[0159] S704, the terminal device determines the processing mode of the timer according to the new handover message.

[0160] If the new switching message is a new CHO command, and the new CHO command includes information indicating to update the configuration information of all or part of the candidate cells in the previous CHO configuration information, the terminal device can restart the timer corresponding to all or part of the updated candidate cells. For example, the candidate cells in the CHO configuration information (i.e., the previous CHO configuration information) received in S701 are the configuration information corresponding to cell 2, cell 3 and cell 4, and the new CHO switching command indicates to update the configuration information of cell 2, then the first timer and / or the second timer corresponding to cell 2 can be restarted, or the running first timer and / or the second timer corresponding to cell 2 are stopped, and a new first timer and / or a second timer corresponding to cell 2 are started. For example, in S701, the terminal device starts the first timer T2-1 corresponding to cell 2, and in S704, the terminal device can stop T2-1 and start a new first timer T2-2. Optionally, the first timer and / or the second timer of the candidate cells that are not updated can continue to run.

[0161] If the new switching message is a new CHO command, and the new CHO command includes information indicating to delete the configuration information of all or part of the candidate cells in the previous CHO configuration information, the terminal device can delete the timer corresponding to all or part of the candidate cells indicated to be deleted. For example, the candidate cells in the CHO configuration information (i.e., the previous CHO configuration information) received in S701 are the configuration information corresponding to cell 2, cell 3 and cell 4, and the new CHO switching command indicates to delete the configuration information of cell 3, then the terminal device can stop or delete the first timer and / or the second timer corresponding to cell 3. Optionally, the first timer and / or the second timer of the candidate cells that are not deleted can continue to run.

[0162] If the new switching message is a new CHO command, and the new CHO command includes information indicating to add the configuration information of a new candidate cell, the terminal device can add the timer corresponding to the added candidate cell. For example, the candidate cells in the CHO configuration information (i.e., the previous CHO configuration information) received in S701 are the configuration information corresponding to cell 2, cell 3 and cell 4, and the new CHO switching command in S704 indicates to add the configuration information of cell 5, then the terminal device can add the first timer and / or the second timer corresponding to cell 5 and start the timer. Optionally, the first timer and / or the second timer of the other previously configured candidate cells can continue to run.

[0163] Optionally, if the new handover message is a normal handover command or a DAPS handover command, the terminal device can stop the timers corresponding to all candidate cells in the CHO configuration information. Optionally, the corresponding first timer and / or second timer can be restarted for DAPS HO or normal handover.

[0164] After S704, the terminal device can perform step S705 and step S705, or perform step S706, such as when the terminal device performs normal handover or does not trigger CHO execution, the terminal device can only perform step 706.

[0165] S705, the terminal device determines to trigger CHO execution.

[0166] If the terminal device determines to trigger CHO execution, or the terminal device determines to complete time synchronization with the target cell, at this time the running time (timer value) of the first timer of the target cell is the value of "the time length from the last time the terminal device receives the handover message to triggering CHO execution". Optionally, the terminal device can stop the first timer. Alternatively, the terminal device can continue to run the first timer. Optionally, the terminal device can continue to perform step S707. Optionally, after the terminal device starts handover to the target cell, except that the timer corresponding to the target cell continues to run, the timers corresponding to other candidate cells can stop running, that is, the timers corresponding to other candidate cells are cleared (or discarded), and the corresponding time information can not be reported to the network device.

[0167] Alternatively, the timers corresponding to other candidate cells can also not stop, until the terminal device cannot attempt CHO in the candidate cell. For example, assuming that the candidate cells are cell1, cell2 and cell3, the terminal device can attempt CHO execution at most once after the first connection failure, then the terminal device attempts to perform CHO in cell 1 the first time, then the timer of cell 1 continues to run, the timers corresponding to cell2 and cell3 can stop, or the timers of cell2 and cell3 can continue to run, the terminal device occurs connection failure in cell1, the timer of cell 1 stops, and if the terminal device continues to attempt CHO in cell2, the timer of cell3 stops, and the timer of cell2 continues to run.

[0168] S706, the terminal device determines whether connection failure occurs in the target cell.

[0169] If the terminal device determines that a connection failure occurs, at this time, the running time length (timing value) of the second timer of the target cell is the value from the last time the handover message is received to the connection failure. It can be understood that the connection failure here can be the first connection failure, or any connection failure, for example, the second connection failure.

[0170] The terminal device can record the running time length information of the second timer when the first connection failure occurs. After the first connection failure occurs, the second timer can be stopped, or the second timer can continue to run. When the subsequent connection failure occurs, the terminal device obtains the running time length information of the second timer at this time, and then the terminal device can calculate or record the time length information of the subsequent connection failure.

[0171] Then, in the case where no new handover message is received or the new handover message is not a CHO configuration update to the target cell, the time period from S701 to S706 is the value of the second timer of the target cell, or, in the case where the new handover message is received and the new handover message is a CHO configuration message update to the target cell, the time period from S704 to S706 is the value of the second timer.

[0172] Optionally, the method can further include S707.

[0173] S707, the terminal device sends the connection failure information to the service network device.

[0174] After the terminal device accesses the service network device, the terminal device sends the connection failure information to the service network device for subsequent processing. As described above, the connection failure information includes the time length information of the timer. The present embodiment does not limit and specifically describe the processing of the service network device after receiving the connection failure information, for example, the description of the foregoing embodiments can be referred to.

[0175] In the case where the terminal device determines that a connection failure occurs, at this time, the running time length (timing value) of the second timer of the target cell is the value from the last time the handover message is received to the connection failure. It can be understood that the connection failure here can be the first connection failure, or any connection failure, for example, the second connection failure. Figure 8For a specific example, when the terminal device receives CHO configuration 1 (the candidate cells are cell2, cell3 and cell4) in cell 1 at time point t1, it starts timer 2, timer 3 and timer 4 corresponding to cell 2, cell 3 and cell 4 respectively. At time t2, before the terminal device reaches the execution condition corresponding to the most recently received CHO command, or before it synchronizes time with the target cell, it receives an updated CHO configuration 2 sent by the network device (updates the configuration of cell 2, deletes the configuration information of cell 3, and adds the configuration information of cell 5). According to the method of the embodiment of the present application, the terminal device will restart the timer 2 corresponding to cell 2, delete the timer 3 corresponding to cell 3, and add the timer 5 corresponding to cell 5 at time t2. Assume that the terminal device triggers handover to Cell 4 at time t3, timer 2 and timer 5 stop running, and a connection failure (such as HOF or RLF) occurs in cell 4 at time t4, then the timing duration of the timer corresponding to cell 4 includes [t1, t3] and [t2, t4]. It can be seen that since CHO configuration 2 is the latest handover configuration of the network device, the terminal device will also switch based on this configuration. Therefore, the method of the embodiment of the present application can more accurately reflect the time information of the CHO process, so that the network device can make a correct judgment on the mobility problem based on this information and determine a reasonable mobility policy adjustment.

[0176] above Figures 7-8 The embodiment shown can be implemented independently or in conjunction with the previous Figure 3 or Figure 4 The embodiments are combined to implement, for example Figure 3 or Figure 4 In the embodiment shown, the timeCHOcfgExe and / or timeConnFailure in the connection failure information can be Figures 7-8 The embodiment shown is implemented.

[0177] It is understandable that the above Figures 5-8 The embodiment shown uses the timer to illustrate the timing control of timeConnFailure. Timing can also be achieved in other ways, such as by timestamps, which is not limited in this embodiment of the present application. Figures 5-8 The illustrated embodiment uses the time information from receiving the CHO configuration to triggering the CHO execution and the time information from the last receipt of the switching message to triggering the CHO execution as examples to illustrate the timing control in the CHO process. Other time information in the CHO process can also be processed similarly, and the embodiments of this application do not list them one by one.

[0178] The device used to implement the method in the embodiments of the present application is described below with reference to the drawings. Therefore, the content in the foregoing can be used in the subsequent embodiments, and the repeated content is not described again. In order to implement the functions in the method provided in the embodiments of the present application, each network element or device can include a hardware structure and / or a software module, and the functions are implemented in the form of hardware structure, software module, or hardware structure plus software module. Whether a certain function in the foregoing functions is implemented in the form of hardware structure, software module, or hardware structure plus software module depends on the specific application and design constraints of the technical solution.

[0179] Figure 9 A schematic block diagram of the communication device 900 provided in the embodiments of the present application is shown. The communication device 900 can correspond to the functions or steps implemented by the terminal device in the method embodiments shown in the foregoing Figure 3 or Figure 4 . The communication device 900 can be a terminal device or a component (for example, a chip or a circuit, etc.) applicable to the terminal device, or the communication device 900 can be a chip system. In the embodiments of the present application, the chip system can be composed of a chip or can include a chip and other discrete devices.

[0180] In some possible implementation manners, the communication device can include a detection unit 910 and a processing unit 920. Optionally, a transceiver unit 930 can also be included.

[0181] For example, when used to implement the method in the embodiments shown in the foregoing Figure 3 , the communication device can be used as follows:

[0182] The detection unit 910 can be used to detect a first connection failure and record first connection failure information corresponding to the first connection failure, and detect a second connection failure occurring after the first connection failure; and the processing unit 920 can be used to determine a processing manner of the connection failure information according to a switching type of the first switching procedure.

[0183] For example, when used to implement the method in the embodiments shown in the foregoing Figure 4 , the communication device can be used as follows:

[0184] The detection unit 910 can be used to detect at least one connection failure, and the at least one connection failure belongs to the first switching procedure; and the processing unit 920 can be used to record and save connection failure information corresponding to each connection failure.

[0185] Optionally, the transceiver unit 930 can be used to send the connection failure information to a network device.

[0186] It should be understood that the detection unit 910 and the processing unit 920 in the embodiments of the present application can be implemented by at least one processor or processor-related circuit components, and the transceiver unit 930 can be implemented by a transceiver or transceiver-related circuit components or a communication interface. In addition, the above-mentioned units can be separated or integrated, and the embodiments of the present application are not limited to this.

[0187] Optionally, the communication device 900 may further include a storage unit 940, which may be used to store instructions or data. The processing unit 920 may execute or read the instructions or data stored in the storage unit to enable the communication device to perform corresponding operations. Optionally, the storage unit 940 may be implemented by at least one memory.

[0188] It can be understood that, regarding the coupling and specific implementation between the various units of the communication device 900, reference can be made to the description in the method embodiment, which will not be repeated here.

[0189] like Figure 10 As shown, the communication device 1000 provided in the embodiment of the present application can realize the present application Figure 4 The functions of the network device in the method provided in the embodiment. The communication device 1000 may be a network device; or the communication device 1000 may be a device that can support the network device to implement the corresponding functions of the method provided in the embodiment of the present application; or the communication device 1000 may be a chip system. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0190] The communication device 1000 may include a transceiver unit 1010 and a processing unit 1020. Exemplarily, the transceiver unit 1010 may be configured to receive connection failure information from a terminal device indicating at least one connection failure, where the at least one connection failure belongs to a first handover process. The processing unit 1020 may be configured to determine a first cell based on the number of connection failure information in the first handover process in the received connection failure information. Optionally, the transceiver unit 1010 may also be configured to send the received connection failure information to a network device to which the first cell belongs.

[0191] The processing unit 1020 in the embodiment of the present application can be implemented by at least one processor or processor-related circuit components, and the transceiver unit 1010 can be implemented by a transceiver or transceiver-related circuit components or a communication interface. In addition, the above-mentioned units can be separated or integrated, and the embodiment of the present application does not limit this.

[0192] Optionally, the communication apparatus 1000 further includes a storage unit 1030, which can be configured to store instructions or data. The processing unit 1020 can execute or read the instructions or data stored in the storage unit 1030, so that the communication apparatus implements corresponding operations. Optionally, the storage unit 1030 can be implemented by at least one memory.

[0193] It can be understood that the coupling between the various units of the communication apparatus 1000 and the specific implementation can refer to the description in the method embodiments, which will not be repeated here.

[0194] Figure 11 A schematic block diagram of a communication apparatus 1100 is provided in the embodiments of the present application. The communication apparatus 1100 can correspond to the implementation of the functions or steps implemented by the terminal device in the method embodiments described above. The communication apparatus 1100 can be a terminal device or a component (such as a chip or circuit, etc.) applicable to the terminal device, or the communication apparatus 900 can be a chip system. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices. The communication apparatus can include a transceiver unit 1110 and a processing unit 1120. Figures 5-8

[0195] In some possible implementation manners, the transceiver unit 1110 is configured to receive conditional handover (CHO) configuration information, and the processing unit 1120 is configured to start a timer after the transceiver unit receives the CHO configuration information. The processing unit 1120 is configured to determine a processing manner of the timer according to whether a new handover message is received before the terminal device reaches an execution condition corresponding to the CHO configuration information, or before time synchronization with a target cell is performed.

[0196] Optionally, the transceiver unit 1130 can be configured to send connection failure information to a network device.

[0197] It should be understood that the processing unit 1120 in the embodiments of the present application can be implemented by at least one processor or processor-related circuit component, and the transceiver unit 1110 can be implemented by a transceiver or a transceiver-related circuit component or a communication interface. In addition, the various units described above can be separate or integrated, and the embodiments of the present application do not limit this.

[0198] Optionally, the communication apparatus 1100 further includes a storage unit 1130, which can be configured to store instructions or data. The processing unit 1120 can execute or read the instructions or data stored in the storage unit 1130, so that the communication apparatus implements corresponding operations. Optionally, the storage unit 1130 can be implemented by at least one memory.

[0199] ​It can be understood that, regarding the coupling between the various units of the communication device 1100 and the specific implementation, reference can be made to the description in the method embodiment, which will not be repeated here.

[0200] It can be understood that, regarding the coupling between the various units of the communication device 1100 and the specific implementation, reference can be made to the description in the method embodiment, which will not be repeated here.

[0201] The embodiment of the present application also provides a communication device 1200, which can be used to implement or support the communication device 1200 to implement the functions of the network device or terminal device in the methods provided in various embodiments of the present application. The communication device 1200 includes at least one processor 1210 and at least one memory 1220 for storing program instructions and / or data. The memory 1220 and the processor 1210 are coupled. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1210 may operate in conjunction with the memory 1220. The processor 1210 may execute the program instructions and / or data stored in the memory 1220 so that the communication device 1200 implements the corresponding method. Optionally, at least one of the at least one memory may be included in the processor.

[0202] The communication apparatus 1200 may further include a communication interface 1230 for communicating with other devices via a transmission medium, so that the device used in the communication apparatus 1200 can communicate with other devices.

[0203] The specific connection medium between the communication interface 1230, the processor 1210 and the memory 1220 is not limited in the embodiment of the present application. Figure 12 The memory 1220, the processor 1210 and the communication interface 1230 are connected via a bus 1240. Figure 12 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 12 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0204] In the embodiments of the present application, the processor can be a general 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, a discrete hardware component, and can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The general processor can be a microprocessor or any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as hardware processor execution or executed by a combination of hardware and software modules in the processor.

[0205] In the embodiments of the present application, the memory can be a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), and can also be a volatile memory such as a random-access memory (RAM). The memory can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by a computer, but is not limited to this. The memory in the embodiments of the present application can also be a circuit or any other device capable of realizing a storage function, used for storing program instructions and / or data.

[0206] The embodiments of the present application also provide a communication system for implementing all or part of the steps of the above-mentioned method embodiments. For example, the communication system can include the above-mentioned terminal device. Optionally, the communication system can also include at least one network device.

[0207] The embodiments of the present application also provide a computer readable storage medium including instructions, when executed on a computer, cause Figures 3-8 The method executed by the terminal device in the illustrated embodiments is executed.

[0208] The embodiments of the present application also provide a computer readable storage medium including instructions, when executed on a computer, cause Figures 3-8 The method executed by the network device in the illustrated embodiments is executed.

[0209] The embodiments of the present application also provide a computer program product including instructions, when executed on a computer, cause Figures 3-8 The method executed by the network device or the terminal device in the illustrated embodiments is executed.

[0210] It should be understood that the terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b or c can represent a, b, c, a-b, a-c, b-c or a-b-c, where a, b and c can be single or multiple.

[0211] In addition, unless otherwise stated, the ordinal numbers mentioned in the embodiments of the present application are not used to limit the order, time sequence, priority or importance of multiple objects. For example, the first timer and the second timer are only used to distinguish the functions.

[0212] It should be understood that the processor mentioned in the embodiments of the present application can be a CPU, and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

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

[0214] It should be noted that when the processor is a general processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.

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

[0216] It should be understood that in various embodiments of the present application, the size of the sequence number of each process described above does not mean the order of execution, the execution order of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0217] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0218] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0219] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0220] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0221] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0222] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented 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, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. 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, data center, etc. integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, DVD), or semiconductor media (for example, solid state drive (SSD)) and the like.

[0223] The above is only a specific implementation 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 can easily think of changes or replacements within the technical range disclosed in the embodiments of the present application, which 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 subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method comprises: receiving conditional handover (CHO) configuration information, starting a timer, wherein the timer is used to calculate or record a time from the last time a handover message is received to a connection failure, and the CHO configuration information comprises information of at least one candidate cell; before a terminal device reaches an execution condition corresponding to the CHO configuration information or before the terminal device performs time synchronization with a target cell, determining a processing manner of the timer according to whether a new handover message is received, wherein the new handover message comprises a handover message carrying new CHO configuration information, a normal handover command or a dual active protocol stack handover command; determining that a connection failure occurs in the target cell, a running time of the timer is the time from the last time the handover message is received to the connection failure, and the connection failure comprises a first connection failure after the CHO configuration information is received and / or at least one connection failure after the first connection failure; sending connection failure information to a serving network device, wherein the connection failure information comprises the running time of the timer.

2. The method of claim 1, wherein, The determining the processing manner of the timer according to whether the new handover message is received comprises: in a case where the new handover message is received, restarting the timer.

3. The method of claim 1, wherein, The timer corresponds to the at least one candidate cell, and the determining the processing manner of the timer according to whether the new handover message is received comprises: if the new handover message is received and the new handover message is the handover message carrying the new CHO configuration information, the new CHO configuration information comprises information of updating configuration information of all or part of candidate cells in previous CHO configuration information, and timers corresponding to the updated all or part of candidate cells are restarted.

4. The method according to claim 1 or 3, characterized in that, The timer corresponds to the at least one candidate cell, and the determining the processing manner of the timer according to whether the new handover message is received comprises: if the new handover message is received and the new handover message is the handover message carrying the new CHO configuration information, the new CHO configuration information comprises information indicating deletion of configuration information of all or part of candidate cells in previous CHO configuration information, and timers corresponding to the all or part of candidate cells indicated to be deleted are deleted.

5. The method according to claim 1 or 3, characterized in that, The timer corresponds to the at least one candidate cell, and the determining the processing manner of the timer according to whether the new handover message is received comprises: if the new handover message is received and the new handover message is the handover message carrying the new CHO configuration information, the new CHO configuration information comprises information indicating addition of configuration information of a new candidate cell, and a timer corresponding to the new candidate cell is added.

6. The method according to claim 1 or 3, characterized in that, The timer corresponds to the at least one candidate cell, and the determining the processing manner of the timer according to whether the new handover message is received comprises: if the new handover message is received and the new handover message is the normal handover command or the dual active protocol stack handover command, timers corresponding to all candidate cells are stopped.

7. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: After time synchronization with the target cell, it is not detected whether a new handover message is received.

8. A communication method characterized by comprising: Comprising: Receiving connection failure information of at least one connection failure from a terminal device, the at least one connection failure belonging to a first handover procedure, the connection failure information including a running time length of a timer in conditional handover CHO, the connection failure information being used by the terminal device to determine subsequent processing after connection failure in a target cell, the running time length of the timer being the time from the last time a handover message is received to connection failure, the connection failure including a first connection failure after receiving conditional handover CHO configuration information and / or at least one connection failure after the first connection failure; Determining a first cell according to the number of connection failure information in the first handover procedure in the received connection failure information, the first cell being an object to which a serving network device determines to forward connection failure information.

9. The method of claim 8, wherein, Further comprising: Sending the received connection failure information to a network device to which the first cell belongs.

10. The method according to claim 8 or 9, characterized in that, When the number of connection failure information in the first handover procedure is 1, determining the first cell according to the failure type of the connection failure information.

11. The method of claim 10, wherein, Determining the first cell according to the failure type, comprising: When the failure type is handover failure, determining the cell corresponding to the previous primary cell identifier as the first cell.

12. The method of claim 10, wherein, Determining the first cell according to the failure type, comprising: When the failure type is conditional handover or timer timeout, determining the cell corresponding to the failed primary cell identifier as the first cell.

13. The method of claim 8 or 9, wherein, When the number of connection failure information in the first handover procedure is greater than 1, determining the first cell according to the failure type corresponding to the first connection failure.

14. A communications device, characterized by The communication device comprises a processor and a memory, the memory is used to store computer programs or instructions or data, the processor is coupled with the memory, and when the processor reads the computer programs or instructions or data, it is used to implement the method of any one of claims 1-7.

15. A communications device, characterized by The communication device comprises a processor and a memory, the memory is used to store computer programs or instructions or data, the processor is coupled with the memory, and when the processor reads the computer programs or instructions or data, it is used to implement the method of any one of claims 8-13.

16. A computer readable storage medium characterized by: The computer readable storage medium stores a computer program, which when executed, causes the method of any one of claims 1-13 to be executed.

17. A computer program product, characterised in that, The computer program product comprises instructions, which when executed, cause the method of any one of claims 1-13 to be implemented.

Images