Information transmission method and device, and storage medium

Abstract

The present disclosure provides an information transmission method and device, and a storage medium. The method comprises: sending a first message to a second node, wherein the first message comprises first information, and the first information is used for requesting layer 1 / layer 2 triggered mobility (LTM). According to the present disclosure, an LTM interaction can be carried out between the nodes, so that an LTM configuration is supported, thereby improving the availability of LTM.

Description

Information transmission method and device, and storage medium Technical Field

[0001] The present disclosure relates to the field of communications, and in particular to an information transmission method and device, and a storage medium. Background Art

[0002] Serving cell changes are triggered by Layer 3 (L3) measurements and are handled by switching between the primary cell (PCell) and the primary secondary cell (PSCell) via Radio Resource Control (RRC) signaling. This switching approach requires reconfiguration of upper layers, such as the RRC layer or the Packet Data Convergence Protocol (PDCP), and lower layers, such as the Medium Access Control (MAC) layer or the physical layer (PHY). This results in high switching overhead and a long switching time.

[0003] Through Layer 1 / Layer 2 triggered mobility (L1 / L2 triggered mobility, LTM), the upper layer configuration can be maintained during the cell handover process, which helps to reduce the handover overhead and latency.

[0004] Summary of the Invention

[0005] In order to optimize the signaling interaction process between nodes of LTM, the embodiments of the present disclosure provide an information transmission method and device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, an information transmission method is provided, which is executed by a first node and includes: sending a first message to a second node, where the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0007] According to a second aspect of an embodiment of the present disclosure, an information transmission method is provided, which is executed by a second node and includes: receiving a first message sent by a first node, where the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0008] According to a third aspect of an embodiment of the present disclosure, a method for information transmission is provided, which is executed by a third node and includes: sending a first message to a first node so that the first node sends a first message to a second node, wherein the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a first node is provided, comprising: a transceiver module configured to send a first message to a second node, wherein the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a second node is provided, including: a transceiver module, configured to receive a first message sent by a first node, the first message including first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0011] According to the sixth aspect of an embodiment of the present disclosure, a third node is provided, including: a transceiver module, configured to send a first message to a first node, so that the first node sends a first message to a second node, the first message including first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0012] According to a seventh aspect of an embodiment of the present disclosure, there is provided a first node, comprising: one or more processors; wherein the processor is configured to execute any one of the information transmission methods of the first aspect.

[0013] According to an eighth aspect of an embodiment of the present disclosure, there is provided a second node, comprising: one or more processors; wherein the processor is configured to execute the method of information transmission behavior of any one of the second aspects.

[0014] According to a ninth aspect of an embodiment of the present disclosure, a third node is provided, comprising: one or more processors; wherein the processor is configured to execute the method of information transmission behavior of any one of the third aspects.

[0015] According to the tenth aspect of an embodiment of the present disclosure, a communication system is provided, including a first node, a second node, and a third node, wherein the first node is configured to implement the information transmission method of any one of the first aspect, the second node is configured to implement the information transmission method of any one of the second aspect, and the third node is configured to implement the information transmission method of any one of the third aspect.

[0016] According to an eleventh aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes an information transmission method as described in any one of the first, second or third aspects.

[0017] In an embodiment of the present disclosure, a first node may send a first message to a second node, including first information, and the first information may be used to request an LTM, thereby enabling LTM interaction between nodes, supporting LTM configuration, and improving LTM availability.

[0018] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0020] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0021] FIG1B is an exemplary schematic diagram of an NR-DC architecture provided according to an embodiment of the present disclosure.

[0022] FIG1C is an exemplary schematic diagram of a dual-connectivity architecture provided according to an embodiment of the present disclosure.

[0023] FIG1D is an exemplary interaction diagram of an LTM cell handover process provided according to an embodiment of the present disclosure.

[0024] FIG. 1E is a schematic diagram of an exemplary interaction of an SCG LTM process initiated by an SN without the participation of an MN (using SRB3) according to an embodiment of the present disclosure.

[0025] FIG1F is an exemplary interaction diagram of an SCG LTM process initiated by an SN without the participation of an MN (without using SRB3) according to an embodiment of the present disclosure.

[0026] FIG2 is an exemplary interaction diagram of an information transmission method provided according to an embodiment of the present disclosure.

[0027] FIG3A is an exemplary interaction diagram of an information transmission method provided according to an embodiment of the present disclosure.

[0028] FIG3B is an exemplary interaction diagram of the information transmission method provided according to an embodiment of the present disclosure.

[0029] FIG3C is an exemplary interaction diagram of the information transmission method provided according to an embodiment of the present disclosure.

[0030] FIG4A is an exemplary interaction diagram of an information transmission method provided according to an embodiment of the present disclosure.

[0031] FIG4B is an exemplary interaction diagram of the information transmission method provided according to an embodiment of the present disclosure.

[0032] FIG4C is an exemplary interaction diagram of the information transmission method provided according to an embodiment of the present disclosure.

[0033] FIG4D is an exemplary interaction diagram of the information transmission method provided according to an embodiment of the present disclosure.

[0034] FIG5A is an exemplary block diagram of a first node provided according to an embodiment of the present disclosure.

[0035] FIG5B is an exemplary block diagram of a second node provided according to an embodiment of the present disclosure.

[0036] FIG5C is an exemplary block diagram of a third node provided according to an embodiment of the present disclosure.

[0037] FIG6A is a schematic diagram of an exemplary interaction of a communication device according to an embodiment of the present disclosure.

[0038] FIG6B is an exemplary interaction diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0040] The embodiments of the present disclosure provide an information transmission method, an information transmission device, and a storage medium.

[0041] In a first aspect, an embodiment of the present disclosure proposes an information transmission method, which is executed by a first node and includes: sending a first message to a second node, where the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0042] In the above embodiment, the first node may send a first message to the second node, including first information, and the first information may be used to request LTM, thereby enabling LTM interaction between nodes, supporting LTM configuration, and improving LTM availability.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: an LTM candidate cell identifier; an LTM candidate configuration identifier; LTM indication information, the LTM indication information is used to request an LTM candidate configuration or an LTM candidate configuration update; first indication information, the first indication information is used to indicate that the second node is allowed to prepare layer 3 mobility configuration for the terminal when the configuration of the LTM candidate cell is not supported; the maximum number of configurable candidate cells; a recommended candidate cell list; an LTM candidate cell identifier list; and an LTM candidate configuration identifier list.

[0044] In the above embodiment, the first information may include but is not limited to at least one of the above items, so as to achieve the purpose of requesting LTM between nodes with high availability.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the first message is any one of the following messages: a switching request message; a secondary node SN addition request message; an SN modification request message; an SN change request message; a first Xn message, the first Xn message is used to request LTM; a first inter-node RRC message, the first inter-node RRC message is used to request LTM.

[0046] In the above embodiment, the first information may be sent to the second node by reusing an existing message or using a newly defined message, which has a minor change to the protocol and high usability.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a second message sent by the second node, the second message including at least one of the following: LTM candidate configuration; layer 3 mobility configuration.

[0048] In the above embodiment, the first node may receive the second message returned by the second node, thereby obtaining the LTM candidate configuration and / or the layer 3 mobility configuration, which is compatible with the existing layer 3 mobility configuration acquisition process and has high availability.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the second message is any one of the following messages: a switching request confirmation message; an SN addition request confirmation message; an SN modification request confirmation message; an SN change request confirmation message; a second Xn message, the second Xn message is used for LTM request confirmation; a second inter-node RRC message, the second inter-node RRC message is used for LTM request confirmation.

[0050] In the above embodiment, the second message can reuse an existing message or use a newly defined message for LTM, which is simple to implement and has high availability.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a third message sent by the second node, where the third message is used to notify the first node that the LTM has been successfully executed.

[0052] In the above embodiment, the first node can determine that the LTM has been successfully executed based on the third message sent by the second node, thereby ensuring that the network side has a consistent understanding of the LTM execution and high availability.

[0053] In combination with some embodiments of the first aspect, in some embodiments, when the third message includes LTM indication information, the third message is used to indicate that the change of the terminal service node is triggered by the LTM.

[0054] In the above embodiment, if the third message received by the first node includes LTM indication information, the third message can be used to indicate that the change of the terminal service node is triggered by LTM.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the third message is any one of the following messages: a switching success message; an SN adding success message; an SN modifying success message; an SN changing success message; a third Xn message, the third Xn message is used to indicate that the LTM has been successfully executed; a third inter-node RRC message, the third inter-node RRC message is used to indicate that the LTM has been successfully executed.

[0056] In the above embodiment, the third message may reuse an existing Xn message or may be a new message agreed upon by the protocol, and has high availability.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0058] A fourth message is sent to the second node, where the fourth message is used to cancel the LTM candidate configuration prepared by the second node for the terminal.

[0059] In the above embodiment, the first node may initiate the LTM cancellation process to achieve the purpose of canceling the LTM candidate configuration between nodes.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the fourth message includes at least one of the following: an LTM candidate cell identifier; an LTM candidate configuration identifier; an LTM candidate cell identifier list; or an LTM candidate configuration identifier list.

[0061] In the above embodiment, the fourth message may include but is not limited to at least one of the above items. The first node may use the first message to inform the second node of the candidate cell and candidate configuration identifier corresponding to the candidate configuration that it wishes to cancel, so that the second node can cancel the corresponding LTM candidate configuration, which has high availability.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0063] A fifth message is received, which is sent by the second node after the second node prepares the LTM candidate configuration for the terminal, where the fifth message is used to cancel the LTM candidate configuration prepared by the second node for the terminal.

[0064] In the above embodiment, the second node may also actively initiate cancellation after preparing the LTM candidate configuration for the terminal, and inform the first node through the fifth message, thereby achieving the purpose of canceling the LTM candidate configuration between nodes.

[0065] In combination with some embodiments of the first aspect, in some embodiments, the fifth message includes at least one of the following: an LTM candidate cell identifier; an LTM candidate configuration identifier; an LTM candidate cell identifier list; or an LTM candidate configuration identifier list.

[0066] In the above embodiment, the fifth message may include but is not limited to at least one of the above items. The second node may inform the first node of the candidate cell and candidate configuration identifier corresponding to the canceled candidate configuration through the fifth message, which is simple to implement and has high availability.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0068] A sixth message is sent to the second node, where the sixth message is used to request modification of the LTM candidate configuration prepared by the second node for the terminal.

[0069] In the above embodiment, the first node can initiate the LTM modification process, thereby achieving the purpose of modifying the LTM candidate configuration between nodes, and having high availability.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the sixth message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; LTM candidate cell identifier list; LTM candidate configuration identifier list.

[0071] In the above embodiment, the sixth message may include but is not limited to at least one of the above items, thereby synchronizing the cancelled LTM candidate configuration among nodes, with high availability.

[0072] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a seventh message sent by the second node, where the seventh message is used to request the first node to initiate modification of the LTM candidate configuration.

[0073] In the above embodiment, the second node may request the first node to initiate an LTM modification process through the seventh message, thereby achieving the purpose of modifying the LTM candidate configuration between nodes.

[0074] In combination with some embodiments of the first aspect, in some embodiments, the seventh message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; LTM candidate cell identifier list; LTM candidate configuration identifier list.

[0075] In the above embodiment, the seventh message may include but is not limited to at least one of the above items, thereby synchronizing the LTM candidate configuration requested to be canceled by the second node among nodes, with high availability.

[0076] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: after receiving the third message sent by the second node, sending an eighth message to the third node, the third message is used to indicate that the terminal has successfully accessed the second node, and the eighth message is used to release the resources of the third node.

[0077] In the above embodiment, the first node may send an eighth message to the third node after the terminal successfully accesses the second node, thereby instructing the third node to release resources, thereby avoiding resource waste caused by continuing to occupy the resources of the third node.

[0078] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a first message sent by a third node.

[0079] In the above embodiment, the third node can send the first message to the first node, and the first node can send it to the second node, thereby achieving the purpose of LTM interaction between nodes in the SCG LTM process triggered by SN in the dual connection scenario.

[0080] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: after receiving the second message sent by the second node, sending a ninth message to the third node, the second message including the LTM candidate configuration, and the ninth message including at least one of the following: the second node identifier for preparing the LTM candidate configuration for the terminal; the secondary cell group SCG LTM candidate cell identifier; the SCG LTM candidate cell configuration identifier.

[0081] In the above embodiment, during the SCG LTM process triggered by the SN in a dual connectivity scenario, relevant information of the SCG LTM candidate configuration prepared by the second node can be provided to the SN, thereby improving the availability of LTM in the dual connectivity scenario.

[0082] In a second aspect, an embodiment of the present disclosure proposes an information transmission method, which is executed by a second node and includes: receiving a first message sent by a first node, where the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0083] In the above embodiment, the second node can receive the first message sent by the first node, and the first message can be used to request LTM, thereby enabling LTM interaction between nodes, supporting LTM configuration, and improving LTM availability.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following: an LTM candidate cell identifier; an LTM candidate configuration identifier; LTM indication information, the LTM indication information is used to request an LTM candidate configuration or an LTM candidate configuration update; first indication information, the first indication information is used to indicate that the second node is allowed to prepare layer 3 mobility configuration for the terminal when the configuration of the LTM candidate cell is not supported; the maximum number of configurable candidate cells; a recommended candidate cell list; an LTM candidate cell identifier list; and an LTM candidate configuration identifier list.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the first message is any one of the following messages: a switching request message; a secondary node SN addition request message; an SN modification request message; an SN change request message; a first Xn message, the first Xn message is used to request LTM; a first inter-node RRC message, the first inter-node RRC message is used to request LTM.

[0086] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: preparing an LTM candidate configuration for the terminal based on the first message.

[0087] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: it is impossible to prepare the LTM candidate configuration for the terminal, and the first message includes second indication information, preparing the layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal, and the second indication information is used to request the layer 3 mobility configuration; or it is impossible to prepare the LTM candidate configuration for the terminal, and the first message includes first indication information, preparing the layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal, and the first indication allows the second node to prepare the layer 3 mobility configuration for the terminal when the configuration of the LTM candidate cell is not supported.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes any one of the following: the first message includes first indication information and second indication information, preparing an LTM candidate configuration for the terminal, and preparing a layer 3 mobility configuration for the terminal when the LTM candidate configuration cannot be prepared for the terminal; wherein the first indication information is used to indicate that the second node is allowed to prepare the layer 3 mobility configuration for the terminal when the configuration of the LTM candidate cell is not supported, and the second indication information is used to request the layer 3 mobility configuration;

[0089] The first message includes first indication information and second indication information, which prepare LTM candidate configuration and / or layer 3 mobility configuration for the terminal; wherein the first indication information is used to indicate that the second node is allowed to prepare layer 3 mobility configuration for the terminal when the configuration of LTM candidate cells is not supported, and the second indication information is used to request layer 3 mobility configuration.

[0090] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a second message to the first node, the second message including at least one of the following: LTM candidate configuration; layer 3 mobility configuration.

[0091] In combination with some embodiments of the second aspect, in some embodiments, the second message is any one of the following messages: a switching request confirmation message; an SN addition request confirmation message; an SN modification request confirmation message; an SN change request confirmation message; a second Xn message, the second Xn message is used for LTM request confirmation; a second inter-node RRC message, the second inter-node RRC message is used for LTM request confirmation.

[0092] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a third message to the first node, where the third message is used to notify the first node that the LTM has been successfully executed.

[0093] In combination with some embodiments of the second aspect, in some embodiments, when the third message includes LTM indication information, the third message is used to indicate that the change of the terminal service node is triggered by LTM.

[0094] In combination with some embodiments of the second aspect, in some embodiments, the third message is any one of the following messages: a switching success message; an SN adding success message; an SN modifying success message; an SN changing success message; a third Xn message, the third Xn message is used to indicate that the LTM has been successfully executed; a third inter-node RRC message, the third inter-node RRC message is used to indicate that the LTM has been successfully executed.

[0095] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a fourth message sent by the first node, where the fourth message is used to cancel the LTM candidate configuration prepared by the second node for the terminal;

[0096] Based on the fourth message, the LTM candidate configuration prepared for the terminal is canceled.

[0097] In combination with some embodiments of the second aspect, in some embodiments, the fourth message includes at least one of the following: an LTM candidate cell identifier; an LTM candidate configuration identifier; an LTM candidate cell identifier list; or an LTM candidate configuration identifier list.

[0098] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: after preparing the LTM candidate configuration for the terminal, sending a fifth message to the first node, where the fifth message is used to cancel the LTM candidate configuration prepared by the second node for the terminal.

[0099] In combination with some embodiments of the second aspect, in some embodiments, the fifth message includes at least one of the following: an LTM candidate cell identifier; an LTM candidate configuration identifier; an LTM candidate cell identifier list; or an LTM candidate configuration identifier list.

[0100] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: receiving a sixth message sent by the first node, the sixth message being used to request modification of the LTM candidate configuration prepared by the second node for the terminal; and modifying the LTM candidate configuration prepared for the terminal based on the sixth message.

[0101] In combination with some embodiments of the second aspect, in some embodiments, the sixth message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; LTM candidate cell identifier list; LTM candidate configuration identifier list.

[0102] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a seventh message to the first node, where the seventh message is used to request the first node to initiate modification of the LTM candidate configuration.

[0103] In combination with some embodiments of the second aspect, in some embodiments, the seventh message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; LTM candidate cell identifier list; LTM candidate configuration identifier list.

[0104] In a third aspect, an embodiment of the present disclosure proposes an information transmission method, which is executed by a third node and includes: sending a first message to a first node so that the first node sends a first message to a second node, wherein the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0105] In the above embodiment, in the SCG LTM process triggered by the SN in the dual connectivity scenario, LTM can be exchanged between nodes, thereby improving the availability of LTM.

[0106] In combination with some embodiments of the third aspect, in some embodiments, the first information includes at least one of the following: an LTM candidate cell identifier; an LTM candidate configuration identifier; LTM indication information, the LTM indication information is used to request an LTM candidate configuration or an LTM candidate configuration update; first indication information, the first indication information is used to indicate that the second node is allowed to prepare layer 3 mobility configuration for the terminal when the configuration of the LTM candidate cell is not supported; the maximum number of configurable candidate cells; a recommended candidate cell list; an LTM candidate cell identifier list; and an LTM candidate configuration identifier list.

[0107] In combination with some embodiments of the third aspect, in some embodiments, the first message is any one of the following messages: a switching request message; a secondary node SN addition request message; an SN modification request message; an SN change request message; a first Xn message, the first Xn message is used to request LTM; a first inter-node RRC message, the first inter-node RRC message is used to request LTM.

[0108] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: receiving an eighth message sent by the first node, the eighth message being used to release resources of the third node; and releasing the resources based on the eighth message.

[0109] In combination with some embodiments of the third aspect, in some embodiments, the method also includes: receiving a ninth message sent by the first node, the ninth message including at least one of the following: a second node identifier for preparing LTM candidate configuration for the terminal; a secondary cell group SCG LTM candidate cell identifier; and an SCG LTM candidate cell configuration identifier.

[0110] In a fourth aspect, an embodiment of the present disclosure proposes a first node, comprising: a transceiver module, configured to send a first message to a second node, wherein the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0111] In a fifth aspect, an embodiment of the present disclosure proposes a second node, comprising: a transceiver module, configured to receive a first message sent by a first node, wherein the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0112] In the sixth aspect, an embodiment of the present disclosure proposes a third node, including: a transceiver module, configured to send a first message to a first node, so that the first node sends a first message to a second node, the first message including first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

[0113] In a seventh aspect, an embodiment of the present disclosure proposes a first node, comprising: one or more processors; wherein the processor is used to execute any information transmission method of the first aspect.

[0114] In an eighth aspect, an embodiment of the present disclosure proposes a second node, comprising: one or more processors; wherein the processor is used to execute the method of information transmission behavior of any one of the second aspects.

[0115] In the ninth aspect, an embodiment of the present disclosure proposes a third node, comprising: one or more processors; wherein the processor is used to execute the method of information transmission behavior of any one of the third aspects.

[0116] In the tenth aspect, an embodiment of the present disclosure proposes a communication system, including a first node, a second node, and a third node, wherein the first node is configured to implement the information transmission method of any one of the first aspect, the second node is configured to implement the information transmission method of any one of the second aspect, and the third node is configured to implement the information transmission method of any one of the third aspect.

[0117] In the eleventh aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes an information transmission method as described in any one of the first aspect, the second aspect, or the third aspect.

[0118] It is understandable that the first node, the second node, the third node, the communication system, the storage medium, and the computer program are all used to execute the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0119] The present disclosure provides an information transmission method, apparatus, and storage medium. In some embodiments, the terms "information transmission method," "information processing method," and "communication method" are interchangeable; the terms "information transmission apparatus," "information processing apparatus," and "communication apparatus" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

[0120] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0121] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0122] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0123] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when articles such as "a", "an", "the" in English are used in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0124] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0125] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0126] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0127] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0128] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0129] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0130] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "entity", "subject", etc.

[0131] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0132] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0133] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0134] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0135] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0136] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0137] As shown in FIG1A , a communication system 100 includes a first node 101 , a second node 102 , and a third node 103 .

[0138] In some embodiments, in a non-dual connectivity (non-DC) scenario, the first node 101 may be a source access network device, such as a source base station.

[0139] In some embodiments, in a dual connectivity (DC) scenario, the first node 101 may be a master node (MN).

[0140] In some embodiments, in a non-DC scenario, the second node 102 may be a candidate access network device, such as a candidate base station.

[0141] In some embodiments, in a DC scenario, the second node 102 may be a candidate-secondary node (C-SN).

[0142] In some embodiments, the number of the second node 102 may be one or more, which is not limited in this disclosure.

[0143] In some embodiments, the third node 103 may be a source-secondary node (S-SN) in a DC scenario.

[0144] In some embodiments, the above-mentioned access network device is, for example, a node or device that accesses the terminal to the wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0145] In some embodiments, the above-mentioned access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, and the functions of some protocol layers are centrally controlled by the CU, while the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU, but is not limited to this.

[0146] In some embodiments, the communication system 100 may further include a core network device (not shown in FIG1A ). The core network device may be a single device including one or more network elements, or may be multiple devices or a group of devices. The network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0147] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0148] In some embodiments, the terminal is connected to the core network device through the access network device.

[0149] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0150] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0151] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, systems utilizing other communication methods, and next-generation systems based on these. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be used.

[0152] Before introducing the solutions provided by the present disclosure, the terminology and technical scenarios involved in the present disclosure are first introduced.

[0153] 1. Multi-Rate Dual Connectivity (MR-DC).

[0154] MR-DC is a generalized Intra-Evolved Universal Terrestrial Radio Access (Intra-E-UTRA) dual connectivity in which a terminal can utilize radio resources provided by two different schedulers located on two different Next Generation Radio Access Network (NG-RAN) nodes, connected via a non-ideal backhaul: one providing NR access and the other providing E-UTRA or NR access. One acts as a mobile node (MN) and the other as a network node (SN). The MN and SN are connected via a network interface, with at least one MN connected to the core network.

[0155] 2. NR-NR Dual Connectivity

[0156] NG-RAN supports NR-NR DC (NR-DC), in which a UE connects to a gNB acting as a mobile node and another gNB acting as a network node. The primary gNB connects to the 5GC via the NG interface, and the two gNBs are connected via the Xn interface. The secondary gNB can also connect to the 5GC via the NG-U interface. NR-DC can also be used for UEs to access a single gNB acting as both a mobile node and a network node, with both a mobile group and a network group configured. The NR-DC architecture is shown in Figure 1B.

[0157] In dual connectivity, as shown in Figure 1C, the terminal can access two cell groups, namely the Main Cell Group (MCG) and the Secondary Cell group (SCG). Under the MCG, there may be many cells, one of which is used to initiate initial access, and this cell is called the Primary Cell (PCell). As the name suggests, PCell is the most "main" cell in the MCG. The PCell under the MCG and the Secondary Cell (SCell) under the MCG are combined through carrier aggregation (CA). The main cell in the MCG is the PCell, and the secondary cell is the SCell. The primary and secondary cells in the SCG are the PSCell (Primary Secondary Cell), and the secondary cell is the SCell. Because many signalings are only sent on the PCell and PSCell, for the convenience of description, a concept of special cell (sPCell) is also defined, where PCell and PSCell are collectively referred to as sPCell.

[0158] 3. Layer 1 or Layer 2-triggered mobility (LTM)

[0159] LTM refers to a process of PCell and / or PSCell cell switch triggered by the network through the Medium Access Control Element (MAC CE) based on L1 or L2 measurement results, which may be accompanied by changes in MCG and / or SCG.

[0160] In LTM, the access network device receives an L1 measurement report from the terminal. Based on this report, the access network device changes the terminal's serving cell via a cell switch command issued by the MAC CE. The cell switch command indicates an LTM candidate cell configuration that the access network device has previously provided to the terminal via radio resource control (RRC) signaling. Based on the received cell switch command, the terminal accesses the target cell indicated in the cell change command. LTM can be used to reduce mobility delay.

[0161] The LTM candidate cell configuration can only be added, modified, and released by the network through RRC signaling. The LTM process can be used to reduce mobility delays.

[0162] For LTM, subsequent LTM is supported. Subsequent LTM refers to the subsequent LTM cell handover process between candidate cells without the need for RRC reconfiguration by the network. In other words, after performing a mobility operation, the terminal does not autonomously delete the LTM configuration information. The LTM configuration information can continue to be used to trigger subsequent LTM (Subsequent LTM) even without RRC reconfiguration and update.

[0163] LTM supports the following scenarios:

[0164] LTM supports intra-gNB DU and inter-DU mobility within a gNB CU. LTM supports intra-frequency and inter-frequency mobility, including mobility to inter-frequency cells that are not the current serving cell. The following scenarios are supported:

[0165] -PCell changes in non-CA and non-DC scenarios;

[0166] -PCell changes in CA scenarios;

[0167] - Dual connectivity scenario, MCG PCell change and SCG PSCell change without MN participation (e.g. intra-SN PSCell change). Simultaneous changes of PCell and PSCell LTM are not supported.

[0168] In some embodiments, only intra-DU and inter-DU intra-CU LTMs are supported, but this will be expanded to support inter-CU (or inter-node / gNB) LTMs in the future. Inter-CU (inter-node / gNB) LTMs during SCG PSCell changes involve the Mobile Mobile Network (MN). The MN can coordinate the configuration of candidate PSCells in different CUs.

[0169] 4. LTM configuration:

[0170] LTM uses LTM-Config to configure LTM configuration information.

[0171] The LTM configuration information may include, but is not limited to, one or more of the following:

[0172] LTM reference configuration;

[0173] One or more candidate cell configurations (candidate cell configurations can be added, modified, or deleted through ltm-CandidateToReleaseList and ltm-CandidateToAddModList);

[0174] LTM Channel State Information (CSI) resource configuration.

[0175] The candidate cell configuration may be configured through LTM-Candidate, which includes but is not limited to one or more of the following information:

[0176] candidate configuration identifier;

[0177] Candidate cell identifier;

[0178] Candidate configuration (represented by RRCReconfiguration).

[0179] For example, a candidate configuration may also be referred to as an LTM candidate configuration. An LTM candidate configuration is the configuration portion of an RRC reconfiguration message associated with a candidate cell, for example, a configuration portion for LTM or subsequent conditional pscell addition / change (CPAC). An LTM candidate configuration may be a complete LTM candidate configuration or an incremental configuration relative to a reference configuration.

[0180] For example, the reference configuration may also be referred to as the LTM reference configuration. The LTM reference configuration is a configuration provided by the network to the terminal and is common to a group of incomplete candidate configurations within the same cell group. That is, for an MCG or SCG, the LTM reference configuration is the common portion of the incomplete LTM candidate configurations. The incomplete candidate configuration is combined with the LTM reference configuration to obtain a complete LTM candidate configuration.

[0181] Among them, the incomplete LTM candidate configuration can also be called an incremental configuration. In other words, when the LTM candidate configuration is an incremental configuration. For MCG LTM, the incremental candidate configurations corresponding to all candidate cells of all MCG LTMs correspond to the same reference configuration. Based on this reference configuration and the incremental configurations of the candidate cells, the complete configuration corresponding to all candidate cells of MCG LTM can be generated. For SCG LTM, the incremental candidate configurations corresponding to all candidate cells of SCG LTMs correspond to the same reference configuration. Based on this reference configuration and the incremental configurations of the candidate cells, the complete configuration corresponding to all candidate cells of SCG LTM can be generated.

[0182] 5. LTM execution process:

[0183] Figure 1D shows the overall LTM process. Subsequent LTMs are completed by repeating the early synchronization, LTM cell switch execution, and LTM cell switch completion steps without releasing other LTM candidate configurations after each LTM cell switch. The general air interface process applies to SCG LTM.

[0184] The steps of LTM include:

[0185] Step 1: The terminal sends a MeasurementReport message to the access network device (e.g., gNB). The gNB decides to configure LTM and starts LTM preparation.

[0186] Step 2: The gNB sends an RRCReconfiguration message including the LTM candidate configuration to the terminal.

[0187] Step 3. The terminal stores the LTM candidate configuration and sends an RRCReconfigurationComplete message to the gNB.

[0188] Step 4a: Before receiving the cell switching command, the terminal performs downlink (DL) synchronization with the candidate cell.

[0189] Step 4b: Before receiving the cell switching command, the terminal performs uplink (UL) synchronization with the candidate cell.

[0190] When timing advance (TA) measurement is configured on the network side, the terminal obtains the TA value of the candidate cell through measurement. Before receiving the cell handover command, the terminal obtains the TA value of the candidate cell according to the network's request. The terminal then sends a preamble to the candidate cell indicated by the network side.

[0191] The terminal does not maintain the TA timer for the candidate cells and relies on the network implementation to ensure the validity of the TA.

[0192] Step 5. The terminal performs L1 measurements on the configured candidate cells and sends an L1 measurement report to the gNB. L1 measurements should be performed whenever RRC reconfiguration (from step 2) is applicable.

[0193] Step 6: The gNB decides to perform cell handover to the target cell and sends a MAC CE triggering cell handover by including the candidate configuration index of the target cell. The terminal switches to the target cell and applies the configuration indicated by the candidate configuration index.

[0194] Step 7: If the terminal does not have a valid TA for the target cell, the terminal performs a random access procedure to the target cell.

[0195] Step 8: The terminal completes the LTM cell handover process by sending an RRCReconfigurationComplete message to the target cell.

[0196] If the terminal has performed a random access procedure in step 7, the terminal considers that the LTM cell handover has been successfully completed when the random access procedure is successfully completed. For LTM without a random access procedure, the terminal considers that the LTM cell handover has been successfully completed when it determines that the network has successfully received its first uplink data.

[0197] Steps 4-8 can be performed multiple times for subsequent LTMs using the LTM candidate configuration provided in step 2.

[0198] The over-the-air procedure described in Figure 1D applies to both intra-gNB DU LTM and inter-gNB DU LTM.

[0199] 6. SCG LTM.

[0200] For example, the SCG LTM process initiated by the SN without the participation of the MN (using SRB3) is shown in FIG. 1E .

[0201] When the SN needs to transmit an NR RRC message to the terminal and Signaling Radio Bearer 3 (SRB3) is used to configure the SCG LTM in the SN, the SN initiates this process. It includes the following steps:

[0202] Step 1: The SN sends an SN RRCReconfiguration message including the SCG LTM configuration to the terminal via SRB3.

[0203] Step 2: The terminal stores the SCG LTM candidate cell configuration and sends an RRCReconfigurationComplete message to the SN.

[0204] Step 3a: If the SN indicates, the terminal performs DL synchronization with the candidate cell before receiving the cell switching command.

[0205] Step 3b: If the SN indicates, the terminal performs UL synchronization with the candidate cell before receiving the cell handover command, such as early TA acquisition.

[0206] Step 4: The terminal performs L1 measurement on the configured candidate cells according to the L1 measurement configuration in the RRCReconfiguration received in step 1, and sends an L1 measurement report to the SN. Once the L1 measurement configuration is applicable, the terminal starts performing L1 measurement.

[0207] Step 5: The SN decides to perform cell handover to the target cell and sends a MAC CE triggering cell handover by including the candidate configuration index of the target cell. The terminal switches to the target cell and applies the configuration indicated by the candidate configuration index.

[0208] Step 6: If the terminal does not have a valid TA for the target cell, the terminal performs a random access procedure to the target cell.

[0209] Step 7: The terminal completes the SCG LTM cell handover process by sending an RRCReconfigurationComplete message to the target cell.

[0210] If the terminal has performed a random access procedure in step 6, the terminal considers that the LTM execution is successfully completed when the random access procedure is successfully completed. For LTM without random access, the terminal considers that the LTM execution is successfully completed when the terminal determines that the target cell has successfully received its first UL data.

[0211] Among them, using the SCG LTM candidate configuration provided in step 1, steps 3-7 can be performed multiple times to perform subsequent SCG LTM.

[0212] For example, the SCG LTM process initiated by the SN without the participation of the MN (without using SRB3) is shown in FIG1F .

[0213] When the SN needs to transmit an NR RRC message to the terminal and SRB3 is not used to configure the SCG LTM in the SN, the SN initiates this process. The process includes the following steps:

[0214] Step 1: The SN initiates the process by sending a secondary node modification request (SN Modification Required) including an SN RRCReconfiguration message with SCG LTM configuration to the MN.

[0215] Step 2: The MN includes the SN RRCReconfiguration message in the RRCReconfiguration message and forwards it to the terminal.

[0216] Step 3: The terminal responds with an RRCReconfigurationComplete message including an SN RRCReconfigurationComplete message.

[0217] Step 4. If an SN RRC Response message is received from the terminal, the MN forwards it to the SN by including it in an SN Modification Confirm message.

[0218] Step 5a: If the SN indicates, the terminal performs DL synchronization with the candidate cell before receiving the cell switching command.

[0219] Step 5b: If the SN indicates, the terminal performs UL synchronization with the candidate cell before receiving the cell handover command, such as early TA acquisition.

[0220] Step 6: The terminal performs L1 measurement on the configured candidate cells according to the L1 measurement configuration in the RRCReconfiguration received in step 2, and sends an L1 measurement report to the SN. Once the L1 measurement configuration is applicable, the terminal starts performing L1 measurement.

[0221] Step 7: The SN decides to perform a cell handover to the target cell and sends the cell handover command via a MAC CE to the terminal. The terminal switches to the target cell and applies the configuration indicated by the candidate configuration index.

[0222] Step 8: The terminal sends a ULInformationTransferMRDC message to the MN, which includes an embedded RRCReconfigurationComplete message to the target cell.

[0223] Step 9: Forward the RRCReconfigurationComplete message to the SN embedded in the RRC Transfer message.

[0224] Step 10: If the terminal does not have a valid TA for the target cell, the terminal performs a random access procedure to the target cell.

[0225] Step 11: The terminal completes the SCG LTM cell handover process by sending UL transmission to the target cell.

[0226] If the terminal has performed a random access procedure in step 10, the terminal considers that the LTM execution is successfully completed when the random access procedure is successfully completed. For LTM without random access, the terminal considers that the LTM execution is successfully completed when the terminal determines that the SN has successfully received its first UL data.

[0227] Here, using the SCG LTM candidate configuration provided in step 2, steps 5-11 may be performed multiple times for subsequent SCG LTMs.

[0228] Currently, LTM only supports intra-DU and inter-DU intra-CU LTM. Support for the following research scenarios may be expanded in the future:

[0229] Inter-CU (or inter-node) LTM;

[0230] Conditional LTM (the terminal triggers LTM based on network configuration conditions).

[0231] For inter-CU LTM in non-DC scenarios, such as MCG LTM.

[0232] For inter-CU LTM in NR-DC scenarios, the following mobility scenarios need to be discussed:

[0233] Scenario 1, LTM for MCG change with SN release

[0234] Scenario 2: LTM for PSCell / SCG change with MN involvement

[0235] Among them, in scenario 2.1, the MN initiates the SCG LTM.

[0236] Scenario 2.2, SCG LTM initiated by SN.

[0237] Scenario 3, LTM for MCG with / without SCG change.

[0238] Among them, the terminal will apply the configurations of MCG and SCG at the same time when executing LTM, and an LTM candidate configuration will include the configurations of candidate PCell and candidate PSCell at the same time.

[0239] Since LTM does not involve interaction between nodes, to support LTM configuration, the present disclosure provides the following information transmission method, device, and storage medium. LTM interaction can be performed between nodes, supporting LTM configuration and improving LTM availability. Figure 2 is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in Figure 2, the present disclosure embodiment relates to an information transmission method, which includes:

[0240] Step S2101 : The third node 103 sends a first message to the first node 101 .

[0241] In some embodiments, the third node 103 may be a source secondary node (S-SN) in a dual connectivity (DC) scenario.

[0242] In some embodiments, in a DC scenario, the first node 101 may be a MN.

[0243] In some embodiments, the first message includes first information, which can be used to request LTM. The specific content of the first message and the first information will be introduced in the subsequent step S2102 and will not be introduced here for the time being.

[0244] In some embodiments, in a DC scenario, for SCG LTM with MN participation and triggered by SN, the third node 103 may send the first message to the first node 101 to start the SCG LTM. In this case, the first message may be an SN Change Required message.

[0245] In some embodiments, in a non-DC scenario, or in a DC scenario with MN participation and SCG LTM triggered by the MN, step S2101 may not be performed.

[0246] Step S2102 : The first node 101 sends a first message to the second node 102 .

[0247] In some embodiments, in a non-DC scenario, the first node 101 may be a source access network device, and the second node 102 may be a candidate access network device. In the embodiments of the present disclosure, the access network device may be a gNB, or may be replaced by an NG-RAN node, a 6G network node, or a future network node.

[0248] In some embodiments, in a DC scenario, the first node 101 may be a MN, and the second node 102 may be a candidate secondary node (C-SN).

[0249] In some embodiments, the first message includes first information, and the first information can be used to request the LTM.

[0250] In some embodiments, the first information may include but is not limited to at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; LTM indication information, LTM indication information is used to request LTM candidate configuration or update; first indication information, the first indication information is used to indicate that the second node is allowed to prepare layer 3 mobility configuration for the terminal when the configuration of LTM candidate cells is not supported; the maximum number of configurable candidate cells; a recommended candidate cell list; an LTM candidate cell identifier list; an LTM candidate configuration identifier list.

[0251] The LTM candidate cell may also be referred to as a candidate cell, which refers to a candidate serving cell of a terminal in LTM.

[0252] The LTM indication information may be used to request an LTM candidate configuration, or may be used to request replacement, update, deletion, etc. of an LTM candidate configuration, which is not limited in the present disclosure.

[0253] The name of the LTM indication information is not limited and can be interchanged with indication information, LTM request indication information, etc.

[0254] The name of the first indication information is not limited and can be interchangeable with the fallback indication information.

[0255] The configurable candidate cells may include but are not limited to configurable primary and secondary cells (PSCells).

[0256] The recommended candidate cell list may include one or more LTM candidate cells recommended by the first node 101 .

[0257] The LTM candidate cell identifier list may include one or more LTM candidate cell identifiers.

[0258] The LTM candidate configuration identifier list may include one or more LTM candidate configuration identifiers.

[0259] In some embodiments, the first message may be any of the following messages:

[0260] Handover request message;

[0261] SN Addition Request message;

[0262] SN Modification Request message;

[0263] SN change request (SN ChangeRequired) message;

[0264] The first Xn message is used to request LTM;

[0265] The first inter-node RRC message is used to request LTM.

[0266] In an example, the inter-node RRC message may be a message transmitted between nodes on the network side, which may be carried in an Xn message.

[0267] In one example, a handover request message may be sent by a source access network device to a candidate access network device, and a new information element (IE) may be added to the handover request message, such as LTM Information Setup, which includes LTM indication information (LTM Indicator), LTM configuration identifier (LTM Configuration ID), indication information for conditional switching, etc., as shown in Table 1.

[0268] Table 1

[0269] In one example, the SN Addition Request message may be sent by the MN to the C-SN, and a new IE may be added to the SN Addition Request, such as the SCG LTM Information Setup, which includes LTM indication information (LTM Indicator), the maximum number of configurable primary and secondary cells PSCell, indication information for CPAC, etc., as shown in Table 2.

[0270] Table 2

[0271] In an example, the SN Addition Request message may be sent from the MN to the C-SN. A new IE, such as SCG LTM Request Information, may be added to the SN Addition Request, as shown in Table 3.

[0272] Table 3

[0273] In one example, the SN Modification Request message may be sent from the MN to the C-SN, and a new IE may be added to the SN Modification Request, such as the SCG LTM Addition Information Modification Request, which includes the maximum number of configurable primary and secondary cells PSCell, the estimated arrival probability (Estimated Arrival Probability), SCG LTM request information, SCG LTM inter-SN execution notification, etc., as shown in Table 4.

[0274] Table 4

[0275] In one example, the SN change request (SN ChangeRequired) message can be sent by the MN to the C-SN, and a new IE can be added to the SN change request, such as the SCG LTM information request (SCG LTM Information Required), which includes a multi-target SN node list. The multi-target SN node list may include multi-target SN node items. Further, the multi-target SN node item may include a target SN node identifier, SCG LTM indication information, a configurable maximum number of primary and secondary cells PSCell, an estimated arrival probability (Estimated Arrival Probability), an SN node to SN node container, etc., as shown in Table 5.

[0276] Table 5

[0277] In one example, the first Xn message may be an Xn message newly defined in the protocol for requesting LTM.

[0278] In an example, the first inter-node RRC message may be carried in an Xn message and sent to the second node 102 .

[0279] Among them, the first inter-node RRC message can be cell group configuration information (CG-ConfigInfo), and a new message can be introduced in CG-ConfigInfo. For example, the MN candidate cell information list (ltmcandidateCellInfoListMN) contains one or more recommended candidate LTM cells, which can be represented by the latest L3 or L1 measurement results, that is, the CG-ConfigInfo contains one or more recommended candidate LTM cells and contains corresponding L1 or L3 measurement results. The following is an example:

[0280] It should be noted that some other information included in CG-ConfigInfo is not related to the present invention and is therefore not reflected in the above example.

[0281] The master eNB or gNB uses, for example, a CG-ConfigInfo message to request the SgNB or SeNB to perform certain actions, such as establishing, modifying, or releasing an SCG. This message may include additional information, such as to help the SgNB or SeNB set the SCG configuration. The CU may also use it to request the DU to perform certain actions, such as establishing or modifying an MCG or SCG. The CG-ConfigInfo message is sent from the master eNB or gNB to the candidate gNB or eNB, or from the CU to the DU.

[0282] The above description is merely an exemplary description, and the present disclosure does not limit the message type of the first message.

[0283] In some embodiments, the second node 102 receives the first message.

[0284] Step S2103: The second node 102 prepares an LTM candidate configuration for the terminal.

[0285] In some embodiments, the second node 102 prepares an LTM candidate configuration for the terminal based on the first message.

[0286] In some embodiments, the second node 102 generates an LTM candidate configuration for the terminal based on the first information.

[0287] In some embodiments, the LTM candidate configuration is the configuration portion of an RRC reconfiguration message associated with a candidate cell, for example, for LTM or subsequent CPAC. The candidate configuration can be a complete candidate configuration or an incremental configuration relative to a reference configuration.

[0288] In some embodiments, the present disclosure does not limit the scheme for configuring the LTM candidate configuration by the second node.

[0289] Step S2104: the second node 102 prepares a layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal.

[0290] In some embodiments, if the second node 102 is unable to prepare or generate an LTM candidate configuration for the terminal, and the first message includes second indication information, i.e., the first message requests both LTM and Layer 3 mobility configuration, the second node 102 may prepare or generate a Layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal. The second indication information is used to request the Layer 3 mobility configuration.

[0291] In some embodiments, the second node 102 is unable to prepare or generate an LTM candidate configuration for the terminal, and the first message includes first indication information, that is, when the second node 102 is allowed to fall back, the second node 102 prepares or generates a layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal. The first indication allows the second node to prepare or generate a layer 3 mobility configuration for the terminal when the configuration of the LTM candidate cell is not supported.

[0292] In some embodiments, the first message includes both first indication information and second indication information. The second node 102 may preferably first perform step S2102 to prepare or generate an LTM candidate configuration for the terminal, and when the LTM candidate configuration cannot be prepared for the terminal, perform step S2103 to prepare or generate a Layer 3 mobility configuration for the terminal. The first indication information is used to indicate that the second node is allowed to prepare or generate a Layer 3 mobility configuration for the terminal when configuration of an LTM candidate cell is not supported, and the second indication information is used to request a Layer 3 mobility configuration.

[0293] In some embodiments, the first message includes the first indication information and the second indication information, and the second node 102 may execute step S2103 or step S2104 based on its own decision, that is, prepare or generate an LTM candidate configuration or a layer 3 mobility configuration for the terminal.

[0294] In some embodiments, the first message includes the first indication information and the second indication information, and the second node 102 may execute step S2103 and step S2104, ie, simultaneously prepare or generate an LTM candidate configuration and a layer 3 mobility configuration for the terminal.

[0295] The above description is merely an example, and the present disclosure does not limit whether step S2103 and step S2104 are executed, and the order in which they are executed.

[0296] In some embodiments, the present disclosure does not limit the scheme of configuring layer 3 mobility configuration by the second node.

[0297] Step S2105 : The second node 102 sends a second message to the first node 101 .

[0298] In some embodiments, the second message may include but is not limited to at least one of the following:

[0299] LTM candidate configuration;

[0300] Layer 3 mobility configuration.

[0301] In some embodiments, the second message may be any of the following messages:

[0302] Handover request confirmation message;

[0303] SN add request confirmation message;

[0304] SN modification request confirmation message;

[0305] SN change request confirmation message;

[0306] The second Xn message is used to confirm the LTM request;

[0307] The second inter-node RRC message is used to confirm the LTM request.

[0308] In some embodiments, the second message may include LTM indication information, where the LTM indication information is used to indicate that the second node has prepared or generated an LTM candidate configuration for the terminal.

[0309] In some embodiments, the second message may include layer 3 mobility indication information, where the layer 3 mobility indication information is used to indicate that the second node has prepared or generated a layer 3 mobility configuration for the terminal.

[0310] The above is merely an exemplary description. The second message may also include other information, which is not limited in this disclosure.

[0311] In some embodiments, the first node 101 receives the second message. The second message may include the LTM candidate configuration and / or the layer 3 mobility configuration prepared or generated by the second node 102 for the terminal.

[0312] Step S2106 : The second node 102 sends a third message to the first node 101 .

[0313] In some embodiments, the second node 102 may send a third message to the first node 101 after the LTM is completed.

[0314] In some embodiments, the first node 101 receives the third message.

[0315] In some embodiments, the third message is used to notify the first node 101 that the LTM has been successfully executed.

[0316] In some embodiments, when the third message includes LTM indication information, the third message is used to indicate that the change of the terminal service node is triggered by the LTM.

[0317] In some embodiments, the third message may be any of the following messages:

[0318] Handover Success message;

[0319] SN added successfully message;

[0320] SN modification success message;

[0321] SN change success message;

[0322] The third Xn message is used to indicate that the LTM has been successfully executed;

[0323] The third inter-node RRC message is used to indicate that the LTM has been successfully executed.

[0324] In an example, the third message is a handover success message, to which LTM indication information may be added, as shown in Table 6, for example.

[0325] Table 6

[0326] The above description is merely an exemplary description, and the present disclosure does not limit the type of the third message and the scheme of the LTM indication information added to the third message.

[0327] Step S2107 : The first node 101 sends a fourth message to the second node 102 .

[0328] In some embodiments, the fourth message is used to cancel the LTM candidate configuration prepared or generated by the second node 102 for the terminal.

[0329] In some embodiments, the fourth message may include, but is not limited to, at least one of the following:

[0330] LTM candidate cell identifier;

[0331] LTM candidate configuration identifier;

[0332] LTM candidate cell identifier list;

[0333] LTM candidate configuration identifier list;

[0334] LTM cancels all instructions.

[0335] In some embodiments, the fourth message may carry LTM all cancellation indication information, where the LTM all cancellation indication information is used to indicate the cancellation of all LTM candidate configurations prepared or generated by the second node 102 for the terminal.

[0336] In some embodiments, the fourth message may include LTM partial cancellation indication information, which may be used to indicate the cancellation of part of the LTM candidate configuration prepared or generated by the second node 102 for the terminal. The second node 102 may determine the LTM candidate configuration to be cancelled based on a predefined method, such as a protocol agreement, or the second node 102 may determine the LTM candidate configuration to be cancelled based on at least one of the LTM candidate cell identifier, LTM candidate configuration identifier, LTM candidate cell identifier list, and LTM candidate configuration identifier list included in the fourth message.

[0337] In some embodiments, the fourth message may be any of the following messages:

[0338] Handover Cancel message;

[0339] The fourth Xn message is used to cancel the LTM candidate configuration;

[0340] The fourth inter-node RRC message is used to cancel the LTM candidate configuration.

[0341] In one example, the fourth message is a Handover Cancel message, to which a list of candidate cells to be cancelled for LTM may be added, as shown in Table 7.

[0342] Table 7

[0343] The above description is merely an exemplary description, and all solutions in which the first node 101 cancels the LTM candidate configuration prepared by the second node 102 for the terminal through the fourth message should fall within the protection scope of the present disclosure.

[0344] In some embodiments, the second node 102 receives the fourth message.

[0345] In some embodiments, the second node 102 cancels the LTM candidate configuration prepared for the terminal based on the fourth message.

[0346] In an example, the fourth message includes an LTM candidate cell identifier, and the second node 102 may cancel the LTM candidate configuration corresponding to the LTM candidate cell indicated by the fourth message.

[0347] In an example, the fourth message includes an LTM candidate configuration identifier, and the second node 102 may cancel the LTM candidate configuration indicated by the fourth message.

[0348] In an example, the fourth message includes a list of LTM candidate cell identifiers, and the second node 102 may cancel the LTM candidate configuration corresponding to each LTM candidate cell in the list of LTM candidate cell identifiers.

[0349] In an example, the fourth message includes a list of LTM candidate configuration identifiers, and the second node 102 may cancel each LTM candidate configuration in the list of LTM candidate configuration identifiers.

[0350] In an example, the fourth message includes an LTM candidate cell identifier and an LTM candidate configuration identifier, and the second node 102 cancels the LTM candidate cell and the LTM candidate configuration corresponding to the LTM candidate configuration identifier indicated by the fourth message.

[0351] In an example, the fourth message includes an LTM candidate cell identifier list and an LTM candidate configuration identifier list. The second node 102 cancels each LTM candidate cell in the LTM candidate cell identifier list and each LTM candidate configuration identifier in the LTM candidate configuration identifier list.

[0352] The above description is merely exemplary, and all solutions in which the second node 102 cancels the LTM candidate configuration based on the fourth message should fall within the protection scope of the present disclosure.

[0353] Step S2108: Receive a fifth message sent by the second node 102 after preparing the LTM candidate configuration for the terminal.

[0354] In some embodiments, the fifth message is used to cancel the LTM candidate configuration prepared by the second node 102 for the terminal.

[0355] In some embodiments, the second node 102 may also proactively cancel the LTM candidate configuration.

[0356] In some embodiments, the fifth message may include, but is not limited to, at least one of the following:

[0357] LTM candidate cell identifier;

[0358] LTM candidate configuration identifier;

[0359] LTM candidate cell identifier list;

[0360] LTM candidate configuration identifier list;

[0361] LTM cancels all instructions.

[0362] In some embodiments, the fifth message may carry LTM all cancellation indication information, where the LTM all cancellation indication information is used to indicate the cancellation of all LTM candidate configurations prepared by the second node 102 for the terminal.

[0363] In some embodiments, the fifth message may include LTM partial cancellation indication information, which may be used to indicate the cancellation of a portion of the LTM candidate configurations prepared by the second node 102 for the terminal. The first node 101 may determine the LTM candidate configuration to be cancelled based on a predefined method, such as a protocol agreement. Alternatively, the first node 101 determines the LTM candidate configuration to be cancelled based on at least one of the LTM candidate cell identifier, the LTM candidate configuration identifier, the LTM candidate cell identifier list, and the LTM candidate configuration identifier list included in the fifth message.

[0364] In some embodiments, the fifth message may be any of the following messages:

[0365] Conditional Handover Cancel message;

[0366] The fifth Xn message is used to cancel the conditional switching of the LTM candidate configuration;

[0367] The fifth inter-node RRC message is used to cancel the conditional switching of the LTM candidate configuration.

[0368] In an example, the fifth message is a Conditional Handover Cancel message, to which a list of candidate cells to be cancelled for LTM may be added, as shown in Table 8, for example.

[0369] Table 8

[0370] The above description is merely exemplary. The second node 102 notifies the first node 101 through the fifth message that the second node 102 cancels the LTM candidate configuration prepared for the terminal should all fall within the protection scope of the present disclosure.

[0371] In some embodiments, the solution in which the second node 102 cancels the LTM candidate configuration is similar to the solution in which the second node 102 cancels the LTM candidate configuration based on the fourth message, and is not described again here.

[0372] Step S2109 : The second node 102 sends a seventh message to the first node 101 .

[0373] In some embodiments, the seventh message may be used to request the first node 101 to initiate modification of the LTM candidate configuration.

[0374] In some embodiments, after receiving the seventh message, the first node 101 sends the sixth message to the second node. The specific implementation process is referred to the subsequent step S2109 and will not be described here.

[0375] In some embodiments, the second node 102 may request the first node 101 to initiate modification of the LTM candidate configuration.

[0376] In some embodiments, the seventh message may include, but is not limited to, at least one of the following:

[0377] LTM indication information;

[0378] LTM candidate cell identifier;

[0379] LTM candidate configuration identifier;

[0380] LTM candidate cell identifier list;

[0381] List of LTM candidate configuration identifiers.

[0382] In some embodiments, the seventh message may be any of the following messages:

[0383] SN Modification Required message;

[0384] The seventh Xn message is used to request to initiate modification of the LTM candidate configuration;

[0385] The seventh inter-node RRC message is used to request to initiate modification of the LTM candidate configuration.

[0386] In an example, the seventh message includes LTM indication information, and the second node 102 may modify one or more LTM candidate configurations prepared by itself for the terminal based on the LTM indication information.

[0387] In an example, the seventh message includes an LTM candidate cell identifier, and the second node 102 may modify the LTM candidate configuration corresponding to the LTM candidate cell indicated by the LTM candidate cell identifier.

[0388] In an example, the seventh message includes an LTM candidate configuration identifier, and the second node 102 may modify the LTM candidate configuration corresponding to the LTM candidate configuration identifier.

[0389] In an example, the seventh message includes a list of LTM candidate cell identifiers, and the second node 102 may modify the LTM candidate configuration corresponding to each LTM candidate message in the list of LTM candidate cell identifiers.

[0390] In an example, the seventh message includes a list of LTM candidate configuration identifiers, and the second node 102 may modify each LTM candidate configuration included in the list of LTM candidate configuration identifiers.

[0391] In an example, the seventh message includes LTM indication information and an LTM candidate cell identifier, and the second node 102 may modify the LTM candidate configuration corresponding to the LTM candidate cell indicated by the LTM candidate cell identifier.

[0392] In an example, the seventh message includes LTM indication information and an LTM candidate configuration identifier, and the second node 102 may modify the LTM candidate configuration corresponding to the LTM candidate configuration identifier.

[0393] In an example, the seventh message includes LTM indication information, an LTM candidate cell identifier, and an LTM candidate configuration identifier. The second node 102 may modify the LTM candidate configuration corresponding to the LTM candidate cell identifier and the LTM candidate configuration identifier.

[0394] In an example, in the LTM candidate cell identifier list and the LTM candidate configuration identifier list in the seventh message, the second node 102 modifies the LTM candidate configuration corresponding to each LTM candidate cell identifier (from the LTM candidate cell identifier list) and each LTM candidate configuration identifier (from the LTM candidate configuration identifier list).

[0395] The above description is merely an exemplary description, and all solutions in which the second node 102 modifies the LTM candidate configuration based on the seventh message should fall within the protection scope of the present disclosure.

[0396] Step S2110 : The first node 101 sends a sixth message to the second node 102 .

[0397] In some embodiments, the sixth message may be used to request modification of the LTM candidate configuration prepared by the second node 102 for the terminal.

[0398] In some embodiments, the first node 101 may proactively initiate modification of the LTM candidate configuration, in which case the above step S2109 may not be performed.

[0399] In some embodiments, the first node 101 may initiate a modification of the LTM candidate configuration based on a request from the second node 102 , and step S2109 may be executed at this time.

[0400] In some embodiments, the sixth message may include but is not limited to at least one of the following:

[0401] LTM indication information;

[0402] LTM candidate cell identifier;

[0403] LTM candidate configuration identifier;

[0404] LTM candidate cell identifier list;

[0405] List of LTM candidate configuration identifiers.

[0406] In some embodiments, the sixth message may be any of the following messages:

[0407] SN Modification Request message;

[0408] The sixth Xn message is used to modify the LTM candidate configuration;

[0409] The sixth inter-node RRC message is used for modifying the LTM candidate configuration.

[0410] In one example, the sixth message is an SN modification request (SN ModificationRequest) message, to which an SCG LTM additional information modification request can be added. Further, it can include the configurable maximum number of primary and secondary cells PSCell, estimated arrival probability (Estimated Arrival Probability), SCG LTM request information, SCG LTM inter-SN execution notification, etc., as shown in Table 9.

[0411] Table 9

[0412] The above description is merely exemplary, and all solutions in which the first node 101 modifies the LTM candidate configuration prepared by the second node 102 for the terminal through the sixth message should fall within the protection scope of the present disclosure.

[0413] In some embodiments, the scheme in which the second node 102 modifies the LTM candidate configuration prepared for the terminal is similar to the above-mentioned scheme in which the second node 102 modifies the LTM candidate configuration prepared for the terminal based on the seventh message, and is not repeated here.

[0414] Step S2111 : The first node 101 sends an eighth message to the third node 103 .

[0415] In some embodiments, the third node 103 may include but is not limited to a source SN in a dual connectivity scenario.

[0416] In some embodiments, after receiving the third message sent by the second node 102, the first node 101 sends an eighth message to the third node. The third message is used to indicate that the terminal has successfully accessed the second node 102, and the eighth message can be used to release resources of the third node 103. This avoids resource waste caused by the terminal still occupying the resources of the third node 103 (S-SN) for a long time when the terminal has already accessed the second node 102.

[0417] In some embodiments, the eighth message may be any of the following messages:

[0418] SN release request (SNReleaseRequest) message;

[0419] The eighth Xn message is used to release SN resources;

[0420] The eighth inter-node RRC message is used to release SN resources.

[0421] In some embodiments, the eighth message may include, but is not limited to, at least one of the following:

[0422] LTM indication information;

[0423] Release reason indication information.

[0424] Exemplarily, when the eighth message includes LTM indication information, the eighth message is further used to inform the third node 103 that the change of the terminal service node is triggered by LTM.

[0425] Exemplarily, the release cause indication information may be used to indicate the SCG LTM, that is, the release cause is the occurrence of the SCG LTM in which the MN participates (triggered by the MN or the SN).

[0426] In some embodiments, the third node 103 receives the eighth message.

[0427] In some embodiments, the third node 103 releases the LTM candidate configuration resources corresponding to the terminal based on the eighth message.

[0428] Step S2112 : The first node 101 sends a ninth message to the third node 103 .

[0429] In some embodiments, after executing step S2101, if the first node 101 receives the second message sent by the second node 102, the first node 101 may send the ninth message to the third node 103. The second message includes the LTM candidate configuration.

[0430] In some embodiments, the ninth message may be used for SN change confirmation.

[0431] In some embodiments, the ninth message may include but is not limited to at least one of the following:

[0432] A second node identifier of an LTM candidate configuration is prepared for the terminal;

[0433] Secondary cell group SCG LTM candidate cell identifier;

[0434] SCG LTM candidate cell configuration identifier.

[0435] In some embodiments, the ninth message may be any of the following messages:

[0436] SN Change Confirm message;

[0437] The ninth Xn message is used to confirm the SN change;

[0438] The ninth inter-node RRC message is used for SN change confirmation.

[0439] In one example, the ninth message is an SN change confirmation (SNChangeConfirm) message, to which an SCG LTM information confirmation information unit can be added. Further, the SCG LTM information confirmation information unit can include a multi-target SN node list, and the multi-target SN node list can further include a multi-target SN node item. Further, the multi-target SN node item can include a target SN node identifier, a candidate primary and secondary cell PSCell list, and the candidate primary and secondary cell PSCell list can further include a candidate cell item, and the candidate cell item can also include a PSCell identifier, as shown in Table 10.

[0440] Table 10

[0441] In some embodiments, the first node 101 may provide at least one of the second node identifier for preparing the LTM candidate configuration for the terminal, the SCG LTM candidate cell identifier, and the SCG LTM candidate configuration identifier to the third node 103 so that the third node 103 determines that the SCG LTM is completed.

[0442] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0443] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0444] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0445] In some embodiments, terms such as "certain", "preseted", "preset", "setting", "indicated", "a certain", "any", "first", and "designated" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0446] In some embodiments, the information transmission method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2112. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, steps S2101+S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, steps S2103+S2104 can be implemented as an independent embodiment, step S2105 can be implemented as an independent embodiment, step S2106 can be implemented as an independent embodiment, step S2107 can be implemented as an independent embodiment, and step S2108 can be implemented as an independent embodiment. As an independent embodiment, step S2109 can be implemented as an independent embodiment, step S2107+S2109 can be implemented as an independent embodiment, step S2110 can be implemented as an independent embodiment, step S2111 can be implemented as an independent embodiment, step S2112 can be implemented as an independent embodiment, step S2101+S2111 can be implemented as an independent embodiment, step S2101+S2112 can be implemented as an independent embodiment, and steps S2101 to S2112 can be implemented as independent embodiments, but are not limited thereto.

[0447] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, in a non-DC scenario, or in a DC scenario with a MN participating and SCG LTM triggered by the MN, step S2101 may not be performed.

[0448] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second node 102 receives the first message from another execution subject, step S2102 may not be executed.

[0449] In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node 102 is unable to prepare or generate an LTM candidate configuration for the terminal or if the second node 102 prepares or generates a Layer 3 mobility configuration for the terminal based on its own policy, step S2103 may not be performed.

[0450] In some embodiments, step S2104 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second node 102 prepares or generates an LTM candidate configuration for the terminal, step S2104 may not be performed.

[0451] In some embodiments, step S2103 and step S2104 can be performed selectively.

[0452] In some embodiments, both step S2103 and step S2104 may be performed.

[0453] In some embodiments, step S2105 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node 101 obtains the LTM candidate configuration and / or the layer 3 mobility configuration from other execution entities, step S2105 may not be performed.

[0454] In some embodiments, step S2106 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the first node receives the third message from another execution entity or the change of the first node's default terminal service node is triggered by the LTM, step S2106 may not be performed.

[0455] In some embodiments, step S2107 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second node proactively initiates cancellation of the LTM candidate configuration, step S2107 may not be performed.

[0456] In some embodiments, step S2108 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node initiates cancellation of the LTM candidate configuration, step S2108 may not be performed.

[0457] In some embodiments, step S2107 and step S2108 can be performed selectively.

[0458] In some embodiments, step S2109 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node 101 proactively initiates modification of the LTM candidate configuration, step S2109 may not be performed.

[0459] In some embodiments, step S2110 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the LTM candidate configuration does not need to be modified, step S2110 may not be performed.

[0460] In some embodiments, step S2111 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the third node has released resources, step S2111 may not be performed.

[0461] In some embodiments, step S2112 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, in a non-DC scenario, or in a DC scenario with a MN participating and SCG LTM triggered by the MN, step S2111 may not be performed.

[0462] In some embodiments, when both step S2103 and step S2104 are executed, the execution order is not limited.

[0463] In some embodiments, the execution order of steps S2101 to S2112 is not limited. For example, nodes may execute the preceding steps after executing one or more subsequent steps based on network implementation. This disclosure does not limit this.

[0464] In some embodiments, steps S2101 to S2112 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0465] In the above embodiment, LTM interaction can be performed between nodes, and LTM configuration is supported, thereby improving the availability of LTM.

[0466] FIG3A is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information transmission method, which can be executed by a first node 101. The method includes:

[0467] Step S3101, obtain the first message.

[0468] In some embodiments, the first node 101 may obtain the first message from the third node 103, but is not limited thereto. The first node 101 may also receive the first message sent by other entities.

[0469] In some embodiments, the first node 101 obtains a first message determined according to a predefined rule.

[0470] In some embodiments, the first node 101 performs processing to obtain the first message.

[0471] In some embodiments, step S3101 is omitted, the first node 101 autonomously implements the function indicated by the first message, or the first node 101 obtains the first message based on predefined rules or protocol agreements, or the above functions are default or default.

[0472] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0473] Step S3102, sending the first message.

[0474] In some embodiments, the first node 101 sends a first message to the second node 102 .

[0475] In some embodiments, the second node 102 receives the first message.

[0476] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0477] Step S3103, obtain the second message.

[0478] In some embodiments, the second message may include but is not limited to at least one of the following:

[0479] LTM candidate configuration;

[0480] Layer 3 mobility configuration.

[0481] In some embodiments, the first node 102 may obtain the second message from the second node 102, but is not limited thereto. The first node 102 may also receive the second message sent by other entities.

[0482] In some embodiments, the first node 102 obtains the second message determined according to a predefined rule.

[0483] In some embodiments, the first node 102 performs processing to obtain the second message.

[0484] In some embodiments, step S3103 is omitted, the first node 102 autonomously implements the function indicated by the second message, or the first node 102 obtains the second message based on predefined rules or protocol agreements, or the above functions are default or default.

[0485] In some embodiments, the optional implementation of step S3103 can refer to the optional implementation of step S2105 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0486] Step S3104, obtain the third message.

[0487] In some embodiments, the third message is used to notify the first node 101 that the LTM has been successfully executed.

[0488] In some embodiments, the first node 102 may obtain the third message from the second node 102, but is not limited thereto. The first node 102 may also receive the third message sent by other entities.

[0489] In some embodiments, the first node 102 obtains the third message determined according to a predefined rule.

[0490] In some embodiments, the first node 102 performs processing to obtain the third message.

[0491] In some embodiments, step S3104 is omitted, the first node 102 autonomously implements the function indicated by the third message, or the first node 102 obtains the third message based on predefined rules or protocol agreements, or the above functions are default or default.

[0492] In some embodiments, the optional implementation of step S3104 can refer to the optional implementation of step S2106 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0493] Step S3105: Send the fourth message.

[0494] In some embodiments, the fourth message is used to cancel the LTM candidate configuration prepared by the second node 102 for the terminal.

[0495] In some embodiments, the first node 101 sends a fourth message to the second node 102 .

[0496] In some embodiments, the second node 102 receives the fourth message.

[0497] In some embodiments, the optional implementation of step S3105 can refer to the optional implementation of step S2107 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0498] Step S3106, obtain the fifth message.

[0499] In some embodiments, the fifth message is used to cancel the LTM candidate configuration prepared by the second node 102 for the terminal.

[0500] In some embodiments, the first node 102 may obtain the fifth message from the second node 102, but is not limited thereto. The first node 102 may also receive the fifth message sent by other entities.

[0501] In some embodiments, the first node 102 obtains the fifth message determined according to a predefined rule.

[0502] In some embodiments, the first node 102 performs processing to obtain the fifth message.

[0503] In some embodiments, step S3106 is omitted, the first node 102 autonomously implements the function indicated by the fifth message, or the first node 102 obtains the fifth message based on predefined rules or protocol agreements, or the above functions are default or default.

[0504] In some embodiments, the optional implementation of step S3106 can refer to the optional implementation of step S2108 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0505] Step S3107, obtain the seventh message.

[0506] In some embodiments, the seventh message may be used to request the first node 101 to initiate modification of the LTM candidate configuration.

[0507] In some embodiments, the first node 102 may obtain the seventh message from the second node 102, but is not limited thereto. The first node 102 may also receive the seventh message sent by other entities.

[0508] In some embodiments, the first node 102 obtains the seventh message determined according to a predefined rule.

[0509] In some embodiments, the first node 102 performs processing to obtain the seventh message.

[0510] In some embodiments, step S3107 is omitted, the first node 102 autonomously implements the function indicated by the seventh message, or the first node 102 obtains the seventh message based on predefined rules or protocol agreements, or the above functions are default or default.

[0511] In some embodiments, the optional implementation of step S3106 can refer to the optional implementation of step S2109 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0512] Step S3108, sending the sixth message.

[0513] In some embodiments, the sixth message may be used to request modification of the LTM candidate configuration prepared by the second node 102 for the terminal.

[0514] In some embodiments, the first node 101 sends a sixth message to the second node 102 .

[0515] In some embodiments, the second node 102 receives the sixth message.

[0516] In some embodiments, the optional implementation of step S3108 can refer to the optional implementation of step S2110 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0517] Step S3109, sending the eighth message.

[0518] In some embodiments, the eighth message may be used to release resources of the third node 103 .

[0519] In some embodiments, the first node 101 sends an eighth message to the third node 103 .

[0520] In some embodiments, the third node 103 receives the eighth message.

[0521] In some embodiments, the optional implementation of step S3109 can refer to the optional implementation of step S2111 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0522] Step S3110, sending the ninth message.

[0523] In some embodiments, the ninth message may include but is not limited to at least one of the following:

[0524] A second node identifier of an LTM candidate configuration is prepared for the terminal;

[0525] Secondary cell group SCG LTM candidate cell identifier;

[0526] SCG LTM candidate cell configuration identifier.

[0527] In some embodiments, the first node 101 sends a ninth message to the third node 103 .

[0528] In some embodiments, the third node 103 receives the ninth message.

[0529] In some embodiments, the optional implementation of step S3110 can refer to the optional implementation of step S2112 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0530] In some embodiments, steps S3101 to S3110 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0531] In some embodiments, the execution order of steps S3101 to S3110 is not limited.

[0532] In the above embodiment, the first node can request LTM candidate configuration, modify or cancel the LTM candidate configuration, thereby achieving LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM.

[0533] FIG3B is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to an information transmission method, which can be executed by the second node 102. The method includes:

[0534] Step S3201, obtain the first message.

[0535] In some embodiments, the second node 102 may obtain the first message from the first node 101, but is not limited thereto. The second node 102 may also receive the first message sent by other entities.

[0536] In some embodiments, the second node 102 obtains the first message determined according to a predefined rule.

[0537] In some embodiments, the second node 102 performs processing to obtain the first message.

[0538] In some embodiments, step S3201 is omitted, the second node 102 autonomously implements the function indicated by the first message, or the second node 102 obtains the first message based on predefined rules or protocol agreements, or the above functions are default or default.

[0539] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2102 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0540] Step S3202: Prepare (or generate) an LTM candidate configuration for the terminal.

[0541] In some embodiments, the optional implementation of step S3202 can refer to the optional implementation of step S2103 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0542] Step S3203: prepare (or generate) a layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal.

[0543] In some embodiments, the optional implementation of step S3203 can refer to the optional implementation of step S2104 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0544] Step S3204, sending the second message.

[0545] In some embodiments, the second message may include but is not limited to at least one of the following:

[0546] LTM candidate configuration;

[0547] Layer 3 mobility configuration.

[0548] In some embodiments, the second node 102 sends a second message to the first node 101 .

[0549] In some embodiments, the first node 101 receives the second message.

[0550] In some embodiments, the optional implementation of step S3204 can refer to the optional implementation of step S2105 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0551] Step S3205: Send the third message.

[0552] In some embodiments, the third message is used to notify the first node 101 that the LTM has been successfully executed.

[0553] In some embodiments, the second node 102 sends a third message to the first node 101 .

[0554] In some embodiments, the first node 101 receives the third message.

[0555] In some embodiments, the optional implementation of step S3205 can refer to the optional implementation of step S2106 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0556] Step S3206, obtain the fourth message.

[0557] In some embodiments, the fourth message is used to cancel the LTM candidate configuration prepared by the second node 102 for the terminal.

[0558] In some embodiments, the second node 102 may obtain the fourth message from the first node 101 , but is not limited thereto. The second node 102 may also receive the fourth message sent by other entities.

[0559] In some embodiments, the second node 102 obtains the fourth message determined according to a predefined rule.

[0560] In some embodiments, the second node 102 performs processing to obtain the fourth message.

[0561] In some embodiments, step S3206 is omitted, the second node 102 autonomously implements the function indicated by the fourth message, or the second node 102 obtains the fourth message based on predefined rules or protocol agreements, or the above functions are default or default.

[0562] In some embodiments, the optional implementation of step S3206 can refer to the optional implementation of step S2107 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0563] Step S3207, sending the fifth message.

[0564] In some embodiments, the fifth message is used to cancel the LTM candidate configuration prepared by the second node 102 for the terminal.

[0565] In some embodiments, the second node 102 sends a fifth message to the first node 101 .

[0566] In some embodiments, the first node 101 receives the fifth message.

[0567] In some embodiments, the optional implementation of step S3207 can refer to the optional implementation of step S2108 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0568] Step S3208, sending the seventh message.

[0569] In some embodiments, the seventh message may be used to request the first node 101 to initiate modification of the LTM candidate configuration.

[0570] In some embodiments, the second node 102 sends a seventh message to the first node 101 .

[0571] In some embodiments, the first node 101 receives the seventh message.

[0572] In some embodiments, the optional implementation of step S3208 can refer to the optional implementation of step S2109 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0573] Step S3209, obtain the sixth message.

[0574] In some embodiments, the sixth message may be used to request modification of the LTM candidate configuration prepared by the second node 102 for the terminal.

[0575] In some embodiments, the second node 102 may obtain the sixth message from the first node 101 , but is not limited thereto. The second node 102 may also receive the sixth message sent by other entities.

[0576] In some embodiments, the second node 102 obtains the sixth message determined according to a predefined rule.

[0577] In some embodiments, the second node 102 performs processing to obtain the sixth message.

[0578] In some embodiments, step S3209 is omitted, the second node 102 autonomously implements the function indicated by the sixth message, or the second node 102 obtains the sixth message based on predefined rules or protocol agreements, or the above functions are default or default.

[0579] In some embodiments, the optional implementation of step S3209 can refer to the optional implementation of step S2110 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0580] In some embodiments, steps S3201 to S3209 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0581] In some embodiments, the execution order of steps S3201 to S3209 is not limited.

[0582] In the above embodiment, the second node can prepare LTM candidate configuration for the terminal based on the request of the first node, and can also modify, cancel, etc. the LTM candidate configuration, thereby realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM.

[0583] FIG3C is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to an information transmission method, which can be executed by the third node 103. The method includes:

[0584] Step S3301, sending the first message.

[0585] In some embodiments, the first message includes first information, and the first information can be used to request the LTM.

[0586] In some embodiments, the third node 103 sends a first message to the first node 101 .

[0587] In some embodiments, the first node 101 receives the first message.

[0588] In some embodiments, the optional implementation of step S3301 can refer to the optional implementation of step S2101 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0589] Step S3302, obtain the eighth message.

[0590] In some embodiments, the eighth message may be used to release resources of the third node 103 .

[0591] In some embodiments, the third node 103 may obtain the eighth message from the first node 101, but is not limited thereto. The third node 103 may also receive the eighth message sent by other entities.

[0592] In some embodiments, the third node 103 obtains the eighth message determined according to a predefined rule.

[0593] In some embodiments, the third node 103 performs processing to obtain the eighth message.

[0594] In some embodiments, step S3302 is omitted, the third node 103 autonomously implements the function indicated by the eighth message, or the third node 103 obtains the eighth message based on predefined rules or protocol agreements, or the above functions are default or default.

[0595] In some embodiments, the optional implementation of step S3302 can refer to the optional implementation of step S2111 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0596] Step S3303, obtain the ninth message.

[0597] In some embodiments, the ninth message may include but is not limited to at least one of the following:

[0598] A second node identifier of an LTM candidate configuration is prepared for the terminal;

[0599] Secondary cell group SCG LTM candidate cell identifier;

[0600] SCG LTM candidate cell configuration identifier.

[0601] In some embodiments, the third node 103 may obtain the ninth message from the first node 101, but is not limited thereto. The third node 103 may also receive the ninth message sent by other entities.

[0602] In some embodiments, the third node 103 obtains a ninth message determined according to a predefined rule.

[0603] In some embodiments, the third node 103 performs processing to obtain the ninth message.

[0604] In some embodiments, step S3303 is omitted, the third node 103 autonomously implements the function indicated by the ninth message, or the third node 103 obtains the ninth message based on predefined rules or protocol agreements, or the above functions are default or default.

[0605] In some embodiments, the optional implementation of step S3303 can refer to the optional implementation of step S2112 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0606] In some embodiments, steps S3301 to S3303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0607] In some embodiments, the execution order of steps S3301 to S3303 is not limited.

[0608] In the above embodiment, in the SCG LTM process in which the MN participates and is triggered by the SN, LTM interaction can be achieved between nodes, thereby supporting the purpose of LTM configuration and improving the availability of LTM.

[0609] The above process is further illustrated below with examples.

[0610] In an embodiment of the present disclosure, during the LTM preparation process, the service node (first node) of the terminal carries LTM indication information in the preparation request message sent to the candidate node (second node), and the LTM indication information can be used to indicate that the request message is used to request the candidate node to prepare LTM for the terminal.

[0611] In some embodiments, during the LTM preparation process, the service node of the terminal carries indication information (first indication information) of LTM fallback L3 mobility in the preparation request message sent to the candidate node, which is used to indicate that the request message is used to request the candidate node to prepare LTM for the terminal. When the candidate node refuses to prepare LTM for the terminal, the candidate node can choose to generate layer 3 (L3) mobility-related configurations for the terminal.

[0612] In some embodiments, in LTM, the serving node includes a list of LTM candidate cells to be canceled in a cancel message sent to the candidate node, indicating that the message is used to notify the candidate node to cancel the prepared LTM. The candidate node may also include a list of LTM candidate cells to be canceled in a cancel message sent to the source base station, indicating that the prepared LTM is to be canceled.

[0613] Among them, the LTM indication information in the embodiment of the present disclosure can be the indication information corresponding to the LTM triggered by the network, or it can be the indication information corresponding to the LTM (Conditional LTM, CLTM) triggered by the terminal based on conditions. Based on the above LTM indication information, the network side can prepare or generate LTM and / or CLTM for the terminal.

[0614] In some embodiments, during the configuration process of LTM, that is, in the corresponding switching request / SN addition (modification, change) request message (first message), LTM indication information may be included to indicate that the first node requests the second node to prepare LTM configuration for the terminal. After receiving this request message, the second node sends a corresponding confirmation message (second message) to the first node, which may also include LTM indication information to indicate that the second node confirms the LTM configuration prepared for the terminal.

[0615] In addition to the LTM indication information, the first node may also carry indication information (first indication information) of LTM fallback to L3 mobility in the request message, and the second node may also carry indication information of LTM fallback to L3 mobility in the feedback message.

[0616] After performing the LTM configuration, the first node may initiate an LTM configuration deletion process, or may include LTM indication information in a corresponding handover cancel / SN release (modification) request message (fourth message / sixth message), indicating that the first node requests the second node to delete the corresponding LTM configuration. The second node may also initiate a corresponding deletion request (fifth message / seventh message), which carries the LTM indication information.

[0617] The LTM indication information can be implemented in the following ways:

[0618] Solution 1: Introduce new Xn messages for LTM preparation and configuration update deletion.

[0619] Solution 2: Include parameters and information elements for LTM in the existing Xn message used for handover preparation and PSCell addition and change, indicating that the message is related to LTM configuration. For details, please refer to Tables 1 to 10 above.

[0620] Solution 3: Reuse the information in the existing Xn message used for handover configuration (such as CHO configuration) and PSCell addition and change configuration (such as CPAC configuration) in the LTM configuration and update process, and add 1-bit indication information to indicate that this information is used for LTM.

[0621] Exemplarily, 1 bit of indication information may be used to indicate that the entire Xn message is used for LTM configuration and update.

[0622] Exemplarily, the 1-bit indication information can also be indicated separately for each candidate node or candidate cell. This request message is used to request the second node to prepare mobility configuration for the terminal, which includes candidate cells 1, 2, and 3. Candidate cell 3 is associated with the LTM indication information. Therefore, the second node needs to prepare L3 mobility configuration associated with candidate cells 1 and 2, and LTM configuration associated with candidate cell 3 for the terminal.

[0623] In the non-DC scenario, the first node is the source gNB and the second node is the candidate gNB. The information transmission process is shown in FIG4A and includes the following steps:

[0624] In step S4100, the terminal sends a measurement report to the source gNB. The source gNB decides to configure LTM and starts LTM preparation.

[0625] In step S4101, the source gNB sends a first message (e.g., a Handover Request message or a new Xn message, such as an LTM Request message) to the candidate gNB, where the first message includes first information, and the first information is used to request LTM.

[0626] In the embodiments of this disclosure, a candidate gNB may also be referred to as a target gNB (a target gNB is a serving gNB that a terminal accesses after performing a cell handover and is one of the candidate gNBs). The gNB may be replaced by an NG-RAN node, a 6G network node, or a node in a future network, and is not limited to a gNB. A candidate cell may also be referred to as a target cell.

[0627] In some embodiments, the first information may include an LTM candidate cell identifier, which is used to indicate a candidate cell of the LTM, such as a target cell global identifier (Target Cell Global ID), and may also include an LTM candidate configuration identifier.

[0628] In some embodiments, the first information may include LTM indication information, where the LTM indication information is used to instruct the source gNB to request the candidate gNB to prepare LTM configuration and / or related resources for the terminal.

[0629] Exemplarily, LTM indication information may be included in the first message. If the first message includes this indication information, it indicates that the first message is used for preparation of MCG LTM.

[0630] Exemplarily, the LTM indication information can be of an enumeration type, for example, true. When the LTM indication information is true, it indicates that the first message is used to request LTM. For example, the first message is a handover request message, which includes a Target Cell Global ID. The first message is used to request the candidate gNB to configure LTM for the cell corresponding to the Target Cell Global ID.

[0631] Exemplarily, the LTM indication information may also be used for initial LTM (LTM-initiation) or LTM replacement (LTM-replace).

[0632] For example, if the LTM indication information indicates an initial LTM, the candidate gNB is requested to prepare or generate an LTM for the terminal. The candidate cell corresponding to the LTM can be indicated by the LTM candidate cell identifier.

[0633] For another example, if the LTM indication information indicates LTM replacement, the first information also includes the Xn interface terminal identifier (XnAP ID) assigned by the candidate gNB to the terminal. The candidate gNB should delete the LTM candidate configuration corresponding to this XnAP ID and LTM candidate cell identifier.

[0634] Accordingly, if the LTM indication information indicates LTM replacement / update, but the candidate gNB has not prepared LTM for the terminal indicated by this XnAP ID, or the LTM candidate cell identifier is not prepared for the terminal-related signaling connection, the candidate gNB should reject the process using the H message (e.g., handover preparation failure message), as shown in Figure 4B.

[0635] In some embodiments, if the candidate gNB refuses to configure the LTM corresponding to the LTM candidate cell for this terminal, the candidate gNB can prepare the L3 mobility configuration and resources corresponding to this LTM candidate cell for this terminal, where L3 mobility includes switching and CHO.

[0636] Exemplarily, the first information includes first indication information (also referred to as fallback indication information), and the first indication information is used to indicate that the candidate gNB is allowed to prepare or generate L3 mobility for the terminal when the configuration of the LTM candidate cell is not supported. If the candidate gNB refuses to configure the LTM corresponding to the LTM candidate cell for this UE, the candidate gNB may prepare the L3 mobility configuration and resources corresponding to the LTM candidate cell for this terminal based on the first indication information.

[0637] Exemplarily, in response to the first message including both the first information and relevant information for requesting L3 mobility (e.g., CHO), the candidate gNB may:

[0638] Prioritize preparing LTM for the terminal. If LTM cannot be prepared, prepare L3 mobility configuration of the corresponding target cell for the terminal; or

[0639] Preparing a mobility for the terminal and the corresponding target cell based on the base station implementation determination; or

[0640] It not only prepares the LTM corresponding to the candidate cell for the terminal, but also prepares the L3 mobility corresponding to the candidate cell for the terminal.

[0641] When the first message is a handover request message, the information units included therein may be as shown in Table 1, for example.

[0642] Step S4102: The candidate gNB sends a second message to the source gNB.

[0643] In response to the candidate gNB receiving the first message sent by the source gNB, if the first message contains the first information, the candidate gNB prepares the LTM based on the first message and sends the LTM candidate configuration and / or the Layer 3 mobility configuration to the source gNB through a second message (e.g., Handover request acknowledge or a new Xn message, such as an LTM request acknowledge message).

[0644] In some embodiments, the first message includes LTM indication information. If the candidate gNB accepts the LTM corresponding to the terminal and candidate cell configuration in this information, the candidate gNB generates an LTM candidate configuration and sends it to the source gNB through a second message.

[0645] In some embodiments, the first message includes LTM indication information and first indication information. If the candidate gNB refuses to configure LTM for this terminal and this candidate cell, it can also configure corresponding L3 mobility for this terminal and this candidate cell. The candidate gNB generates an L3 mobility configuration and sends it to the source gNB through a second message.

[0646] In step S4103, the source gNB sends an RRCReconfiguration message including the LTM candidate configuration to the terminal.

[0647] In step S4104, the terminal sends an RRCReconfigurationComplete message to the source gNB.

[0648] In step x, after LTM is completed, the candidate gNB may send a success indication message (third message) to the source gNB to inform the source gNB that LTM was successfully executed and the terminal has successfully accessed the candidate gNB.

[0649] Exemplarily, the success indication message may include LTM indication information in a handover success message, to indicate that the PCell change is achieved through LTM.

[0650] Exemplarily, it may also be indicated by a new LTM success message.

[0651] When the third message is a handover success message, the information elements included in it are shown in Table 6.

[0652] In step y, after the source gNB prepares or generates the LTM for the terminal, the source gNB can cancel the LTM prepared by the candidate gNB for the terminal by sending a first cancellation message (fourth message). The first cancellation message can include LTM indication information in the existing Handover Cancel message, or it can be a new Xn message for canceling the LTM configuration.

[0653] Exemplarily, the fourth message may further include an LTM candidate cell identifier (or an LTM candidate cell identifier list) and / or an LTM candidate configuration identifier (or an LTM candidate configuration identifier list) for indicating one or more LTM candidate cells to be cancelled.

[0654] Exemplarily, the fourth message is a Handover Cancel message, which includes information units such as shown in Table 7.

[0655] In step z, after the candidate gNB prepares LTM for the terminal and sends the configuration information of the prepared LTM to the source gNB, the candidate gNB can also cancel the LTM prepared by the candidate gNB for the terminal through a second cancellation message (fifth message). The fifth message can include LTM indication information in the existing Conditional Handover Cancel message, or it can be a new Xn message (Candidate LTM Cancel message) for canceling the LTM configuration.

[0656] Exemplarily, the fifth message may further include an LTM candidate cell identifier (or an LTM candidate cell identifier list) and / or an LTM candidate configuration identifier (or an LTM candidate configuration identifier list) to indicate one or more LTM candidate cells to be cancelled.

[0657] Illustratively, the fifth message is a Conditional Handover Cancel message, which includes information elements shown in Table 8.

[0658] It should be noted that either step y or step z can be performed alternatively.

[0659] The above-mentioned LTM indication information can be the indication information corresponding to the LTM triggered by the network, or it can be the indication information corresponding to the LTM (Conditional LTM, CLTM) triggered by the terminal based on conditions. Based on the above-mentioned indication information, the network side can prepare or generate LTM and / or CLTM for the terminal.

[0660] Example 2, for NR-DC scenario.

[0661] Scenario 1, MCG LTM with SCG Release.

[0662] For scenario 1, after the first node MN triggers LTM, the MN needs to release the associated SN, and this release cannot be rejected by the SN, thereby avoiding mismatches between the terminal and the network. For this scenario, the MCG LTM process in the above non-DC scenario can be reused. The source MN only needs to send an SN release request message (S-NODE RELEASE REQUEST) to the associated SN after receiving the LTM success message sent by the target MN to which the terminal accesses. After receiving this message, the SN releases the corresponding resources.

[0663] Scenario 2: SCG LTM between CUs

[0664] Scenario 2.1: SCG LTM with MN participation and triggered by MN.

[0665] The information transmission process is shown in FIG4C , where the first node is the MN and the second node is the candidate SN (C-SN). The process includes the following steps:

[0666] Step S4300: The terminal sends a measurement report to the MN, and the MN decides to configure LTM and starts LTM preparation.

[0667] Step S4301: The MN sends a first message (SN adding request message) to a candidate SN, wherein the first message includes first information.

[0668] In some embodiments, the candidate SN may also be referred to as a target SN, and the candidate cell may also be referred to as a target cell.

[0669] In some embodiments, the first information may include one or more LTM candidate cell identifiers recommended by the MN, and may be implemented in one or more of the following ways:

[0670] The information is carried in a first message and sent to the C-SN through the first message, and the first message indicates that the information is used to indicate an LTM candidate cell or an LTM candidate cell list;

[0671] The inter-node RRC message is sent to the C-SN via an inter-node RRC message. The inter-node RRC message may be carried in the first message and sent to the C-SN.

[0672] For example, when sending to C-SN via inter-node RRC message, a new message ltmcandidateCellInfoListMN can be introduced in CG-ConfigInfo, which contains one or more recommended candidate LTM cells and can be represented by the latest L3 or L1 measurement results, that is, one or more recommended candidate LTM cells are included in CG-ConfigInfo, and the corresponding L1 or L3 measurement results are included therein.

[0673] Exemplarily, the first information includes LTM indication information, where the LTM indication information is used to instruct the MN to request the C-SN to prepare LTM configuration and / or related resources for the terminal.

[0674] Exemplarily, the LTM indication information may be true. When the LTM indication information is true, it indicates that the first message is used to request LTM.

[0675] Exemplarily, LTM indication information may be included in the first message. If the first message includes this indication information, it indicates that the first message is used for preparation of SCG LTM.

[0676] In some embodiments, if the C-SN refuses to configure the LTM corresponding to the LTM candidate cell for this terminal, the C-SN can prepare the L3 mobility configuration and resources corresponding to the LTM candidate cell for this terminal, where L3 mobility includes PSCell change and CPA / CPC (including CPAC that supports subsequent mobility).

[0677] Exemplarily, the first information further includes first indication information, where the first indication information is used to indicate that the candidate gNB is allowed to prepare or generate L3 mobility for the terminal when the configuration of the LTM candidate cell is not supported. When the C-SN refuses to configure the LTM corresponding to the LTM candidate cell for this UE, the L3 mobility configuration and resources corresponding to the LTM candidate cell can be prepared for the terminal based on the first indication information.

[0678] Exemplarily, the first message includes both the first information and relevant information (e.g., CPAC) for requesting L3 mobility. Then, the C-SN may:

[0679] Prioritize preparing LTM for the terminal. If LTM cannot be prepared, L3 mobility of the corresponding target cell can be prepared for the terminal; or

[0680] Determining to prepare a mobility for the terminal and the corresponding target cell based on the C-SN implementation; or

[0681] It not only prepares the LTM corresponding to the candidate cell for the terminal, but also prepares the L3 mobility corresponding to the candidate cell for the terminal.

[0682] Exemplarily, the first information further includes the maximum number of configurable candidate cells, such as the maximum number of configurable PSCells, which is used to indicate the maximum number of candidate PSCells that the C-SN receiving the message can configure for the terminal.

[0683] Exemplarily, the first message may be an SN adding request message, which includes information units such as shown in Table 2.

[0684] Exemplarily, the first message may be CG-ConfigInfo, the information content of which has been introduced in the aforementioned embodiment and will not be repeated here.

[0685] Step S4302: In response to the C-SN receiving the first message sent by the MN, if the first message contains the first information, the C-SN prepares the LTM based on the first message and sends the LTM configuration to the MN through a second message (e.g., an S-NODE ADDITION REQUEST ACKNOWLEDGE message).

[0686] In response to the LTM indication information included in the first message, if the C-SN accepts to configure the corresponding LTM for the terminal and candidate cell corresponding to the information, the C-SN generates a second message for LTM configuration and sends it to the MN.

[0687] In response to the first indication information included in the first message, if the C-SN refuses to configure LTM for this terminal and this candidate cell, it can also configure corresponding L3 mobility for this terminal and this candidate cell, then the C-SN generates L3 mobility configuration and sends it to the MN through a second message.

[0688] Step S4303: The MN sends an RRCReconfiguration message including LTM candidate configuration to the terminal.

[0689] Step S4304: The terminal sends an RRCReconfigurationComplete message to the MN.

[0690] Step S4305: The terminal sends an RRCReconfigurationComplete message to the MN, which includes the message content of the SN RRC reconfiguration complete message.

[0691] Step S4205a: The MN sends an SN RRC reconfiguration complete message to the C-SN.

[0692] Step S4206a, after MN prepares or generates LTM for the terminal, if S-SN does not prepare SCG LTM configuration for the terminal, when the terminal triggers LTM to access the candidate SN, MN sends a release request message (the eighth message) to S-SN, which carries indication information (or release reason indication information (such as a new cause)) to indicate that the SN release is triggered by LTM.

[0693] The MN can send an SN Modification Request message to the S-SN. The SN Modification Request message includes LTM indication information (such as inter-SN SCG LTM execution notification). The LTM indication information is used to inform the S-SN that the terminal has successfully executed the inter-SN SCG LTM and changed the serving SN.

[0694] Based on the LTM indication information, the S-SN stops providing user data to the terminal and changes to the ready state, that is, the S-SN becomes the C-SN.

[0695] Step S4206b: After releasing resources, the S-SN may send an SN Modification RequestAcknowledge message to the MN.

[0696] In step S4207a, the C-SN may initiate a fifth message to the MN to cancel the (SCG) LTM candidate configuration.

[0697] The C-SN may cancel all prepared SCG LTMs or release all resources prepared by the C-SN through the SN Release message.

[0698] For example, after the C-SN prepares an LTM for the terminal and sends configuration information of the prepared LTM to the MN, the C-SN may also cancel the LTM prepared by the C-SN for the terminal through a fifth message such as S-NODE RELEASE REQUIRED.

[0699] In step S4207b, the MN may send a fourth message to the C-SN to cancel the (SCG) LTM candidate configuration.

[0700] The MN may cancel all prepared SCG LTMs or release all resources prepared by the C-SN through the SN Release message.

[0701] Exemplarily, after the MN prepares or generates the LTM for the terminal, the MN can cancel the LTM prepared by the C-SN for the terminal by sending a fourth message (e.g., SN Release request). When the C-SN receives the fourth message, the SN releases the configuration and resources prepared for the terminal.

[0702] It should be noted that either step S4207a or step S4207b can be performed selectively.

[0703] It should also be noted that MN and C-SN can initiate the process of modifying the SCG LTM configuration, where MN and C-SN can modify the prepared SCG LTM candidate configuration through the SN Modification process, such as deleting part of the SCG LTM configured by T-SN for the UE, adding new SCG LTM candidate configuration, and modifying the existing SCG LTM candidate configuration.

[0704] Exemplarily, steps S4207b and S4207c are performed. In step S4207b, the MN sends a sixth message carrying information for LTM configuration modification, such as an SN Modification Request message to the C-SN. After receiving the sixth message, the C-SN modifies the SCG LTM configuration based on the information for LTM configuration modification. Step S4207c is performed, and the C-SN sends an SN Modification Request Ack message to the MN. The modification process includes deleting the SCG LTM configuration corresponding to some candidate SCGs, updating the existing SCG LTM configuration information, and adding additional SCG LTM configurations. The information used for LTM configuration modification includes LTM indication information, one or more recommended SCG LTM candidate cells, and may also include one or more SCG LTM candidate cells to be deleted / updated.

[0705] Exemplarily, steps S4207a to S4207c are executed, and the C-SN sends a seventh message carrying information for LTM configuration modification, such as an SN Modification Required message to the MN, requesting the MN to initiate an LTM configuration modification process. The SN Modification Required message carries LTM indication information and one or more SCG LTM candidate cells to be deleted / updated. After receiving this message, the MN can send a sixth message to the C-SN and receive the SN Modification Request Ack message sent by the C-SN.

[0706] When the sixth message is an SN modification request (SN ModificationRequest) message, the information units included therein are shown in Table 9, for example.

[0707] Scenario 2.2: SCG LTM with MN participation and triggered by SN.

[0708] For SN-initiated SCG LTM, compared with scenario 2.1, the S-SN initiates the SCG LTM process by sending a first message, such as an SN Change Required message, to the MN. The subsequent process is similar to scenario 2.1. After the C-SN completes the SCG LTM preparation process, it sends a second message, such as an SN add request confirmation message, to the MN. The MN sends a ninth message, such as an SN Change Confirm message, to the C-SN to confirm that the SCG preparation process has been completed.

[0709] The process is shown in FIG4D , where the first node is the MN, the second node is the C-SN, and the third node is the S-SN. The process includes the following steps:

[0710] Step S4400: The terminal sends a measurement report to the MN, and the MN decides to configure LTM and starts LTM preparation.

[0711] Step S4401: The S-SN sends a first message to the MN.

[0712] The SN sends a first message (eg, SN change request) to the MN, wherein the first message includes first information.

[0713] In some embodiments, the first information includes one or more LTM candidate cell identifiers recommended by the S-SN, wherein the S-SN sends one or more recommended C-SNs to the MN, each C-SN corresponding to a group of LTM candidate cell identifiers. The recommended LTM candidate cells may be implemented in one or more of the following ways:

[0714] The information is carried in a first message and sent to the C-SN through the first message, and the first message indicates that the information is used to indicate an LTM candidate cell or cell list;

[0715] The inter-node RRC message is sent to the T-SN. The inter-node RRC message may be carried in the first message and sent to the C-SN.

[0716] Illustratively, the first message may be an SN change required (SN Change Required) message, including information elements shown in Table 5.

[0717] Step S4402: In response to the C-SN receiving the first message sent by the MN, if the first message contains the first information, the C-SN prepares the LTM based on the first message and sends the LTM configuration to the MN through a second message (e.g., an SN add request confirmation message).

[0718] Step S4403: The MN sends an RRCReconfiguration message including LTM candidate configuration to the terminal.

[0719] Step S4404: The MN sends an RRCReconfiguration message including LTM candidate configuration to the terminal.

[0720] Step S4405: The terminal sends an RRCReconfigurationComplete message to the MN, which includes the message content of the SN RRC reconfiguration complete message.

[0721] Step S4406: MN sends a ninth message to S-SN.

[0722] In some embodiments, after the MN receives the SN add request confirmation message replied by the C-SN, the MN sends a ninth message, such as an SN Change Confirm message, to the S-SN to inform the S-SN of the LTM candidate cells configured by the C-SN.

[0723] Exemplarily, the SN Change Confirm message includes one or more T-SNs for which LTM configuration is prepared and a corresponding SCG LTM candidate cell list.

[0724] Exemplarily, the ninth message may be an SN change confirmation (eg, SNChangeConfirm) message, the information units included in which are shown in Table 10, for example.

[0725] Steps S4407 to S4410 are similar to the above-mentioned steps S4305 to S4307 and will not be repeated here.

[0726] Scenario 3, MCG LTM with / without SCG changes.

[0727] In the case where the network side configures MCG LTM and SCG LTM for the terminal at the same time, the above-mentioned LTM indication information can be used to instruct the network to request the configuration of inter node LTM for the terminal to trigger the change of MCG and SCG.

[0728] The specific implementation process is similar to the above embodiment and will not be repeated here.

[0729] The embodiments of the present disclosure also propose a device for implementing any of the above methods. For example, a device is proposed, which includes units or modules for implementing each step performed by each node (such as the first node, the second node, and the third node) in any of the above methods.

[0730] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0731] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0732] FIG5A is a schematic diagram of the structure of a first node proposed in an embodiment of the present disclosure. As shown in FIG5A , the first node 5100 may include: a transceiver module 5101 .

[0733] In some embodiments, the transceiver module 5101 is configured to send a first message to the second node, where the first message includes first information, and the first information is used to request a layer 1 or layer 2 triggered mobility LTM.

[0734] Optionally, the above-mentioned transceiver module 5101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first node 5100 in any of the above methods (for example, step S2101, step S2102, step S2105, step S2106, step S2107, step S2108, step S2109, step S2110, step S2111, step S2112, but not limited to these), which are not repeated here.

[0735] FIG5B is a schematic diagram of the structure of a second node proposed in an embodiment of the present disclosure. As shown in FIG5B , the second node 5200 may include: a transceiver module 5201 .

[0736] In some embodiments, the transceiver module 5201 is configured to receive a first message sent by a first node, where the first message includes first information, and the first information is used to request a layer 1 or layer 2 triggered mobility LTM.

[0737] Optionally, the above-mentioned transceiver module 5201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the second node 5200 in any of the above methods (for example, step S2102, step S2105, step S2106, step S2107, step S2108, step S2109, step S2110, but not limited to these), which will not be repeated here.

[0738] In some embodiments, the second node 5200 may further include a processing module 5202 (not shown in FIG. 5B ).

[0739] Optionally, the processing module 5202 is used to execute at least one of the other steps (such as step S2103 and step S2104, but not limited thereto) executed by the second node 5200 in any of the above methods, which will not be repeated here.

[0740] FIG5C is a schematic diagram of the structure of a third node proposed in an embodiment of the present disclosure. As shown in FIG5C , the third node 5300 may include: a transceiver module 5301 .

[0741] In some embodiments, the transceiver module 5201 is configured to send a first message to the first node so that the first node sends the first message to the second node, where the first message includes first information, and the first information is used to request layer 1 or layer 2 triggered mobility LTM.

[0742] Optionally, the above-mentioned transceiver module 5301 is used to execute at least one of the communication steps such as sending and / or receiving performed by the third node 5300 in any of the above methods (for example, step S2101, step S2111, step S2112, but not limited to this), which will not be repeated here.

[0743] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0744] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0745] Figure 6A is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., a first node, a second node, a third node, etc.), or a chip, a chip system, or a processor that supports a network device in implementing any of the above methods. It can also be a chip, a chip system, or a processor that supports a terminal in implementing any of the above methods. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0746] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0747] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., steps S2101, S2102, S2105, S2106, S2107, S2108, S2109, S2110, S2111, and S2112, but not limited thereto) in the above method, and the processor 6101 performs at least one of the other steps (e.g., steps S2103 and S2104, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

[0748] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memories 6103 may be located outside the communication device 6100. In alternative embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memory 6102 and may be configured to receive data from the memory 6102 or other devices, or to send data to the memory 6102 or other devices. For example, the interface circuits 6104 may read data stored in the memory 6102 and send the data to the processor 6101.

[0749] The communication device 6100 described in the above embodiment may be a network device, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG. 6A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0750] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.

[0751] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

[0752] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Alternatively, all or part of memory 6203 may be located external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203 and may be used to receive data from memory 6203 or other devices, or may be used to send data to memory 6203 or other devices. For example, interface circuit 6202 may read data stored in memory 6203 and send the data to processor 6201.

[0753] In some embodiments, the interface circuit 6202 performs at least one of the communication steps (e.g., steps S2101, S2102, S2105, S2106, S2107, S2108, S2109, S2110, S2111, and S2112) of the aforementioned method. The interface circuit 6202 performing the communication steps (e.g., steps S2101, S2102, S2105, S2106, S2107, S2108, S2109, S2110, S2111, and S2112) of the aforementioned method, for example, means that the interface circuit 6202 performs data exchange between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps (e.g., steps S2103 and S2104, but not limited thereto).

[0754] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0755] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0756] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0757] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0758] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0759] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An information transmission method, characterized in that, The method is executed by a first node and includes: Sending a first message to a second node, where the first message includes first information for requesting a mobility LTM triggered by layer 1 or layer 2.

2. The method according to claim 1, wherein The first information includes at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; LTM indication information for requesting an LTM candidate configuration or an LTM candidate configuration update; First indication information for indicating that the second node is allowed to prepare a layer 3 mobility configuration for a terminal when the second node does not support configuring an LTM candidate cell; Maximum number of configurable candidate cells; List of recommended candidate cells; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

3. The method according to claim 1 or 2, characterized in that, The first message is any one of the following messages: Handover request message; Secondary node SN addition request message; SN modification request message; SN change request message; First Xn message for requesting an LTM; First inter-node RRC message for requesting an LTM.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Receiving a second message sent by the second node, where the second message includes at least one of the following: LTM candidate configuration; Layer 3 mobility configuration.

5. The method according to claim 4, wherein The second message is any one of the following messages: Handover request confirmation message; SN addition request confirmation message; SN modification request confirmation message; SN change request confirmation message; Second Xn message for performing an LTM request confirmation; Second inter-node RRC message for performing an LTM request confirmation.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receiving a third message sent by the second node for notifying the first node that the LTM has been successfully executed.

7. The method according to claim 6, wherein When the third message includes LTM indication information, the third message is used to indicate that the change of the terminal serving node is triggered by the LTM.

8. The method according to claim 6 or 7, characterized in that The third message is any one of the following messages: Handover success message; SN addition success message; SN modification success message; SN change success message; Third Xn message for indicating that the LTM has been successfully executed; Third inter-node RRC message for indicating that the LTM has been successfully executed.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Sending a fourth message to the second node, where the fourth message is used to cancel the LTM candidate configuration prepared by the second node for the terminal.

10. The method according to claim 9, wherein The fourth message includes at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

11. The method according to any one of claims 1 - 8, characterized in that, The method further includes: Receiving a fifth message sent by the second node after preparing an LTM candidate configuration for the terminal, where the fifth message is used to cancel the LTM candidate configuration prepared by the second node for the terminal.

12. The method according to claim 11, wherein The fifth message includes at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

13. The method according to any one of claims 1 to 12, characterized in that, The method further includes: Send a sixth message to the second node, where the sixth message is used to request modifying the LTM candidate configuration prepared by the second node for the terminal.

14. The method according to claim 13, wherein The sixth message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

15. The method according to any one of claims 1-14, characterized in that, The method further includes: Receiving a seventh message sent by the second node, where the seventh message is used to request the first node to initiate modification of the LTM candidate configuration.

16. The method according to claim 15, characterized in that, The seventh message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

17. The method according to any one of claims 1-16, characterized in that, The method further includes: After receiving the third message sent by the second node, sending an eighth message to a third node, where the third message is used to indicate that the terminal has successfully accessed the second node, and the eighth message is used to release the resources of the third node.

18. The method according to any one of claims 1-17, characterized in that, The method further includes: Receiving the first message sent by the third node.

19. The method according to claim 18, characterized in that, The method further includes: After receiving the second message sent by the second node, sending a ninth message to the third node, where the second message includes an LTM candidate configuration, and the ninth message includes at least one of the following: Identifier of the second node that has prepared the LTM candidate configuration for the terminal; Secondary cell group (SCG) LTM candidate cell identifier; SCG LTM candidate cell configuration identifier.

20. An information transmission method, characterized in that, The method is executed by a second node and includes: Receiving a first message sent by a first node, where the first message includes first information, and the first information is used to request a mobility LTM triggered by layer 1 or layer 2.

21. The method according to claim 20, wherein The first information includes at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; LTM indication information, where the LTM indication information is used to request an LTM candidate configuration or an LTM candidate configuration update; First indication information, where the first indication information is used to indicate that the second node is allowed to prepare a layer 3 mobility configuration for the terminal when it does not support configuring an LTM candidate cell; Maximum number of configurable candidate cells; List of recommended candidate cells; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

22. The method according to claim 20 or 21, characterized in that The first message is any of the following messages: Handover request message; Secondary node (SN) addition request message; SN modification request message; SN change request message; First Xn message, where the first Xn message is used to request an LTM; First inter-node RRC message, where the first inter-node RRC message is used to request an LTM.

23. The method according to any one of claims 20 - 22, characterized in that, The method further includes: Preparing an LTM candidate configuration for the terminal based on the first message.

24. The method according to any one of claims 20-22, characterized in that The method further includes: When it is unable to prepare an LTM candidate configuration for the terminal and the first message includes second indication information, preparing a layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal, where the second indication information is used to request a layer 3 mobility configuration; or It is not possible to prepare an LTM candidate configuration for the terminal, and the first message includes first indication information for preparing a layer 3 mobility configuration corresponding to the LTM candidate cell for the terminal, and the first indication allows the second node to prepare a layer 3 mobility configuration for the terminal when it does not support configuring the LTM candidate cell.

25. The method according to any one of claims 20-22, characterized in that, The method further includes any one of the following: The first message includes first indication information and second indication information for preparing an LTM candidate configuration for the terminal and, when it is not possible to prepare an LTM candidate configuration for the terminal, preparing a layer 3 mobility configuration for the terminal; wherein, the first indication information is used to indicate that the second node is allowed to prepare a layer 3 mobility configuration for the terminal when it does not support configuring the LTM candidate cell, and the second indication information is used to request a layer 3 mobility configuration; The first message includes first indication information and second indication information for preparing an LTM candidate configuration and / or a layer 3 mobility configuration for the terminal; wherein, the first indication information is used to indicate that the second node is allowed to prepare a layer 3 mobility configuration for the terminal when it does not support configuring the LTM candidate cell, and the second indication information is used to request a layer 3 mobility configuration.

26. The method according to any one of claims 23-25, characterized in that, The method further includes: Sending a second message to the first node, the second message including at least one of the following: LTM candidate configuration; Layer 3 mobility configuration.

27. The method according to claim 26, wherein The second message is any one of the following messages: Handover request confirmation message; SN addition request confirmation message; SN modification request confirmation message; SN change request confirmation message; Second Xn message, the second Xn message being used for LTM request confirmation; Second inter-node RRC message, the second inter-node RRC message being used for LTM request confirmation.

28. The method according to any one of claims 20-27, characterized in that, The method further includes: Sending a third message to the first node, the third message being used to notify the first node that the LTM has been successfully executed.

29. The method according to claim 28, wherein When the third message includes LTM indication information, the third message is used to indicate that the change of the terminal serving node is triggered by the LTM.

30. The method according to claim 28 or 29, characterized in that, The third message is any one of the following messages: Handover success message; SN addition success message; SN modification success message; SN change success message; Third Xn message, the third Xn message being used to indicate that the LTM has been successfully executed; Third inter-node RRC message, the third inter-node RRC message being used to indicate that the LTM has been successfully executed.

31. The method according to any one of claims 20-30, characterized in that, The method further includes: Receiving a fourth message sent by the first node, the fourth message being used to cancel the LTM candidate configuration prepared by the second node for the terminal; Based on the fourth message, canceling the LTM candidate configuration prepared for the terminal.

32. The method according to claim 31, wherein The fourth message includes at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; LTM candidate cell identifier list; LTM candidate configuration identifier list.

33. The method according to any one of claims 20-30, characterized in that, The method further includes: After preparing an LTM candidate configuration for the terminal, sending a fifth message to the first node, the fifth message being used to cancel the LTM candidate configuration prepared by the second node for the terminal.

34. The method according to claim 33, characterized in that, The fifth message includes at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

35. The method according to any one of claims 20-34, characterized in that, The method further includes: Receiving a sixth message sent by the first node, the sixth message being used to request modification of the LTM candidate configuration prepared by the second node for the terminal; Based on the sixth message, modifying the LTM candidate configuration prepared for the terminal.

36. The method according to claim 35, characterized in that The sixth message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; List of LTM candidate cell identifiers; List of LTM candidate configuration identifiers.

37. The method according to any one of claims 20-36, characterized in that, The method further includes:

38. The method according to claim 37, characterized in that Sending a seventh message to the first node, the seventh message being used to request the first node to initiate modification of the LTM candidate configuration. The seventh message includes at least one of the following: LTM indication information; LTM candidate cell identifier; LTM candidate configuration identifier; List of LTM candidate cell identifiers; 39. An information transmission method, characterized in that, List of LTM candidate configuration identifiers. The method is executed by a third node and includes:

40. The method according to claim 39, wherein Sending a first message to a first node, so that the first node sends the first message to a second node, the first message including first information, the first information being used to request layer 1 or layer 2 triggered mobility LTM. The first information includes at least one of the following: LTM candidate cell identifier; LTM candidate configuration identifier; LTM indication information, the LTM indication information being used to request an LTM candidate configuration or an LTM candidate configuration update; First indication information, the first indication information being used to indicate that the second node is allowed to prepare a layer 3 mobility configuration for the terminal when it does not support configuring LTM candidate cells; Maximum number of configurable candidate cells; List of recommended candidate cells; List of LTM candidate cell identifiers; 41. The method according to claim 39 or 40, characterized in that, List of LTM candidate configuration identifiers. The first message is any one of the following messages: Handover request message; Secondary node SN addition request message; SN modification request message; SN change request message; First Xn message, the first Xn message being used to request LTM; 42. The method according to any one of claims 39 - 41, characterized in that, First inter-node RRC message, the first inter-node RRC message being used to request LTM. The method further includes: Receiving an eighth message sent by the first node, the eighth message being used to release the resources of the third node; 43. The method according to any one of claims 39 to 42, characterized in that, Based on the eighth message, releasing the resources. The method further includes: Receiving a ninth message sent by the first node, the ninth message including at least one of the following: Identifier of the second node that has prepared an LTM candidate configuration for the terminal; Secondary cell group SCG LTM candidate cell identifier; 44. A first node, characterized in that, SCG LTM candidate cell configuration identifier. Includes:

45. A second node, characterized in that, A transceiver module, configured to send a first message to a second node, the first message including first information, the first information being used to request layer 1 or layer 2 triggered mobility LTM. Includes:

46. A third node, characterized in that, A transceiver module, configured to receive a first message sent by a first node, the first message including first information, the first information being used to request layer 1 or layer 2 triggered mobility LTM. Includes: A transceiver module, configured to send a first message to a first node, so that the first node sends the first message to a second node, where the first message includes first information for requesting layer 1 or layer 2 triggered mobility LTM.

47. A first node, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the information transmission method according to any one of claims 1-19.

48. A second node, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the method of information transmission behavior according to any one of claims 20-38.

49. A third node, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the method of information transmission behavior according to any one of claims 39-43.

50. A communication system, characterized in that, Comprising a first node, a second node, and a third node, wherein the first node is configured to implement the information transmission method according to any one of claims 1-19, the second node is configured to implement the information transmission method according to any one of claims 20-38, and the third node is configured to implement the information transmission method according to any one of claims 39-43.

51. A storage medium, the storage medium stores instructions, characterized in that, When the instruction runs on a communication device, the communication device is caused to execute the information transmission method according to any one of claims 1-19, 20-38, or 39-43.

Images