Mobility optimization method and apparatus, communication apparatus, and storage medium

Abstract

The present disclosure relates to a mobility optimization method and apparatus, a communication apparatus, and a storage medium. In at least one embodiment of the present disclosure, when a terminal is configured with multiple pieces of configuration information, the terminal is in a scenario in which multiple configurations coexist. In the scenario in which multiple configurations coexist, if link failure occurs for the terminal, then the terminal records failure related information, and the terminal sends the failure related information to a network device. The failure related information is used to perform mobility optimization of the network device, that is, the network device, based on the failure related information generated in the scenario in which multiple configurations coexist and reported by the terminal, performs mobility optimization. Compared with the prior art, in which a network device cannot perform mobility optimization for a scenario in which multiple configurations coexist, said embodiment enables the network device to perform mobility optimization for a scenario in which multiple configurations coexist, thereby providing a guarantee of mobility for the terminal in a scenario in which multiple configurations coexist.

Description

Mobility optimization method, device, communication device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on December 8, 2023, with application number 202311688756.5 and application name “A mobility optimization method, device, communication device and storage medium”, the entire contents of which are incorporated by reference in this disclosure. Technical Field

[0003] The embodiments of the present disclosure relate to the field of communication technologies, and in particular to a mobility optimization method, device, communication device, and storage medium. Background Art

[0004] With the advancement of communication technology, terminals may be configured with different mobility configurations by the network. When a terminal is configured with multiple configurations and fails to execute any one configuration, resulting in mobility issues, the network only performs mobility optimization for the single configuration that failed to execute. However, other unexecuted configurations of the terminal may also cause mobility issues. Therefore, even after the network currently performs mobility optimization for a single configuration, the terminal may still experience mobility issues, failing to meet the mobility needs of terminals in scenarios where multiple configurations coexist. Currently, the network cannot perform mobility optimization for mobility issues in scenarios where multiple configurations coexist. Summary of the Invention

[0005] At least one embodiment of the present disclosure provides a mobility optimization method, device, communication device, and storage medium.

[0006] In a first aspect, an embodiment of the present disclosure provides a mobility optimization method, which is applied to a terminal. The mobility optimization method includes:

[0007] When a terminal is configured with configuration information and a link failure occurs, the terminal records failure-related information. The configuration information includes at least two of the following:

[0008] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, primary cell group fast failure recovery configuration information;

[0009] The terminal sends information about the failure to the network device.

[0010] In some embodiments, the link failure of the terminal includes at least one of the following:

[0011] The terminal experiences a radio link failure (RLF) in the source cell;

[0012] The terminal fails to execute LTM;

[0013] The terminal fails to perform LTM recovery;

[0014] The terminal fails to execute CHO;

[0015] The terminal fails to perform CHO recovery;

[0016] The terminal fails to perform traditional switching;

[0017] The terminal fails to execute CPAC;

[0018] The terminal fails to perform fast failure recovery of the primary cell group.

[0019] In some embodiments, the failure-related information includes at least one of the following:

[0020] Candidate cell information;

[0021] Time information;

[0022] Instructions.

[0023] In some embodiments, the candidate cell information includes at least one of the following:

[0024] LTM candidate cell information;

[0025] CHO candidate cell information;

[0026] CPAC candidate cell information.

[0027] In some embodiments, the time information includes at least one of the following:

[0028] The time interval between the terminal receiving the LTM configuration information and the terminal receiving the CHO configuration information;

[0029] The time interval between the terminal receiving the LTM configuration information and the CPAC configuration information;

[0030] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO;

[0031] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM;

[0032] The time interval between the terminal receiving the LTM configuration information and starting to execute CPAC;

[0033] The time interval between the terminal receiving the CPAC configuration information and starting to execute LTM;

[0034] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO recovery or the success or failure of CHO recovery execution;

[0035] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM recovery or the success or failure of LTM recovery execution;

[0036] The time interval between the terminal receiving the LTM configuration information and starting to execute the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery;

[0037] The time interval between the failure of the terminal to execute LTM and the start of CHO recovery, or the success or failure of CHO recovery;

[0038] The time interval between the failure of the terminal to execute CHO and the start of LTM recovery, or the success or failure of LTM recovery;

[0039] The time interval between the failure of the terminal to execute LTM and the start of the primary cell group fast failure recovery, or the success or failure of the primary cell group fast failure recovery.

[0040] In some embodiments, the indication information includes at least one of the following:

[0041] Type information of the recovery cell to which the terminal performs recovery;

[0042] Indication information for coexistence scenarios;

[0043] Instructions for continuous execution;

[0044] Timing advance indication information, the timing advance indication information is used to indicate whether the terminal has a timing advance TA value and / or TA value size of the recovery cell, and the recovery cell performed by the terminal is an LTM candidate cell;

[0045] Downlink synchronization indication information, which is used to indicate whether the terminal has been downlink synchronized with the recovery cell, and whether the recovery cell to be recovered by the terminal is an LTM candidate cell;

[0046] The indication information of the same distribution unit is used to indicate whether the source cell and the recovery cell of the terminal are cells under the same distribution unit DU, and the recovery cell where the terminal performs recovery is an LTM candidate cell.

[0047] In some embodiments, the candidate cell information includes at least one of the following:

[0048] identification information of candidate cells;

[0049] Execution conditions of candidate cells;

[0050] Measurement results of candidate cells.

[0051] In some embodiments, the terminal sends failure-related information to the network device, including:

[0052] The terminal sends a notification message to the network device, where the notification message is used to indicate that the terminal has recorded the failure related information, and the terminal responds to the failure related information request message sent by the network device and sends the failure related information to the network device;

[0053] or,

[0054] After recording the failure-related information, the terminal sends the failure-related information to the network device;

[0055] and / or,

[0056] The terminal receives the failure related information request message sent by the network device; and in response to the failure related information request message, the terminal sends the failure related information to the network device.

[0057] In a second aspect, an embodiment of the present disclosure further proposes a mobility optimization method, which is applied to a network device. The mobility optimization method includes:

[0058] The network device receives failure related information sent by the terminal. The failure related information is configuration information that the terminal is configured with and is recorded when a link failure occurs in the terminal. The configuration information includes at least two of the following:

[0059] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information.

[0060] In some embodiments, the network device receives the failure-related information sent by the terminal, including:

[0061] The network device receives a notification message sent by the terminal, the notification message being used to indicate that the terminal has recorded failure-related information; the network device sends a failure-related information request message to the terminal; the network device receives failure-related information sent by the terminal in response to the failure-related information request message;

[0062] and / or,

[0063] The network device sends a failure related information request message to the terminal; and the network device receives failure related information sent by the terminal in response to the failure related information request message.

[0064] In some embodiments, the mobility optimization method further includes:

[0065] The network device performs mobility optimization based on the failure related information, or the network device sends the failure related information to the network device related to the failure related information through interface signaling, so that the network device performs mobility optimization based on the received failure related information.

[0066] In a third aspect, an embodiment of the present disclosure further provides a communication device, applied to a terminal, comprising a memory, a transceiver, and a processor:

[0067] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer programs in the memory and executing:

[0068] If a link failure occurs, the terminal is configured with configuration information, and relevant information about the failure is recorded. The configuration information includes at least two of the following:

[0069] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, primary cell group fast failure recovery configuration information;

[0070] Send information about the failure to the network device.

[0071] In some embodiments, the occurrence of a link failure includes at least one of the following:

[0072] The terminal experiences a radio link failure (RLF) in the source cell;

[0073] The terminal fails to execute LTM;

[0074] The terminal fails to perform LTM recovery;

[0075] The terminal fails to execute CHO;

[0076] The terminal fails to perform CHO recovery;

[0077] The terminal fails to perform traditional switching;

[0078] The terminal fails to execute CPAC;

[0079] The terminal fails to perform fast failure recovery of the primary cell group.

[0080] In some embodiments, the failure-related information includes at least one of the following:

[0081] Candidate cell information;

[0082] Time information;

[0083] Instructions.

[0084] In some embodiments, the candidate cell information includes at least one of the following:

[0085] LTM candidate cell information;

[0086] CHO candidate cell information;

[0087] CPAC candidate cell information.

[0088] In some embodiments, the time information includes at least one of the following:

[0089] The time interval between the terminal receiving the LTM configuration information and the terminal receiving the CHO configuration information;

[0090] The time interval between the terminal receiving the LTM configuration information and the CPAC configuration information;

[0091] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO;

[0092] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM;

[0093] The time interval between the terminal receiving the LTM configuration information and starting to execute CPAC;

[0094] The time interval between the terminal receiving the CPAC configuration information and starting to execute LTM;

[0095] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO recovery or the success or failure of CHO recovery execution;

[0096] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM recovery or the success or failure of LTM recovery execution;

[0097] The time interval between the terminal receiving the LTM configuration information and starting to execute the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery;

[0098] The time interval between the failure of the terminal to execute LTM and the start of CHO recovery, or the success or failure of CHO recovery;

[0099] The time interval between the failure of the terminal to execute CHO and the start of LTM recovery, or the success or failure of LTM recovery;

[0100] The time interval between the failure of the terminal to execute LTM and the start of the primary cell group fast failure recovery, or the success or failure of the primary cell group fast failure recovery.

[0101] In some embodiments, the indication information includes at least one of the following:

[0102] Type information of the recovery cell to which the terminal performs recovery;

[0103] Indication information for coexistence scenarios;

[0104] Instructions for continuous execution;

[0105] Timing advance indication information, the timing advance indication information is used to indicate whether the terminal has a timing advance TA value and / or TA value size of the recovery cell, and the recovery cell performed by the terminal is an LTM candidate cell;

[0106] Downlink synchronization indication information, which is used to indicate whether the terminal has been downlink synchronized with the recovery cell, and whether the recovery cell to be recovered by the terminal is an LTM candidate cell;

[0107] The indication information of the same distribution unit is used to indicate whether the source cell and the recovery cell of the terminal are cells under the same distribution unit DU, and the recovery cell where the terminal performs recovery is an LTM candidate cell.

[0108] In some embodiments, the candidate cell information includes at least one of the following:

[0109] identification information of candidate cells;

[0110] Execution conditions of candidate cells;

[0111] Measurement results of candidate cells.

[0112] In some embodiments, sending failure-related information to the network device includes:

[0113] Sending a notification message to the network device, the notification message is used to indicate that the terminal has recorded the failure-related information, and in response to the failure-related information request message sent by the network device, sending the failure-related information to the network device;

[0114] or,

[0115] After recording the failure related information, the failure related information is sent to the network device;

[0116] and / or,

[0117] Receive a failure related information request message sent by a network device; and send failure related information to the network device in response to the failure related information request message.

[0118] In a fourth aspect, an embodiment of the present disclosure further provides a communication device, applied to a network device, comprising a memory, a transceiver, and a processor:

[0119] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer programs in the memory and executing:

[0120] Receive failure-related information sent by the terminal. The failure-related information is configuration information that the terminal is configured with and is recorded when a link failure occurs on the terminal. The configuration information includes at least two of the following:

[0121] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information.

[0122] In some embodiments, receiving the failure-related information sent by the terminal includes:

[0123] Receiving a notification message sent by a terminal, the notification message being used to indicate that the terminal has recorded failure-related information; sending a failure-related information request message to the terminal; and receiving failure-related information sent by the terminal in response to the failure-related information request message;

[0124] and / or,

[0125] Sending a failure related information request message to the terminal; and receiving failure related information sent by the terminal in response to the failure related information request message.

[0126] In some embodiments, the processor is further configured to read the computer program in the memory and execute:

[0127] Mobility optimization is performed based on the failure related information, or the failure related information is sent to a network device related to the failure related information through interface signaling, so that the network device performs mobility optimization based on the received failure related information.

[0128] In the fifth aspect, the embodiments of the present disclosure further propose a processor-readable storage medium, which stores a program, and the program is used to enable the processor to execute the mobility optimization method of any embodiment of the first aspect or the mobility optimization method of any embodiment of the second aspect.

[0129] In at least one embodiment of the present disclosure, when a terminal is configured with multiple configuration information and is in a multiple configuration coexistence scenario, in the multiple configuration coexistence scenario, if a link failure occurs in the terminal, the terminal will record failure-related information, and then the terminal will send the failure-related information to the network device, and the failure-related information is used by the network device to perform mobility optimization, that is, the network device triggers the network device to perform mobility optimization based on the failure-related information generated in the multiple configuration coexistence scenario reported by the terminal. Compared with the existing technology, the network device cannot perform mobility optimization for the multiple configuration coexistence scenario. This embodiment enables the network device to perform mobility optimization for the multiple configuration coexistence scenario, thereby providing a guarantee for the mobility of the terminal in the multiple configuration coexistence scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0130] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present disclosure, and a person skilled in the art can also obtain other drawings based on these drawings.

[0131] FIG1 is a schematic diagram of a flow chart of a mobility optimization method provided by an embodiment of the present disclosure;

[0132] FIG2 is a schematic diagram of a flow chart of another mobility optimization method provided by an embodiment of the present disclosure;

[0133] FIG3 is a schematic diagram of a mobility optimization device provided by an embodiment of the present disclosure;

[0134] FIG4 is a schematic diagram of another mobility optimization device provided by an embodiment of the present disclosure;

[0135] FIG5 is a schematic diagram of a communication device provided by an embodiment of the present disclosure;

[0136] FIG6 is a schematic diagram of another communication device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0137] In order to more clearly understand the above-mentioned purposes, features and advantages of the present disclosure, the present disclosure is further described in detail below with reference to the accompanying drawings and examples. It will be understood that the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. The specific embodiments described herein are merely used to explain the present disclosure, rather than to limit the present disclosure. Based on the described embodiments of the present disclosure, all other embodiments obtained by those of ordinary skill in the art are within the scope of protection of the present disclosure.

[0138] It should be noted that, in this document, relational terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0139] The terminal may be configured with different mobility configuration information by the network, but the network can only perform mobility optimization for the configuration information that fails to execute:

[0140] For example, the terminal is configured with layer 1 and / or layer 2 triggered mobility (L1 / L2 triggered mobility, LTM) configuration information and conditional handover (CHO) configuration information. When CHO execution fails, only mobility optimization is performed for CHO; when LTM execution fails, only mobility optimization is performed for LTM.

[0141] However, if CHO fails, the network also configured LTM for the terminal, but LTM is not running. This LTM configuration may also cause mobility issues. Similarly, if LTM fails, the network also configured CHO for the terminal, but CHO is not running. This CHO configuration may also cause mobility issues. In other words, even after optimizing mobility for a single configuration, the terminal may still experience mobility issues, failing to meet the mobility requirements of the terminal in scenarios where multiple configurations coexist.

[0142] The network can send various mobility configuration information to the terminal, such as LTM configuration information, CHO configuration information, Conditional PSCell addition / change (CPAC) configuration information, and fast MCG recovery configuration information. Based on this configuration information, the terminal can perform mobility, but the network equipment cannot optimize mobility issues in scenarios where multiple configurations coexist.

[0143] (1) LTM

[0144] The LTM mechanism pre-configures multiple candidate cell configurations and their L1 measurement configurations for the terminal. The terminal performs L1 measurement based on the L1 measurement configuration configured by the network and reports it. The network sends an LTM cell switch command to the terminal based on the L1 measurement results reported by the terminal. This LTM cell switch command is sent to the terminal via the MAC Control Element (MAC CE).

[0145] When a terminal receives an LTM cell switch command from the network, it executes the LTM cell switch. If the LTM cell switch fails, it performs the cell selection process. If the target cell selected by the terminal is an LTM candidate cell, it performs LTM recovery. If the target cell selected by the terminal is not an LTM candidate cell, the terminal triggers the reestablishment process. If the target cell selected by the terminal is an LTM candidate cell, if the LTM recovery fails, the terminal triggers the reestablishment process.

[0146] (2) Conditional PSCell addition / change (CPAC)

[0147] CHO (Cell Handover) involves configuring multiple CHO candidate cells and their corresponding execution conditions for the terminal. The terminal then evaluates the CHO candidate cells based on measurement results. If a candidate cell meets the execution conditions, the terminal accesses that candidate cell. This applies to PCell changes (handovers) on the MCG (Master Cell Group) side.

[0148] Similarly, on the SCG (Secondary Cell Group) side, the network can also configure multiple CPAC candidate cells and their corresponding execution conditions for the terminal. The terminal evaluates the CPAC candidate cells based on the measurement results. If a candidate cell meets the execution conditions, the terminal accesses this candidate target cell. This is for PSCell addition / change on the SCG side.

[0149] (3) Fast MCG recovery

[0150] The English name of fast failure recovery of the main cell group can be fast MCG link failure recovery or fast MCG failure recovery or fast MCG recovery or fast MCG link recovery, etc. If a radio link failure occurs on the MCG side, when T316 is configured and the transmission on the SCG side is not suspended, the terminal will trigger the fast MCG recovery process, the terminal starts the T316 timer, and sends MCGFailureInformation to the MN (master node) through the SCG to request the recovery of the MCG. When the MN receives the MCGFailureInformation message sent by the terminal, the MN can send RRCReconfiguration / RRC release / MobilityFromNR to the terminal. When the terminal receives the message sent by the MN, the terminal executes and successfully completes fast MCG recovery. If the terminal does not receive feedback from the network side before T316 times out, when T316 times out, fast MCG recovery fails, and the terminal will trigger the reconstruction process.

[0151] At least one embodiment of the present disclosure provides a mobility optimization method, device, communication device or storage medium. When a terminal is configured with multiple configuration information and is in a scenario where multiple configurations coexist, in the scenario where multiple configurations coexist, if a link failure occurs in the terminal, the terminal will record the failure-related information, and then the terminal will send the failure-related information to the network device. The failure-related information is used by the network device to perform mobility optimization, that is, the failure-related information generated in the scenario where multiple configurations coexist triggers the network device to perform mobility optimization. Compared with the prior art, the network device needs to trigger mobility optimization by detecting the network status. This embodiment enables the network device to perform mobility optimization in a timely manner when the terminal link fails, so that the connection status between the terminal and the network is optimized in a timely manner, providing a guarantee for the application of various network services.

[0152] FIG1 is a flow chart of a mobility optimization method provided by an embodiment of the present disclosure, which is applied to a terminal. As shown in FIG1 , the mobility optimization method may include but is not limited to steps 101 to 103:

[0153] In step 101, the terminal is configured with multiple configuration information, including at least two of the following:

[0154] Mobility LTM configuration information triggered by layer 1 and / or layer 2. This LTM configuration information can be MCG LTM configuration information and / or SCG LTM configuration information;

[0155] Conditional switching CHO configuration information;

[0156] Conditional secondary cell group primary cell PSCell adds or changes CPAC configuration information;

[0157] Master cell group fast failure recovery (fast MCG recovery) configuration information.

[0158] For example, the coexistence scenarios may include, but are not limited to, the following:

[0159] (1) LTM (MCG) configuration information and CHO configuration information coexist;

[0160] (2) LTM (MCG) configuration information and fast MCG recovery configuration information coexist;

[0161] (3) LTM (MCG) configuration information, CHO configuration information, and fast MCG recovery configuration information coexist;

[0162] (4) LTM (SCG) configuration information and CPAC configuration information coexist.

[0163] Specifically, for example, a scenario where LTM configuration information and CHO configuration information coexist refers to a scenario where the terminal is configured with both LTM configuration information (LTM candidate cell configuration, L1 measurement configuration, and other configuration information) and CHO configuration information (CHO candidate cell configuration, execution condition configuration, and other configuration information). A scenario where LTM configuration information and fast MCG recovery configuration information coexist refers to a scenario where the terminal is configured with both LTM configuration information and fast MCG recovery configuration information (i.e., T316 configuration).

[0164] In this embodiment, when the terminal is configured with multiple configuration information, the terminal is in a scenario where multiple configurations coexist, and this embodiment limits the scenario where multiple configurations coexist to include at least two of the configuration information mentioned above. Currently, although the terminal may be configured with multiple configuration information, the network side can only perform mobility optimization for one of the configurations, such as mobility optimization for CHO execution failure, even if the terminal is configured with LTM configuration information and CHO configuration information. However, in this case, there may be a problem if the LTM configured by the network is not executed, and LTM-related information should also be reported to the network for analysis and optimization on the network side, and vice versa. The present application can perform mobility optimization for scenarios where multiple configurations coexist.

[0165] In step 102, if a link failure occurs at the terminal, the terminal records failure-related information.

[0166] At present, if a link failure occurs in a terminal, the terminal will not record the failure-related information of multiple configuration coexistence scenarios, that is, the terminal will not record the various configuration-related information in the multiple configuration coexistence scenario, but will only record the failure-related information related to a certain configuration. In the present application, if a link failure occurs in a terminal and the terminal is in a multiple configuration coexistence scenario, the terminal will record the failure-related information of the coexistence scenario, and the failure-related information may include not only the failure-related information of each configuration information in the multiple configuration coexistence scenario, but also the relative relationship information between different configuration information, etc. The failure-related information of the coexistence scenario refers to the failure-related information related to two or more configuration information in the coexistence scenario, such as the failure-related information related to LTM and CHO configurations.

[0167] In some embodiments, the terminal records failure-related information in a report, where the report includes at least one of the following: a radio link failure (RLF) report, a non-RLF report, and a custom report. The non-RLF report can be one or more of a CEF report, a RACH report, a SHR, a SPR, an SCGFailureInformation message, and the like.

[0168] For example, in a scenario where multiple configurations coexist, for a single failure, the terminal may record other configuration information in addition to failure-related information. For example, for a scenario where LTM execution fails but is successfully recovered (LTM recovery is successful or CHO recovery is successful), the terminal may also record CHO configuration information (such as CHO candidate cells and execution condition information) or configuration indication information. This configuration indication information is used to indicate that the terminal is configured with CHO configuration information.

[0169] In a scenario where multiple configurations coexist, for continuous failures, the terminal may record information related to the continuous failures as well as other configuration information. For example, for LTM execution failure and LTM / CHO recovery failure, the terminal may record LTM failure and LTM / CHO recovery failure information. The terminal may also record CHO configuration information or configuration indication information such as CHO candidate cells and execution condition information. This configuration indication information is used to indicate that the terminal is configured with CHO configuration information.

[0170] The failure-related information recorded by the terminal can be recorded in one report, but is not limited to being recorded in only one report.

[0171] In step 103, the terminal sends failure related information to the network device.

[0172] In this embodiment, the network device is, for example, a base station of an access network. The failure-related information is used by the network device to perform mobility optimization. That is, the network device performs mobility optimization based on the failure-related information generated in a scenario where multiple configurations coexist and reported by the terminal. Compared to the prior art, in which the network device cannot perform mobility optimization for a scenario where multiple configurations coexist, this embodiment enables the network device to perform mobility optimization for a scenario where multiple configurations coexist, thereby ensuring the mobility of the terminal in such a scenario.

[0173] In some embodiments, the “terminal link failure” in step 102 includes at least one of the following:

[0174] The terminal experiences a radio link failure (RLF) in the source cell;

[0175] The terminal fails to execute LTM;

[0176] The terminal fails to perform LTM recovery;

[0177] The terminal fails to execute CHO;

[0178] The terminal fails to perform CHO recovery;

[0179] The terminal fails to perform traditional switching;

[0180] The terminal fails to execute CPAC;

[0181] The terminal fails to perform fast failure recovery of the primary cell group.

[0182] In this embodiment, the terminal performing LTM recovery can be understood as: when a link failure occurs in the terminal, the terminal performs cell selection. If the selected cell is a candidate cell among the LTM candidate cells, the terminal will perform the LTM configuration of this candidate cell, which is LTM recovery.

[0183] In this embodiment, the terminal performing CHO recovery can be understood as: when a link failure occurs in the terminal, the terminal performs cell selection. If the selected cell is a candidate cell among the CHO candidate cells, the terminal will perform the CHO configuration of the candidate cell, which is CHO recovery.

[0184] In step 102, “a link failure occurs at the terminal” includes, but is not limited to, the following 10 failure scenarios:

[0185] (1) The terminal experiences RLF in the source cell and the terminal successfully (or fails) performs the CHO / LTM recovery process; (the terminal is configured with both CHO configuration information and LTM configuration information).

[0186] (2) The terminal experiences an RLF in the source cell. The terminal successfully performs the CHO / LTM recovery process, but an RLF occurs in the CHO / LTM recovery cell shortly thereafter. (The terminal is configured with both CHO and LTM configuration information.)

[0187] (3) The terminal fails to execute LTM, and the terminal succeeds / fails to execute the CHO recovery process; (the terminal is configured with CHO configuration information and LTM configuration information at the same time).

[0188] (4) The terminal fails to execute LTM, but succeeds in the CHO recovery process. However, RLF occurs in the CHO recovery cell for a short time. (The terminal is configured with both CHO configuration information and LTM configuration information.)

[0189] (5) The terminal fails to execute CHO, and the terminal succeeds / fails to execute the LTM recovery process; (the terminal is configured with CHO configuration information and LTM configuration information at the same time).

[0190] (6) The terminal fails to perform CHO and succeeds in LTM recovery, but RLF occurs in the LTM recovery cell for a short time; (the terminal is configured with both CHO configuration information and LTM configuration information).

[0191] (7) The terminal fails to execute legacy HO, and the terminal succeeds (or fails) in executing the CHO / LTM recovery process; (the terminal is configured with both CHO configuration information and LTM configuration information).

[0192] (8) The terminal fails to perform legacy HO and succeeds in CHO / LTM recovery, but RLF occurs in the CHO / LTM recovery cell for a short time; (the terminal is configured with both CHO configuration information and LTM configuration information).

[0193] (9) The terminal fails to execute LTM, and the terminal succeeds (or fails) in executing the fast MCG recovery process; (the terminal is configured with both LTM configuration information and fast MCG recovery configuration information).

[0194] (10) The terminal fails to execute LTM, but succeeds in fast MCG recovery. However, RLF occurs in the target cell for a short time. (The terminal is configured with both LTM configuration information and fast MCG recovery configuration information.)

[0195] In some embodiments, the failure-related information recorded by the terminal in step 102 includes at least one of the following:

[0196] Candidate cell information;

[0197] Time information;

[0198] Instructions.

[0199] In some embodiments, the candidate cell information in the failure-related information includes at least one of the following:

[0200] LTM candidate cell information;

[0201] CHO candidate cell information;

[0202] CPAC candidate cell information.

[0203] In some embodiments, the candidate cell information in the failure-related information includes at least one of the following (1) to (3):

[0204] (1) Identification information of candidate cells.

[0205] The identification information of the candidate cell can be PCI (Physical Cell ID) + frequency or CGI (Cell Global Identifier). The LTM candidate cell identification information is the identification information of each LTM candidate cell configured by the network for the terminal, the CHO candidate cell identification information is the identification information of each CHO candidate cell configured by the network for the terminal, and the CPAC candidate cell identification information is the identification information of each CPAC candidate cell configured by the network for the terminal.

[0206] The identification information can be recorded in one of the following ways:

[0207] Record in list format, that is, introduce a list to record the candidate cell identification information, and each entry in this list is the identification information of a candidate cell;

[0208] Introduce an indication to indicate whether the neighboring cell in the neighboring cell measurement is a candidate cell configured by the network; for example, in the L3 neighboring cell measurement result report, a 1-bit indication is introduced for each neighboring cell to indicate whether this neighboring cell is a CHO candidate cell, or in the L1 measurement result report, a 1-bit indication is introduced for each neighboring cell to indicate whether this neighboring cell is a LTM candidate cell.

[0209] Combined mode: Part of the candidate cell identification information is recorded in a list, and part of the candidate cell identification information is indicated in the neighboring cell measurement results. For example, for neighboring cells included in the neighboring cell measurement, the candidate cell identification information can be reported in the manner indicated in the neighboring cell measurement results. For candidate cells not included in the neighboring cell measurement, the candidate cell identification information can be reported in a list manner.

[0210] (2) Execution conditions of candidate cells.

[0211] The execution condition of a candidate cell is the execution condition configured by the network for each candidate cell. When the terminal evaluates that this execution condition is met, the terminal will access this candidate cell. This execution condition can be an A3 / A4 / A5 event, etc. For example, for the execution condition of a CHO candidate cell: the network will configure an execution condition for each CHO candidate cell (one or two execution conditions, which can be A3 and / or A5 event). When the execution condition of a CHO candidate cell is met, the terminal accesses this CHO candidate cell. For the execution condition of a CPAC candidate cell: the network will configure an execution condition for each CPAC candidate cell (one or two execution conditions, which can be A3 and / or A4 and / or A5 event). When the execution condition of a CPCA candidate cell is met, the terminal accesses this CPAC candidate cell.

[0212] (3) Measurement results of candidate cells.

[0213] Measurement result information for candidate cells. This measurement result information can be L3 measurement results (including cell-level measurement results and / or beam-level measurement results) or L1 measurement results. For example, for CHO or CPAC candidate cells, the L3 measurement results of these candidate cells can be reported, and for LTM candidate cells, the L1 measurement results can be reported. L3 measurement results can include RSRP, RSRP, SIRN, etc., and L1 measurement results can include L1-RSRP, etc.

[0214] Therefore, if the candidate cell information includes LTM candidate cell information, the LTM candidate cell information includes at least one of the following: identification information of the LTM candidate cell; execution conditions of the LTM candidate cell; and measurement results of the LTM candidate cell.

[0215] If the candidate cell information includes CHO candidate cell information, the CHO candidate cell information includes at least one of the following: identification information of the CHO candidate cell; execution conditions of the CHO candidate cell; and measurement results of the CHO candidate cell.

[0216] If the candidate cell information includes CPAC candidate cell information, the CPAC candidate cell information includes at least one of the following: identification information of the CPAC candidate cell; execution conditions of the CPAC candidate cell; and measurement results of the CPAC candidate cell.

[0217] In some embodiments, the time information in the failure-related information includes at least one of the following:

[0218] The time interval between the terminal receiving the LTM configuration information and the terminal receiving the CHO configuration information;

[0219] The time interval between the terminal receiving the LTM configuration information and the CPAC configuration information;

[0220] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO;

[0221] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM;

[0222] The time interval between the terminal receiving the LTM configuration information and starting to execute CPAC;

[0223] The time interval between the terminal receiving the CPAC configuration information and starting to execute LTM;

[0224] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO recovery or the success or failure of CHO recovery execution;

[0225] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM recovery or the success or failure of LTM recovery execution;

[0226] The time interval between the terminal receiving the LTM configuration information and starting to execute the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery;

[0227] The time interval between the failure of the terminal to execute LTM and the start of CHO recovery, or the success or failure of CHO recovery;

[0228] The time interval between the failure of the terminal to execute CHO and the start of LTM recovery, or the success or failure of LTM recovery;

[0229] The time interval between the failure of the terminal to execute LTM and the start of the primary cell group fast failure recovery, or the success or failure of the primary cell group fast failure recovery.

[0230] The time units of the above various time information can be milliseconds, seconds, etc., which are not limited here, and the above various time information are not limited in order.

[0231] It can be seen that the time information in the failure-related information reflects the relative relationship information between different configuration information.

[0232] In some embodiments, the indication information in the failure-related information includes at least one of the following (1) to (6):

[0233] (1) Information on the type of the recovery cell to which the terminal performs recovery.

[0234] In this embodiment, this indication information is used to indicate the type information of the recovery cell to which the terminal performs recovery. That is, if a link failure occurs in the terminal, the terminal performs cell selection, and a cell is selected as a candidate cell among the LTM candidate cell and / or the CHO candidate cell, then this indication information can be used to indicate that the candidate cell is an LTM candidate cell or a CHO candidate cell or an LTM and CHO candidate cell, and the reporting method can be an enumeration type: {CHO candidate cell, LTM candidate cell, both}.

[0235] (2) Indication information of coexistence scenario.

[0236] In this embodiment, this indication information is used to indicate the coexistence scenario, that is, when the terminal fails, which coexistence scenario the terminal is in. It can be an enumeration type, such as {LTM+CHO, LTM+CPAC, LTM+fast MCG recovery, LTM+CHO+fast MCG recovery}, or it can be separate indication information. For example, for the LTM+CHO coexistence scenario, an LTM indication information and a CHO indication information can be introduced respectively, or it can be an implicit indication, that is, the recorded information includes relevant information about LTM and CHO.

[0237] (3) Continuous execution instructions.

[0238] In this embodiment, this indication information is used to indicate the order in which the terminal continuously executes LTM, CHO, CPCA, and fast MCG recovery. For example, if the terminal executes LTM and CHO recovery in the order in which the terminal first executes LTM and then CHO recovery, the indication information may be expressed in an explicit manner or an implicit manner. The explicit manner is that the terminal explicitly records whether the terminal first executes LTM and then CHO recovery, such as by using the enumeration type {LTM-CHO recovery, CHO-LTM recovery, ...}. It may also be used in scenarios of continuous failures to indicate the order of continuous failures. The implicit manner may be to determine whether LTM is executed first or CHO recovery is executed later based on failure-related information recorded by the terminal, such as if the information of the first failure is LTM failure-related information, and the recovery cell is a CHO candidate cell, or by recording the order, where the first LTM failure-related information is recorded at the front of the report, and the subsequent CHO recovery-related information is recorded at the back of the report.

[0239] (4) Timing Advance (TA) indication information: The timing advance indication information is used to indicate whether the terminal has a timing advance TA value and / or TA value size of the recovery cell, and whether the recovery cell to be recovered by the terminal is an LTM candidate cell.

[0240] In this embodiment, if the recovery cell in which the terminal performs recovery is an LTM candidate cell, it indicates whether the terminal has a timing advance TA value and / or TA value size of the recovery cell, which is used to indicate whether the terminal has calculated the TA value of the recovery cell and what the calculated TA value is when the recovery cell is an LTM candidate cell.

[0241] (5) Downlink synchronization indication information: The downlink synchronization indication information is used to indicate whether the terminal has synchronized downlink with the recovery cell, and whether the recovery cell to which the terminal is performing recovery is an LTM candidate cell.

[0242] In this embodiment, if the recovery cell where the terminal performs recovery is an LTM candidate cell, it indicates whether the terminal has been downlink synchronized with the recovery cell. It is used to indicate whether the terminal has completed downlink synchronization with the recovery cell or has performed early downlink synchronization when the recovery cell is an LTM candidate cell.

[0243] (6) Indication information of the same distributed unit (DU): The indication information of the same distributed unit is used to indicate whether the source cell and the restoration cell of the terminal are cells under the same distributed unit DU, and whether the restoration cell where the terminal performs restoration is an LTM candidate cell.

[0244] In this embodiment, if the recovery cell where the terminal performs recovery is an LTM candidate cell, it indicates whether the source cell and the recovery cell of the terminal are cells under the same distribution unit DU, which is used to indicate whether the source cell and the recovery cell are cells under the same DU when the recovery cell is an LTM candidate cell.

[0245] In some embodiments, in step 103, the terminal sends the failure related information to the network device in at least one of the following three ways:

[0246] Method 1: The terminal sends a notification message to the network device, where the notification message is used to indicate that the terminal has recorded failure related information, and the terminal responds to the failure related information request message sent by the network device and sends the failure related information to the network device.

[0247] The notification message may be one or more of an RRC reconfiguration complete message, an RRC connection establishment complete message, an RRC connection recovery complete message, and an RRC connection reestablishment complete message. A 1-bit notification bit is set in the notification message, and the notification bit is 1, indicating that the terminal has recorded information related to the failure. In some embodiments, the notification message may be a custom message, that is, the notification is not sent using an existing message.

[0248] As can be seen, in method 1, the terminal actively notifies the network device: the terminal has recorded the failure-related information. After receiving the notification message, the network device can send a failure-related information request message to the terminal. After receiving the failure-related information request message, the terminal sends the failure-related information to the network device.

[0249] Method 2: After the terminal records the failure-related information, it sends the failure-related information to the network device.

[0250] As can be seen, in method 2, the terminal no longer notifies the network device. Instead, the terminal records the failure-related information and directly sends it to the network device. The terminal does not need to send a notification message to the network device, and the network device does not need to send a request message to the terminal, thus reducing signaling interaction and overhead.

[0251] Method three: the terminal receives a failure related information request message sent by the network device; the terminal responds to the failure related information request message and sends failure related information to the network device.

[0252] It can be seen that in method three, the terminal no longer has any active operations (including actively sending notification messages and actively sending failure-related information), but passively responds to the request message of the network device. Specifically, only when the terminal receives the failure-related information request message sent by the network device, the terminal will respond to the failure-related information request message and send the failure-related information to the network device.

[0253] It should be noted that in method three, since the terminal does not send a notification message to the network device, when the network device sends a failure-related information request message to the terminal, it does not know whether the terminal has recorded the identification-related information. Therefore, when the network device sends the failure-related information request message, the terminal may not have recorded the failure-related information. Even if the terminal receives the failure-related information request message, it has no failure-related information to feedback to the network device.

[0254] Those skilled in the art can configure the terminal to execute at least one of the above three methods according to actual needs.

[0255] FIG2 is a flow chart of another mobility optimization method provided by an embodiment of the present disclosure, which is applied to a network device. As shown in FIG2 , the mobility optimization method may include but is not limited to steps 201 and 202:

[0256] In step 201, the network device receives failure-related information sent by the terminal. The failure-related information is failure-related information recorded when the terminal is configured with multiple configuration information and a link failure occurs in the terminal. The multiple configuration information includes at least two of the following:

[0257] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information.

[0258] In step 202, the network device performs mobility optimization based on the failure related information, or the network device sends the failure related information to the network device related to the failure related information through interface signaling, so that the network device performs mobility optimization based on the received failure related information.

[0259] The interface signaling may be one or more of Xn, X2, E1, F1 and other interface signaling.

[0260] In some embodiments, in step 201, the network device may receive the failure-related information sent by the terminal in at least one of the following three ways:

[0261] Method 1: The network device receives a notification message sent by the terminal, the notification message is used to indicate that the terminal has recorded failure-related information; the network device sends a failure-related information request message to the terminal; the network device receives failure-related information sent by the terminal in response to the failure-related information request message.

[0262] It can be seen that in method 1, after receiving the notification message, the network device can know that the terminal has recorded the failure-related information, and then the network device can send a failure-related information request message to the terminal to receive the failure-related information sent by the terminal in response to the failure-related information request message.

[0263] Method 2: The network device sends a failure related information request message to the terminal; the network device receives failure related information sent by the terminal in response to the failure related information request message.

[0264] It can be seen that in method 2, since the terminal does not send a notification message to the network device, when the network device sends a failure-related information request message to the terminal, it does not know whether the terminal has recorded the identification-related information. Therefore, when the network device sends the failure-related information request message, the terminal may not have recorded the failure-related information. Even if the terminal receives the failure-related information request message, it has no failure-related information to feedback to the network device.

[0265] Method 3: The network device passively receives failure-related information sent by the terminal.

[0266] It can be seen that in the third method, the network device no longer actively sends a failure-related information request message to the terminal, but passively receives the failure-related information sent by the terminal.

[0267] Those skilled in the art can configure the network device to execute at least one of the above three methods according to actual needs.

[0268] It should be noted that for the aforementioned method embodiments, for simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art will understand that the embodiments of the present disclosure are not limited by the order of the actions described, because according to the embodiments of the present disclosure, certain steps can be performed in other orders or simultaneously. In addition, those skilled in the art will understand that the embodiments described in the specification are all optional embodiments.

[0269] FIG3 is a schematic diagram of a mobility optimization device provided by an embodiment of the present disclosure. The mobility optimization device is applied to a terminal. As shown in FIG3 , the mobility optimization device includes but is not limited to: a first unit 31, a second unit 32, and a third unit 33. The specific description is as follows:

[0270] The first unit 31 is configured to be configured with multiple configuration information, the multiple configuration information including at least two of the following: layer 1 and / or layer 2 triggered mobility LTM configuration information, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information;

[0271] The second unit 32 is used to record failure related information if a link failure occurs;

[0272] The third unit 33 is configured to send failure related information to the network device.

[0273] In some embodiments, the occurrence of a link failure includes at least one of the following:

[0274] The terminal experiences a radio link failure (RLF) in the source cell;

[0275] The terminal fails to execute LTM;

[0276] The terminal fails to perform LTM recovery;

[0277] The terminal fails to execute CHO;

[0278] The terminal fails to perform CHO recovery;

[0279] The terminal fails to perform traditional switching;

[0280] The terminal fails to execute CPAC;

[0281] The terminal fails to perform fast failure recovery of the primary cell group.

[0282] In some embodiments, the failure-related information includes at least one of the following:

[0283] Candidate cell information;

[0284] Time information;

[0285] Instructions.

[0286] In some embodiments, the candidate cell information includes at least one of the following:

[0287] LTM candidate cell information;

[0288] CHO candidate cell information;

[0289] CPAC candidate cell information.

[0290] In some embodiments, the time information includes at least one of the following:

[0291] The time interval between the terminal receiving the LTM configuration information and the terminal receiving the CHO configuration information;

[0292] The time interval between the terminal receiving the LTM configuration information and the CPAC configuration information;

[0293] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO;

[0294] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM;

[0295] The time interval between the terminal receiving the LTM configuration information and starting to execute CPAC;

[0296] The time interval between the terminal receiving the CPAC configuration information and starting to execute LTM;

[0297] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO recovery or the success or failure of CHO recovery execution;

[0298] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM recovery or the success or failure of LTM recovery execution;

[0299] The time interval between the terminal receiving the LTM configuration information and starting to execute the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery;

[0300] The time interval between the failure of the terminal to execute LTM and the start of CHO recovery, or the success or failure of CHO recovery;

[0301] The time interval between the failure of the terminal to execute CHO and the start of LTM recovery, or the success or failure of LTM recovery;

[0302] The time interval between the failure of the terminal to execute LTM and the start of the primary cell group fast failure recovery, or the success or failure of the primary cell group fast failure recovery.

[0303] In some embodiments, the indication information includes at least one of the following:

[0304] Type information of the recovery cell to which the terminal performs recovery;

[0305] Indication information for coexistence scenarios;

[0306] Instructions for continuous execution;

[0307] Timing advance indication information, the timing advance indication information is used to indicate whether the terminal has a timing advance TA value and / or TA value size of the recovery cell, and the recovery cell performed by the terminal is an LTM candidate cell;

[0308] Downlink synchronization indication information, which is used to indicate whether the terminal has been downlink synchronized with the recovery cell, and whether the recovery cell to be recovered by the terminal is an LTM candidate cell;

[0309] The indication information of the same distribution unit is used to indicate whether the source cell and the recovery cell of the terminal are cells under the same distribution unit DU, and the recovery cell where the terminal performs recovery is an LTM candidate cell.

[0310] In some embodiments, the candidate cell information includes at least one of the following:

[0311] identification information of candidate cells;

[0312] Execution conditions of candidate cells;

[0313] Measurement results of candidate cells.

[0314] In some embodiments, the third unit 33 is configured to:

[0315] Sending a notification message to the network device, the notification message is used to indicate that the terminal has recorded the failure-related information, and in response to the failure-related information request message sent by the network device, sending the failure-related information to the network device;

[0316] and / or,

[0317] After recording the failure-related information, the second unit 22 sends the failure-related information to the network device;

[0318] and / or,

[0319] Receive a failure related information request message sent by a network device; and send failure related information to the network device in response to the failure related information request message.

[0320] For details of the various embodiments of the mobility optimization device shown in FIG3 , reference may be made to the various embodiments of the mobility optimization method shown in FIG1 , and to avoid repetition, details will be omitted.

[0321] FIG4 is a schematic diagram of another mobility optimization device provided by an embodiment of the present disclosure. The mobility optimization device is applied to a network device. As shown in FIG4 , the mobility optimization device includes but is not limited to: a first unit 41 and a second unit 42, which are specifically described as follows:

[0322] The first unit 41 is configured to receive failure-related information sent by a terminal. The failure-related information is failure-related information recorded when the terminal is configured with multiple configuration information and a link failure occurs in the terminal. The multiple configuration information includes at least two of the following:

[0323] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information.

[0324] The second unit 41 is configured to perform mobility optimization based on the failure related information, or send the failure related information to a network device related to the failure related information through interface signaling, so that the network device performs mobility optimization based on the received failure related information.

[0325] In some embodiments, the first unit 41 is configured to:

[0326] Receiving a notification message sent by a terminal, the notification message being used to indicate that the terminal has recorded failure-related information; sending a failure-related information request message to the terminal; and receiving failure-related information sent by the terminal in response to the failure-related information request message;

[0327] and / or,

[0328] Sending a failure related information request message to the terminal; and receiving failure related information sent by the terminal in response to the failure related information request message.

[0329] For details of the various embodiments of the mobility optimization device shown in FIG4 , reference may be made to the various embodiments of the mobility optimization method shown in FIG2 , and to avoid repetition, details will be omitted.

[0330] The present disclosure also provides a processor-readable storage medium storing a program for causing a processor to execute the steps of each embodiment of the mobility optimization method. The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0331] FIG5 is a schematic diagram of a communication device provided in an embodiment of the present disclosure, which is applied to a terminal. As shown in FIG5 , the communication device provided in an embodiment of the present disclosure includes a memory 51, a transceiver 52, and a processor 53.

[0332] The memory 51 is used to store computer programs; the transceiver 52 is used to send and receive data under the control of the processor 53; the processor 53 is used to read the computer program in the memory 51 and execute:

[0333] The system is configured with multiple configuration information, including at least two of the following:

[0334] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, primary cell group fast failure recovery configuration information;

[0335] If a link failure occurs, record the failure-related information;

[0336] Send information about the failure to the network device.

[0337] In some embodiments, the occurrence of a link failure includes at least one of the following:

[0338] The terminal experiences a radio link failure (RLF) in the source cell;

[0339] The terminal fails to execute LTM;

[0340] The terminal fails to perform LTM recovery;

[0341] The terminal fails to execute CHO;

[0342] The terminal fails to perform CHO recovery;

[0343] The terminal fails to perform traditional switching;

[0344] The terminal fails to execute CPAC;

[0345] The terminal fails to perform fast failure recovery of the primary cell group.

[0346] In some embodiments, the failure-related information includes at least one of the following:

[0347] Candidate cell information;

[0348] Time information;

[0349] Instructions.

[0350] In some embodiments, the candidate cell information includes at least one of the following:

[0351] LTM candidate cell information;

[0352] CHO candidate cell information;

[0353] CPAC candidate cell information.

[0354] In some embodiments, the time information includes at least one of the following:

[0355] The time interval between the terminal receiving the LTM configuration information and the terminal receiving the CHO configuration information;

[0356] The time interval between the terminal receiving the LTM configuration information and the CPAC configuration information;

[0357] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO;

[0358] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM;

[0359] The time interval between the terminal receiving the LTM configuration information and starting to execute CPAC;

[0360] The time interval between the terminal receiving the CPAC configuration information and starting to execute LTM;

[0361] The time interval between the terminal receiving the LTM configuration information and starting to execute CHO recovery or the success or failure of CHO recovery execution;

[0362] The time interval between the terminal receiving the CHO configuration information and starting to execute LTM recovery or the success or failure of LTM recovery execution;

[0363] The time interval between the terminal receiving the LTM configuration information and starting to execute the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery;

[0364] The time interval between the failure of the terminal to execute LTM and the start of CHO recovery, or the success or failure of CHO recovery;

[0365] The time interval between the failure of the terminal to execute CHO and the start of LTM recovery, or the success or failure of LTM recovery;

[0366] The time interval between the failure of the terminal to execute LTM and the start of the primary cell group fast failure recovery, or the success or failure of the primary cell group fast failure recovery.

[0367] In some embodiments, the indication information includes at least one of the following:

[0368] Type information of the recovery cell to which the terminal performs recovery;

[0369] Indication information for coexistence scenarios;

[0370] Instructions for continuous execution;

[0371] Timing advance indication information, the timing advance indication information is used to indicate whether the terminal has a timing advance TA value and / or TA value size of the recovery cell, and the recovery cell performed by the terminal is an LTM candidate cell;

[0372] Downlink synchronization indication information, which is used to indicate whether the terminal has been downlink synchronized with the recovery cell, and whether the recovery cell to be recovered by the terminal is an LTM candidate cell;

[0373] The indication information of the same distribution unit is used to indicate whether the source cell and the recovery cell of the terminal are cells under the same distribution unit DU, and the recovery cell where the terminal performs recovery is an LTM candidate cell.

[0374] In some embodiments, the candidate cell information includes at least one of the following:

[0375] identification information of candidate cells;

[0376] Execution conditions of candidate cells;

[0377] Measurement results of candidate cells.

[0378] In some embodiments, sending failure-related information to the network device includes:

[0379] Sending a notification message to the network device, the notification message is used to indicate that the terminal has recorded the failure-related information, and in response to the failure-related information request message sent by the network device, sending the failure-related information to the network device;

[0380] and / or,

[0381] After recording the failure related information, the failure related information is sent to the network device;

[0382] and / or,

[0383] Receive a failure related information request message sent by a network device; and send failure related information to the network device in response to the failure related information request message.

[0384] In Figure 5, transceiver 52 is used to receive and send data under the control of processor 53. The bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 53 and memory represented by memory 51. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 52 can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 53 is responsible for managing the bus architecture and general processing, and the memory 51 can store data used by the processor 53 when performing operations.

[0385] In FIG5 , the processor 53 can be an integrated circuit chip having signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in the processor 53 or by software instructions. The processor 53 can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor.

[0386] FIG6 is a schematic diagram of another communication device provided in an embodiment of the present disclosure, which is applied to a network device. As shown in FIG6 , the communication device provided in an embodiment of the present disclosure includes a memory 61, a transceiver 62, and a processor 63:

[0387] The memory 61 is used to store computer programs; the transceiver 62 is used to send and receive data under the control of the processor 63; the processor 63 is used to read the computer program in the memory 61 and execute:

[0388] Receive failure-related information sent by the terminal, where the failure-related information is failure-related information recorded when the terminal is configured with multiple configuration information and a link failure occurs on the terminal, and the multiple configuration information includes at least two of the following:

[0389] Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information.

[0390] In some embodiments, receiving the failure-related information sent by the terminal includes:

[0391] Receiving a notification message sent by a terminal, the notification message being used to indicate that the terminal has recorded failure-related information; sending a failure-related information request message to the terminal; and receiving failure-related information sent by the terminal in response to the failure-related information request message;

[0392] and / or,

[0393] Sending a failure related information request message to the terminal; and receiving failure related information sent by the terminal in response to the failure related information request message.

[0394] In some embodiments, the processor 63′ is further configured to read a computer program in the memory and execute:

[0395] Mobility optimization is performed based on the failure related information, or the failure related information is sent to a network device related to the failure related information through interface signaling, so that the network device performs mobility optimization based on the received failure related information.

[0396] In Figure 6, transceiver 62 is used to receive and send data under the control of processor 63. The bus architecture can include any number of interconnected buses and bridges, specifically one or more processors represented by processor 63 and various circuits of memory represented by memory 61. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 62 can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 63 is responsible for managing the bus architecture and general processing, and the memory 61 can store data used by the processor 63 when performing operations.

[0397] In FIG6 , the processor 63 can be an integrated circuit chip having signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in the processor 63 or by software instructions. The processor 63 can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor.

[0398] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0399] Those skilled in the art will appreciate that although some embodiments described herein include certain features and not others included in other embodiments, the combination of features from different embodiments is intended to be within the scope of this disclosure and to form different embodiments.

[0400] Those skilled in the art will appreciate that the description of each embodiment has its own focus, and for parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0401] Although the embodiments of the present disclosure have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A mobility optimization method, applied to a terminal, the method comprising: In the case where the terminal is configured with configuration information, if a link failure occurs to the terminal, the terminal records failure related information; The configuration information includes at least two of the following: Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, primary cell group fast failure recovery configuration information; The terminal sends the failure related information to the network device.

2. The method according to claim 1, wherein: The terminal link failure includes at least one of the following: The terminal has a radio link failure RLF in the source cell; The terminal fails to execute LTM; The terminal fails to perform LTM recovery; The terminal fails to execute CHO; The terminal fails to perform CHO recovery; The terminal fails to perform conventional switching; The terminal fails to execute CPAC; The terminal fails to perform fast failure recovery of the primary cell group.

3. The method according to claim 1, wherein: The failure related information includes at least one of the following: Candidate cell information; Time information; Instructions.

4. The method according to claim 3, wherein: The candidate cell information includes at least one of the following: LTM candidate cell information; CHO candidate cell information; CPAC candidate cell information.

5. The method according to claim 3, wherein: The time information includes at least one of the following: The time interval between the terminal receiving the LTM configuration information and receiving the CHO configuration information; The time interval between the terminal receiving the LTM configuration information and receiving the CPAC configuration information; The time interval between the terminal receiving the LTM configuration information and starting to execute CHO; The time interval between the terminal receiving the CHO configuration information and starting to execute LTM; The time interval between the terminal receiving the LTM configuration information and starting to execute CPAC; The time interval between the terminal receiving the CPAC configuration information and starting to execute the LTM; The time interval between the terminal receiving the LTM configuration information and starting to execute CHO recovery or the success or failure of CHO recovery execution; The time interval between the terminal receiving the CHO configuration information and starting to execute LTM recovery or the success or failure of LTM recovery execution; The time interval between the terminal receiving the LTM configuration information and starting to execute the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery; The time interval between the failure of the terminal to execute LTM and the start of CHO recovery or the success or failure of CHO recovery; The time interval between the failure of the terminal to execute CHO and the start of LTM recovery or the success or failure of LTM recovery; The time interval between the failure of the terminal to execute LTM and the start of the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery.

6. The method according to claim 3, wherein: The indication information includes at least one of the following: Type information of the recovery cell to which the terminal performs recovery; Indicative information for coexistence scenarios; Instructions for continuous execution; Timing advance indication information, the timing advance indication information is used to indicate whether the terminal has a timing advance TA value and / or TA value size of a recovery cell, and the recovery cell for the terminal to perform recovery is an LTM candidate cell; Downlink synchronization indication information, the downlink synchronization indication information is used to indicate whether the terminal has been downlink synchronized with the recovery cell, and the recovery cell in which the terminal performs recovery is an LTM candidate cell; The indication information of the same distribution unit is used to indicate whether the source cell and the recovery cell of the terminal are cells under the same distribution unit DU, and the recovery cell where the terminal performs recovery is an LTM candidate cell.

7. The method according to claim 3 or 4, wherein: The candidate cell information includes at least one of the following: identification information of candidate cells; Execution conditions of candidate cells; Measurement results of candidate cells.

8. The method according to claim 1, wherein: The terminal sends the failure related information to the network device, including: The terminal sends a notification message to the network device, the notification message is used to indicate that the terminal has recorded failure related information, and the terminal sends the failure related information to the network device in response to the failure related information request message sent by the network device; or, After recording the failure-related information, the terminal sends the failure-related information to the network device; and / or, The terminal receives a failure related information request message sent by the network device; and in response to the failure related information request message, the terminal sends the failure related information to the network device.

9. A mobility optimization method, applied to a network device, the method comprising: The network device receives failure related information sent by the terminal, where the failure related information is configuration information configured on the terminal and recorded when a link failure occurs on the terminal, and the configuration information includes at least two of the following: Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional switching CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information.

10. The method according to claim 9, wherein: The network device receives the failure related information sent by the terminal, including: The network device receives a notification message sent by the terminal, the notification message is used to indicate that the terminal has recorded failure related information; the network device sends a failure related information request message to the terminal; the network device receives failure related information sent by the terminal in response to the failure related information request message; and / or, The network device sends a failure related information request message to the terminal; and the network device receives failure related information sent by the terminal in response to the failure related information request message.

11. The method according to claim 9, wherein: The method further comprises: The network device performs mobility optimization based on the failure related information, or the network device sends the failure related information to the network device related to the failure related information through interface signaling, so that the network device performs mobility optimization based on the received failure related information.

12. A communication device, applied to a terminal, wherein: Including memory, transceiver, processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor, configured to read the computer program in the memory and execute: In the case where the terminal is configured with configuration information, if a link failure occurs, failure related information is recorded; the configuration information includes at least two of the following: Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional handover CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, primary cell group fast failure recovery configuration information; The failure related information is sent to the network device.

13. The communication device according to claim 12, wherein: The link failure includes at least one of the following: The terminal has a radio link failure RLF in the source cell; The terminal fails to execute LTM; The terminal fails to perform LTM recovery; The terminal fails to execute CHO; The terminal fails to perform CHO recovery; The terminal fails to perform conventional switching; The terminal fails to execute CPAC; The terminal fails to perform fast failure recovery of the primary cell group.

14. The communication device according to claim 12, wherein: The failure related information includes at least one of the following: Candidate cell information; Time information; Instructions.

15. The communication device according to claim 14, wherein: The candidate cell information includes at least one of the following: LTM candidate cell information; CHO candidate cell information; CPAC candidate cell information.

16. The communication device according to claim 14, wherein: The time information includes at least one of the following: The time interval between the terminal receiving the LTM configuration information and receiving the CHO configuration information; The time interval between the terminal receiving the LTM configuration information and receiving the CPAC configuration information; The time interval between the terminal receiving the LTM configuration information and starting to execute CHO; The time interval between the terminal receiving the CHO configuration information and starting to execute LTM; The time interval between the terminal receiving the LTM configuration information and starting to execute CPAC; The time interval between the terminal receiving the CPAC configuration information and starting to execute the LTM; The time interval between the terminal receiving the LTM configuration information and starting to execute CHO recovery or the success or failure of CHO recovery execution; The time interval between the terminal receiving the CHO configuration information and starting to execute LTM recovery or the success or failure of LTM recovery execution; The time interval between the terminal receiving the LTM configuration information and starting to execute the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery; The time interval between the failure of the terminal to execute LTM and the start of CHO recovery or the success or failure of CHO recovery; The time interval between the failure of the terminal to execute CHO and the start of LTM recovery or the success or failure of LTM recovery; The time interval between the failure of the terminal to execute LTM and the start of the primary cell group fast failure recovery or the success or failure of the primary cell group fast failure recovery.

17. The communication device according to claim 14, wherein: The indication information includes at least one of the following: Type information of the recovery cell to which the terminal performs recovery; Indicative information for coexistence scenarios; Instructions for continuous execution; Timing advance indication information, the timing advance indication information is used to indicate whether the terminal has a timing advance TA value and / or TA value size of a recovery cell, and the recovery cell for the terminal to perform recovery is an LTM candidate cell; Downlink synchronization indication information, the downlink synchronization indication information is used to indicate whether the terminal has been downlink synchronized with the recovery cell, and the recovery cell in which the terminal performs recovery is an LTM candidate cell; The indication information of the same distribution unit is used to indicate whether the source cell and the recovery cell of the terminal are cells under the same distribution unit DU, and the recovery cell where the terminal performs recovery is an LTM candidate cell.

18. The communication device according to claim 14 or 15, wherein: The candidate cell information includes at least one of the following: identification information of candidate cells; Execution conditions of candidate cells; Measurement results of candidate cells.

19. The communication device according to claim 12, wherein: The sending the failure related information to the network device comprises: Sending a notification message to the network device, the notification message is used to indicate that the terminal has recorded failure related information, and in response to the failure related information request message sent by the network device, sending the failure related information to the network device; or, After recording the failure related information, sending the failure related information to the network device; and / or, receiving a failure related information request message sent by the network device; and sending the failure related information to the network device in response to the failure related information request message.

20. A communication device, applied to a network device, wherein: Including memory, transceiver, processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor, configured to read the computer program in the memory and execute: Receive failure related information sent by a terminal, where the failure related information is configuration information that the terminal is configured with and is recorded when a link failure occurs in the terminal, and the configuration information includes at least two of the following: Mobility LTM configuration information triggered by layer 1 and / or layer 2, conditional switching CHO configuration information, conditional secondary cell group primary cell PSCell addition or change CPAC configuration information, and primary cell group fast failure recovery configuration information.

21. The communication device according to claim 20, wherein: The failure related information sent by the receiving terminal includes: receiving a notification message sent by the terminal, the notification message being used to indicate that the terminal has recorded failure related information; sending a failure related information request message to the terminal; and receiving failure related information sent by the terminal in response to the failure related information request message; and / or, Sending a failure related information request message to the terminal; and receiving failure related information sent by the terminal in response to the failure related information request message.

22. The communication device according to claim 20, wherein: The processor is further configured to read the computer program in the memory and execute: Mobility optimization is performed based on the failure related information, or the failure related information is sent to a network device related to the failure related information through interface signaling, so that the network device performs mobility optimization based on the received failure related information.

23. A processor-readable storage medium, wherein: The processor-readable storage medium stores a program, and the program is used to enable the processor to execute the mobility optimization method according to any one of claims 1 to 8 or the mobility optimization method according to any one of claims 9 to 11.

Images