Node in wireless communication system, user equipment and method performed by same

Abstract

The invention provides a node in a wireless communication system, user equipment and a method performed by the same. A method performed by a first node in a wireless communication system includes transmitting a third message to a user equipment (UE) or a second node, the third message including configuration information associated with Layer 1 / Layer 2 triggered mobility LTM successful handover information, the configuration information associated with the LTM successful switching information comprises one or more of the following information: a timing advance (TA) value is overtime, access cannot be performed based on a first TA value, access is performed based on a random access mechanism, and the first TA value is invalid; receiving a sixth message from the second node, wherein the sixth message comprises the LTM successful switching information; and performing corresponding configuration adjustment based on the LTM successful switching information.

Description

Technical Field

[0001] The present disclosure relates to the technical field of wireless communications, and more particularly, to a node, a user equipment and a method executed by the node in a wireless communication system. Background Art

[0002] In order to meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems."

[0003] Wireless communication is one of the most successful innovations in modern history. The number of subscribers to wireless communication services recently exceeded 5 billion and continues to grow rapidly. The demand for wireless data services is growing rapidly due to the increasing popularity of smartphones and other mobile data devices (e.g., tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and enterprises. In order to meet the high growth of mobile data services and support new applications and deployments, it is critical to improve the efficiency and coverage of the wireless interface.

[0004] The node may collect successful handover reports from the UE for self-optimization of handovers and the like.

[0005] In Layer 1 / Layer 2 triggered mobility (L1 / L2-triggered mobility, LTM), the UE sends a random access preamble code to the target node before switching. The target node obtains the timing advance (TA) value and forwards it to the source node. The source node sends the obtained TA value to the UE when sending the switching command. The UE can directly access the target node based on the TA value to achieve interruption-free switching.

[0006] Currently, there is no self-optimization mechanism based on LTM. In order to improve performance, an enhanced self-optimization related solution is needed. Summary of the invention

[0007] An embodiment of the present disclosure provides a method performed by a first node in a wireless communication system, comprising: sending a third message to a user equipment UE or a second node, wherein the third message includes configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, inability to access based on a first TA value, access based on a random access mechanism, and failure of the first TA value;

[0008] receiving a sixth message from the second node, the sixth message including the LTM successful switching information; and making corresponding configuration adjustments based on the LTM successful switching information.

[0009] According to an embodiment of the present disclosure, the LTM successful switching information includes one or more of the following: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, a second measurement result, an LTM switching identifier, and LTM command information.

[0010] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first TA value and the second TA value.

[0011] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first measurement result and / or the second measurement result.

[0012] According to an embodiment of the present disclosure, making corresponding configuration adjustments based on the LTM successful switching information further includes: when it is determined based on the LTM successful switching information that the first TA value is invalid, adjusting the validity period of the first TA value.

[0013] According to an embodiment of the present disclosure, the first TA value is a TA value in an LTM command, and the second TA value is a TA value acquired based on a random access mechanism.

[0014] According to an embodiment of the present disclosure, the first measurement result is a layer 1 measurement result, and the second measurement result is a layer 3 measurement result.

[0015] An embodiment of the present disclosure provides a method performed by a user equipment UE in a wireless communication system, comprising: receiving a third message from a first node or a second node, the third message including configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, inability to access based on a first TA value, access based on a random access mechanism, and failure of the first TA value; and sending a sixth message to the second node or the third node, the sixth message including the LTM successful switching information.

[0016] According to an embodiment of the present disclosure, the method further includes: in a case where the configuration information associated with the LTM successful switching information is satisfied during the switching process, saving the LTM successful switching information.

[0017] According to an embodiment of the present disclosure, the method further includes: when the UE performs LTM switching, including the LTM switching identifier and / or LTM command information in the LTM successful switching information.

[0018] According to an embodiment of the present disclosure, the method also includes: when the UE cannot access based on the first TA value and switches to a third node through random access, one or more of the following are included in the LTM successful switching information: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, and a second measurement result.

[0019] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first TA value and the second TA value.

[0020] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first measurement result and / or the second measurement result.

[0021] According to an embodiment of the present disclosure, the first TA value is a TA value in an LTM command, and the second TA value is a TA value acquired based on a random access mechanism.

[0022] According to an embodiment of the present disclosure, the first measurement result is a layer 1 measurement result, and the second measurement result is a layer 3 measurement result.

[0023] An embodiment of the present disclosure provides a method executed by a second node in a wireless communication system, comprising: receiving a third message from a first node, the third message including configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, inability to access based on a first TA value, access based on a random access mechanism, and failure of the first TA value; sending the configuration information to a user equipment UE; receiving a sixth message from the UE or the third node, the sixth message including the LTM successful switching information; and sending the LTM successful switching information to the first node.

[0024] According to an embodiment of the present disclosure, the LTM successful switching information includes one or more of the following: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, a second measurement result, an LTM switching identifier, and LTM command information.

[0025] An embodiment of the present disclosure provides a first node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the first node in the wireless communication system according to an embodiment of the present disclosure.

[0026] An embodiment of the present disclosure provides a second node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the second node in the wireless communication system according to an embodiment of the present disclosure.

[0027] An embodiment of the present disclosure provides a user equipment UE in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the user equipment UE in the wireless communication system according to an embodiment of the present disclosure.

[0028] An embodiment of the present disclosure provides a computer-readable medium having computer-readable instructions stored thereon, which, when executed by a processor, are used to implement a method performed by a first node and / or a second node and / or a user equipment in a wireless communication system according to an embodiment of the present disclosure.

[0029] The method provided by the present disclosure and executed by the first node and / or the second node and / or the user equipment in the wireless communication system can support the node to perform self-optimization related to LTM switching by exchanging information related to successful LTM switching between the nodes and / or the user equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0031] Figure 1 is an exemplary system architecture 100 of System Architecture Evolution (SAE);

[0032] Figure 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure;

[0033] Figures 3A-3H Schematic diagrams of one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure are respectively shown;

[0034] Figure 4 A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure;

[0035] Figure 5A-5B Schematic diagrams of one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure are respectively shown;

[0036] Figures 6A-6K Schematic diagrams of one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure are respectively shown;

[0037] Figure 7 A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure;

[0038] Figures 8A-8B Schematic diagrams of one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure are respectively shown;

[0039] Fig. 9 A flowchart of a method performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0040] Fig.10 A flow chart of a method performed by a user equipment in a wireless communication system according to an embodiment of the present disclosure is shown;

[0041] Fig.11 A flowchart of a method performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0042] Fig.12 A schematic diagram of a node according to an embodiment of the present disclosure is shown; and

[0043] Fig.13 A schematic diagram of a user equipment according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0044] The following description with reference to the accompanying drawings is provided to facilitate a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. This description includes various specific details to facilitate understanding but should be considered as exemplary only. Therefore, one of ordinary skill in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures may be omitted.

[0045] The terms and expressions used in the following specification and claims are not limited to their dictionary meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purposes only and not for the purpose of limiting the present disclosure as defined in the appended claims and their equivalents.

[0046] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0047] The term "include" or "may include" refers to the presence of the corresponding disclosed functions, operations or components that can be used in various embodiments of the present disclosure, rather than limiting the presence of one or more additional functions, operations or features. In addition, the term "include" or "have" may be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components or combinations thereof, but should not be interpreted as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

[0048] The term "or" used in various embodiments of the present disclosure includes any of the listed terms and all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B.

[0049] Unless defined differently, all terms (including technical terms or scientific terms) used in the present disclosure have the same meanings as understood by those skilled in the art described in the present disclosure. Common terms as defined in dictionaries are interpreted as having meanings consistent with the context in the relevant technical field, and should not be interpreted ideally or overly formally unless clearly defined in the present disclosure.

[0050] The accompanying drawings discussed below and the various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0051] Figure 1 It is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides a wireless network interface for the UE to access. The Mobility Management Entity (MME) 103 is responsible for managing the mobility context, session context and security information of the UE. The Serving Gateway (SGW) 104 mainly provides user plane functions, and the MME 103 and SGW 104 may be in the same physical entity. The Packet Data Network Gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104. The Policy and Charging Rules Function Entity (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. The General Packet Radio Service Support Node (SGSN) 108 is a network node device that provides routing for data transmission in the Universal Mobile Telecommunications System (UMTS). The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, and the packet data context of the user equipment.

[0052] Figure 2 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.

[0053] User equipment (UE) 201 is a terminal device used to receive data. The next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (gNB or eNB connected to the 5G core network 5GC, the eNB connected to the 5GC is also called ng-gNB) that provides the UE with an access wireless network interface. The access control and mobility management function entity (AMF) 203 is responsible for managing the mobility context and security information of the UE. The user plane function entity (UPF) 204 mainly provides user plane functions. The session management function entity SMF 205 is responsible for session management. The data network (DN) 206 includes services such as operators, Internet access, and third-party services.

[0054] The nodes described in the present disclosure may include: gNB, gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), gNB-CU-ControlPlane (gNB CU-CP)), gNB-CU-User Plane (gNB CU-UP)), en-gNB, eNB, ng-eNB, UE, Access and Mobility Management Function (AMF), Session Management Function (SMF), Mobility Management Entity (MME) and other network entities or network logical units.

[0055] The signal strength and / or signal quality described in the present disclosure may be a received signal strength indicator (RSSI), a reference signal received power (RSRP), a reference signal received quality (RSRQ), a signal to interference plus noise ratio (SINR), etc.

[0056] In the present disclosure, a failure type and / or a problem type may also be a report type.

[0057] In the present disclosure, Self Optimization Network (SON) related reports may include one or more of the following: Connection Establishment Failure (CEF) report, or Random Access (Random Access) report, or Successful Handover (Successful Handover) report, or Radio Link Failure (RLF) report, or measurement report, or other reports related to wireless connection.

[0058] In the present disclosure, radio link failure may include two situations: radio link failure and handover failure.

[0059] In the present disclosure, a user equipment (UE) may also be referred to as a user.

[0060] In the present disclosure, invalidation and ineffectiveness etc. may also be used interchangeably.

[0061] In the present disclosure, the random access mechanism may be a contention-based random access mechanism or a contention-free random access mechanism.

[0062] In the present disclosure, the LTM command may also be a cell switch command.

[0063] In the present disclosure, the TA in the LTM command and / or the TA obtained in the LTM command may also be an early synchronization (EarlySync) TA, a TA obtained by early synchronization, a TA obtained in advance, and the like.

[0064] In the present disclosure, erroneous LTM handover cell selection may also be referred to as handover to a wrong cell.

[0065] In the present disclosure, handover may also be referred to as cell switch.

[0066] Example 1

[0067] In some embodiments, the present disclosure proposes a method for supporting mobility self-optimization, which may include: in some embodiments, a second node sends a first message to a first node including a failure type and / or problem type request (for example, associated with wireless link failure and switching failure, or associated with problems in successful switching, or associated with problems discovered by the second node during communication, etc.), and after receiving the request, the first node analyzes the failure type and / or problem type, and sends the analysis result to the second node for the second node to perform self-optimization.

[0068] In some embodiments, the first message may be included in one or more of the following: a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message or a FAILURE INDICATION message of Xn; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0069] In some implementations, the first message and / or the failure type and / or problem type request may include one or more of the following fields or related information:

[0070] UE ID: indicates the user corresponding to the failure type and / or problem type and / or report type request.

[0071] Sending node ID: used to identify the node that sends the message.

[0072] Receiving node ID: used to identify the node that receives the message.

[0073] Analysis result feedback time: The analysis result feedback time requirement. The first node needs to provide feedback to the second node within the analysis result feedback time.

[0074] In some embodiments, the first node may send a second message containing a failure type and / or a problem type to the second node based on its own situation and / or based on a first message containing a failure type and / or a problem type request received from the second node. After receiving the message, the second node may perform self-optimization, for example, optimizing its own configuration, or forward the message to other nodes for the other nodes to perform self-optimization operations. In some embodiments, for a split architecture, for example, in layer 1 / layer 2 triggered mobility (LTM), the cause analysis may be performed by the gNB CU or by the gNB DU. When the cause analysis is performed by the gNB CU, the analyzed failure type and / or problem type may be sent to the gNB DU when sending the relevant report. If the cause analysis is performed by the gNB DU, the gNB DU may perform the cause analysis after receiving the relevant report, and send the analyzed failure type and / or problem type to the gNB CU. In other embodiments, for example, if the target node has a downlink transmission failure and / or a resource allocation problem resulting in a handover failure (Handover Failure) and / or a radio link failure (Radio Link Failure), the target node may notify the source node of the problem type and / or failure type, and the source node may be based on or refer to the received problem type and / or failure type when subsequently analyzing the cause of the failure and / or performing self-optimization. If the second node indicates the analysis result feedback time in the first message, the first node needs to return the analysis result within the feedback time range. For example, the gNB CU sends a first message to the gNB DU, which includes the analysis result feedback time. The gNB DU needs to return the analyzed failure type and / or problem type to the gNBU within the analysis result feedback time. When the analysis result feedback time is exceeded, the gNB CU may release the stored SON-related reports and / or user contexts to avoid unnecessary content storage. In some other embodiments, the gNB CU may maintain a time (e.g., through a timer), and if the analyzed failure type and / or problem type is not received from the gNB DU within the time range, the gNBCU may release the stored SON-related reports and / or user contexts to avoid unnecessary content storage.

[0075] In some embodiments, the second message may be included in one or more of the following: a HANDOVER REPORT message or an ACCESS AND MOBILITY INDICATION message or a FAILURE INDICATION message of Xn; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0076] In some implementations, the second message may include one or more of the following fields or related information:

[0077] UE ID: indicates the user corresponding to the failure type and / or problem type and / or report type.

[0078] Sending node ID: used to identify the node that sends the message.

[0079] Receiving node ID: used to identify the node that receives the message.

[0080] Failure type: used to indicate the analyzed failure type. The failure type may include one or more of the following: premature handover, late handover, ping-pong handover, handover to wrong cell, wrong LTM handover cell selection, wrong LTM candidate cell selection, invalid TA value, inconsistent TA value, wrong TA value, downlink failure, target node downlink failure, problem from target node, problem from second message sending node, node identifier where problem occurs, resource allocation problem, resource allocation problem at target node, resource allocation problem at second message sending node, etc.

[0081] ·Problem type: used to indicate the type of problem analyzed. The problem type may include one or more of the following: premature handover, late handover, ping-pong handover, handover to wrong cell, wrong LTM handover cell selection, wrong LTM candidate cell selection, invalid TA value, inconsistent TA value, wrong TA value, downlink failure, target node downlink failure, problem from target node, problem from second message sending node, node identifier where problem occurs, resource allocation problem, resource allocation problem at target node, resource allocation problem at second message sending node, etc.

[0082] Report type: used to indicate the analyzed report type. The report type may include one or more of the following: premature handover, late handover, ping-pong handover, handover to wrong cell, wrong LTM handover cell selection, wrong LTM candidate cell selection, invalid TA value, inconsistent TA value, wrong TA value, downlink failure, target node downlink failure, problem from target node, problem from second message sending node, node identifier where problem occurs, resource allocation problem, resource allocation problem at target node, resource allocation problem at second message sending node, etc.

[0083] · Conditional handover configuration: may include one or more of the following: (candidate) target cell identifier,

[0084] (Candidate) Target cell corresponding execution conditions, (Candidate) Target cell supported slices,

[0085] (Candidate) Protocol Data Unit (PDU) accepted by the target cell

[0086] The PDU session (resource) situation accepted by the (candidate) target cell may include one or more of the following: PDU session identifier, the number of PDU sessions (resources) accepted, etc. In one embodiment, for example, if the UE (simultaneously)

[0087] If conditional switching and LTM are configured, the configuration of the conditional switching needs to be added. The configuration of the conditional switching can be used to optimize the node for switching. For example, the configuration of conditional switching and / or LTM is optimized to improve mobility robustness.

[0088] In LTM, the gNB CU may select one or more LTM candidate cells, and the gNB DU may select one of the one or more LTM candidate cells selected by the gNB CU as the handover target cell for the UE. Incorrect LTM handover cell selection means that in the LTM mechanism, the gNB DU incorrectly selects the cell to which the UE is handed over. Incorrect LTM handover cell selection may be when a radio link failure occurs shortly after a successful handover from the source cell or when a handover failure occurs during the handover process, and the UE attempts to reestablish a radio link connection on a cell that is neither the source cell nor the target cell. Incorrect LTM candidate cell selection means that in LTM, the gNB CU incorrectly selects a cell that can be used for LTM handover, resulting in the gNB DU being unable to handover the UE to a suitable cell. Incorrect LTM candidate cell selection may be when a radio link failure occurs shortly after a successful handover from the source cell or when a handover failure occurs during the handover process, and the UE attempts to reestablish a radio link connection on a cell that is neither the source cell nor the target cell nor the LTM candidate cell.

[0089] Invalid TA value means that the TA value used for access is not applicable and / or the TA value has expired and / or the TA value has timed out. Inconsistent TA value means that the TA value sent by the node to the user is not applicable to the user, and the TA value is applicable to other users. Incorrect TA value means that the TA value used for access is incorrect.

[0090] Among the failure types and / or problem types and / or report types, for the case of LTM, the failure types and / or problem types and / or report types attributed to the gNB CU may include one or more of the following: incorrect LTM candidate cell selection, ping-pong handover, handover to an incorrect cell, downlink failure, target node downlink failure, problem from the target node, problem from the second message sending node, node identifier of the problem, resource allocation problem, resource allocation problem at the target node, resource allocation problem at the second message sending node, etc. The failure types and / or problem types and / or report types attributed to the gNB CU should be self-optimized by the gNB CU. The failure types and / or problem types and / or report types attributed to the gNB DU may include one or more of the following: premature handover, late handover, ping-pong handover, handover to an incorrect cell, incorrect LTM handover cell selection, invalid TA value, inconsistent TA value, incorrect TA value, downlink failure, target node downlink failure, problem from the target node, problem from the second message sending node, node identifier of the problem, resource allocation problem, resource allocation problem at the target node, resource allocation problem at the second message sending node, etc. The failure type and / or problem type and / or report type attributed to the gNB DU shall be self-optimized by the gNB DU.

[0091] When the second node receives information that a problem occurs at the first node and / or other nodes, for example, the second node receives information such as downlink failure, target node downlink failure, problem from the target node, problem from the second message sending node, node identifier of the problem, resource allocation problem, resource allocation problem at the target node, and resource allocation problem at the second message sending node, the second node needs to consider the above information when performing self-optimization. In some embodiments, for example, the second node knows that the problem comes from the first node and / or other nodes, and the second node does not adjust and / or update its own configuration to avoid unnecessary adjustments and / or updates.

[0092] Example 2

[0093] In some embodiments, the present disclosure proposes a method for supporting mobility self-optimization, which may include: a third node sends a third message containing information associated with an LTM successful handover information request and / or configuration to a fourth node. After receiving the message, the fourth node may send the request and / or configuration to other nodes and / or UEs. The fourth node may also be a UE. The UE may record LTM handover related information in the LTM successful handover information, and report the LTM successful handover information to the node, and the node may perform self-optimization based on the information in the LTM successful handover information. For example, the UE records LTM handover related information in the LTM successful handover information, and the node (gNB CU and / or gNB DU) may optimize LTM based on the information in the LTM successful handover information. For example, when the UE cannot access based on the TA value obtained in advance, the UE re-accesses the random access to obtain synchronization information to complete the access. Although the handover is successful, the service is interrupted due to the UE re-accessing the random access. The mechanism of the above-mentioned LTM successful handover information can avoid the service interruption caused by the UE re-accessing the random access. The LTM successful handover information may be included in a successful handover report (Successful Handover Report, SHR). The LTM successful handover information may also be referred to as an LTM successful handover report.

[0094] In some embodiments, the third message may be included in one or more of the following: F1's user context modification required (UE CONTEXT MODIFICATION REQUIRED) message; RRC's other configuration (OtherConfig) or (successHO-Config) or RRC reconfiguration (RRCReconfiguration) message or RRC recovery (RRCResume) message; it may also be sent by MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0095] In some embodiments, the third message or information associated with the Layer 1 / Layer 2 Triggered Mobility LTM Successful Handover Information Request and / or Configuration may include one or more of the following fields or related information:

[0096] UE ID: indicates the user corresponding to the LTM successful handover information request and / or configuration.

[0097] Sending node ID: used to identify the node that sends the message.

[0098] Receiving node ID: used to identify the node that receives the message.

[0099] LTM successful switching information request indication: used to indicate a request to collect and / or report LTM successful switching information.

[0100] ·Information triggering the generation and / or reporting of LTM successful handover information: used to indicate information triggering the generation and / or reporting of LTM successful handover information. When the information triggering the generation and / or reporting of LTM successful handover information is met, the UE saves and / or generates and / or reports the LTM successful handover information. In some embodiments, the information triggering the generation and / or reporting of LTM successful handover information may be included in a successful handover report configuration, for example, it may be a successful handover configuration (successHO-Config). The information triggering the generation and / or reporting of LTM successful handover information may include one or more of the following: TA timeout, unable to access based on the TA acquired in advance (or the TA in the LTM command), access based on a random access mechanism, the TA acquired in advance (or the TA in the LTM command) is invalid, the time ratio threshold of the timer, in the dual active protocol stack (DAPS) handover in the source primary cell

[0101] (Primary Cell, PCell) RLF occurs. The timer may include one or more of the following: T304, T310, T312, etc. Among them, access based on the random access mechanism may also be random access after receiving the TA value. For example, the UE receives the LTM command containing the TA value and (re) accesses based on the random access mechanism.

[0102] LTM command information: informs the UE of the LTM command information, which is used for the UE to include the LTM command information when generating LTM successful handover information. When the node receives the LTM successful handover information, it can find the handover configuration information applied by the node to the UE according to the LTM command information, so as to analyze the problem and / or the cause of the problem and perform corresponding self-optimization operations. The LTM command information can be any information that the node can understand, for example, it can be composed of one or more numbers. When the node obtains the information, it can find the configuration information corresponding to the handover.

[0103] In some implementations, the third message may also be used for other SON-related reports, for example, other SON-related reports may be a Connection Establishment Failure (CEF) report, or a Random Access (Random Access) report, or a Successful Handover (Successful Handover) report, or a Radio Link Failure (RLF) report, or a measurement report, or other reports related to a wireless connection. The nodes exchange the content related to the third message, for example, between a source node and a target node, between an original access node and a new access node, etc. The node may send the content related to the third message to the UE for configuration of other SON-related reports, for example, through an RRC Reestablishment (RRCReestablishment) message, an RRC Reconfiguration Complete (RRCReconfiguration) message, an RRC Recovery Complete (RRCResume) message, or an RRC Setup Complete (RRCSetup) message; it may also be sent by way of MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message. In some implementations, after the node sends the third message related content to the UE, the UE may add the LTM command information to other SON related reports. When the node receives the report from the UE and / or other nodes (for example, the UE sends the report to other nodes, and other nodes forward it to the node), the node may find the switching configuration information applied by the node to the UE according to the LTM command information, and perform corresponding self-optimization. This can avoid the node needing to store the switching configuration and / or the UE context for a long time, and can also avoid the inability to perform self-optimization due to the node releasing the UE context.

[0104] Example 3

[0105] In some embodiments, the present disclosure proposes a method for supporting mobility self-optimization, which may include: a fifth node sends a fourth message that LTM successful switching information is available to a sixth node, so that the sixth node knows that the fifth node has the LTM successful switching information.

[0106] In some embodiments, the fourth message may be included in one or more of the following: RRC user measurements available (UE-MeasurementsAvailable) or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC reconfiguration complete (RRCReconfigurationComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC establishment complete (RRCSetupComplete) message; it may also be sent by MAC CE; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0107] In some implementations, the fourth message may include one or more of the following fields or related information:

[0108] UE ID: indicates the user to which the LTM successful handover information is available.

[0109] Sending node ID: used to identify the node that sends the message.

[0110] Receiving node ID: used to identify the node that receives the message.

[0111] LTM successful switching information available: used to indicate that LTM successful switching information is available, indicating that LTM successful switching information is stored. This field can be represented by a single bit, for example, when this bit is 1, it indicates that LTM successful switching information is available, and when this bit is 0, it indicates that LTM successful switching information is not available; it can also be that when this bit is 0, it indicates that LTM successful switching information is available, and when this bit is 1, it indicates that LTM successful switching information is not available.

[0112] In some embodiments, the sixth node may send a fifth message containing an LTM successful switching information request to the fifth node based on its own situation and / or based on the fourth message received from the fifth node indicating that LTM successful switching information is available, to request the fifth node to report LTM successful switching information.

[0113] In some embodiments, the fifth message may be included in one or more of the following: a UE Information Request message of RRC; or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message.

[0114] In some implementations, the fifth message may include one or more of the following fields or related information:

[0115] UE ID: indicates the user to which the LTM successful handover information is available.

[0116] Sending node ID: used to identify the node that sends the message.

[0117] Receiving node ID: used to identify the node that receives the message.

[0118] LTM successful switching information request: used to indicate LTM successful switching information request, indicating requesting LTM successful switching information. This field can be represented by a single bit, for example, when this bit is 1, it indicates requesting LTM successful switching information, and when this bit is 0, it indicates not requesting LTM successful switching information; it can also be that when this bit is 0, it indicates requesting LTM successful switching information, and when this bit is 1, it indicates not requesting LTM successful switching information.

[0119] Example 4

[0120] In some embodiments, the present disclosure proposes a method for supporting mobility self-optimization, which may include: the seventh node sends a sixth message including LTM successful handover information to the eighth node, so that the eighth node can obtain LTM handover related information. In some embodiments, for example, the UE may record the LTM handover related information in the LTM successful handover information, and report the LTM successful handover information to the node, and the node may perform self-optimization according to the information in the LTM successful handover information. For example, the UE may record the LTM related information in the LTM successful handover information, and the node (gNB CU and / or gNBDU) may optimize the LTM according to the information in the LTM successful handover information. For example, when the UE cannot access based on the TA value acquired in advance, the UE (re) obtains synchronization information based on the random access mechanism to complete the access. Although the handover is successful, the service is interrupted due to the UE re-doing random access. The mechanism of the above-mentioned LTM successful handover information can avoid the service interruption caused by the UE re-doing random access. The LTM successful handover information may be included in a successful handover report (Successful Handover Report, SHR). The LTM successful handover information may also be referred to as an LTM successful handover report.

[0121] In some implementations, the sixth message may include one or more of the following fields or related information:

[0122] UE ID: indicates the user corresponding to the LTM successful handover information.

[0123] LTM handover flag: indicates whether the handover is an LTM handover. This field can be represented by a single bit. For example, when the bit is 1, it indicates that the handover is an LTM handover, and when the bit is 0, it indicates that the handover is not an LTM handover. When the bit is 0, it indicates that the handover is an LTM handover, and when the bit is 1, it indicates that the handover is not an LTM handover. For example, if the handover is an LTM handover, this information is set and / or included in the LTM successful handover information.

[0124] ·LTM command information: that is, LTM command information associated with LTM successful switching information, which is used for UE to include the LTM command information when generating LTM successful switching information. The LTM command information can come from the LTM successful switching information request and / or configuration. When the node receives the LTM successful switching information, it can find the switching configuration information applied by the node to the UE according to the LTM command information, so as to analyze the problem and / or the cause of the problem, and perform corresponding self-optimization operations. The LTM command information can be any information that the node can understand, for example, it can be composed of one or more numbers. When the node obtains the information, it can find the configuration information corresponding to the switching.

[0125] TA value in the LTM command: After receiving this information, the node can perform self-optimization. For example,

[0126] The node can adjust and / or update its maintenance of the TA effective time based on the information, so as to avoid service interruption and / or radio link failure due to TA failure. For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command and / or the difference is greater than a threshold value, it means that the TA value in the LTM command is invalid, or it can be said that the UE cannot access based on the TA value in the LTM command. The node can adjust and / or update its maintenance of the TA effective time based on the information. For example, if access cannot be made based on the TA value in the LTM command, the information is set and / or included in the LTM successful switching information. TA value used for successful access: After receiving the information, the node can perform self-optimization. For example, the node can adjust and / or update its maintenance of the TA effective time based on the information, so as to avoid service interruption and / or radio link failure due to TA failure. For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command and / or the difference is greater than a threshold value, it means that the TA value in the LTM command is invalid, or it can be said that the UE cannot access based on the TA value in the LTM command, and the node can adjust and / or update its maintenance of the TA validity period based on this information. For example, if access cannot be made based on the TA value in the LTM command, this information is set and / or included in the LTM successful handover information. For example, if the LTM command does not include a TA value, this information is set and / or included in the LTM successful handover information.

[0127] ·TA failure identifier: used to identify the failure of the TA value. In some embodiments, for example, the TA value obtained from the LTM command may be invalid. After the node obtains this information, the node may know that the TA value obtained in advance for this switch is invalid so that the user cannot directly access the target cell, resulting in service interruption. For example, the UE needs to redo the random access process, resulting in service interruption. The node can adjust and / or update its maintenance of the TA validity period based on this information to avoid service interruption due to TA failure. The TA failure identifier can also be placed in the cause field. For example, if the UE cannot access based on the TA value in the LTM command, this information is set and / or included in the LTM successful switching information.

[0128] For example, if the TA fails, this information is set and / or included in the LTM successful handover information. · (Re) Access based on random access mechanism identifier: indicates that the UE accesses the target node through (re) access based on random access mechanism. For example, the reason for (re)doing the random access process is that it is impossible to access based on the TA value obtained in advance. This field can inform the node that although the user has successfully switched, the service is interrupted due to (re)access based on random access mechanism. The node needs to optimize this situation to avoid this situation.

[0129] This field can also be an identifier for receiving a TA value for random access. For example, the UE receives an LTM command containing a TA value, but cannot access based on the TA value in the LTM command, and (re)accesses based on the random access mechanism. For example, if access is performed through a random access mechanism when accessing the target node, this information is set and / or included in the LTM successful handover information. For example, if access cannot be performed using the TA value in the LTM command, access is performed through a random access mechanism, and this information is set and / or included in the LTM successful handover information.

[0130] · Identification of failure to access based on the TA value in the LTM command: Indicates that the UE cannot access based on the TA value in the LTM command when accessing the target node. This field can inform the node that although the user has successfully switched, it cannot access based on the TA value in the LTM command, and the random access process is repeated, resulting in service interruption. The node needs to optimize this situation to avoid this situation. This field can also be an identification of failed access based on the TA value in the LTM command. For example, if the UE cannot access based on the TA value in the LTM command, this information is set and / or included in the LTM successful switching information.

[0131] Layer 1 measurement results: used to record the layer 1 measurement results before and / or during and / or after the handover. In some embodiments, for example, the node can determine whether the handover target node is correctly selected based on this information. In other embodiments, for example, the node can determine whether the reason why the user cannot access based on the TA value obtained in advance is due to the failure of the TA value based on this information. For example, if the layer 1 measurement result when the TA value is obtained in advance (i.e., the TA value in the LTM command) is too different from the layer 1 measurement result when the TA value is actually accessed, for example,

[0132] If it is greater than and / or equal to a certain threshold value, it indicates that the reason for the failure of access is that the TA value is invalid.

[0133] · Layer 3 measurement results: used to record the layer 3 measurement results before and / or during and / or after the switch. In some embodiments, for example, the node can determine whether the target node for the switch is correctly selected based on the information. In other embodiments, for example, the node can determine whether the reason why the user cannot access based on the TA value obtained in advance is due to the invalidity of the TA value based on the information. For example, if the layer 1 measurement result when the TA value is obtained in advance (i.e., the TA value in the LTM command) is too different from the layer 1 measurement result at the time of actual access, for example, it is greater than and / or equal to a certain threshold value, indicating that the reason for the inability to access is the invalidity of the TA value in the LTM command.

[0134] Access type: indicates the access type of the target cell. The access type may include one or more of the following: random access based, random access free. The random access based may include one or more of the following: contention-based random access, contention-free random access, etc.

[0135] Configured access type: indicates the configured access type. The access type may include one or more of the following: random access based, random access free. The random access based may include one or more of the following: contention-based random access, contention-free random access, etc. For example, if the LTM command contains a TA value, the configured access type is random access free.

[0136] Actual access type: indicates the access type of the actual access target cell. The access type may include one or more of the following: random access based, random access free. The random access based may include one or more of the following: contention-based random access, contention-free random access, etc.

[0137] · Conditional handover configuration: may include one or more of the following: (candidate) target cell identifier,

[0138] (Candidate) Target cell corresponding execution conditions, (Candidate) Target cell supported slices,

[0139] The PDU session (resource) situation accepted by the (candidate) target cell, etc. The PDU session (resource) situation accepted by the (candidate) target cell may include one or more of the following:

[0140] PDU session identifier, number of received PDU sessions (resources), etc. In one implementation, for example, if the UE is configured with conditional switching and LTM (simultaneously), the configuration of the conditional switching needs to be included. The configuration of the conditional switching can be used for node optimization for switching.

[0141] For example, the configuration of conditional switching and / or LTM is optimized to improve mobility robustness.

[0142] In some implementations, after receiving the LTM successful handover information request and / or configuration, if the trigger information configured in the LTM successful handover information request and / or configuration is met during the handover process, the UE saves and / or generates (and / or reports) the LTM successful handover information and determines the content in the LTM successful handover information. For example, the following situations may be included:

[0143] In some embodiments, the switching performed by the UE is LTM, for example, the switching is triggered by an LTM command, and the UE records the LTM switching identifier and / or LTM command information (for example, LTM command information associated with the LTM command that triggered the LTM switching) in the successful switching information.

[0144] And / or, in some embodiments, when the UE cannot access based on the TA value in the LTM command and re-does random access to switch to the target node, the UE records one or more of the following in the LTM successful switching information: an identifier for re-doing random access, the TA value in the LTM command, the TA value used for successful access, an identifier for TA failure, an identifier for re-doing random access, an identifier for not being able to access based on the TA value in the LTM command, layer 1 measurement results, layer 3 measurement results, etc.

[0145] And / or, in some implementations, the UE determines whether the TA value in the LTM command is invalid based on the TA value in the LTM command and the TA value at the time of successful access. For example, the difference between the TA value in the LTM command and the TA value at the time of successful access is used to determine whether the reason why the user cannot access based on the TA value acquired in advance is that the TA value in the LTM command is invalid. For example, if the difference between the TA value in the LTM command and the TA value at the time of successful access is greater than and / or equal to a certain threshold value, it indicates that the TA value in the LTM command is invalid. The UE records the TA invalidation flag in the LTM successful switching information.

[0146] In some implementations, after receiving the LTM successful switching information, the node may analyze the cause of the problem based on the information therein and perform corresponding self-optimization, for example, the following situations may be included:

[0147] In some embodiments, after receiving the LTM successful switching information, the node can determine whether the TA value in the LTM command is invalid based on the difference between the TA value in the LTM command and the TA value at the time of successful access, for example, determine whether the reason why the user cannot access based on the TA value obtained in advance is that the TA value in the LTM command is invalid. For example, if the difference between the TA value in the LTM command and the TA value at the time of successful access is greater than and / or equal to a certain threshold value, it means that the TA value in the LTM command is invalid. The node (for example, the source gNB DU and / or the target gNB DU) performs self-optimization based on the received LTM successful switching information. For example, the node adjusts and / or updates the maintenance of the effective time of the TA value (for example, the effective time of the TA value can be shortened). In the subsequent LTM, service interruption caused by the invalidity of the TA value in the LTM command can be avoided, thereby ensuring the robustness of the LTM switching.

[0148] In other embodiments, after receiving the LTM successful handover information, the node may determine whether the TA value in the LTM command is invalid based on the measurement results therein (for example, it may be a layer 1 measurement result or a layer 3 measurement result), for example, determine whether the reason why the user cannot access based on the TA value in the LTM command is due to the invalidity of the TA value. For example, if the difference between the measurement result when obtaining the TA value in advance (i.e., obtaining the TA value in the LTM command) and the measurement result when actually accessing is too large, for example, greater than and / or equal to a certain threshold value, it indicates that the reason for the inability to access is the invalidity of the TA value in the LTM command. The node (for example, the source gNB DU and / or the target gNB DU) performs self-optimization based on the received LTM successful handover information, for example, the node adjusts and / or updates the maintenance of the valid time of the TA value (for example, the valid time of the TA value can be shortened). In the subsequent LTM, the service interruption caused by the invalidity of the TA value in the LTM command can be avoided, and the robustness of the LTM handover can be guaranteed.

[0149] In some other embodiments, after receiving the LTM successful switching information, the node can know that the reason for the service interruption is that the TA value is invalid according to the identifier of the invalid (or failed) TA value. The node (e.g., the source gNB DU and / or the target gNBDU) performs self-optimization based on the received LTM successful switching information. For example, the node adjusts and / or updates the maintenance of the TA value validity period (e.g., the TA value validity period can be shortened). In the subsequent LTM, the service interruption caused by the invalid TA value in the LTM command can be avoided, and the robustness of the LTM switching can be guaranteed.

[0150] If the node finds that the TA value in the LTM command of the UE is invalid when accessing (for example, when the TA value in the LTM command used for the UE to perform LTM switching is determined to be invalid based on the LTM successful switching information), the node performs self-optimization based on the received LTM successful switching information and / or the problem type, for example, the node adjusts and / or updates the maintenance of the effective time of the TA value (for example, the effective time of the TA value can be shortened). The LTM successful switching information may be the aforementioned sixth message, and the problem type may be the aforementioned second message.

[0151] Example 5

[0152] In some embodiments, the present disclosure proposes a method for supporting mobility self-optimization, which may include: a ninth node sends a seventh message containing LTM-related and / or target side-related wireless link failure information to a tenth node, so that the tenth node can obtain LTM-related and / or target side-related wireless link failure information, for example, it can be used by the tenth node to analyze the cause of the LTM-related wireless link failure and perform related self-optimization, or it can be used by the tenth node to analyze whether the problem originates from itself or other nodes (for example, the target node side) when analyzing the cause of the wireless link and perform related self-optimization, or it can be forwarded by the tenth node to other nodes for other nodes to analyze the cause of the failure and perform related self-optimization.

[0153] In some embodiments, the seventh message may be included in one or more of the following: RRC user information response (UEInformationResponse), secondary cell group failure information (SCGFailureInformation), primary cell group failure information (MCGFailureInformation); Xn's failure indication (FAILURE INDICATION) message, handover report (HANDOVER REPORT) message, access and mobility indication (ACCESS AND MOBILITY INDICATION) message, secondary node modification request (S-NODE MODIFICATION REQUEST) message, secondary gNB modification request (SgNB MODIFICATIONREQUEST) message, secondary cell group failure information report (SCG FAILURE INFORMATION REPORT) message, RRC transfer (RRC TRANSFER) message; F1's access and mobility indication (ACCESS AND MOBILITY INDICATION) message; NG's uplink RAN ​​configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, downlink RAN ​​configuration forwarding (DOWNLINK RAN CONFIGURATION The information may be included in a report, wherein the report may be a Connection Establishment Failure (CEF) report, a Random Access (Random Access) report, a Successful Handover (Successful Handover) report, a Radio Link Failure (RLF) report, a measurement report, or other reports related to the radio connection.

[0154] In some implementations, the seventh message may include one or more of the following fields or related information:

[0155] UE ID: indicates the user corresponding to the LTM success or failure information.

[0156] LTM switch flag: indicates whether the switch is an LTM switch. This field can be represented by a single bit. For example, when the bit is 1, it indicates that the switch is an LTM switch, and when the bit is 0, it indicates that the switch is not an LTM switch; when the bit is 0, it indicates that the switch is an LTM switch, and when the bit is 1, it indicates that the switch is not an LTM switch.

[0157] LTM and conditional handover (simultaneously) configured flag: indicates that the UE is (simultaneously) configured with conditional handover and LTM. The node receiving this information can analyze the cause of conditional handover and / or LTM and / or perform corresponding self-optimization. If the UE is (simultaneously) configured with conditional handover and LTM, this information is included.

[0158] LTM command information: used for UE to include the LTM command information when generating LTM-related radio link failure. When a node receives LTM-related radio link failure information, it can find the handover configuration information applied by the node to the UE according to the LTM command information, so as to analyze the problem and / or the cause of the problem and perform corresponding self-optimization operations. The LTM command information can be any information that the node can understand, for example, it can be composed of one or more numbers.

[0159] After the node obtains the information, it can find the configuration information corresponding to the switch.

[0160] TA value in the LTM command: After receiving this information, the node can perform self-optimization. For example,

[0161] The node can adjust and / or update its maintenance of the TA effective time based on the information, so as to avoid service interruption and / or radio link failure due to TA failure. For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command and / or the difference is greater than a threshold value, it means that the TA value in the LTM command is invalid, or it can be said that the UE cannot access based on the TA value in the LTM command. The node can adjust and / or update its maintenance of the TA effective time based on the information. For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command, the information is included. For example, if access is based on a random access mechanism, the information is included. For example, if access cannot be made based on the TA value in the LTM command, the information is included. For example, if access can be made based on the TA value in the LTM command, the information is included. For example, if the LTM command contains a TA value, the information is included.

[0162] ·TA value used for successful access: After receiving this information, the node can perform self-optimization. For example, the node can adjust and / or update its maintenance of the TA effective time based on this information to avoid service interruption and / or wireless link failure due to TA failure. For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command and / or the difference is greater than a threshold value, it means that the TA value in the LTM command is invalid. It can also be that the UE cannot access based on the TA value in the LTM command. The node can adjust and / or update its maintenance of the TA effective time based on this information. For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command, this information is included. For example, if access is based on a random access mechanism, this information is included.

[0163] ·TA failure identifier: used to identify the failure of the TA value. In some embodiments, for example, the TA value obtained from the LTM command may be invalid. After the node obtains this information, the node may know that the TA value obtained in advance for this switch is invalid so that the user cannot directly access the target cell, resulting in a wireless link failure and / or service interruption. The node can adjust and / or update its maintenance of the TA validity period based on this information to avoid service interruption due to TA failure. The TA failure identifier can also be placed in the cause field. For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command, this information is included. For example, if access is based on a random access mechanism, this information is included. For example, if access cannot be made based on the TA value in the LTM command, this information is included.

[0164] For example, if the LTM command contains a TA value, include this information. For example, if the TA value is invalid, include this information. For example, if the TA value obtained from the LTM command is invalid, include this information.

[0165] ·Identifier of (re)access based on random access mechanism: indicates that the UE accesses the target node through (re)access based on random access mechanism. For example, the reason for (re)doing the random access process is that it is impossible to access based on the TA value acquired in advance. This field can also be an identifier of receiving a TA value for random access. For example, the UE receives an LTM command containing a TA value, but is unable to access based on the TA value in the LTM command, and attempts to access (re)based on the random access mechanism. For example, if access is performed through a random access mechanism when accessing the target node, this information is included. For example, if access is unable to be performed using the TA value in the LTM command, access is performed through a random access mechanism, and this information is included.

[0166] Unable to access based on TA value in LTM command: indicates that the UE cannot access the target node based on the TA value in the LTM command. In this case, the radio link may fail and / or the service may be interrupted. The node needs to optimize this situation to avoid this. This field can also be an indicator of access failure based on the TA value in the LTM command.

[0167] For example, if the TA value used for successful access is inconsistent with the TA value in the LTM command, this information is included. For example, if access is based on a random access mechanism, this information is included. For example, if access cannot be made based on the TA value in the LTM command, this information is included. For example, if the TA value is invalid, this information is included. For example, if the TA value obtained from the LTM command is invalid, this information is included.

[0168] · Layer 1 measurement results: used to record the layer 1 measurement results before and / or during and / or after the switch. In some embodiments, for example, the node can determine whether the target node for the switch is correctly selected based on the information. In other embodiments, for example, the node can determine whether the reason why the user cannot access and / or the wireless link fails is due to the invalid TA value based on the information. For example, if the layer 1 measurement result when the TA value is obtained in advance (i.e., the TA value in the LTM command is obtained) is too different from the layer 1 measurement result at the time of actual access, for example, it is greater than and / or equal to a certain threshold value, indicating that the reason for the inability to access is the invalid TA value.

[0169] LTM command reception time to successful re-access time: For example, it can be used for the node to obtain corresponding switching configuration and / or perform cause analysis and / or self-optimization, for example, to determine whether the switching is too early, too late, etc.

[0170] LTM command reception time to failure time: For example, it can be used for the node to obtain the corresponding switching configuration and / or perform cause analysis and / or self-optimization, for example, to determine whether the switching is too early, too late, etc.

[0171] PDCCH order reception time to LTM command reception time: For example, it can be used by the node to obtain the corresponding switching configuration and / or perform cause analysis and / or self-optimization. For example, to determine whether the TA value is invalid. For example, when the PDCCH order reception time to the LTM command reception time is greater than a threshold value, it indicates that the TA value is invalid. For example, if a PDCCH order is received, this information is included.

[0172] · Preamble code sending time to LTM command receiving time: For example, it can be used for the node to obtain the corresponding switching configuration and / or perform cause analysis and / or self-optimization. For example, to determine whether the TA value is invalid. For example, when the preamble code sending time to the LTM command receiving time is greater than a threshold value, it indicates that the TA value is invalid. For example, if a PDCCH order is received, this information is included. For example, if a preamble code is sent, this information is included.

[0173] PDCCH order reception time: For example, it can be used for the node to obtain the corresponding switching configuration and / or perform cause analysis and / or self-optimization. For example, if a PDCCH order is received, this information is included.

[0174] ·PDCCH order reception time to report and / or information reporting time: can be used for the node to find the configuration information for this handover. For example, if a PDCCH order is received, it contains this information.

[0175] LTM command reception time: For example, it can be used for the node to obtain the corresponding switching configuration and / or perform cause analysis and / or perform self-optimization.

[0176] LTM command reception time to report and / or information reporting time: can be used for the node to find the configuration information for this switch.

[0177] Random Access Response (RAR) window expiration: used to indicate that during random access, the UE did not receive a RAR before the RAR window expired. In some implementations, when a node receives this information, the node may know that the problem is due to the UE being unable to receive the RAR sent from the target node, and the node needs to consider this information when performing self-optimization.

[0178] In some embodiments, for example, the node knows that the problem comes from the target node, and the node does not

[0179] Adjust and / or update its own configuration to avoid unnecessary adjustment and / or update. Random access contention resolution timer expiration: used to indicate that during the random access process, the UE did not receive MSG4 when the random access contention resolution timer expired. In some embodiments, when the node receives this information, the node may know that the problem is due to the UE being unable to receive MSG4 sent from the target node, and the node needs to consider this information when performing self-optimization. In some embodiments, for example, the node knows that the problem comes from the target node, and the node does not adjust and / or update its own configuration to avoid unnecessary adjustment and / or update.

[0180] · SSB measurement result: used to indicate the measurement result of the SSB. If the SSB is not received, the SSB measurement result may be set to a predefined value, such as 0. In some embodiments, when the node receives this information, the node may know that the problem is due to the UE being unable to receive the SSB sent from the target node, and the node needs to consider this information when performing self-optimization. In some embodiments, for example, the node knows that the problem comes from the target node, and the node does not adjust and / or update its own configuration to avoid unnecessary adjustments and / or updates.

[0181] Uplink transmission failure: used to indicate an uplink transmission failure. In some embodiments, when a node receives this information, the node may know that the problem is due to the UE being unable to send uplink information on the target node side, and the node needs to consider this information when performing self-optimization. In some embodiments, for example, the node knows that the problem comes from the target node, and the node does not adjust and / or update its own configuration to avoid unnecessary adjustments and / or updates.

[0182] Indication of transmission failure in uplink synchronization: used to indicate the situation where uplink transmission failure occurs in uplink synchronization. In some embodiments, when the node receives this information, the node may know that the problem is due to the uplink failure of the UE on the target node side, and the node needs to consider this information when performing self-optimization. In some embodiments, for example, the node knows that the problem comes from the target node, and the node does not adjust and / or update its own configuration to avoid unnecessary adjustments and / or updates.

[0183] MSG3 transmission failure: used to indicate that MSG3 transmission failed during random access. For example,

[0184] It could be that the LBT failed to be sent, or that NACK feedback was received after sending.

[0185] In some embodiments, when the node receives the information, the node may know that the problem is due to the UE's inability to successfully send MSG3 to the target node, and the node needs to consider the information when performing self-optimization. In some embodiments, for example, the node knows that the problem comes from the target node, and the node does not adjust and / or update its own configuration to avoid unnecessary adjustments and / or updates.

[0186] Access type: indicates the access type of the target cell. The access type may include one or more of the following: random access based, random access free. The random access based may include one or more of the following: contention-based random access, contention-free random access, etc.

[0187] Configured access type: indicates the configured access type. The access type may include one or more of the following: random access based, random access free. The random access based may include one or more of the following: contention-based random access, contention-free random access, etc. For example, if the LTM command contains a TA value, the configured access type is random access free.

[0188] Actual access type: indicates the access type of the actual access target cell. The access type may include one or more of the following: random access based, random access free. The random access based may include one or more of the following: contention-based random access, contention-free random access, etc.

[0189] · Conditional handover configuration: may include one or more of the following: (candidate) target cell identifier,

[0190] (Candidate) Target cell corresponding execution conditions, (Candidate) Target cell supported slices,

[0191] The PDU session (resource) situation accepted by the (candidate) target cell, etc. The PDU session (resource) situation accepted by the (candidate) target cell may include one or more of the following:

[0192] PDU session identifier, number of accepted PDU sessions (resources), etc. In one embodiment, for example, if the UE is (simultaneously) configured with conditional switching and LTM, the configuration of the conditional switching is included. The configuration of the conditional switching can be used for node optimization for switching. For example, the configuration of conditional switching and / or LTM is optimized to improve mobility robustness.

[0193] Whether the reconnected cell is a cell in the configured LTM candidate cells: This information is used to inform the UE whether the cell reconnected after the radio link fails is a cell in the configured LTM candidate cells. If the reconnected cell is not a cell in the configured LTM candidate cells, it means that the LTM candidate cell selection is wrong. For example, if the reconnected cell is and / or is not a cell in the configured LTM candidate cells, this information is included.

[0194] The information in the seventh message can also be used in scenarios other than radio link failure. For example, when the UE encounters a problem during random access, the information in the seventh message can be recorded in a random access report. When the random access node obtains the report, it can analyze it and perform corresponding self-optimization. In one embodiment, for example, it is found that the problem comes from downlink transmission. For example, the report contains one or more of the following: expiration of the random access response (Random Access Response, RAR) window, expiration of the random access contention resolution timer, too low measurement result of SSB, etc. The node can know that the reason for the failure of the random access attempt is that the UE did not receive the downlink message (for example, SSB, RAR, MSG4, etc.), and the node can make corresponding adjustments and / or updates, for example, resource allocation adjustment and / or update and / or transmit power adjustment and / or update, etc., to ensure the success rate of random access. In another embodiment, for example, it is found that the problem comes from uplink transmission, for example, the report includes one or more of the following: uplink transmission failure, indication of transmission failure in uplink synchronization, MSG3 transmission failure, etc. The node can know that the reason for the failure of the random access attempt is a problem with the uplink transmission, and the node can make corresponding adjustments and / or updates, for example, resource allocation adjustment and / or update and / or transmission power configuration adjustment and / or update, etc., to ensure the success rate of random access. In the present disclosure, the TA value obtained in advance and the TA value in the LTM command can refer to each other.

[0195] The self-optimization described in the present disclosure may include making and / or updating network energy saving decisions, making and / or updating load balancing, making and / or updating coverage optimization, making and / or updating mobility optimization and / or management, making and / or updating configuration, etc. and performing corresponding optimization. Among them, making and / or updating configuration may include one or more of the following: adjusting and / or updating the maintenance of the effective time of the TA value, adjusting and / or updating the resource allocation strategy, adjusting and / or updating the transmit power configuration, adjusting and / or updating the transmit power, etc.

[0196] Results and reports may refer to each other in this disclosure.

[0197] In the present disclosure, time may be represented by one or more of the following: timestamp, time point, time interval, timer, time period, time length, time cycle, time interval, etc. The time length may be the time length from a certain time point, and the time point may be the current moment. The time may be a relative time or an absolute time. In some embodiments, the time period may be represented by a separate field, for example, a combination of a start time and an end time, or a combination of a start time and a time period.

[0198] Exemplary embodiments of the present disclosure are further described below in conjunction with the accompanying drawings.

[0199] The text and drawings are provided as examples only to help understand the present disclosure. They should not be interpreted as limiting the scope of the present disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art based on what is disclosed herein that the embodiments and examples shown may be changed without departing from the scope of the present disclosure.

[0200] Figure 3A A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3A The process of interaction of failure type and / or problem type between two nodes is shown, so that the second node can obtain the analysis result of the failure type and / or problem type. The second node can perform self-optimization based on the result, or the second node can forward it to other nodes for other nodes to perform self-optimization.

[0201] In some embodiments, for example, the first node may be a UE, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the first node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the first node may be an AMF or an SMF or an MME, and the second node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the first node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be an AMF or an SMF or an MME.

[0202] Step 301A: The first node sends a failure type and / or a problem type to the second node. The failure type and / or the problem type may be the aforementioned second message.

[0203] Step 302A: The second node may perform self-optimization based on the received failure type and / or problem type.

[0204] Figure 3B A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3B The present invention shows the process of exchanging LTM-related and / or target-side-related radio link failure information between UE and gNB CU and between gNB CU and source gNB DU, and / or exchanging failure type and / or problem type between gNB CU and source gNB DU. gNB CU and / or source gNB DU can perform self-optimization based on the analyzed failure type and / or problem and LTM-related and / or target-side-related radio link failure information.

[0205] Step 301B: The UE fails to send a radio link in the source gNB DU or a handover failure occurs when the UE switches to the target cell.

[0206] Step 302B: The UE sends LTM-related and / or target-side-related radio link failure information to the gNB CU. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0207] Step 303B: The gNB CU performs a cause analysis based on the collected LTM-related and / or target-side-related radio link failure information. In some implementations, if the analysis result indicates that the gNB CU itself needs to be optimized, the gNB CU performs self-optimization.

[0208] Step 304B: The gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU. The failure type and / or problem type may be the aforementioned second message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information may be carried by an access and mobility indication (ACCESSAND MOBILITY INDICATION) message. Among them, the LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report). In some embodiments, for example, when the failure type and / or problem type includes a problem from the source gNB DU, the gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU.

[0209] Step 305B: The source gNB DU may perform self-optimization based on the received failure type and / or problem type, and / or LTM-related and / or target-side related radio link failure information.

[0210] Figure 3C A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3C The present invention shows the process of exchanging LTM-related and / or target-side-related radio link failure information between UE and gNB CU and between gNB CU and source gNB DU, and / or exchanging failure type and / or problem type between gNB CU and source gNB DU. gNB CU and / or source gNB DU can perform self-optimization based on the analyzed failure type and / or problem and LTM-related and / or target-side-related radio link failure information.

[0211] Step 301C: The UE fails to send a radio link in the source gNB DU or a handover failure occurs when the UE switches to the target cell.

[0212] Step 302C: The UE sends LTM-related and / or target-side-related radio link failure information to the gNB CU. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0213] Step 303C: The gNB CU sends a failure type and / or problem type request, and / or LTM-related and / or target side-related radio link failure information to the source gNB DU. The failure type and / or problem request may be the aforementioned first message. The LTM-related and / or target side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type request, and / or LTM-related and / or target side-related radio link failure information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM-related and / or target side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0214] Step 304C: The source gNB DU performs cause analysis based on the collected LTM-related and / or target-side-related wireless link failure information. If the analysis result indicates that it needs to be optimized, the source gNB DU performs self-optimization.

[0215] Step 305C: The source gNB DU sends the analyzed failure type and / or problem type to the gNB CU. The failure type and / or problem type may be the aforementioned second message. In some implementations, the gNB DU sends the failure type and / or problem to the gNB CU only when all and / or part of the problem analyzed by the source gNB DU is from the gNB CU. If step 303C includes a failure type and / or problem type request, the source gNB DU needs to send the analyzed failure type and / or problem type to the gNB CU according to the request.

[0216] Step 306C: The gNB CU performs self-optimization based on the failure type and / or problem type, and / or LTM-related and / or target-side related radio link failure information.

[0217] Figure 3D A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3D The process of exchanging LTM-related and / or target-side-related radio link failure information between the UE and the gNB CU, and between the gNB CU and the source gNB DU is shown. The gNB CU and / or the source gNB DU can analyze the failure type and / or problem based on the LTM-related and / or target-side-related radio link failure information and perform corresponding self-optimization.

[0218] Step 301D: The UE fails to send a radio link in the source gNB DU or a handover failure occurs when the UE switches to the target cell.

[0219] Step 302D: The UE sends LTM-related and / or target-side-related radio link failure information to the gNB CU. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0220] Step 303D: The gNB CU performs a cause analysis based on the collected LTM-related and / or target-side-related radio link failure information. In some implementations, the gNB CU analyzes whether the problem is caused by itself. If the analysis result shows that it needs to be optimized, the gNB CU performs self-optimization.

[0221] Step 304D: The gNB CU sends LTM-related and / or target-side-related radio link failure information to the source gNBDU. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The LTM-related and / or target-side-related radio link failure information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0222] Step 305D: The source gNB DU may perform cause analysis based on LTM-related and / or target-side-related radio link failure information. If the analysis result indicates that the problem comes from the source gNB DU, the source gNB DU performs self-optimization.

[0223] Figure 3E A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3E The process of exchanging LTM-related and / or target-side-related radio link failure information between UE and node and between nodes, and / or the process of exchanging failure type and / or problem type between nodes is shown. The source gNB CU and / or source gNB DU can perform self-optimization based on the analyzed failure type and / or problem and LTM-related and / or target-side-related radio link failure information.

[0224] Step 301E: The UE sends a radio link failure at the target node (e.g., including the target gNB DU, target gNB CU, etc.).

[0225] Step 302E: The UE sends LTM-related and / or target-side-related radio link failure information to the target gNB CU. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0226] Step 303E: The target gNB CU performs cause analysis based on the collected LTM-related and / or target-side related radio link failure information.

[0227] Step 304E: The target gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB CU. The failure type and / or problem type may be the aforementioned second message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information may be carried by a handover report (HANDOVERREQUEST) message. Among them, the LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report). If the result of the failure type and / or problem type is that it needs to be optimized, the source gNB CU performs self-optimization.

[0228] Step 305E: The source gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU. The failure type and / or problem type may be the aforementioned second message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report). In some embodiments, for example, when the failure type and / or problem type includes a problem from the source gNB DU, the source gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU.

[0229] Step 306E: The source gNB DU may perform self-optimization based on the received failure type and / or problem type, and / or LTM-related and / or target-side related radio link failure information.

[0230] Figure 3FA schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3F The process of exchanging LTM-related and / or target-side-related radio link failure information between UE and node and between nodes, and / or the process of exchanging failure type and / or problem type between nodes is shown. The source gNB CU and / or source gNB DU can perform self-optimization based on the analyzed failure type and / or problem and LTM-related and / or target-side-related radio link failure information.

[0231] Step 301F: The UE sends a radio link failure at the target node (e.g., including the target gNB DU, target gNB CU, etc.).

[0232] Step 302F: The UE sends LTM-related and / or target-side-related radio link failure information to the target gNB CU. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0233] Step 303F: The target gNB CU sends the failure type and / or problem type request, and / or LTM-related and / or target side-related radio link failure information to the target gNB DU. The failure type and / or problem request may be the aforementioned first message. The LTM-related and / or target side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type request, and / or LTM-related and / or target side-related radio link failure information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM-related and / or target side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0234] Step 304F: The target gNB DU performs cause analysis based on the collected LTM-related and / or target-side related radio link failure information.

[0235] Step 305F: The target gNB DU sends the analyzed failure type and / or problem type to the target gNB CU. The failure type and / or problem type may be the aforementioned second message. If step 303F includes a failure type and / or problem type request, the target gNB DU needs to send the analyzed failure type and / or problem type to the target gNB CU according to the request.

[0236] Step 306F: The target gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB CU. The failure type and / or problem type may be the aforementioned second message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information may be carried by a handover report (HANDOVERREQUEST) message. Among them, the LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report). If the result of the failure type and / or problem type is that it needs to be optimized, the source gNB CU performs self-optimization.

[0237] Step 307F: The source gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU. The failure type and / or problem type may be the aforementioned second message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report). In some embodiments, for example, when the failure type and / or problem type includes a problem from the source gNB DU, the source gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU.

[0238] Step 308F: The source gNB DU may perform self-optimization based on the received failure type and / or problem type, and / or LTM-related and / or target-side related radio link failure information.

[0239] Figure 3G A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3G The process of exchanging LTM-related and / or target-side-related radio link failure information between UE and node and between nodes, and / or the process of exchanging failure type and / or problem type between nodes is shown. The source gNB CU and / or source gNB DU can perform self-optimization based on the analyzed failure type and / or problem and LTM-related and / or target-side-related radio link failure information.

[0240] Step 301G: The UE sends a radio link failure at the target node (e.g., including the target gNB DU, target gNB CU, etc.).

[0241] Step 302G: The UE sends LTM-related and / or target-side-related radio link failure information to the target gNB CU. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0242] Step 303G: The target gNB CU performs cause analysis.

[0243] Step 304G: The target gNB CU sends a failure type and / or problem type request, and / or LTM-related and / or target-side-related radio link failure information to the target gNB DU. The failure type and / or problem request may be the aforementioned first message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type request, and / or LTM-related and / or target-side-related radio link failure information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report).

[0244] Step 305G: The target gNB DU performs cause analysis based on the collected LTM-related and / or target-side related radio link failure information.

[0245] Step 306G: The target gNB DU sends the analyzed failure type and / or problem type to the target gNB CU. The failure type and / or problem type may be the aforementioned second message. If step 304G includes a failure type and / or problem type request, the target gNB DU needs to send the analyzed failure type and / or problem type to the target gNB CU according to the request.

[0246] Step 307G: The target gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB CU. The failure type and / or problem type includes the analysis result of the target gNB CU and / or the analysis result of the target gNB DU obtained from the target gNB DU. The failure type and / or problem type may be the aforementioned second message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information may be carried by a handover report (HANDOVER REQUEST) message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report). If the result of the failure type and / or problem type is that it needs to be optimized, the source gNB CU performs self-optimization.

[0247] Step 308G: The source gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU. The failure type and / or problem type may be the aforementioned second message. The LTM-related and / or target-side-related radio link failure information may be the aforementioned seventh message. The failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. The LTM-related and / or target-side-related radio link failure information is carried by a radio link failure report (RLF Report). In some embodiments, for example, when the failure type and / or problem type includes a problem from the source gNB DU, the source gNB CU sends the failure type and / or problem type, and / or LTM-related and / or target-side-related radio link failure information to the source gNB DU.

[0248] Step 309G: The source gNB DU may perform self-optimization based on the received failure type and / or problem type, and / or LTM-related and / or target side-related radio link failure information.

[0249] Figure 3H A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 3H The process of interaction of failure type and / or problem type between two nodes is shown, so that the second node can obtain the analysis result of the failure type and / or problem type. The second node can perform self-optimization based on the result, or the second node can forward it to other nodes for other nodes to perform self-optimization.

[0250] In some embodiments, for example, the first node may be a UE, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the first node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the first node may be an AMF or an SMF or an MME, and the second node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the first node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be an AMF or an SMF or an MME.

[0251] Step 301H: The second node sends a failure type and / or problem type request to the first node. The failure type and / or problem type request may be the aforementioned first message.

[0252] Step 302H: The first node sends a failure type and / or a problem type to the second node. The failure type and / or the problem type may be the aforementioned second message.

[0253] Step 303H: The second node may perform self-optimization based on the received failure type and / or problem type. The second node may also forward the received failure type and / or problem type for other nodes to perform self-optimization.

[0254] Figure 4 A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 4 It shows the exchange of LTM successful switching information request and / or configuration between two nodes, so that the fourth node can forward it to other nodes and / or be used for LTM successful switching information generation.

[0255] In some embodiments, for example, the third node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the fourth node may be a UE. In other embodiments, for example, the third node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the third node may be an AMF or an SMF or an MME, and the fourth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the third node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourth node may be an AMF or an SMF or an MME.

[0256] Step 401A: The third node sends an LTM successful switching information request and / or configuration to the fourth node. The LTM successful switching information request and / or configuration may be the aforementioned third message.

[0257] Step 402A: The fourth node may forward the information to other nodes and / or be used for LTM successful switching information generation.

[0258] Figure 5A A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 5A It shows the successful switching information of the LTM interaction between the two nodes, so that the sixth node can forward it to other nodes for the other nodes to perform self-optimization, or the sixth node can perform self-optimization.

[0259] In some embodiments, for example, the fifth node may be a UE, and the sixth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the fifth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the fifth node may be an AMF or an SMF or an MME, and the sixth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the fifth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixth node may be an AMF or an SMF or an MME.

[0260] Step 501A: The fifth node sends LTM successful switching information available to the sixth node. The LTM successful switching information available may be the aforementioned fourth message.

[0261] Step 502A: The sixth node sends an LTM successful switching information request to the fifth node. The LTM successful switching information request may be the aforementioned fifth message.

[0262] Step 503A: The fifth node sends LTM successful switching information to the sixth node. The LTM successful switching information may be the aforementioned sixth message.

[0263] Step 504A: The sixth node may forward the information to other nodes for the other nodes to perform self-optimization, or the sixth node may perform self-optimization based on the collected LTM successful switching information.

[0264] Figure 5B A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 5B The two nodes exchange LTM successful switching information, which is forwarded by the sixth node to other nodes for other nodes to perform self-optimization. Alternatively, the sixth node can perform self-optimization based on the collected LTM successful switching information.

[0265] In some embodiments, for example, the fifth node may be a UE, and the sixth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the fifth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the fifth node may be an AMF or an SMF or an MME, and the sixth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the fifth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixth node may be an AMF or an SMF or an MME.

[0266] Step 501B: The sixth node sends an LTM successful switching information request to the fifth node. The LTM successful switching information request may be the aforementioned fifth message.

[0267] Step 502B: The fifth node sends LTM successful switching information to the sixth node. The LTM successful switching information may be the aforementioned sixth message.

[0268] Step 503B: the sixth node may forward the information to other nodes for other nodes to perform self-optimization, or the sixth node may perform self-optimization based on the collected LTM successful switching information.

[0269] Fig. 6A A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Fig. 6A The two nodes exchange LTM successful switching information, so that the seventh node can forward it to other nodes for self-optimization, or the eighth node can perform self-optimization based on the collected LTM successful switching information.

[0270] In some embodiments, for example, the seventh node may be a UE, and the eighth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the seventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the seventh node may be an AMF or an SMF or an MME, and the eighth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the seventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighth node may be an AMF or an SMF or an MME.

[0271] Step 601A: The seventh node sends LTM successful switching information to the eighth node. The LTM successful switching information may be the aforementioned sixth message.

[0272] Step 602A: The eighth node may forward the information to other nodes for self-optimization by the other nodes, or the seventh node may perform self-optimization based on the collected LTM successful switching information.

[0273] Figure 6B A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 6B The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0274] Step 601B: The source gNB DU sends an LTM successful handover information request and / or configuration to the gNB CU so that the source gNB DU can configure it to the UE. The LTM successful handover information request and / or configuration can be the aforementioned third information. The LTM successful handover information request and / or configuration can be carried by the UE context modification required message and / or the UE context modification response message.

[0275] Step 602B: The gNB CU sends an LTM successful handover information request and / or configuration to the UE, so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration may be the aforementioned third information.

[0276] Step 603B: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0277] Step 604B: The UE sends LTM successful handover information available to the gNB CU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in an RRC reconfiguration complete message.

[0278] Step 605B: The gNB CU sends an LTM success information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by a UE Information Request message.

[0279] Step 606B: The UE sends LTM handover success information to the gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0280] Step 607B: The gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0281] Step 608B: The source gNB DU performs self-optimization based on the received LTM success information.

[0282] Figure 6C A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 6C The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0283] Step 601C: The source gNB DU sends an LTM successful handover information request and / or configuration to the UE, so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration can be the aforementioned third information. This information can be configured through MAC CE.

[0284] Step 602C: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0285] Step 603C: The UE sends LTM successful handover information available to the gNB CU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in an RRC reconfiguration complete message.

[0286] Step 604C: The gNB CU sends an LTM success information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by a UE Information Request message.

[0287] Step 605C: The UE sends LTM handover success information to the gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0288] Step 606C: The gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0289] Step 607C: The source gNB DU performs self-optimization based on the received LTM success information.

[0290] Fig.6D A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Fig.6D The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0291] Step 601D: The source gNB DU sends an LTM successful handover information request and / or configuration to the UE so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration may be the aforementioned third information. This information may be configured via MAC CE.

[0292] Step 602D: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0293] Step 603D: The UE sends LTM successful handover information available to the target gNB DU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in MAC CE mode.

[0294] Step 604D: The target gNB DU sends an LTM success information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by MAC CE.

[0295] Step 605D: The UE sends LTM handover success information to the target gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by MAC CE.

[0296] Step 606D: The target gNB DU sends LTM switching success information to the gNB CU. The LTM switching success information may be the aforementioned sixth message.

[0297] Step 607D: The gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0298] Step 608D: The source gNB DU performs self-optimization based on the received LTM success information.

[0299] Fig. 6E A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Fig. 6E The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0300] Step 601E: The source gNB DU sends an LTM successful handover information request and / or configuration to the source gNB CU so that the source gNB DU can configure it to the UE. The LTM successful handover information request and / or configuration can be the aforementioned third information. The LTM successful handover information request and / or configuration can be carried by the UE context modification required message and / or the UE context modification response message.

[0301] Step 602E: The source gNB CU sends an LTM successful handover information request and / or configuration to the UE so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration may be the aforementioned third information.

[0302] Step 603E: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0303] Step 604E: The UE sends LTM successful handover information available to the target gNB CU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in an RRC reconfiguration complete message.

[0304] Step 605E: The target gNB CU sends an LTM success handover information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by a UE Information Request message.

[0305] Step 606E: The UE sends LTM handover success information to the target gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0306] Step 607E: The target gNB CU sends LTM handover success information to the source gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a handover report (HANDOVER REPORT) message or an access and mobility indication (ACCESS AND MOBILITY INDICATION) message or a failure indication (FAILURE INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0307] Step 608E: The source gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0308] Step 609E: The source gNB DU performs self-optimization based on the received LTM success information.

[0309] Fig. 6F A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Fig. 6F The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0310] Step 601F: The source gNB DU sends an LTM successful handover information request and / or configuration to the UE so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration may be the aforementioned third information. This information may be configured via MAC CE.

[0311] Step 602F: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0312] Step 603F: The UE sends LTM successful handover information available to the target gNB CU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in an RRC reconfiguration complete message.

[0313] Step 604F: The target gNB CU sends an LTM success information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by a UE Information Request message.

[0314] Step 605F: The UE sends LTM handover success information to the target gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0315] Step 606F: The target gNB CU sends LTM handover success information to the source gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a handover report (HANDOVER REPORT) message or an access and mobility indication (ACCESS AND MOBILITY INDICATION) message or a failure indication (FAILURE INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0316] Step 607F: The source gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0317] Step 608F: The source gNB DU performs self-optimization based on the received LTM success information.

[0318] Figure 6G A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 6G The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0319] Step 601G: The source gNB DU sends an LTM successful handover information request and / or configuration to the UE so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration may be the aforementioned third information. This information may be configured via MAC CE.

[0320] Step 602G: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0321] Step 603G: The UE sends LTM successful handover information available to the target gNB DU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in MAC CE mode.

[0322] Step 604G: The target gNB DU sends an LTM success information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by MAC CE.

[0323] Step 605G: The UE sends LTM switching success information to the target gNB DU. The LTM switching success information may be the aforementioned sixth message. The LTM switching success information may be carried by MAC CE.

[0324] Step 606G: The target gNB DU sends LTM handover success information to the target gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0325] Step 607G: The target gNB DU sends LTM success switching information to the target gNB CU. The LTM success switching information may be the aforementioned sixth message.

[0326] Step 608G: The target gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0327] Step 609G: The source gNB DU performs self-optimization based on the received LTM success information.

[0328] Figure 6H A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 6H The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0329] Step 601H: The source gNB CU sends an LTM successful handover information request and / or configuration to the UE, so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration can be the aforementioned third information.

[0330] Step 602H: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0331] Step 603H: The UE sends LTM successful handover information available to the target gNB CU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in an RRC reconfiguration complete message.

[0332] Step 604H: The target gNB CU sends an LTM success handover information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by a UE Information Request message.

[0333] Step 605H: The UE sends LTM handover success information to the target gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0334] Step 606H: The target gNB CU sends LTM handover success information to the source gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a handover report (HANDOVER REPORT) message or an access and mobility indication (ACCESS AND MOBILITY INDICATION) message or a failure indication (FAILURE INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0335] Step 607H: The source gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report). In one embodiment, the source gNB CU may perform a cause analysis, and the source gNB CU may send the analyzed problem type to the source gNB DU. The problem type may be the aforementioned second message. The problem type may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message.

[0336] Step 608H: The source gNB DU performs self-optimization based on the received LTM success information and / or problem type.

[0337] Fig.6I A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Fig.6I The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB CU can obtain the successful LTM switching information for self-optimization.

[0338] Step 601I: The source gNB CU sends an LTM successful handover information request and / or configuration to the UE, so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration may be the aforementioned third information.

[0339] Step 602I: The process of switching the UE to the cell of the target gNB CU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0340] Step 603I: The UE sends LTM successful handover information available to the target gNB CU. The LTM successful handover information available may be the aforementioned fourth message. The LTM successful handover information may be carried in an RRC reconfiguration complete message.

[0341] Step 604I: The target gNB CU sends an LTM success information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by a UE Information Request message.

[0342] Step 605I: The UE sends LTM handover success information to the target gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0343] Step 606I: The target gNB CU sends LTM handover success information to the source gNB CU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a handover report (HANDOVER REPORT) message or an access and mobility indication (ACCESS AND MOBILITY INDICATION) message or a failure indication (FAILURE INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0344] Step 607I: The source gNB DU performs self-optimization based on the received LTM success information.

[0345] Figure 6J A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 6J The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source node can obtain the successful LTM switching information for self-optimization.

[0346] Step 601J: The source node sends an LTM successful handover information request and / or configuration to the UE, so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration can be the aforementioned third information.

[0347] Step 602J: The process of handing over the UE to the cell of the target node. In some implementations, for example, if the trigger information configured in the LTM successful handover information request and / or configuration is satisfied during the handover process, the UE generates the LTM successful handover information.

[0348] Step 603J: The UE sends an LTM successful handover information available message to the target node. The LTM successful handover information available message may be the aforementioned fourth message. The LTM successful handover information may be carried in an RRC reconfiguration complete message.

[0349] Step 604J: The target node sends an LTM success information request to the UE. The LTM success information request may be the fifth message mentioned above. The LTM success information request may be carried by a UE Information Request message.

[0350] Step 605J: The UE sends LTM handover success information to the target node. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a successful handover report (Successful Handover Report).

[0351] Step 606J: The target node sends LTM handover success information to the source node. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by a HANDOVER REPORT message, an ACCESS AND MOBILITY INDICATION message, or a FAILURE INDICATION message. The LTM handover success information may be carried by a Successful Handover Report.

[0352] Step 607J: The source node performs self-optimization based on the received LTM success information.

[0353] Figure 6K A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 6K The information of successful LTM switching exchanged between nodes and UEs and between nodes is shown, so that the source gNB DU can obtain the LTM successful switching information for self-optimization.

[0354] Step 601K: The source gNB CU sends an LTM successful handover information request and / or configuration to the UE so that the UE can generate LTM successful handover information. The LTM successful handover information request and / or configuration may be the aforementioned third information.

[0355] Step 602K: The process of switching the UE to the cell of the target gNB DU. In some embodiments, for example, if the trigger information configured in the LTM successful switching information request and / or configuration is met during the switching process, the UE generates LTM successful switching information.

[0356] Step 603K: The UE sends LTM successful switching information available to the target gNB DU. The LTM successful switching information available may be the aforementioned fourth message. The LTM successful switching information may be carried in MAC CE mode.

[0357] Step 604K: The target gNB DU sends an LTM success information request to the UE. The LTM success information request may be the aforementioned fifth message. The LTM success information request may be carried by MAC CE.

[0358] Step 605K: The UE sends LTM switching success information to the target gNB DU. The LTM switching success information may be the aforementioned sixth message. The LTM switching success information may be carried by MAC CE.

[0359] Step 606K: The target gNB DU sends LTM switching success information to the gNB CU. The LTM switching success information may be the aforementioned sixth message.

[0360] Step 607K: The gNB CU sends LTM handover success information to the source gNB DU. The LTM handover success information may be the aforementioned sixth message. The LTM handover success information may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. Among them, the LTM handover success information may be carried by a successful handover report (Successful Handover Report). In one embodiment, the source gNB CU may perform a cause analysis, and the source gNB CU may send the analyzed problem type to the source gNB DU. The problem type may be the aforementioned second message. The problem type may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message.

[0361] Step 608K: The source gNB DU performs self-optimization based on the received LTM success information and / or problem type.

[0362] Figure 7 A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 7 It shows that two nodes exchange LTM-related and / or target-side-related wireless link failure information for the tenth node to perform self-optimization.

[0363] In some embodiments, for example, the seventh node may be a UE, and the eighth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the seventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the seventh node may be an AMF or an SMF or an MME, and the eighth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the seventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighth node may be an AMF or an SMF or an MME.

[0364] Step 701A: The ninth node sends LTM-related and / or target-side-related radio link failure information to the tenth node. The LTM-related and / or target-side-related radio link failure information may be the seventh message mentioned above.

[0365] Step 702A: The ninth node performs self-optimization based on the received LTM-related and / or target-side-related radio link failure information.

[0366] Fig. 8A A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Fig. 8A The process of the UE, source node and target node exchanging switching command information is shown, so that the source node can find the relevant configuration for LTM switching based on the LTM command information after releasing the UE context, and can perform self-optimization based on the collected SON-related reports.

[0367] Step 801A: The source node sends LTM command information to the target node. The LTM command information may be the LTM command information in the third information mentioned above.

[0368] Step 802A: Handover process of switching the UE to the target node cell. The source node releases the UE context information.

[0369] Step 803A: The target node collects SON-related reports from other nodes and / or UEs.

[0370] Step 804A: The target node sends LTM command information and / or SON-related reports to the source node. The LTM command information and / or SON-related reports may be carried by a HANDOVER REPORT message and / or an ACCESS AND MOBILITY INDICATION message and / or a FAILURE INDICATION message. The source node finds the configuration used for the LTM handover according to the LTM command information, and performs self-optimization based on the obtained SON report. The LTM command information may be the LTM command information in the aforementioned third information.

[0371] Figure 8B A schematic diagram showing one aspect of a method for supporting mobility self-optimization according to an embodiment of the present disclosure is shown. Specifically, Figure 8B The process of the UE, source node and target node exchanging switching command information is shown, so that the source node can find the relevant configuration for LTM switching based on the LTM command information after releasing the UE context, and can perform self-optimization based on the collected SON-related reports.

[0372] Step 801B: The source gNB DU sends LTM command information to the source gNB CU. The LTM command information may be the LTM command information in the aforementioned third information.

[0373] Step 802B: The source gNB CU sends LTM command information to the target gNB DU. The LTM command information may be the LTM command information in the aforementioned third information.

[0374] Step 803B: The handover process of switching the UE to the target node cell. The source node (including the source gNB CU and / or the source gNB DU) releases the UE context information.

[0375] Step 804B: The target gNB CU collects SON-related reports from other nodes and / or UEs.

[0376] Step 805B: The target gNB CU sends LTM command information and / or SON-related reports to the source gNB CU. The LTM command information may be the LTM command information in the aforementioned third information. The LTM command information and / or SON-related reports may be sent via a HANDOVER REPORT message, an ACCESS AND MOBILITY INDICATION message, or a FAILURE INDICATION message.

[0377] Step 806B: The source gNB CU sends LTM command information and / or SON-related reports to the source gNB DU. The LTM command information may be the LTM command information in the aforementioned third information. The LTM command information and / or SON-related reports may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message. The source gNB DU finds the configuration used for this LTM switching based on the LTM command information, and performs self-optimization based on the acquired SON report. The source gNB DU may also perform cause analysis based on the collected SON-related reports, and the source gNB CU may send the analyzed failure type and / or problem type to the source gNB DU in this step. The failure type and / or problem type may be the aforementioned second message. The failure type and / or problem type may be carried by an access and mobility indication (ACCESS AND MOBILITY INDICATION) message.

[0378] Figure 8B An example of different CUs with different DUs is shown. If it is an example of the same CU with different DUs, Figure 8B The target gNBCU and source gNB CU are one node, where 802B and 805B can be omitted.

[0379] It should be understood that, depending on the application scenario, the various exemplary aspects, methods, steps, processes, etc. shown in the above-mentioned drawings can be combined and implemented in any manner, and this document does not limit this.

[0380] Next, Fig. 9 A flowchart of a method 900 performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown.

[0381] like Fig. 9 As shown, according to an embodiment of the present disclosure, a method 900 executed by a first node in a wireless communication system may include: in step S901, a third message is sent to a user equipment UE or a second node, the third message including configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, inability to access based on the first TA value, access based on a random access mechanism, and failure of the first TA value; in step S902, a sixth message is received from the second node, the sixth message including the LTM successful switching information; and in step S903, corresponding configuration adjustments are made based on the LTM successful switching information.

[0382] According to an embodiment of the present disclosure, the LTM successful switching information includes one or more of the following: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, a second measurement result, an LTM switching identifier, and LTM command information.

[0383] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first TA value and the second TA value.

[0384] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first measurement result and / or the second measurement result.

[0385] According to an embodiment of the present disclosure, making corresponding configuration adjustments based on the LTM successful switching information further includes: when it is determined based on the LTM successful switching information that the first TA value is invalid, adjusting the validity period of the first TA value.

[0386] According to an embodiment of the present disclosure, the first TA value is a TA value in an LTM command, and the second TA value is a TA value acquired based on a random access mechanism.

[0387] According to an embodiment of the present disclosure, the first measurement result is a layer 1 measurement result, and the second measurement result is a layer 3 measurement result.

[0388] Fig.10 A flowchart of a method 1000 executed by a user equipment UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0389] like Fig.10 As shown, the method 1000 performed by the user equipment UE in the wireless communication system according to the embodiment of the present disclosure may include: in step S1001, receiving a third message from the first node or the second node, the third message including configuration information associated with the layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, unable to access based on the first TA value, access based on the random access mechanism, and first TA value failure; and in step S1002, sending a sixth message to the second node or the third node, the sixth message including the LTM successful switching information. In some embodiments, the third node may be a target node for UE switching, such as a target gNB or a target gNB CU or a target gNB DU, etc.

[0390] According to an embodiment of the present disclosure, the method further includes: in a case where the configuration information associated with the LTM successful switching information is satisfied during the switching process, saving the LTM successful switching information.

[0391] According to an embodiment of the present disclosure, the method further includes: when the UE performs LTM switching, including the LTM switching identifier and / or LTM command information in the LTM successful switching information.

[0392] According to an embodiment of the present disclosure, the method also includes: when the UE cannot access based on the first TA value and switches to a third node through random access, one or more of the following are included in the LTM successful switching information: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, and a second measurement result.

[0393] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first TA value and the second TA value.

[0394] According to an embodiment of the present disclosure, the method further includes: determining whether the first TA value is invalid based on the first measurement result and / or the second measurement result.

[0395] According to an embodiment of the present disclosure, the first TA value is a TA value in an LTM command, and the second TA value is a TA value acquired based on a random access mechanism.

[0396] According to an embodiment of the present disclosure, the first measurement result is a layer 1 measurement result, and the second measurement result is a layer 3 measurement result.

[0397] Fig.11 A flowchart of a method 1100 performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown.

[0398] like Fig.11As shown, according to an embodiment of the present disclosure, the method 1100 executed by the second node in the wireless communication system may include: in step S1101, receiving a third message from the first node, the third message including configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, inability to access based on the first TA value, access based on a random access mechanism, and failure of the first TA value; in step S1102, sending the configuration information to a user equipment UE; in step S1103, receiving a sixth message from the UE or the third node, the sixth message including the LTM successful switching information; and in step S1104, sending the LTM successful switching information to the first node.

[0399] According to an embodiment of the present disclosure, the LTM successful switching information includes one or more of the following: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, a second measurement result, an LTM switching identifier, and LTM command information.

[0400] It should be understood that methods 900, 1000, 1100, etc. according to the embodiments of the present disclosure may also include any steps described in combination with the various examples, aspects, drawings, etc. of the present disclosure.

[0401] Next, Fig.12 A schematic diagram of a node 1200 according to an embodiment of the present disclosure is shown.

[0402] like Fig.12 As shown, a node (or node device, such as the first node or the second node as described above) 1200 according to an embodiment of the present disclosure may include a transceiver 1210 and a processor 1220. The transceiver 1210 may be configured to send and receive signals. The processor 1220 may be coupled to the transceiver 1210 and may be configured to (e.g., control the transceiver 1210) execute a method performed by a node (e.g., the first node and / or the second node) according to an embodiment of the present disclosure.

[0403] Fig.13 A schematic diagram of a user equipment 1300 according to an embodiment of the present disclosure is shown.

[0404] like Fig.13As shown, the user equipment 1300 according to an embodiment of the present disclosure may include a transceiver 1310 and a processor 1320. The transceiver 1310 may be configured to send and receive signals. The processor 1320 may be coupled to the transceiver 1310 and may be configured to (e.g., control the transceiver 1310) execute the method performed by the user equipment according to an embodiment of the present disclosure. In the present disclosure, the processor may also be referred to as a controller.

[0405] The embodiments of the present disclosure further provide a computer-readable medium on which computer-readable instructions are stored. When the instructions are executed by a processor, they can be used to implement any method according to the embodiments of the present disclosure.

[0406] Various embodiments of the present disclosure may be implemented as computer-readable codes embodied on a computer-readable recording medium from a specific perspective. A computer-readable recording medium is any data storage device that can store data readable by a computer system. Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), and the like. Computer-readable recording media may be distributed via a computer system connected via a network, and therefore computer-readable codes may be stored and executed in a distributed manner. Moreover, the functional programs, codes, and code segments for implementing the various embodiments of the present disclosure may be easily interpreted by a technician in the field of the embodiments of the present disclosure.

[0407] It will be understood that the embodiments of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. Software may be stored as program instructions or computer-readable codes executable on a processor on a non-transient computer-readable medium. Examples of non-transient computer-readable recording media include magnetic storage media (e.g., ROM, floppy disk, hard disk, etc.) and optical recording media (e.g., CD-ROM, digital video disk (DVD), etc.). Non-transient computer-readable recording media may also be distributed on network-coupled computer systems so that computer-readable codes are stored and executed in a distributed manner. The medium may be read by a computer, stored in a memory, and executed by a processor. Various embodiments may be implemented by a computer or a portable terminal including a controller and a memory, and the memory may be an example of a non-transient computer-readable recording medium suitable for storing (multiple) programs having instructions for implementing embodiments of the present disclosure. The present disclosure may be implemented by a program having a code for specifically implementing the apparatus and method described in the claims, the program being stored in a machine (or computer) readable storage medium. The program may be electronically carried on any medium, such as a communication signal transmitted via a wired or wireless connection, and the present disclosure suitably includes its equivalents.

[0408] The above description is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any technician familiar with the technical field can make various changes or substitutions within the technical scope disclosed in the present disclosure, and these changes or substitutions should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A method performed by a first node in a wireless communication system, comprising: Sending a third message to a user equipment UE or a second node, the third message including configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, inability to access based on the first TA value, access based on a random access mechanism, and failure of the first TA value; receiving a sixth message from the second node, the sixth message including the LTM successful switching information; and Make corresponding configuration adjustments based on the LTM successful switching information.

2. The method according to claim 1, wherein: The LTM successful switching information includes one or more of the following: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, a second measurement result, an LTM switching identifier, and LTM command information, The first TA value is a TA value in the LTM command, and the second TA value is a TA value obtained based on a random access mechanism; The first measurement result is a layer 1 measurement result, and the second measurement result is a layer 3 measurement result.

3. The method according to claim 1, wherein: The method further comprises: It is determined whether the first TA value is invalid based on the first TA value and the second TA value.

4. The method according to claim 1, wherein: The method further comprises: It is determined whether the first TA value is invalid based on the first measurement result and / or the second measurement result.

5. The method according to claim 1, wherein: The configuration adjustment based on the LTM successful switching information also includes: When it is determined based on the LTM successful switching information that the first TA value is invalid, the validity period of the first TA value is adjusted.

6. A method performed by a user equipment UE in a wireless communication system, comprising: receiving a third message from the first node or the second node, the third message including configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, unable to access based on the first TA value, access based on a random access mechanism, and invalidation of the first TA value; and A sixth message is sent to the second node or the third node, where the sixth message includes the LTM successful switching information.

7. The method according to claim 6, wherein: The method further comprises: In the case where the configuration information associated with the LTM successful switching information is satisfied during the switching process, the LTM successful switching information is saved.

8. The method according to claim 6 or 7, wherein: The method further comprises: In the case where the UE performs LTM switching, the LTM switching identifier and / or LTM command information is included in the LTM successful switching information.

9. The method according to claim 6 or 8, wherein: The method further comprises: When the UE cannot access the third node based on the first TA value and switches to the third node through random access, one or more of the following are included in the LTM successful switching information: an identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, and a second measurement result, The first TA value is a TA value in the LTM command, and the second TA value is a TA value obtained based on a random access mechanism; The first measurement result is a layer 1 measurement result, and the second measurement result is a layer 3 measurement result.

10. The method according to claim 6 or 9, wherein: The method further comprises: It is determined whether the first TA value is invalid based on the first TA value and the second TA value.

11. The method according to claim 6 or 9, wherein: The method further comprises: It is determined whether the first TA value is invalid based on the first measurement result and / or the second measurement result.

12. A method performed by a second node in a wireless communication system, comprising: Receiving a third message from the first node, the third message including configuration information associated with layer 1 / layer 2 triggered mobility LTM successful switching information, wherein the configuration information associated with the LTM successful switching information includes one or more of the following: timing advance TA value timeout, unable to access based on the first TA value, access based on a random access mechanism, and failure of the first TA value; Sending the configuration information to a user equipment UE; receiving a sixth message from the UE or the third node, the sixth message including the LTM successful switching information; and Send the LTM successful switching information to the first node.

13. The method according to claim 12, wherein: The LTM successful switching information includes one or more of the following: An identifier of access based on a random access mechanism, a first TA value, a second TA value, an identifier of failure of the first TA value, an identifier of inability to access based on the first TA value, a first measurement result, a second measurement result, an LTM switching identifier, and LTM command information.

14. A node device in a wireless communication system, comprising: Transceiver; as well as A processor is coupled to the transceiver and configured to execute the method as described in any one of claims 1-5 or 12-13.

15. A user equipment in a wireless communication system, comprising: Transceiver; as well as A processor is coupled to the transceiver and configured to execute the method according to any one of claims 6 to 11.

Images