WO2025119034A1 - 一种移动性优化方法、装置、通信装置及存储介质 - Google Patents

一种移动性优化方法、装置、通信装置及存储介质 Download PDF

Info

Publication number
WO2025119034A1
WO2025119034A1 PCT/CN2024/134533 CN2024134533W WO2025119034A1 WO 2025119034 A1 WO2025119034 A1 WO 2025119034A1 CN 2024134533 W CN2024134533 W CN 2024134533W WO 2025119034 A1 WO2025119034 A1 WO 2025119034A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
failure
recovery
ltm
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/134533
Other languages
English (en)
French (fr)
Inventor
严雪
彦楠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Publication of WO2025119034A1 publication Critical patent/WO2025119034A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/04—Reselecting a cell layer in multi-layered cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/165—Performing reselection for specific purposes for reducing network power consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • the embodiments of the present disclosure relate to the field of communication technology, and in particular to a mobility optimization method, device, communication device, and storage medium.
  • terminals may be configured with different mobility configuration information by the network.
  • the network When a terminal is configured with multiple configuration information and the terminal fails to execute any configuration information, resulting in mobility problems, the network only optimizes the mobility of the single configuration information that failed to execute.
  • other unexecuted configuration information of the terminal may also cause mobility problems. Therefore, after the current network optimizes the mobility for a single configuration information, the terminal may still have mobility problems and cannot meet the mobility requirements of the terminal in scenarios where multiple configurations coexist.
  • the network cannot optimize the mobility for mobility problems in scenarios where multiple configuration information coexist.
  • At least one embodiment of the present disclosure provides a mobility optimization method, device, communication device, and storage medium.
  • an embodiment of the present disclosure proposes a mobility optimization method, which is applied to a terminal.
  • the mobility optimization method includes:
  • the terminal When a terminal is configured with configuration information, if a link failure occurs in the terminal, the terminal records failure-related information;
  • the configuration information includes at least the following two types:
  • 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 information related to the failure to the network device.
  • the link failure of the terminal includes at least one of the following:
  • the terminal experiences 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 traditional switching
  • the terminal fails to execute CPAC
  • the terminal fails to execute fast failure recovery of the primary cell group.
  • the failure-related information includes at least one of the following:
  • the candidate cell information includes at least one of the following:
  • the time information includes at least one of the following:
  • the indication information includes at least one of the following:
  • Timing advance indication information where 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 which the terminal performs recovery is an LTM candidate cell;
  • 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 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.
  • the candidate cell information includes at least one of the following:
  • the terminal sends 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 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;
  • the terminal After recording the failure-related information, the terminal sends the failure-related information to the network device;
  • the terminal receives the failure related information request message sent by the network device; the terminal responds to the failure related information request message and sends the failure related information to the network device.
  • the embodiment of the present disclosure further proposes a mobility optimization method, which is applied to a network device.
  • the mobility optimization method includes:
  • the network device receives failure related information sent by the terminal, where the failure related information is configuration information that the terminal is configured with and 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.
  • 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 the failure related information; the network device sends a failure related information request message to the terminal; the network device receives the failure related information sent by the terminal in response to the failure related information request message;
  • 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.
  • the mobility optimization method further includes:
  • 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.
  • an embodiment of the present disclosure further proposes a communication device, applied to a terminal, which includes a memory, a transceiver, and a processor:
  • 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:
  • the configuration information includes at least the following two types:
  • 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 occurrence of a link failure includes at least one of the following:
  • the terminal experiences 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 traditional switching
  • the terminal fails to execute CPAC
  • the terminal fails to execute fast failure recovery of the primary cell group.
  • the failure-related information includes at least one of the following:
  • the candidate cell information includes at least one of the following:
  • the time information includes at least one of the following:
  • the indication information includes at least one of the following:
  • Timing advance indication information where 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 which the terminal performs recovery is an LTM candidate cell;
  • 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 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.
  • the candidate cell information includes at least one of the following:
  • sending failure related information to the network device includes:
  • 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;
  • the failure-related information is sent to the network device;
  • an embodiment of the present disclosure further provides a communication device, which is applied to a network device, and includes a memory, a transceiver, and a processor:
  • 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:
  • the failure related information sent by the receiving terminal 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:
  • 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.
  • receiving failure-related information sent by the terminal includes:
  • the notification message is used to indicate that the terminal has recorded failure related information; sending a failure related information request message to the terminal; receiving failure related information sent by the terminal in response to the failure related information request message;
  • the processor is further configured to read a 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.
  • 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 execute the mobility optimization method of any embodiment of the second aspect.
  • a terminal when a terminal is configured with multiple configuration information and the terminal 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 information related to the failure, and then the terminal will send information related to the failure to a network device, and the information related to the failure 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 scenario where multiple configurations coexist and reported by the terminal.
  • the network device cannot perform mobility optimization for the scenario where multiple configurations coexist, and this embodiment enables the network device to perform mobility optimization for the scenario where multiple configurations coexist, thereby providing a guarantee for the mobility of the terminal in the scenario where multiple configurations coexist.
  • FIG1 is a schematic diagram of a flow chart of a mobility optimization method provided by an embodiment of the present disclosure
  • FIG2 is a schematic diagram of a flow chart of another mobility optimization method provided by an embodiment of the present disclosure.
  • FIG3 is a schematic diagram of a mobility optimization device provided by an embodiment of the present disclosure.
  • FIG4 is a schematic diagram of another mobility optimization device provided by an embodiment of the present disclosure.
  • FIG5 is a schematic diagram of a communication device provided by an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of another communication device provided in an embodiment of the present disclosure.
  • the terminal may be configured with different mobility configuration information by the network, but the network side can only perform mobility optimization for the configuration information that fails to execute:
  • 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.
  • L1/L2 triggered mobility, LTM layer 1 and/or layer 2 triggered mobility
  • CHO conditional handover
  • the LTM configuration information may also cause mobility problems.
  • the CHO configuration information may also cause mobility problems. That is, after mobility optimization for a single configuration information, the terminal may still have mobility problems, and cannot meet the mobility requirements of the terminal in a scenario where multiple configurations coexist.
  • the network can send multiple 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 these configuration information, the terminal can perform mobility, but the network equipment cannot optimize mobility based on mobility issues in scenarios where multiple configurations coexist.
  • LTM configuration information such as LTM configuration information, CHO configuration information, Conditional PSCell addition/change (CPAC) configuration information, and fast MCG recovery configuration information.
  • CPAC Conditional PSCell addition/change
  • LTM mechanism that is, the network pre-configures multiple candidate cell configurations and their L1 measurement configurations for the terminal.
  • the terminal performs L1 measurement and reports based on the L1 measurement configuration configured by the network.
  • the network sends an LTM cell switch command to the terminal based on the L1 measurement result reported by the terminal. This LTM cell switch command is sent to the terminal via MAC CE (MAC Control Element).
  • MAC CE MAC Control Element
  • the terminal When the terminal receives the LTM cell switch command sent by the network, the terminal will execute the LTM cell switch. If the terminal fails to execute the LTM cell switch, the terminal will execute the cell selection process. If the target cell selected by the terminal cell selection is an LTM candidate cell, the terminal will execute LTM recovery. If the target cell selected by the terminal cell selection is not an LTM candidate cell, the terminal will trigger the reconstruction process. If the target cell selected by the terminal cell selection is an LTM candidate cell, when the terminal fails to execute the LTM recovery, the terminal will trigger the reconstruction process.
  • CHO means that the network configures multiple CHO candidate cells and their corresponding execution conditions for the terminal.
  • the terminal evaluates the CHO candidate cells based on the measurement results. If a candidate cell is evaluated to meet the execution conditions, the terminal accesses this candidate target cell. This is for PCell change (handover) on the MCG (Master 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 is evaluated to meet the execution conditions, the terminal accesses this candidate target cell. This is for PSCell addition/change on the SCG side.
  • the English name of fast failure recovery of the master 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.
  • the MN receives the MCGFailureInformation message sent by the terminal, the MN can send RRCReconfiguration/RRC release/MobilityFromNR to the terminal.
  • the terminal executes and successfully completes the fast MCG recovery. If the terminal does not receive feedback from the network side before T316 times out, when T316 times out, the fast MCG recovery fails, and the terminal will trigger the reconstruction process.
  • At least one embodiment of the present disclosure provides a mobility optimization method, device, communication device or storage medium.
  • a terminal When a terminal is configured with multiple configuration information and the terminal 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 information related to the failure, and then the terminal will send information related to the failure to a network device.
  • the information related to the failure is used by the network device to perform mobility optimization. That is, the information related to the failure generated in the scenario where multiple configurations coexist triggers the network device to perform mobility optimization.
  • the present 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, thereby providing a guarantee for the application of various network services.
  • FIG1 is a flow chart of a mobility optimization method provided by an embodiment of the present disclosure, and the mobility optimization method is applied to a terminal.
  • the mobility optimization method may include but is not limited to steps 101 to 103:
  • the terminal is configured with a plurality of configuration information, wherein the plurality of configuration information includes at least two of the following:
  • This LTM configuration information can be MCG LTM configuration information and/or SCG LTM configuration information;
  • Conditional secondary cell group primary cell PSCell adds or changes CPAC configuration information
  • the coexistence scenarios may include, but are not limited to, the following types of coexistence:
  • the scenario where LTM configuration information and CHO configuration information coexist means that the terminal is configured with 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).
  • LTM configuration information and fast MCG recovery configuration information coexist means that the terminal is configured with LTM configuration information and fast MCG recovery configuration information (i.e. T316 configuration) at the same time.
  • the terminal 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.
  • 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.
  • mobility optimization for CHO execution failure even if the terminal is configured with LTM configuration information and CHO configuration information.
  • LTM configuration information LTM configuration information and CHO configuration information.
  • the present application can perform mobility optimization for scenarios where multiple configurations coexist.
  • step 102 if a link failure occurs in the terminal, the terminal records information related to the failure.
  • the terminal will not record failure-related information of multiple configuration coexistence scenarios, that is, the terminal will not record various configuration-related information in multiple configuration coexistence scenarios, but will only record failure-related information related to a certain configuration.
  • the terminal will record failure-related information of the coexistence scenario, and the failure-related information may include not only failure-related information of each configuration information in the multiple configuration coexistence scenario, but also relative relationship information between different configuration information, etc.
  • the failure-related information of the coexistence scenario refers to failure-related information related to two or more configuration information in the coexistence scenario, such as failure-related information related to LTM and CHO configurations.
  • the terminal records the failure-related information in a report, wherein 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 may be one or more of a CEF report, a RACH Report, a SHR, a SPR, a SCGFailureInformation message, and the like.
  • the terminal can record other configuration information in addition to failure-related information.
  • the terminal can 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.
  • the terminal may record other configuration information in addition to recording information related to the continuous failures.
  • 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.
  • 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.
  • step 103 the terminal sends failure related information to the network device.
  • 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 the scenario of multiple configurations coexisting reported by the terminal.
  • the network device cannot perform mobility optimization for the scenario of multiple configurations coexisting.
  • the network device can perform mobility optimization for the scenario of multiple configurations coexisting, and provide guarantee for the mobility of the terminal in the scenario of multiple configurations coexisting.
  • step 102 “a link failure occurs at the terminal” includes at least one of the following:
  • the terminal experiences 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 traditional switching
  • the terminal fails to execute CPAC
  • the terminal fails to execute fast failure recovery of the primary cell group.
  • 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.
  • 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.
  • step 102 “a link failure occurs at the terminal” includes, for example, but is not limited to, the following 10 failure scenarios:
  • the terminal has an RLF in the source cell, and the terminal successfully (or fails) performs the CHO/LTM recovery process; (the terminal is configured with CHO configuration information and LTM configuration information at the same time).
  • the terminal has 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 within a short period of time; (the terminal is configured with CHO configuration information and LTM configuration information at the same time).
  • the terminal fails to execute LTM, and the terminal succeeds/fails in executing the CHO recovery process; (the terminal is configured with CHO configuration information and LTM configuration information at the same time).
  • 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 CHO configuration information and LTM configuration information at the same time).
  • the terminal fails to execute CHO, and the terminal succeeds/fails in executing the LTM recovery process; (the terminal is configured with CHO configuration information and LTM configuration information at the same time).
  • the terminal fails to perform CHO, but succeeds in performing LTM recovery. However, RLF occurs in the LTM recovery cell for a short time. (The terminal is configured with CHO configuration information and LTM configuration information at the same time).
  • the terminal fails to execute legacy HO, and the terminal succeeds (or fails) in the CHO/LTM recovery process; (the terminal is configured with CHO configuration information and LTM configuration information at the same time).
  • the terminal fails to execute legacy HO, but succeeds in CHO/LTM recovery. However, RLF occurs in the CHO/LTM recovery cell for a short time. (The terminal is configured with CHO configuration information and LTM configuration information at the same time).
  • the terminal fails to execute LTM, and the terminal succeeds (or fails) in executing the fast MCG recovery process; (the terminal is configured with LTM configuration information and fast MCG recovery configuration information at the same time).
  • the terminal fails to execute LTM, and successfully executes the fast MCG recovery process, but RLF occurs in the recovery target cell for a short time; (the terminal is configured with LTM configuration information and fast MCG recovery configuration information at the same time).
  • the failure-related information recorded by the terminal in step 102 includes at least one of the following:
  • the candidate cell information in the failure related information includes at least one of the following:
  • the candidate cell information in the failure-related information includes at least one of the following (1) to (3):
  • 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
  • the CPAC candidate cell identification information is the identification information of each CPAC candidate cell configured by the network for the terminal.
  • the identification information can be recorded in one of the following ways:
  • an indication information 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.
  • Combined mode that is, part of the candidate cell identification information is recorded in the list, and part of the candidate cell identification information is indicated in the neighboring area measurement result.
  • the candidate cell identification information can be reported in the manner indicated in the neighboring area measurement result.
  • the candidate cell identification information can be reported in the list manner.
  • the execution condition of the 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 A3/A4/A5 event, etc.
  • the network will configure the 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.
  • the execution condition of the CPAC candidate cell the network will configure the 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.
  • the measurement result information of the candidate cell may be L3 measurement results (including cell-level measurement results and/or beam-level measurement results) or L1 measurement results.
  • L3 measurement results including cell-level measurement results and/or beam-level measurement results
  • L1 measurement results may be reported.
  • the L3 measurement results may be RSRP, RSRP, SIRN, etc.
  • the L1 measurement results may be L1-RSRP, etc.
  • 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.
  • 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.
  • 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.
  • the time information in the failure-related information includes at least one of the following:
  • 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 has no restriction on the order.
  • time information in the failure related information reflects the relative relationship information between different configuration information.
  • the indication information in the failure-related information includes at least one of the following (1) to (6):
  • 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 ⁇ .
  • the 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.
  • 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.
  • this indication information is used to indicate the order in which the terminal continuously executes LTM, CHO, CPCA, and fast MCG recovery.
  • the terminal executes in the order of LTM and CHO recovery, that is, the terminal first executes LTM and then CHO recovery.
  • the indication information can be expressed in an explicit manner or an implicit manner.
  • the explicit manner is that the terminal explicitly records that the terminal first executes LTM and then CHO recovery, such as using the enumeration type ⁇ LTM-CHO recovery, CHO-LTM recovery, ... ⁇ . It can also be used in scenarios of continuous failures to indicate the failure order of continuous failures.
  • the implicit manner can be to determine whether to execute LTM first or CHO recovery later through the failure-related information recorded by the terminal, such as the information of the first failure is LTM failure-related information, and the recovery cell is a CHO candidate cell, or through the recording order, 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.
  • Timing Advance (TA) 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.
  • the recovery cell where 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.
  • Downlink synchronization indication information 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.
  • the recovery cell where the terminal performs recovery is an LTM candidate cell
  • the indication information of the same distributed unit is used to indicate whether the source cell and the recovery cell of the terminal are cells under the same distributed unit DU, and whether the recovery cell where the terminal performs recovery is an LTM candidate cell.
  • the recovery cell where the terminal performs recovery is an LTM candidate cell
  • the terminal sends the failure related information to the network device in at least one of the following three ways:
  • 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.
  • 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 failure-related information.
  • the notification message may be a custom message, that is, the notification is not sent using an existing message.
  • the terminal actively notifies the network device: the terminal has recorded the failure related information, and 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.
  • Method 2 After recording the failure-related information, the terminal sends the failure-related information to the network device.
  • the terminal no longer notifies the network device, but the terminal records the failure-related information and directly sends the failure-related information 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, so signaling interaction and overhead can be reduced.
  • Mode 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 the failure related information to the network device.
  • the terminal no longer has any active operation (including actively sending notification messages, actively sending failure-related information), but passively responds to the request message of the network device. Specifically, the terminal only responds to the failure-related information request message and sends the failure-related information to the network device after receiving the failure-related information request message sent by the network device.
  • the terminal 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 a 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.
  • FIG2 is a flow chart of another mobility optimization method provided by an embodiment of the present disclosure, and the mobility optimization method is applied to a network device.
  • the mobility optimization method may include but is not limited to step 201 and step 202:
  • the network device receives 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 in the terminal, and the multiple 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.
  • 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.
  • the interface signaling may be one or more of the interface signalings such as Xn, X2, E1, and F1.
  • the network device receives the failure related information sent by the terminal in at least one of the following three ways:
  • 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.
  • the network device 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.
  • Mode 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.
  • the terminal 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 a 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 feed back to the network device.
  • Method 3 The network device passively receives failure-related information sent by the terminal.
  • 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.
  • 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.
  • the mobility optimization device includes but is not limited to: a first unit 31, a second unit 32 and a third unit 33, which are specifically described as follows:
  • the first unit 31 is configured with a plurality of configuration information, wherein the plurality of configuration information includes at least two of the following: LTM configuration information of mobility triggered by layer 1 and/or layer 2, CHO configuration information of conditional handover, CPAC configuration information of adding or changing the primary cell PSCell of the conditional secondary cell group, and fast failure recovery configuration information of the primary cell group;
  • the second unit 32 is used to record failure related information if a link failure occurs
  • the third unit 33 is used to send failure related information to the network device.
  • the occurrence of a link failure includes at least one of the following:
  • the terminal experiences 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 traditional switching
  • the terminal fails to execute CPAC
  • the terminal fails to execute fast failure recovery of the primary cell group.
  • the failure-related information includes at least one of the following:
  • the candidate cell information includes at least one of the following:
  • the time information includes at least one of the following:
  • the indication information includes at least one of the following:
  • Timing advance indication information where 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 which the terminal performs recovery is an LTM candidate cell;
  • 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 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.
  • the candidate cell information includes at least one of the following:
  • the third unit 33 is used to:
  • 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;
  • the second unit 22 After recording the failure-related information, the second unit 22 sends the failure-related information to the network device;
  • 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.
  • 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:
  • the first unit 41 is configured to receive failure related information sent by a 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 in the terminal, and the multiple 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.
  • the second unit 41 is configured to perform mobility optimization based on the failure related information, or to send the failure related information to a network device related to the failure related information through an interface signaling, so that the network device performs mobility optimization based on the received failure related information.
  • the first unit 41 is configured to:
  • the notification message is used to indicate that the terminal has recorded failure related information; sending a failure related information request message to the terminal; receiving failure related information sent by the terminal in response to the failure related information request message;
  • the disclosed embodiment also provides a processor-readable storage medium, wherein the processor-readable storage medium stores a program, wherein the program is used to enable the 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 that the processor can access, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.
  • FIG5 is a schematic diagram of a communication device provided in an embodiment of the present disclosure, which is applied to a terminal.
  • the communication device provided in an embodiment of the present disclosure includes a memory 51, a transceiver 52, and a processor 53:
  • 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:
  • the multiple configuration information is configured, and the multiple 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 occurrence of a link failure includes at least one of the following:
  • the terminal experiences 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 traditional switching
  • the terminal fails to execute CPAC
  • the terminal fails to execute fast failure recovery of the primary cell group.
  • the failure-related information includes at least one of the following:
  • the candidate cell information includes at least one of the following:
  • the time information includes at least one of the following:
  • the indication information includes at least one of the following:
  • Timing advance indication information where 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 which the terminal performs recovery is an LTM candidate cell;
  • 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 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.
  • the candidate cell information includes at least one of the following:
  • sending failure related information to the network device includes:
  • 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;
  • the failure-related information is sent to the network device;
  • a transceiver 52 is used to receive and send data under the control of a processor 53.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by a processor 53 and various circuits of a memory represented by a memory 51 are linked together.
  • the bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein.
  • the bus interface provides an interface.
  • the transceiver 52 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include 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 may store data used by the processor 53 when performing operations.
  • the processor 53 may be an integrated circuit chip having the ability to process signals. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 53 or by instructions in the form of software.
  • the processor 53 may 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 gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
  • FIG6 is a schematic diagram of another communication device provided in an embodiment of the present disclosure, which is applied to a network device.
  • the communication device provided in an embodiment of the present disclosure includes a memory 61, a transceiver 62, and a processor 63:
  • 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:
  • the failure related information sent by the receiving terminal is failure related information recorded when the terminal is configured with multiple configuration information and a link failure occurs in the terminal, and the multiple 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.
  • receiving failure-related information sent by the terminal includes:
  • the notification message is used to indicate that the terminal has recorded failure related information; sending a failure related information request message to the terminal; receiving failure related information sent by the terminal in response to the failure related information request message;
  • the processor 63 is further configured to read a 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.
  • the transceiver 62 is used to receive and send data under the control of the processor 63.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 63 and various circuits of the memory represented by the memory 61 are linked together.
  • the bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein.
  • the bus interface provides an interface.
  • the transceiver 62 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium includes a wireless channel, a wired channel, an optical cable, and other transmission media.
  • the processor 63 is responsible for managing the bus architecture and general processing, and the memory 61 may store data used by the processor 63 when performing operations.
  • the processor 63 may be an integrated circuit chip having the ability to process signals. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 63 or by instructions in the form of software.
  • the processor 63 may 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 gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

Landscapes

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

Abstract

本公开涉及一种移动性优化方法、装置、通信装置及存储介质。本公开至少一个实施例中，当终端被配置多种配置信息，终端处于多种配置共存场景，在多种配置共存场景下，若终端发生链路失败，则终端会记录失败相关信息，进而终端将失败相关信息发送给网络设备，失败相关信息用于网络设备进行移动性优化，也即，网络设备基于终端上报的多种配置共存场景下产生的失败相关信息进行移动性优化，相比现有技术中，网络设备无法针对多种配置共存场景进行移动性优化，本实施例使得网络设备可以针对多种配置共存场景，进行移动性优化，为终端在多种配置共存场景下的移动性提供保证。

Description

一种移动性优化方法、装置、通信装置及存储介质
相关申请的交叉引用
本公开要求在2023年12月08日提交中国专利局、申请号为202311688756.5、申请名称为“一种移动性优化方法、装置、通信装置及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本公开中。
技术领域
本公开实施例涉及通信技术领域，具体涉及一种移动性优化方法、装置、通信装置及存储介质。
背景技术
随着通信技术发展，终端可能被网络配置不同的移动性配置信息，当终端被配置多种配置信息，且终端执行任一配置信息失败导致移动性问题时，网络只针对执行失败的单一配置信息进行移动性优化。然而，终端其他未执行的配置信息也可能会导致移动性问题，因此，目前网络针对单一配置信息进行移动性优化之后，终端仍然可能存在移动性问题，无法满足多种配置共存场景下终端的移动性需求。目前网络无法针对多种配置信息共存场景下的移动性问题进行移动性优化。
发明内容
本公开的至少一个实施例提供了一种移动性优化方法、装置、通信装置及存储介质。
第一方面，本公开实施例提出一种移动性优化方法，应用于终端，移动性优化方法包括：
在终端被配置配置信息的情况下，若终端发生链路失败，终端记录失败相关信息；配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息；
终端将失败相关信息发送给网络设备。
在一些实施例中，终端发生链路失败包括以下至少一种：
终端在源小区发生无线链路失败RLF；
终端执行LTM失败；
终端执行LTM恢复失败；
终端执行CHO失败；
终端执行CHO恢复失败；
终端执行传统切换失败；
终端执行CPAC失败；
终端执行主小区组快速失败恢复失败。
在一些实施例中，失败相关信息包括以下至少一种：
候选小区信息；
时间信息；
指示信息。
在一些实施例中，候选小区信息包括以下至少一种：
LTM候选小区信息；
CHO候选小区信息；
CPAC候选小区信息。
在一些实施例中，时间信息包括以下至少一种：
终端收到LTM配置信息与收到CHO配置信息之间的时间间隔；
终端收到LTM配置信息与收到CPAC配置信息之间的时间间隔；
终端收到LTM配置信息与开始执行CHO之间的时间间隔；
终端收到CHO配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CPAC之间的时间间隔；
终端收到CPAC配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端收到CHO配置信息与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端收到LTM配置信息与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端执行CHO失败与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔。
在一些实施例中，指示信息包括以下至少一种：
终端执行恢复的恢复小区所属的类型信息；
共存场景的指示信息；
连续执行的指示信息；
定时提前的指示信息，定时提前的指示信息用于指示终端是否有恢复小区的定时提前TA值和/或TA值大小，且终端执行恢复的恢复小区为LTM候选小区；
下行同步的指示信息，下行同步的指示信息用于指示终端是否已经和恢复小区下行同步，且终端执行恢复的恢复小区为LTM候选小区；
同一分布单元的指示信息，同一分布单元的指示信息用于指示终端的源小区与恢复小区是否为同一分布单元DU下的小区，且终端执行恢复的恢复小区为LTM候选小区。
在一些实施例中，候选小区信息包括以下至少一种：
候选小区的标识信息；
候选小区的执行条件；
候选小区的测量结果。
在一些实施例中，终端将失败相关信息发送给网络设备，包括：
终端向网络设备发送通知消息，通知消息用于指示终端记录有失败相关信息，且终端响应于网络设备发送的失败相关信息请求消息，将失败相关信息发送给网络设备；
或，
终端记录失败相关信息后，将失败相关信息发送给网络设备；
和/或，
终端接收网络设备发送的失败相关信息请求消息；终端响应于失败相关信息请求消息，将失败相关信息发送给网络设备。
第二方面，本公开实施例还提出一种移动性优化方法，应用于网络设备，该移动性优化方法包括：
网络设备接收终端发送的失败相关信息，失败相关信息为终端被配置配置信息、且终端发生链路失败时记录的失败相关信息，配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息。
在一些实施例中，网络设备接收终端发送的失败相关信息，包括：
网络设备接收终端发送的通知消息，通知消息用于指示终端记录有失败相关信息；网络设备向终端发送失败相关信息请求消息；网络设备接收终端响应于失败相关信息请求消息而发送的失败相关信息；
和/或，
网络设备向终端发送失败相关信息请求消息；网络设备接收终端响应于失败相关信息请求消息而发送的失败相关信息。
在一些实施例中，移动性优化方法还包括：
网络设备基于失败相关信息进行移动性优化，或者，网络设备通过接口信令将失败相关信息发送给失败相关信息相关的网络设备，以使该网络设备基于接收到的失败相关信息进行移动性优化。
第三方面，本公开实施例还提出一种通信装置，应用于终端，其中，包括存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在处理器的控制下收发数据；处理器，用于读取存储器中的计算机程序并执行：
在终端被配置配置信息的情况下，若发生链路失败，记录失败相关信息；配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息；
将失败相关信息发送给网络设备。
在一些实施例中，发生链路失败包括以下至少一种：
终端在源小区发生无线链路失败RLF；
终端执行LTM失败；
终端执行LTM恢复失败；
终端执行CHO失败；
终端执行CHO恢复失败；
终端执行传统切换失败；
终端执行CPAC失败；
终端执行主小区组快速失败恢复失败。
在一些实施例中，失败相关信息包括以下至少一种：
候选小区信息；
时间信息；
指示信息。
在一些实施例中，候选小区信息包括以下至少一种：
LTM候选小区信息；
CHO候选小区信息；
CPAC候选小区信息。
在一些实施例中，时间信息包括以下至少一种：
终端收到LTM配置信息与收到CHO配置信息之间的时间间隔；
终端收到LTM配置信息与收到CPAC配置信息之间的时间间隔；
终端收到LTM配置信息与开始执行CHO之间的时间间隔；
终端收到CHO配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CPAC之间的时间间隔；
终端收到CPAC配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端收到CHO配置信息与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端收到LTM配置信息与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端执行CHO失败与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔。
在一些实施例中，指示信息包括以下至少一种：
终端执行恢复的恢复小区所属的类型信息；
共存场景的指示信息；
连续执行的指示信息；
定时提前的指示信息，定时提前的指示信息用于指示终端是否有恢复小区的定时提前TA值和/或TA值大小，且终端执行恢复的恢复小区为LTM候选小区；
下行同步的指示信息，下行同步的指示信息用于指示终端是否已经和恢复小区下行同步，且终端执行恢复的恢复小区为LTM候选小区；
同一分布单元的指示信息，同一分布单元的指示信息用于指示终端的源小区与恢复小区是否为同一分布单元DU下的小区，且终端执行恢复的恢复小区为LTM候选小区。
在一些实施例中，候选小区信息包括以下至少一种：
候选小区的标识信息；
候选小区的执行条件；
候选小区的测量结果。
在一些实施例中，将失败相关信息发送给网络设备，包括：
向网络设备发送通知消息，通知消息用于指示终端记录有失败相关信息，且响应于网络设备发送的失败相关信息请求消息，将失败相关信息发送给网络设备；
或，
记录失败相关信息后，将失败相关信息发送给网络设备；
和/或，
接收网络设备发送的失败相关信息请求消息；响应于失败相关信息请求消息，将失败相关信息发送给网络设备。
第四方面，本公开实施例还提出一种通信装置，应用于网络设备，其中，包括存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在处理器的控制下收发数据；处理器，用于读取存储器中的计算机程序并执行：
接收终端发送的失败相关信息，失败相关信息为终端被配置配置信息、且终端发生链路失败时记录的失败相关信息，配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息。
在一些实施例中，接收终端发送的失败相关信息，包括：
接收终端发送的通知消息，通知消息用于指示终端记录有失败相关信息；向终端发送失败相关信息请求消息；接收终端响应于失败相关信息请求消息而发送的失败相关信息；
和/或，
向终端发送失败相关信息请求消息；接收终端响应于失败相关信息请求消息而发送的失败相关信息。
在一些实施例中，处理器，还用于读取存储器中的计算机程序并执行：
基于失败相关信息进行移动性优化，或者，通过接口信令将失败相关信息发送给失败相关信息相关的网络设备，以使该网络设备基于接收到的失败相关信息进行移动性优化。
第五方面，本公开实施例还提出一种处理器可读存储介质，处理器可读存储介质存储有程序，程序用于使处理器执行第一方面任一实施例的移动性优化方法或者执行第二方面任一实施例的移动性优化方法。
本公开的至少一个实施例中，当终端被配置多种配置信息，终端处于多种配置共存场景，在多种配置共存场景下，若终端发生链路失败，则终端会记录失败相关信息，进而终端将失败相关信息发送给网络设备，失败相关信息用于网络设备进行移动性优化，也即，网络设备基于终端上报的多种配置共存场景下产生的失败相关信息触发网络设备进行移动性优化，相比现有技术中，网络设备无法针对多种配置共存场景进行移动性优化，本实施例使得网络设备可以针对多种配置共存场景，进行移动性优化，为终端在多种配置共存场景下的移动性提供保证。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，还可以根据这些附图获得其他的附图。
图1为本公开实施例提供的一种移动性优化方法的流程示意图；
图2为本公开实施例提供的另一种移动性优化方法的流程示意图；
图3为本公开实施例提供的一种移动性优化装置的示意图；
图4为本公开实施例提供的另一种移动性优化装置的示意图；
图5为本公开实施例提供的一种通信装置的示意图；
图6为本公开实施例提供的另一种通信装置的示意图。
具体实施方式
为了能够更清楚地理解本公开的上述目的、特征和优点，下面结合附图和实施例对本公开作进一步的详细说明。可以理解的是，所描述的实施例是本公开的一部分实施例，而不是全部的实施例。此处所描述的具体实施例仅仅用于解释本公开，而非对本公开的限定。基于所描述的本公开的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本公开保护的范围。
需要说明的是，在本文中，诸如“第一”和“第二”等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。
终端可能被网络配置不同的移动性配置信息，但是网络侧只能针对执行失败的配置信息进行移动性优化：
例如，终端被配置了层1和/或层2触发的移动性(L1/L2 triggered mobility，LTM)配置信息和条件切换(Conditional handover CHO)配置信息，当CHO执行失败，只针对CHO进行移动性优化，当LTM执行失败，只针对LTM进行移动性优化。
但是，CHO执行失败时，由于网络也为终端配置了LTM配置信息且LTM没有执行，LTM配置信息可能也会导致移动性问题。同理，LTM执行失败时，由于网络也为终端配置了CHO配置信息且CHO没有执行，CHO配置信息可能也会导致移动性问题。也即，针对单一配置信息进行移动性优化之后，终端仍然可能存在移动性问题，无法满足多种配置共存场景下终端的移动性需求。
网络可以发送多种移动性配置信息给终端，如LTM配置信息，CHO配置信息，条件辅小区组主小区添加或变更(Conditional PSCell addition/change，CPAC)配置信息，主小区组快速失败恢复(fast MCG recovery)配置信息。基于这些配置信息，终端可以进行移动性，但是网络设备无法基于多种配置共存场景下的移动性问题进行移动性优化。
(一)LTM
LTM机制，即网络为终端预配置多个候选小区配置及其L1测量配置，终端基于网络配置的L1测量配置进行L1测量并上报，网络基于终端上报的L1测量结果来发送LTM cell switch命令给终端，此LTM cell switch命令是通过MAC CE(MAC Control Element)发送给终端的。
当终端收到网络发送的LTM cell switch命令，终端将执行LTM cell switch，如果终端执行LTM cell switch失败，终端将执行小区选择过程，若终端小区选择选到的目标小区为LTM候选小区，那么终端将执行LTM恢复，当终端小区选择选到的目标小区不是LTM候选小区，终端触发重建过程。若终端小区选择选到的目标小区为LTM候选小区，当终端执行LTM恢复失败，终端将触发重建过程。
(二)CHO/条件辅小区组主小区添加或变更(Conditional PSCell addition/change，CPAC)
CHO，即网络为终端配置多个CHO候选小区及其相应的执行条件，终端基于测量结果进行CHO候选小区的评估，如果评估某个候选小区满足执行条件，那么终端接入到此候选目标小区。此针对的是MCG(Master Cell Group，主小区组)侧的PCell change(切换/handover)。
类似的，对于SCG(Secondary Cell Group，辅小区组)侧，网络也可以为终端配置多个CPAC候选小区及其相应的执行条件，终端基于测量结果进行CPAC候选小区的评估，如果评估某个候选小区满足执行条件，那么终端接入到此候选目标小区。此针对的是SCG侧的PSCell addition/change。
(三)主小区组快速失败恢复(fast MCG recovery)
主小区组快速失败恢复的英文可以为fast MCG link failure recovery或者fast MCG failure recovery或者fast MCG recovery或者fast MCG link recovery等。如果MCG侧发生无线链路失败，当配置了T316，SCG侧传输没有被挂起，终端将触发fast MCG recovery的过程，终端开启T316timer，通过SCG发送MCGFailureInformation给MN(主节点)来请求恢复MCG，当MN收到终端发送的MCGFailureInformation消息，MN可以发送RRCReconfiguration/RRC release/MobilityFromNR给终端，当终端收到MN发送的消息，终端执行并成功完成fast MCG recovery，如果T316超时前终端没有收到网络侧的反馈，当T316超时，fast MCG recovery失败，终端将触发重建过程。
本公开的至少一个实施例提供了一种移动性优化方法、装置、通信装置或存储介质，当终端被配置多种配置信息，终端处于多种配置共存场景，在多种配置共存场景下，若终端发生链路失败，则终端会记录失败相关信息，进而终端将失败相关信息发送给网络设备，失败相关信息用于网络设备进行移动性优化，也即，多种配置共存场景下产生的失败相关信息触发网络设备进行移动性优化，相比现有技术中，需要由网络设备通过检测网络状态触发移动性优化，本实施例使得网络设备可以在终端链路失败时，及时进行移动性优化，使终端与网络的联系状态及时得到优化，为各种网络服务的应用提供保证。
图1为本公开实施例提供的一种移动性优化方法的流程示意图，该移动性优化方法应用于终端。如图1所示，该移动性优化方法可以包括但不限于步骤101至步骤103：
在步骤101中，终端被配置多种配置信息，多种配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息，这个LTM配置信息可以为MCG LTM配置信息和/或SCG LTM配置信息；
条件切换CHO配置信息；
条件辅小区组主小区PSCell添加或变更CPAC配置信息；
主小区组快速失败恢复(fast MCG recovery)配置信息。
例如，共存场景可以为以下几类的共存，但不限于以下几类：
(1)LTM(MCG)配置信息和CHO配置信息共存；
(2)LTM(MCG)配置信息和fast MCG recovery配置信息共存；
(3)LTM(MCG)配置信息和CHO配置信息和fast MCG recovery配置信息共存；
(4)LTM(SCG)配置信息和CPAC配置信息共存。
具体的，例如，LTM配置信息和CHO配置信息共存场景，指终端被同时配置了LTM配置信息(LTM候选小区配置，L1测量配置等配置信息)和CHO配置信息(CHO候选小区配置，执行条件配置等配置信息)。LTM配置信息和fast MCG recovery配置信息共存场景，指终端被同时配置了LTM配置信息和fast MCG recovery配置信息(即T316配置)。
本实施例中，当终端被配置多种配置信息，终端处于多种配置共存场景，并且本实施例限定了多种配置共存场景中包括上述提及的至少两种配置信息。当前，虽然终端可能被配置多种配置信息，但是网络侧只能针对其中一种配置进行移动性优化，如针对CHO执行失败进行移动性优化，即使终端被配置了LTM配置信息和CHO配置信息。但是在这种情况下，网络配置的LTM没有执行可能也有问题，LTM相关的信息应该也上报给网络，用于网络侧的分析和优化，反之亦然。而本申请可以针对多种配置共存场景进行移动性优化。
在步骤102中，若终端发生链路失败，终端记录失败相关信息。
目前，若终端发生链路失败，终端并不会记录多种配置共存场景的失败相关信息，即终端并不会将多种配置共存场景下的各种配置相关信息进行记录，而是只会记录其中某种配置相关的失败相关信息。而本申请中，若终端发生链路失败，且终端处于多种配置共存场景，则终端会记录共存场景的失败相关信息，且失败相关信息不仅可以包括多种配置共存场景中每种配置信息各自的与失败相关的信息，而且可以包括不同配置信息之间的相对关系信息等。其中共存场景的失败相关信息指共存场景中的两种或两种以上配置信息相关的失败相关信息，如LTM和CHO配置相关的失败相关信息。
在一些实施例中，终端将失败相关信息记录在报告中，其中，报告包括以下至少一个：无线链路失败(Radio Link Failure，RLF)报告、非RLF的报告和自定义报告。其中非RLF的报告可以为CEF报告，RACH Report，SHR，SPR，SCGFailureInformation消息等中的一种或多种。
例如，在多种配置共存场景下，对于单次失败，终端除了记录失败相关信息，也可以记录其它配置信息，如对于LTM执行失败，但是成功恢复的场景(LTM恢复成功或CHO恢复成功)，终端也可以记录CHO配置信息(如CHO各候选小区和执行条件信息)或配置指示信息，此配置指示信息用于指示终端被配置了CHO配置信息。
在多种配置共存场景下，对于连续失败，终端除了记录连续失败相关信息，也可以记录其它配置信息，如对于LTM执行失败，通过LTM/CHO恢复失败，终端可以记录LTM失败，和LTM/CHO恢复失败信息，终端也可以记录如CHO各候选小区和执行条件信息等CHO配置信息或配置指示信息，此配置指示信息用于指示终端被配置了CHO配置信息。
终端记录的失败相关信息可以记录在一个报告中，但是不限制只能记录在一个报告中。
在步骤103中，终端将失败相关信息发送给网络设备。
本实施例中，网络设备例如为接入网的基站。失败相关信息用于网络设备进行移动性优化，也即，网络设备基于终端上报的多种配置共存场景下产生的失败相关信息进行移动性优化，相比现有技术中，网络设备无法针对多种配置共存场景进行移动性优化，本实施例使得网络设备可以针对多种配置共存场景，进行移动性优化，为终端在多种配置共存场景下的移动性提供保证。
在一些实施例中，步骤102中“终端发生链路失败”包括以下至少一种：
终端在源小区发生无线链路失败RLF；
终端执行LTM失败；
终端执行LTM恢复失败；
终端执行CHO失败；
终端执行CHO恢复失败；
终端执行传统切换失败；
终端执行CPAC失败；
终端执行主小区组快速失败恢复失败。
本实施例中，终端执行LTM恢复可以理解为：当终端发生链路失败，终端执行小区选择，选择的小区若为LTM候选小区中的某个候选小区，终端将执行此候选小区的LTM配置，此为LTM恢复。
本实施例中，终端执行CHO恢复可以理解为：当终端发生链路失败，终端执行小区选择，选择的小区若为CHO候选小区中的某个候选小区，终端将执行此候选小区的CHO配置，此为CHO恢复。
步骤102中“终端发生链路失败”例如包括但不限于如下10种失败场景：
(1)终端在源小区发生RLF，终端执行CHO/LTM恢复过程成功(或失败)；(终端同时被配置了CHO配置信息，LTM配置信息)。
(2)终端在源小区发生RLF，终端执行CHO/LTM恢复过程成功，但是短时间在CHO/LTM恢复小区发生RLF；(终端同时被配置了CHO配置信息，LTM配置信息)。
(3)终端执行LTM失败，终端执行CHO恢复过程成功/失败；(终端同时被配置了CHO配置信息，LTM配置信息)。
(4)终端执行LTM失败，终端执行CHO恢复过程成功，但是短时间在CHO恢复小区发生RLF；(终端同时被配置了CHO配置信息，LTM配置信息)。
(5)终端执行CHO失败，终端执行LTM恢复过程成功/失败；(终端同时被配置了CHO配置信息，LTM配置信息)。
(6)终端执行CHO失败，终端执行LTM恢复过程成功，但是短时间在LTM恢复小区发生RLF；(终端同时被配置了CHO配置信息，LTM配置信息)。
(7)终端执行legacy HO失败，终端执行CHO/LTM恢复过程成功(或失败)；(终端同时被配置了CHO配置信息，LTM配置信息)。
(8)终端执行legacy HO失败，终端执行CHO/LTM恢复过程成功，但是短时间在CHO/LTM恢复小区发生RLF；(终端同时被配置了CHO配置信息，LTM配置信息)。
(9)终端执行LTM失败，终端执行fast MCG recovery过程成功(或失败)；(终端同时被配置了LTM配置信息，fast MCG recovery配置信息)。
(10)终端执行LTM失败，终端执行fast MCG recovery过程成功，但是短时间在恢复目标小区发生RLF；(终端同时被配置了LTM配置信息，fast MCG recovery配置信息)。
在一些实施例中，步骤102中终端记录的失败相关信息包括以下至少一种：
候选小区信息；
时间信息；
指示信息。
在一些实施例中，失败相关信息中的候选小区信息包括以下至少一种：
LTM候选小区信息；
CHO候选小区信息；
CPAC候选小区信息。
在一些实施例中，失败相关信息中的候选小区信息包括以下(1)至(3)中至少一种：
(1)候选小区的标识信息。
候选小区的标识信息可以为PCI(Physical Cell ID，物理小区ID)+频点或者CGI(Cell Global Identifier，全球小区统一标识)。LTM候选小区标识信息为网络为终端配置的各LTM候选小区的标识信息，CHO候选小区标识信息为网络为终端配置的各CHO候选小区的标识信息，CPAC候选小区标识信息为网络为终端配置的各CPAC候选小区的标识信息。
标识信息的记录方式可以为以下一种：
·以list方式记录，即引入一个list来记录候选小区标识信息，此list中的每个entry为一个候选小区的标识信息；
·引入一个指示信息，指示邻区测量中的邻区是否为网络配置的候选小区；例如在L3邻区测量结果上报中对于每个邻区引入1bit指示来指示是否此邻区为CHO候选小区，或在L1测量结果上报中对于每个邻区引入1bit指示来指示是否此邻区为LTM候选小区。
·组合方式，即部分候选小区标识信息记录在list中，部分候选小区标识信息在邻区测量结果中指示，如对于邻区测量中包括的邻区，可以通过在邻区测量结果中指示的方式来上报候选小区标识信息，对于不包含在邻区测量中的候选小区，可以以list的方式来上报候选小区标识信息。
(2)候选小区的执行条件。
候选小区的执行条件是网络为每个候选小区配置的执行条件，当终端评估此执行条件满足，终端将接入到此候选小区，此执行条件可以为A3/A4/A5 event等。如对于CHO候选小区执行条件：网络会为每个CHO候选小区配置执行条件(一个或两个执行条件，可以为A3和/或A5 event)，当某个CHO候选小区的执行条件满足时，终端接入此CHO候选小区。对于CPAC候选小区执行条件：网络会为每个CPAC候选小区配置执行条件(一个或两个执行条件，可以为A3和/或A4和/或A5 event)，当某个CPCA候选小区的执行条件满足时，终端接入此CPAC候选小区。
(3)候选小区的测量结果。
候选小区的测量结果信息，此测量结果信息可以为L3测量结果(包括了cell级测量结果和/或beam级测量结果)或L1测量结果，如对于CHO或CPAC的候选小区，可以上报这些候选小区的L3测量结果，对于LTM候选小区，可以上报L1测量结果。L3测量结果可以为RSRP，RSRP，SIRN等，L1测量结果可以为L1-RSRP等。
因此，若候选小区信息包括LTM候选小区信息，则LTM候选小区信息包括以下至少一种：LTM候选小区的标识信息；LTM候选小区的执行条件；LTM候选小区的测量结果。
若候选小区信息包括CHO候选小区信息，则CHO候选小区信息包括以下至少一种：CHO候选小区的标识信息；CHO候选小区的执行条件；CHO候选小区的测量结果。
若候选小区信息包括CPAC候选小区信息，则CPAC候选小区信息包括以下至少一种：CPAC候选小区的标识信息；CPAC候选小区的执行条件；CPAC候选小区的测量结果。
在一些实施例中，失败相关信息中的时间信息包括以下至少一种：
终端收到LTM配置信息与收到CHO配置信息之间的时间间隔；
终端收到LTM配置信息与收到CPAC配置信息之间的时间间隔；
终端收到LTM配置信息与开始执行CHO之间的时间间隔；
终端收到CHO配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CPAC之间的时间间隔；
终端收到CPAC配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端收到CHO配置信息与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端收到LTM配置信息与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端执行CHO失败与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔。
以上各种时间信息的时间单位可以为milliseconds，seconds等，此处不作限制，并且以上各种时间信息没有先后顺序的限制。
可见，失败相关信息中的时间信息体现了不同配置信息之间的相对关系信息。
在一些实施例中，失败相关信息中的指示信息包括以下(1)至(6)中的至少一种：
(1)终端执行恢复的恢复小区所属的类型信息。
本实施例中，此指示信息用于指示终端执行恢复的恢复小区所属的类型信息，也即，若终端发生链路失败，终端进行小区选择，当选到一个小区为LTM候选小区和/或CHO候选小区中的某个候选小区，那么可以用此指示信息来指示这个候选小区为LTM候选小区或CHO候选小区或LTM和CHO候选小区，其上报方式可以为枚举类型：{CHO candidate cell，LTM candidate cell，both}。
(2)共存场景的指示信息。
本实施例中，此指示信息用于指示共存场景，也即终端发生失败的时候，终端所在的共存场景为哪种共存场景，可以为枚举类型，如{LTM+CHO,LTM+CPAC,LTM+fast MCG recovery,LTM+CHO+fast MCG recovery}，也可以为分开的指示信息，如对于LTM+CHO共存的场景，可以分别引入一个LTM指示信息和一个CHO指示信息，或者可以为隐示方式指示，即记录的信息中包括关于LTM和CHO的相关信息。
(3)连续执行的指示信息。
本实施例中，此指示信息用来指示终端连续执行LTM，CHO，CPCA，fast MCG recovery的顺序，如终端执行的顺序为LTM，CHO恢复，即终端先执行的LTM，后执行的CHO恢复，此指示信息的表示方式可以为显示方式或隐示方式，显示方式即为终端明确记录终端先执行的LTM，后执行的CHO恢复，如使用枚举类型{LTM-CHO恢复，CHO-LTM恢复,…},其也可以使用在连续失败的场景，表明连续失败的失败顺序，隐示的方式可以为通过终端记录的失败相关信息来判断先执行的LTM后执行的CHO恢复，如第一次失败的信息为LTM失败相关信息，而恢复cell为CHO候选小区，或者通过记录顺序，第一次LTM失败相关信息记录在报告的前面，后续CHO恢复相关的信息记录在报告的后面。
(4)定时提前(Timing Advance，TA)的指示信息。定时提前的指示信息用于指示终端是否有恢复小区的定时提前TA值和/或TA值大小，且终端执行恢复的恢复小区为LTM候选小区。
本实施例中，若终端执行恢复的恢复小区为LTM候选小区，则指示终端是否有恢复小区的定时提前TA值和/或TA值大小，用于指示当恢复小区是LTM候选小区时，终端是否已经计算了恢复小区的TA值以及计算的TA值为多少。
(5)下行同步的指示信息。下行同步的指示信息用于指示终端是否已经和恢复小区下行同步，且终端执行恢复的恢复小区为LTM候选小区。
本实施例中，若终端执行恢复的恢复小区为LTM候选小区，则指示终端是否已经和恢复小区下行同步，用于指示当恢复小区是LTM候选小区时，指示终端是否已经和恢复小区完成了下行同步，或已经进行了提前下行同步。
(6)同一分布单元(Distributed Unit，DU)的指示信息，同一分布单元的指示信息用于指示终端的源小区与恢复小区是否为同一分布单元DU下的小区，且终端执行恢复的恢复小区为LTM候选小区。
本实施例中，若终端执行恢复的恢复小区为LTM候选小区，则指示终端的源小区与恢复小区是否为同一分布单元DU下的小区，用于指示当恢复小区为LTM候选小区时，源小区和恢复小区是否是相同DU下的小区。
在一些实施例中，步骤103中终端将失败相关信息发送给网络设备，可能存在如下三种方式中的至少一种：
方式一：终端向网络设备发送通知消息，通知消息用于指示终端记录有失败相关信息，且终端响应于网络设备发送的失败相关信息请求消息，将失败相关信息发送给网络设备。
其中，通知消息可以为RRC重配完成消息，RRC连接建立完成消息，RRC连接恢复完成消息，RRC连接重建立完成消息中的一个或多个。在通知消息中设置1bit的通知位，通知位为1，指示终端记录有失败相关信息。在一些实施例中，通知消息可以是自定义的消息，也即不使用已有消息完成通知发送。
可见，方式一中，终端主动通知网络设备：终端已经记录了失败相关信息，网络设备接收到通知消息后，可以向终端发送失败相关信息请求消息。终端接收到失败相关信息请求消息后，将失败相关信息发送给网络设备。
方式二：终端记录失败相关信息后，将失败相关信息发送给网络设备。
可见，方式二中，终端不再通知网络设备，而是终端记录失败相关信息后，直接将失败相关信息发送给网络设备。终端无需向网络设备发送通知消息，网络设备也无需向终端发送请求消息，因此能够减少信令交互和开销。
方式三：终端接收网络设备发送的失败相关信息请求消息；终端响应于失败相关信息请求消息，将失败相关信息发送给网络设备。
可见，方式三中，终端不再有任何主动操作(包括主动发送通知消息，主动发送失败相关信息)，而是被动响应网络设备的请求消息，具体地，终端只有接收到网络设备发送的失败相关信息请求消息，终端才响应失败相关信息请求消息，而将失败相关信息发送给网络设备。
需要说明的是，方式三中，由于终端不向网络设备发送通知消息，因此，网络设备向终端发送失败相关信息请求消息时，并不知道终端是否已经记录了识别相关信息，所以，网络设备发送失败相关信息请求消息时，终端可能还没有记录失败相关信息，终端即使接收到失败相关信息请求消息，也没有可以向网络设备反馈的失败相关信息。
本领域技术人员可以根据实际需要，配置终端执行以上三种方式中的至少一种。
图2为本公开实施例提供的另一种移动性优化方法的流程示意图，该移动性优化方法应用于网络设备。如图2所示，该移动性优化方法可以包括但不限于步骤201和步骤202：
在步骤201中，网络设备接收终端发送的失败相关信息，失败相关信息为终端被配置多种配置信息、且终端发生链路失败时记录的失败相关信息，多种配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息。
在步骤202中，网络设备基于失败相关信息进行移动性优化，或者，网络设备通过接口信令将失败相关信息发送给失败相关信息相关的网络设备，以使该网络设备基于接收到的失败相关信息进行移动性优化。
其中，接口信令可以为Xn，X2，E1，F1等接口信令中的一种或多种。
在一些实施例中，步骤201中网络设备接收终端发送的失败相关信息，可能存在如下三种方式中的至少一种：
方式一：网络设备接收终端发送的通知消息，通知消息用于指示终端记录有失败相关信息；网络设备向终端发送失败相关信息请求消息；网络设备接收终端响应于失败相关信息请求消息而发送的失败相关信息。
可见，方式一中，网络设备在接收到通知消息后，可以知晓终端已经记录了失败相关信息，进而网络设备可以向终端发送失败相关信息请求消息，以便接收终端响应于失败相关信息请求消息而发送的失败相关信息。
方式二：网络设备向终端发送失败相关信息请求消息；网络设备接收终端响应于失败相关信息请求消息而发送的失败相关信息。
可见，方式二中，由于终端不向网络设备发送通知消息，因此，网络设备向终端发送失败相关信息请求消息时，并不知道终端是否已经记录了识别相关信息，所以，网络设备发送失败相关信息请求消息时，终端可能还没有记录失败相关信息，终端即使接收到失败相关信息请求消息，也没有可以向网络设备反馈的失败相关信息。
方式三：网络设备被动接收终端发送的失败相关信息。
可见，方式三中，网络设备不再主动向终端发送失败相关信息请求消息，而是被动接收终端发送的失败相关信息。
本领域技术人员可以根据实际需要，配置网络设备执行以上三种方式中的至少一种。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员能够理解，本公开实施例并不受所描述的动作顺序的限制，因为依据本公开实施例，某些步骤可以采用其他顺序或者同时进行。另外，本领域技术人员能够理解，说明书中所描述的实施例均属于可选实施例。
图3为本公开实施例提供的一种移动性优化装置的示意图，该移动性优化装置应用于终端，如图3所示，该移动性优化装置包括但不限于：第一单元31、第二单元32和第三单元33，具体说明如下：
第一单元31，用于被配置多种配置信息，多种配置信息包括以下至少两种：层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息；
第二单元32，用于若发生链路失败，记录失败相关信息；
第三单元33，用于将失败相关信息发送给网络设备。
在一些实施例中，发生链路失败包括以下至少一种：
终端在源小区发生无线链路失败RLF；
终端执行LTM失败；
终端执行LTM恢复失败；
终端执行CHO失败；
终端执行CHO恢复失败；
终端执行传统切换失败；
终端执行CPAC失败；
终端执行主小区组快速失败恢复失败。
在一些实施例中，失败相关信息包括以下至少一种：
候选小区信息；
时间信息；
指示信息。
在一些实施例中，候选小区信息包括以下至少一种：
LTM候选小区信息；
CHO候选小区信息；
CPAC候选小区信息。
在一些实施例中，时间信息包括以下至少一种：
终端收到LTM配置信息与收到CHO配置信息之间的时间间隔；
终端收到LTM配置信息与收到CPAC配置信息之间的时间间隔；
终端收到LTM配置信息与开始执行CHO之间的时间间隔；
终端收到CHO配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CPAC之间的时间间隔；
终端收到CPAC配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端收到CHO配置信息与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端收到LTM配置信息与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端执行CHO失败与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔。
在一些实施例中，指示信息包括以下至少一种：
终端执行恢复的恢复小区所属的类型信息；
共存场景的指示信息；
连续执行的指示信息；
定时提前的指示信息，定时提前的指示信息用于指示终端是否有恢复小区的定时提前TA值和/或TA值大小，且终端执行恢复的恢复小区为LTM候选小区；
下行同步的指示信息，下行同步的指示信息用于指示终端是否已经和恢复小区下行同步，且终端执行恢复的恢复小区为LTM候选小区；
同一分布单元的指示信息，同一分布单元的指示信息用于指示终端的源小区与恢复小区是否为同一分布单元DU下的小区，且终端执行恢复的恢复小区为LTM候选小区。
在一些实施例中，候选小区信息包括以下至少一种：
候选小区的标识信息；
候选小区的执行条件；
候选小区的测量结果。
在一些实施例中，第三单元33，用于：
向网络设备发送通知消息，通知消息用于指示终端记录有失败相关信息，且响应于网络设备发送的失败相关信息请求消息，将失败相关信息发送给网络设备；
和/或，
第二单元22记录失败相关信息后，将失败相关信息发送给网络设备；
和/或，
接收网络设备发送的失败相关信息请求消息；响应于失败相关信息请求消息，将失败相关信息发送给网络设备。
图3所示的移动性优化装置各实施例的细节，可以参考图1所示的移动性优化方法各实施例，为避免重复，不再赘述。
图4为本公开实施例提供的另一种移动性优化装置的示意图，该移动性优化装置应用于网络设备，如图4所示，该移动性优化装置包括但不限于：第一单元41和第二单元42，具体说明如下：
第一单元41，用于接收终端发送的失败相关信息，失败相关信息为终端被配置多种配置信息、且终端发生链路失败时记录的失败相关信息，多种配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息。
第二单元41，用于基于失败相关信息进行移动性优化，或者，通过接口信令将失败相关信息发送给失败相关信息相关的网络设备，以使该网络设备基于接收到的失败相关信息进行移动性优化。
在一些实施例中，第一单元41，用于：
接收终端发送的通知消息，通知消息用于指示终端记录有失败相关信息；向终端发送失败相关信息请求消息；接收终端响应于失败相关信息请求消息而发送的失败相关信息；
和/或，
向终端发送失败相关信息请求消息；接收终端响应于失败相关信息请求消息而发送的失败相关信息。
图4所示的移动性优化装置各实施例的细节，可以参考图2所示的移动性优化方法各实施例，为避免重复，不再赘述。
本公开实施例还提供一种处理器可读存储介质，所述处理器可读存储介质存储有程序，所述程序用于使处理器执行移动性优化方法各实施例的步骤。所述处理器可读存储介质可以是处理器能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
图5为本公开实施例提供的一种通信装置的示意图，应用于终端，如图5所示，本公开实施例提供的通信装置，包括存储器51，收发机52，处理器53：
存储器51，用于存储计算机程序；收发机52，用于在处理器53的控制下收发数据；处理器53，用于读取存储器51中的计算机程序并执行：
被配置多种配置信息，多种配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息；
若发生链路失败，记录失败相关信息；
将失败相关信息发送给网络设备。
在一些实施例中，发生链路失败包括以下至少一种：
终端在源小区发生无线链路失败RLF；
终端执行LTM失败；
终端执行LTM恢复失败；
终端执行CHO失败；
终端执行CHO恢复失败；
终端执行传统切换失败；
终端执行CPAC失败；
终端执行主小区组快速失败恢复失败。
在一些实施例中，失败相关信息包括以下至少一种：
候选小区信息；
时间信息；
指示信息。
在一些实施例中，候选小区信息包括以下至少一种：
LTM候选小区信息；
CHO候选小区信息；
CPAC候选小区信息。
在一些实施例中，时间信息包括以下至少一种：
终端收到LTM配置信息与收到CHO配置信息之间的时间间隔；
终端收到LTM配置信息与收到CPAC配置信息之间的时间间隔；
终端收到LTM配置信息与开始执行CHO之间的时间间隔；
终端收到CHO配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CPAC之间的时间间隔；
终端收到CPAC配置信息与开始执行LTM之间的时间间隔；
终端收到LTM配置信息与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端收到CHO配置信息与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端收到LTM配置信息与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
终端执行CHO失败与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
终端执行LTM失败与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔。
在一些实施例中，指示信息包括以下至少一种：
终端执行恢复的恢复小区所属的类型信息；
共存场景的指示信息；
连续执行的指示信息；
定时提前的指示信息，定时提前的指示信息用于指示终端是否有恢复小区的定时提前TA值和/或TA值大小，且终端执行恢复的恢复小区为LTM候选小区；
下行同步的指示信息，下行同步的指示信息用于指示终端是否已经和恢复小区下行同步，且终端执行恢复的恢复小区为LTM候选小区；
同一分布单元的指示信息，同一分布单元的指示信息用于指示终端的源小区与恢复小区是否为同一分布单元DU下的小区，且终端执行恢复的恢复小区为LTM候选小区。
在一些实施例中，候选小区信息包括以下至少一种：
候选小区的标识信息；
候选小区的执行条件；
候选小区的测量结果。
在一些实施例中，将失败相关信息发送给网络设备，包括：
向网络设备发送通知消息，通知消息用于指示终端记录有失败相关信息，且响应于网络设备发送的失败相关信息请求消息，将失败相关信息发送给网络设备；
和/或，
记录失败相关信息后，将失败相关信息发送给网络设备；
和/或，
接收网络设备发送的失败相关信息请求消息；响应于失败相关信息请求消息，将失败相关信息发送给网络设备。
图5中，收发机52，用于在处理器53的控制下接收和发送数据。总线架构可以包括任意数量的互联的总线和桥，具体由处理器53代表的一个或多个处理器和存储器51代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机52可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。处理器53负责管理总线架构和通常的处理，存储器51可以存储处理器53在执行操作时所使用的数据。
图5中，处理器53可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器53中的硬件的集成逻辑电路或者软件形式的指令完成。处理器53可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
图6为本公开实施例提供的另一种通信装置的示意图，应用于网络设备，如图6所示，本公开实施例提供的通信装置，包括存储器61，收发机62，处理器63：
存储器61，用于存储计算机程序；收发机62，用于在处理器63的控制下收发数据；处理器63，用于读取存储器61中的计算机程序并执行：
接收终端发送的失败相关信息，失败相关信息为终端被配置多种配置信息、且终端发生链路失败时记录的失败相关信息，多种配置信息包括以下至少两种：
层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息。
在一些实施例中，接收终端发送的失败相关信息，包括：
接收终端发送的通知消息，通知消息用于指示终端记录有失败相关信息；向终端发送失败相关信息请求消息；接收终端响应于失败相关信息请求消息而发送的失败相关信息；
和/或，
向终端发送失败相关信息请求消息；接收终端响应于失败相关信息请求消息而发送的失败相关信息。
在一些实施例中，处理器63，还用于读取存储器中的计算机程序并执行：
基于失败相关信息进行移动性优化，或者，通过接口信令将失败相关信息发送给失败相关信息相关的网络设备，以使该网络设备基于接收到的失败相关信息进行移动性优化。
图6中，收发机62，用于在处理器63的控制下接收和发送数据。总线架构可以包括任意数量的互联的总线和桥，具体由处理器63代表的一个或多个处理器和存储器61代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机62可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括无线信道、有线信道、光缆等传输介质。处理器63负责管理总线架构和通常的处理，存储器61可以存储处理器63在执行操作时所使用的数据。
图6中，处理器63可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器63中的硬件的集成逻辑电路或者软件形式的指令完成。处理器63可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
本领域的技术人员能够理解，尽管在此所述的一些实施例包括其它实施例中所包括的某些特征而不是其它特征，但是不同实施例的特征的组合意味着处于本公开的范围之内并且形成不同的实施例。
本领域的技术人员能够理解，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
虽然结合附图描述了本公开的实施方式，但是本领域技术人员可以在不脱离本公开的精神和范围的情况下做出各种修改和变型，这样的修改和变型均落入由所附权利要求所限定的范围之内。

Claims (23)

  1. 一种移动性优化方法，应用于终端，所述方法包括：
    在所述终端被配置配置信息的情况下，若所述终端发生链路失败，所述终端记录失败相关信息；所述配置信息包括以下至少两种：
    层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息；
    所述终端将所述失败相关信息发送给网络设备。
  2. 根据权利要求1所述的方法，其中，所述终端发生链路失败包括以下至少一种：
    所述终端在源小区发生无线链路失败RLF；
    所述终端执行LTM失败；
    所述终端执行LTM恢复失败；
    所述终端执行CHO失败；
    所述终端执行CHO恢复失败；
    所述终端执行传统切换失败；
    所述终端执行CPAC失败；
    所述终端执行主小区组快速失败恢复失败。
  3. 根据权利要求1所述的方法，其中，所述失败相关信息包括以下至少一种：
    候选小区信息；
    时间信息；
    指示信息。
  4. 根据权利要求3所述的方法，其中，所述候选小区信息包括以下至少一种：
    LTM候选小区信息；
    CHO候选小区信息；
    CPAC候选小区信息。
  5. 根据权利要求3所述的方法，其中，所述时间信息包括以下至少一种：
    所述终端收到LTM配置信息与收到CHO配置信息之间的时间间隔；
    所述终端收到LTM配置信息与收到CPAC配置信息之间的时间间隔；
    所述终端收到LTM配置信息与开始执行CHO之间的时间间隔；
    所述终端收到CHO配置信息与开始执行LTM之间的时间间隔；
    所述终端收到LTM配置信息与开始执行CPAC之间的时间间隔；
    所述终端收到CPAC配置信息与开始执行LTM之间的时间间隔；
    所述终端收到LTM配置信息与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
    所述终端收到CHO配置信息与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
    所述终端收到LTM配置信息与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔；
    所述终端执行LTM失败与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
    所述终端执行CHO失败与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
    所述终端执行LTM失败与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔。
  6. 根据权利要求3所述的方法，其中，所述指示信息包括以下至少一种：
    所述终端执行恢复的恢复小区所属的类型信息；
    共存场景的指示信息；
    连续执行的指示信息；
    定时提前的指示信息，所述定时提前的指示信息用于指示所述终端是否有恢复小区的定时提前TA值和/或TA值大小，且所述终端执行恢复的恢复小区为LTM候选小区；
    下行同步的指示信息，所述下行同步的指示信息用于指示所述终端是否已经和恢复小区下行同步，且所述终端执行恢复的恢复小区为LTM候选小区；
    同一分布单元的指示信息，所述同一分布单元的指示信息用于指示所述终端的源小区与恢复小区是否为同一分布单元DU下的小区，且所述终端执行恢复的恢复小区为LTM候选小区。
  7. 根据权利要求3或4所述的方法，其中，所述候选小区信息包括以下至少一种：
    候选小区的标识信息；
    候选小区的执行条件；
    候选小区的测量结果。
  8. 根据权利要求1所述的方法，其中，所述终端将所述失败相关信息发送给网络设备，包括：
    所述终端向所述网络设备发送通知消息，所述通知消息用于指示所述终端记录有失败相关信息，且所述终端响应于所述网络设备发送的失败相关信息请求消息，将所述失败相关信息发送给所述网络设备；
    或，
    所述终端记录失败相关信息后，将所述失败相关信息发送给所述网络设备；
    和/或，
    所述终端接收所述网络设备发送的失败相关信息请求消息；所述终端响应于所述失败相关信息请求消息，将所述失败相关信息发送给所述网络设备。
  9. 一种移动性优化方法，应用于网络设备，所述方法包括：
    所述网络设备接收终端发送的失败相关信息，所述失败相关信息为所述终端被配置配置信息、且所述终端发生链路失败时记录的失败相关信息，所述配置信息包括以下至少两种：
    层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息。
  10. 根据权利要求9所述的方法，其中，所述网络设备接收终端发送的失败相关信息，包括：
    所述网络设备接收所述终端发送的通知消息，所述通知消息用于指示所述终端记录有失败相关信息；所述网络设备向所述终端发送失败相关信息请求消息；所述网络设备接收所述终端响应于所述失败相关信息请求消息而发送的失败相关信息；
    和/或，
    所述网络设备向所述终端发送失败相关信息请求消息；所述网络设备接收所述终端响应于所述失败相关信息请求消息而发送的失败相关信息。
  11. 根据权利要求9所述的方法，其中，所述方法还包括：
    所述网络设备基于所述失败相关信息进行移动性优化，或者，所述网络设备通过接口信令将所述失败相关信息发送给所述失败相关信息相关的网络设备，以使该网络设备基于接收到的失败相关信息进行移动性优化。
  12. 一种通信装置，应用于终端，其中，包括存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行：
    在所述终端被配置配置信息的情况下，若发生链路失败，记录失败相关信息；所述配置信息包括以下至少两种：
    层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息；
    将所述失败相关信息发送给网络设备。
  13. 根据权利要求12所述的通信装置，其中，所述发生链路失败包括以下至少一种：
    所述终端在源小区发生无线链路失败RLF；
    所述终端执行LTM失败；
    所述终端执行LTM恢复失败；
    所述终端执行CHO失败；
    所述终端执行CHO恢复失败；
    所述终端执行传统切换失败；
    所述终端执行CPAC失败；
    所述终端执行主小区组快速失败恢复失败。
  14. 根据权利要求12所述的通信装置，其中，所述失败相关信息包括以下至少一种：
    候选小区信息；
    时间信息；
    指示信息。
  15. 根据权利要求14所述的通信装置，其中，所述候选小区信息包括以下至少一种：
    LTM候选小区信息；
    CHO候选小区信息；
    CPAC候选小区信息。
  16. 根据权利要求14所述的通信装置，其中，所述时间信息包括以下至少一种：
    所述终端收到LTM配置信息与收到CHO配置信息之间的时间间隔；
    所述终端收到LTM配置信息与收到CPAC配置信息之间的时间间隔；
    所述终端收到LTM配置信息与开始执行CHO之间的时间间隔；
    所述终端收到CHO配置信息与开始执行LTM之间的时间间隔；
    所述终端收到LTM配置信息与开始执行CPAC之间的时间间隔；
    所述终端收到CPAC配置信息与开始执行LTM之间的时间间隔；
    所述终端收到LTM配置信息与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
    所述终端收到CHO配置信息与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
    所述终端收到LTM配置信息与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔；
    所述终端执行LTM失败与开始执行CHO恢复或者CHO恢复执行成功或失败之间的时间间隔；
    所述终端执行CHO失败与开始执行LTM恢复或者LTM恢复执行成功或失败之间的时间间隔；
    所述终端执行LTM失败与开始执行主小区组快速失败恢复或者主小区组快速失败恢复执行成功或失败之间的时间间隔。
  17. 根据权利要求14所述的通信装置，其中，所述指示信息包括以下至少一种：
    所述终端执行恢复的恢复小区所属的类型信息；
    共存场景的指示信息；
    连续执行的指示信息；
    定时提前的指示信息，所述定时提前的指示信息用于指示所述终端是否有恢复小区的定时提前TA值和/或TA值大小，且所述终端执行恢复的恢复小区为LTM候选小区；
    下行同步的指示信息，所述下行同步的指示信息用于指示所述终端是否已经和恢复小区下行同步，且所述终端执行恢复的恢复小区为LTM候选小区；
    同一分布单元的指示信息，所述同一分布单元的指示信息用于指示所述终端的源小区与恢复小区是否为同一分布单元DU下的小区，且所述终端执行恢复的恢复小区为LTM候选小区。
  18. 根据权利要求14或15所述的通信装置，其中，所述候选小区信息包括以下至少一种：
    候选小区的标识信息；
    候选小区的执行条件；
    候选小区的测量结果。
  19. 根据权利要求12所述的通信装置，其中，所述将所述失败相关信息发送给网络设备，包括：
    向所述网络设备发送通知消息，所述通知消息用于指示所述终端记录有失败相关信息，且响应于所述网络设备发送的失败相关信息请求消息，将所述失败相关信息发送给所述网络设备；
    或，
    记录失败相关信息后，将所述失败相关信息发送给所述网络设备；
    和/或，
    接收所述网络设备发送的失败相关信息请求消息；响应于所述失败相关信息请求消息，将所述失败相关信息发送给所述网络设备。
  20. 一种通信装置，应用于网络设备，其中，包括存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行：
    接收终端发送的失败相关信息，所述失败相关信息为所述终端被配置配置信息、且所述终端发生链路失败时记录的失败相关信息，所述配置信息包括以下至少两种：
    层1和/或层2触发的移动性LTM配置信息、条件切换CHO配置信息、条件辅小区组主小区PSCell添加或变更CPAC配置信息、主小区组快速失败恢复配置信息。
  21. 根据权利要求20所述的通信装置，其中，所述接收终端发送的失败相关信息，包括：
    接收所述终端发送的通知消息，所述通知消息用于指示所述终端记录有失败相关信息；向所述终端发送失败相关信息请求消息；接收所述终端响应于所述失败相关信息请求消息而发送的失败相关信息；
    和/或，
    向所述终端发送失败相关信息请求消息；接收所述终端响应于所述失败相关信息请求消息而发送的失败相关信息。
  22. 根据权利要求20所述的通信装置，其中，所述处理器，还用于读取所述存储器中的计算机程序并执行：
    基于所述失败相关信息进行移动性优化，或者，通过接口信令将所述失败相关信息发送给所述失败相关信息相关的网络设备，以使该网络设备基于接收到的失败相关信息进行移动性优化。
  23. 一种处理器可读存储介质，其中，所述处理器可读存储介质存储有程序，所述程序用于使所述处理器执行如权利要求1至8任一项所述的移动性优化方法或者如权利要求9至11任一项所述的移动性优化方法。
PCT/CN2024/134533 2023-12-08 2024-11-26 一种移动性优化方法、装置、通信装置及存储介质 Pending WO2025119034A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202311688756.5A CN120128998A (zh) 2023-12-08 2023-12-08 一种移动性优化方法、装置、通信装置及存储介质
CN202311688756.5 2023-12-08

Publications (1)

Publication Number Publication Date
WO2025119034A1 true WO2025119034A1 (zh) 2025-06-12

Family

ID=95923813

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/134533 Pending WO2025119034A1 (zh) 2023-12-08 2024-11-26 一种移动性优化方法、装置、通信装置及存储介质

Country Status (2)

Country Link
CN (1) CN120128998A (zh)
WO (1) WO2025119034A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230040285A1 (en) * 2020-01-30 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Reporting Failures of Conditional Handover Mobility Operations
CN116349377A (zh) * 2023-02-16 2023-06-27 北京小米移动软件有限公司 基于条件的移动性配置方法、装置、设备及存储介质
US20230300708A1 (en) * 2022-03-15 2023-09-21 Samsung Electronics Co., Ltd. Failure recovery for joint operation of conditional handover and conditional pscell addition or change
CN117158038A (zh) * 2023-05-11 2023-12-01 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质
CN117641469A (zh) * 2022-08-10 2024-03-01 大唐移动通信设备有限公司 一种信息处理方法、装置及可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230040285A1 (en) * 2020-01-30 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Reporting Failures of Conditional Handover Mobility Operations
US20230300708A1 (en) * 2022-03-15 2023-09-21 Samsung Electronics Co., Ltd. Failure recovery for joint operation of conditional handover and conditional pscell addition or change
CN117641469A (zh) * 2022-08-10 2024-03-01 大唐移动通信设备有限公司 一种信息处理方法、装置及可读存储介质
CN116349377A (zh) * 2023-02-16 2023-06-27 北京小米移动软件有限公司 基于条件的移动性配置方法、装置、设备及存储介质
CN117158038A (zh) * 2023-05-11 2023-12-01 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质

Also Published As

Publication number Publication date
CN120128998A (zh) 2025-06-10

Similar Documents

Publication Publication Date Title
US20230292214A1 (en) Mobility information reporting method and ue
US12581376B2 (en) Information reporting method, information receiving method, terminal and network device
JP7430200B2 (ja) 情報報告及び受信方法、装置、関連機器並びに記憶媒体
CN113271632B (zh) 信息的上报、接收方法、终端及网络设备
US20230262572A1 (en) Communication method and related device
CN119014046A (zh) 用于pscell改变或cpac程序的方法及设备
WO2021203824A1 (zh) 一种网络设备的配置方法、装置、设备及存储介质
US12501325B2 (en) Method and apparatus for determining daps handover failure type
CN115442796A (zh) 信息传输方法、装置及计算机可读存储介质
WO2024032436A1 (zh) 一种信息处理方法、装置及可读存储介质
US20230156843A1 (en) Radio link failure information reporting and obtaining method, terminal, and network side device
JP7772909B2 (ja) レポート処理方法、装置、ネットワークノード及び端末
CN116347529A (zh) 辅节点预留资源的方法、基站、辅节点和通信系统
CN120128998A (zh) 一种移动性优化方法、装置、通信装置及存储介质
CN115734315B (zh) 载波关断节能的方法、装置及存储介质
WO2023202703A1 (zh) 信息上报方法、装置、终端、基站及存储介质
WO2023143271A1 (zh) 一种信息处理方法、用户设备和存储介质
WO2025167512A1 (zh) 临界失败信息的上报方法、装置及存储介质
CN117835354A (zh) 通信方法、装置、网络设备、终端及存储介质
US20240306167A1 (en) Data transmission method and apparatus, base station, and terminal
WO2024093934A1 (zh) 配置方法、装置、相关设备及存储介质
CN116017587A (zh) 信息上报方法、装置、终端及存储介质
WO2024239828A1 (zh) 信息传输方法、装置、终端、网络设备及可读存储介质
WO2025180196A9 (zh) 数据传输方法、装置、系统、通信设备和存储介质
WO2023179603A1 (zh) 一种信息收发方法、设备及存储介质

Legal Events

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

Ref document number: 24899674

Country of ref document: EP

Kind code of ref document: A1