Information transmission method and apparatus, and storage medium

Abstract

Provided in the present disclosure are an information transmission method and apparatus, and a storage medium. The method comprises: determining a reference configuration, wherein the reference configuration is generated by a first node and / or a second node and then sent to the first node; and sending a first message to the second node, wherein the first message is used for requesting the second node to generate a layer 1- or layer 2-triggered mobility candidate configuration, and the first message comprises any one of the following: first instruction information, which is used for instructing that the second node is requested to generate a complete candidate configuration, and second instruction information, which is used for instructing that the second node is requested to generate an incremental candidate configuration on the basis of the reference configuration. In the present disclosure, the node for generating a reference configuration is specified, the reference configuration can be exchanged between nodes, and it is specified that the node generates a complete candidate configuration or an incremental candidate configuration, so that the aim of performing LTM interaction between the nodes to support an LTM configuration is achieved, thereby improving the availability of the LTM configuration.

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 improve the availability of LTM configuration, embodiments of the present disclosure provide an information transmission method and apparatus, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, there is provided an information transmission method, which is executed by a first node and includes: determining a reference configuration, where the reference configuration is used to determine a candidate configuration, where the candidate configuration is triggered by layer 1 or layer 2; wherein the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node; sending a first message to the second node, where the first message is used to request the second node to generate a candidate configuration, and the first message includes any one of the following items: first indication information, where the first indication information is used to indicate a request for the second node to generate a complete candidate configuration; and second indication information, where the second indication information is used to indicate a request for the second node to generate an incremental candidate configuration based on the reference configuration.

[0007] According to a second aspect of an embodiment of the present disclosure, there is provided an information transmission method, which is executed by a second node and includes: receiving a first message sent by a first node, the first message being used to request the second node to generate a candidate configuration, the candidate configuration being triggered by layer 1 or layer 2, the first message including any one of the following items: first indication information, the first indication information being used to indicate a request to the second node to generate a complete candidate configuration; second indication information, the second indication information being used to indicate a request to the second node to generate an incremental candidate configuration based on a reference configuration, the reference configuration being used to determine the candidate configuration; the reference configuration being generated by the first node or by the second node, or the reference configuration being generated by the first node and the second node.

[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 second message to the first node, the second message being used to request the first node to generate a reference configuration, the reference configuration being used to determine a candidate configuration, and the candidate configuration being triggered by layer 1 or layer 2; and / or sending a fourth message to the first node, the fourth message being used to request the first node to send a third message to the second node, the third message being used to request the reference configuration, the reference configuration being used to determine a candidate configuration, and the candidate configuration being triggered by layer 1 or layer 2.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a first node is provided, including: a processing module, configured to determine a reference configuration, the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; wherein the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node; a transceiver module, configured to send a first message to the second node, the first message is used to request the second node to generate a candidate configuration, and the first message includes any one of the following items: first indication information, the first indication information is used to indicate a request for the second node to generate a complete candidate configuration; second indication information, the second indication information is used to indicate a request for the second node to generate an incremental candidate configuration based on the reference configuration.

[0010] According to the 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 the first node, the first message being used to request the second node to generate a candidate configuration, the candidate configuration being triggered by layer 1 or layer 2, and the first message including any one of the following: first indication information, the first indication information being used to indicate a request for the second node to generate a complete candidate configuration; second indication information, the second indication information being used to indicate a request for the second node to generate an incremental candidate configuration based on a reference configuration, the reference configuration being used to determine the candidate configuration; the reference configuration being generated by the first node or by the second node, or the reference configuration being generated by the first node and the second node.

[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 second message to the first node, the second message is used to request the first node to generate a reference configuration, the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; and / or send a fourth message to the first node, the fourth message is used to request the first node to send a third message to the second node, the third message is used to request the reference configuration, the reference configuration is used to determine the candidate configuration, and the candidate configuration is 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 the embodiments of the present disclosure, the nodes for generating reference configurations are clarified, and reference configurations can be exchanged between nodes. It is also clarified that nodes generate complete candidate configurations or incremental candidate configurations, thereby realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM configuration.

[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] FIG2A is an exemplary interaction diagram of an information transmission method provided according to an embodiment of the present disclosure.

[0025] FIG2B is a schematic diagram of an information generation method provided according to an embodiment of the present disclosure.

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

[0027] FIG2D is a schematic diagram of an information determination method provided according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

[0037] 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.

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

[0039] In a first aspect, an embodiment of the present disclosure proposes an information transmission method, which is executed by a first node and includes: determining a reference configuration, where the reference configuration is used to determine a candidate configuration, where the candidate configuration is triggered by layer 1 or layer 2; wherein the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node; sending a first message to the second node, where the first message is used to request the second node to generate a candidate configuration, and the first message includes any one of the following items: first indication information, where the first indication information is used to indicate a request for the second node to generate a complete candidate configuration; and second indication information, where the second indication information is used to indicate a request for the second node to generate an incremental candidate configuration based on the reference configuration.

[0040] In the above embodiments, the reference configuration can be generated by the first node or the second node, or the reference configuration can be generated by the first node and the second node, and the reference configuration can be exchanged between the nodes. In addition, the first node can instruct the second node to generate a complete candidate configuration or an incremental candidate configuration, thereby realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM configuration.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the reference configuration is common to a group of incomplete candidate configurations within the same cell group.

[0042] In the above embodiment, the reference configuration may be a configuration that is common to incomplete candidate configurations, so that reference configurations can be exchanged between nodes later, which has high availability.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, when the reference configuration is generated by the first node, the reference configuration includes a master cell group (MCG) reference configuration. In the above embodiments, the first node can generate the MCG reference configuration. The node generating the reference configuration is clarified, and availability is high.

[0044] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a second message sent by a third node, where the second message is used to request the first node to generate a reference configuration.

[0045] In the above embodiment, the first node can receive the second message sent by the third node and generate a reference configuration based on the second message, thereby clarifying the node that generates the reference configuration and achieving high availability.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending a third message to the second node, where the third message is used to request a reference configuration.

[0047] In the above embodiment, the first node may send the third message to the second node, thereby requesting the second node to generate a reference configuration. This clarifies the node that generates the reference configuration, and has high availability.

[0048] In combination with some embodiments of the first aspect, in some embodiments, determining the reference configuration includes: receiving a third response message sent by the first node, where the third response message includes the reference configuration generated by the second node.

[0049] In the above embodiment, the first node may obtain the reference configuration generated by the second node from the second node, thereby achieving the purpose of exchanging reference configurations between nodes.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the third message is any one of the following messages: a switching request message; a secondary node SN addition request message; a SN modification request message; a SN reconfiguration completion message; an SM modification confirmation message; an SN change confirmation message; a switching preparation information; a cell group configuration information; a first Xn message, the first Xn message is used for an LTM request; a first inter-node RRC message, the first inter-node RRC message is used for an LTM request.

[0051] In the above embodiment, the third message can be any of the above messages, thereby achieving the purpose of triggering the second node to generate a reference configuration. The implementation is simple and the availability is high.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the third response message is any one of the following messages: a handover request confirmation message; an SN add request confirmation message; an SN modification request confirmation message; an SN modification request message; an SN change request message; a handover command; a cell group configuration; a cell group candidate list; a second Xn message, the second Xn message is used for LTM request confirmation; a first inter-node RRC message, the first inter-node RRC message is used for LTM request; a second inter-node RRC message, the second inter-node RRC message is used for LTM request confirmation.

[0053] In the above embodiment, the third response message may be any of the above messages. The third response message may be used to implement interaction of reference configurations, thereby improving the availability of LTM configurations.

[0054] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a fourth message sent by the third node, where the fourth message is used to request the first node to send a third message to the second node.

[0055] In the above embodiment, the third node can request the second node to generate a reference configuration through the first node, which has high availability.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the reference configuration includes any one of the following: MCG reference configuration, the MCG reference configuration is generated by the first node or the second node; SCG reference configuration, the SCG reference configuration is generated by the second node; MCG reference configuration and SCG reference configuration, the MCG reference configuration is generated by the first node, and the SCG reference configuration is generated by the second node.

[0057] In the above embodiments, the reference configuration may include only the MCG reference configuration or the SCG reference configuration, or the reference configuration may include the MCG reference configuration and the SCG reference configuration, thereby improving the flexibility of reference configuration generation.

[0058] 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 reconfiguration completion message; an SM modification confirmation message; an SN change confirmation message; a first Xn message, the first Xn message is used for an LTM request; a first inter-node RRC message, the first inter-node RRC message is used for an LTM request.

[0059] In the above embodiment, the first node may send any of the above messages as the first message to the second node to inform the second node to generate a complete candidate configuration or an incremental candidate configuration, thereby achieving the purpose of generating and exchanging reference configurations between nodes.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the first message also includes at least one of the following: a reference configuration; and third indication information, where the third indication information is used to request the second node to generate a candidate configuration for the first node or the LTM candidate cell.

[0061] In the above embodiment, the first message may further include but is not limited to at least one of the above items, so that the second node can generate a candidate configuration, thereby improving the availability of the LTM.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a first response message sent by the second node, where the first response message includes the candidate configuration generated by the second node.

[0063] In the above embodiment, the second node can provide the complete candidate configuration or incremental candidate configuration to the first node through the first response message, so that the first node can provide it to the terminal, thereby achieving the purpose of exchanging candidate configurations between nodes and improving the availability of LTM configuration.

[0064] In combination with some embodiments of the first aspect, in some embodiments, the first response 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 modification request message; an SN change request 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.

[0065] In the above embodiment, the first response message may be any of the above messages, which enables providing the complete candidate configuration or the incremental candidate configuration to the first node, and is simple to implement and has high availability.

[0066] In combination with some embodiments of the first aspect, in some embodiments, the first response message includes: fourth indication information, and the fourth indication information is used to indicate whether the candidate configuration generated by the second node is a complete candidate configuration.

[0067] In the above embodiment, the first response message may further include fourth indication information so that the second node can inform the first node whether the candidate configuration generated by the second node is a complete candidate configuration, thereby ensuring that the nodes have a consistent understanding of the integrity of the candidate configuration and high availability.

[0068] In the second aspect, an embodiment of the present disclosure proposes an information transmission method, which is executed by a second node, including: receiving a first message sent by a first node, the first message is used to request the second node to generate a candidate configuration, the candidate configuration is triggered by layer 1 or layer 2, and the first message includes any one of the following items: first indication information, the first indication information is used to indicate the request for the second node to generate a complete candidate configuration; second indication information, the second indication information is used to indicate the request for the second node to generate an incremental candidate configuration based on a reference configuration, and the reference configuration is used to determine the candidate configuration; the reference configuration is generated by the first node or by the second node, or the reference configuration is generated by the first node and the second node.

[0069] In the above embodiment, the second node can receive the first message sent by the first node, thereby generating a complete candidate configuration or an incremental candidate configuration based on the first message, realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM configuration.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the reference configuration is common to a group of incomplete candidate configurations within the same cell group.

[0071] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: receiving a third message sent by the first node, the third message being used to request the second node to generate a reference configuration; generating a reference configuration; and sending a third response message to the first node, the third response message including the reference configuration generated by the second node.

[0072] In combination with some embodiments of the second aspect, in some embodiments, the third 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 modification confirmation message; an SN change request message; a first Xn message, the first Xn message is used for an LTM request; a first inter-node RRC message, the first inter-node RRC message is used for an LTM request.

[0073] In combination with some embodiments of the second aspect, in some embodiments, the third response 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 modification request message; an SN change request 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.

[0074] In combination with some embodiments of the second aspect, in some embodiments, the reference configuration includes any one of the following: MCG reference configuration, the MCG reference configuration is generated by the first node or the second node; SCG reference configuration, the SCG reference configuration is generated by the second node; MCG reference configuration and SCG reference configuration, the MCG reference configuration is generated by the first node, and the SCG reference configuration is generated by the second node.

[0075] 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 modification confirmation message; an SN change request message; a first Xn message, the first Xn message is used for an LTM request; a first inter-node radio resource control RRC message, the first inter-node RRC message is used for an LTM request.

[0076] In combination with some embodiments of the second aspect, in some embodiments, the first message also includes at least one of the following: a reference configuration; and third indication information, where the third indication information is used to request the second node to generate a candidate configuration for the first node or the LTM candidate cell.

[0077] In combination with some embodiments of the second aspect, in some embodiments, the method also includes any one of the following: the first message includes first indication information to generate a complete candidate configuration; the first message does not include a reference configuration to generate a complete candidate configuration; the first message includes second indication information to generate an incremental candidate configuration based on the reference configuration.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a first response message to the first node, where the first response message includes the candidate configuration generated by the second node.

[0079] In combination with some embodiments of the second aspect, in some embodiments, the first response 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 modification request message; an SN change request 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.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the first response message includes: fourth indication information, and the fourth indication information is used to indicate whether the candidate configuration generated by the second node is a complete candidate configuration.

[0081] In a third aspect, an embodiment of the present disclosure proposes an information transmission method, which is executed by a third node, including: sending a second message to the first node, the second message is used to request the first node to generate a reference configuration, the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; and / or sending a fourth message to the first node, the fourth message is used to request the first node to send a third message to the second node, the third message is used to request the reference configuration, the reference configuration is used to determine the candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2.

[0082] In the above embodiment, the third node can send the second message and / or the fourth message to the first node, clarifying the node that generates the reference configuration, and can exchange reference configurations between nodes, and clarifying that the node generates a complete candidate configuration or an incremental candidate configuration, thereby realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM configuration.

[0083] In conjunction with some embodiments of the third aspect, in some embodiments, the reference configuration is common to a group of incomplete candidate configurations within the same cell group.

[0084] In the fourth aspect, an embodiment of the present disclosure proposes a first node, comprising: a processing module, configured to determine a reference configuration, the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; wherein, the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node; a transceiver module, configured to send a first message to the second node, the first message is used to request the second node to generate a candidate configuration, and the first message includes any one of the following items: first indication information, the first indication information is used to indicate a request for the second node to generate a complete candidate configuration; second indication information, the second indication information is used to indicate a request for the second node to generate an incremental candidate configuration based on the reference configuration.

[0085] In the fifth aspect, an embodiment of the present disclosure proposes a second node, including: a transceiver module, configured to receive a first message sent by the first node, the first message is used to request the second node to generate a candidate configuration, the candidate configuration is triggered by layer 1 or layer 2, and the first message includes any one of the following items: first indication information, the first indication information is used to indicate the request for the second node to generate a complete candidate configuration; second indication information, the second indication information is used to indicate the request for the second node to generate an incremental candidate configuration based on a reference configuration; the reference configuration is generated by the first node or by the second node, or the reference configuration is generated by the first node and the second node.

[0086] In the sixth aspect, an embodiment of the present disclosure proposes a third node, including: a transceiver module, configured to send a second message to the first node, the second message is used to request the first node to generate a reference configuration, the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; and / or send a fourth message to the first node, the fourth message is used to request the first node to send a third message to the second node, the third message is used to request the reference configuration, the reference configuration is used to determine the candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2.

[0087] 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.

[0088] 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.

[0089] In a 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 in the third aspect.

[0090] 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 the third aspect.

[0091] In the eleventh aspect, an embodiment of the present disclosure proposes a storage medium storing instructions, characterized in that 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

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

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

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

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

[0106] 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.

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

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

[0109] 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.

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

[0111] As shown in FIG. 1A , a communication system 100 includes a first node 101 , a second node 102 , and a third node 103 .

[0112] 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. Alternatively, the first node 101 may be a candidate access network device, such as a candidate base station. Exemplarily, the first node 101 may be a source-master node (S-MN) or a candidate-master node (C-MN).

[0113] In some embodiments, in a dual connectivity (DC) scenario, such as an NR-DC scenario, for an SCG LTM where the MCG remains unchanged, the first node 101 may be a master node (MN).

[0114] In the NR-DC scenario, for the MCG LTM released by the SCG, the first node 101 may be an S-MN or a C-MN.

[0115] In the NR-DC scenario, for the MCG LTM where the SCG does not change, the first node 101 may be an S-MN or a C-MN.

[0116] 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. For example, the second node 102 may be a C-MN.

[0117] In some embodiments, in a DC scenario, such as an NR-DC scenario, for an SCG LTM where the MCG remains unchanged, the second node 102 may be a source-secondary node (S-SN) or a candidate-secondary node (C-SN).

[0118] In the NR-DC scenario, for the MCG LTM released by the SCG, the second node 102 may be a C-MN.

[0119] In the NR-DC scenario, for the MCG LTM whose SCG does not change, the second node 102 may be the S-SN.

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

[0121] In some embodiments, the third node 103 may be an S-SN in a DC scenario.

[0122] 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.

[0123] 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.

[0124] 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).

[0125] 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.

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

[0127] 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.

[0128] 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.

[0129] 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.

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

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

[0132] 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.

[0133] 2. NR-NR Dual Connectivity

[0134] 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.

[0135] 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.

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

[0137] LTM refers to a process of PCell and / or PSCell cell change (e.g., 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.

[0138] 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.

[0139] 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.

[0140] For LTM, LTM supports subsequent LTM (e.g., subsequent LTM), where Subsequent LTM means that the subsequent LTM cell handover process between candidate cells does not require RRC reconfiguration by the network. In other words, after performing the mobility operation, the terminal will not autonomously delete the LTM configuration information. The LTM configuration information can continue to be used to trigger subsequent LTM (e.g., Subsequent LTM) even if RRC reconfiguration and update are not performed.

[0141] LTM supports the following scenarios:

[0142] 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:

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

[0144] -PCell changes in CA scenarios;

[0145] - 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.

[0146] Currently, only intra-DU and inter-DU intra-CU LTMs are supported, but support for inter-CU (or inter-node / gNB) LTMs will be expanded in the future. Inter-CU (inter-node / gNB) LTMs during SCG PSCell changes involve the mobile network (MN). The MN is responsible for coordinating the configuration of candidate PSCells in different CUs.

[0147] 4. LTM configuration:

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

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

[0150] LTM reference configuration;

[0151] One or more candidate cell configurations (using, for example, ltm-CandidateToReleaseList and ltm-CandidateToAddModList to add, modify, or delete candidate cell configurations);

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

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

[0154] candidate configuration identifier;

[0155] Candidate cell identifier;

[0156] Candidate configuration (represented by RRCReconfiguration).

[0157] For example, a candidate configuration may also be referred to as an LTM candidate configuration. A 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). A candidate configuration may be a complete candidate configuration or an incremental configuration relative to a reference configuration.

[0158] 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 set 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 candidate configurations. The incomplete candidate configuration is combined with the LTM reference configuration to obtain a complete candidate configuration.

[0159] Among them, the incomplete candidate configuration can also be called an incremental configuration. In other words, when the 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 configuration of the candidate cells, a complete configuration corresponding to all candidate cells of MCG LTM can be generated.

[0160] For SCG LTM, the incremental candidate configurations corresponding to all candidate cells of all SCG LTMs correspond to the same reference configuration. Based on this reference configuration and the incremental configurations of the candidate cells, a complete configuration corresponding to all candidate cells of the SCG LTM can be generated.

[0161] 5. LTM execution process:

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

[0163] The steps of LTM include:

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

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

[0166] Step 3. The terminal stores the candidate configuration and sends an RRC reconfiguration complete message (e.g., RRCReconfigurationComplete) to the gNB.

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

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

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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.

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

[0175] 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0189] LTM supports subsequent LTM, that is, it ensures that cell switching (Cell Switch) between multiple candidate LTM cells does not require RRC reconfiguration. In order to support incremental configuration during the LTM process, LTM introduces a reference configuration, where the reference configuration is provided by the network to the terminal and is common to a set of configured incomplete candidate configurations within the MCG or SCG. In other words, the candidate configuration can be an incremental configuration relative to the reference configuration. Of course, the candidate configuration can also be a complete candidate configuration. If the candidate configuration is an incremental configuration of the reference configuration, the terminal applies the candidate configuration based on the reference configuration when executing LTM.

[0190] In LTM, all MCG (or SCG) candidate cell groups share a common reference configuration. Since only intra-CU LTM is supported, the reference configuration is generated by the current node, and the node currently accessed by the terminal generates the corresponding candidate configuration based on this reference configuration. There is no need for information exchange between nodes or to specify which node generates the candidate configuration information.

[0191] However, LTM supports inter-gNB (or inter-gNB-CU) LTM. In order to support candidate nodes in generating candidate configurations for LTM candidate cells, the present disclosure provides the following information transmission method, device, and storage medium, which clarify the nodes that generate reference configurations, and can exchange reference configurations between nodes. It also clarifies that nodes generate complete candidate configurations or incremental candidate configurations, thereby achieving LTM interaction between nodes, supporting LTM configuration, and improving the availability of LTM configuration.

[0192] FIG2A is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to an information transmission method, which includes:

[0193] Step S2100 : The third node 103 sends the second message and / or the fourth message to the first node 101 .

[0194] In some embodiments, the second message is used to request the first node 101 to generate a reference configuration.

[0195] In some embodiments, the reference configuration is provided by a network device to the terminal and is common to a group of incomplete candidate configurations within the same cell group.

[0196] 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 set 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 candidate configurations. The incomplete candidate configuration is combined with the LTM reference configuration to obtain a complete candidate configuration.

[0197] Among them, the incomplete candidate configuration can also be called an incremental configuration. In other words, when the 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 configuration of the candidate cells, a complete configuration corresponding to all candidate cells of MCG LTM can be generated.

[0198] For SCG LTM, the incremental candidate configurations corresponding to all candidate cells of all SCG LTMs correspond to the same reference configuration. Based on this reference configuration and the incremental configurations of the candidate cells, a complete configuration corresponding to all candidate cells of the SCG LTM can be generated.

[0199] In some embodiments, the fourth message is used to request the first node 101 to send the third message to the second node 102 .

[0200] In some embodiments, the third message is used to request a reference configuration.

[0201] In some embodiments, the third node 103 may be an S-SN in an NR-DC scenario.

[0202] In some embodiments, the reference configuration is generated by the first node 101 , and the third node 103 may send a second message to the first node 101 , requesting the first node 101 to generate the reference configuration.

[0203] In some embodiments, the reference configuration is generated by the second node 102, and the third node 103 may send a fourth message to the first node 101, requesting the first node 101 to send a third message to the second node 102, so that the second node 102 generates the reference configuration based on the third message.

[0204] In some embodiments, the reference configuration is generated by the first node 101 and the second node 102, and the third node 103 can send a second message to the first node 101, requesting the first node 101 to generate the reference configuration, and / or send a fourth message to the first node 101, requesting the first node 101 to send a third message to the second node 102, so that the second node 102 generates the reference configuration based on the third message.

[0205] In some embodiments, step S2100 may not be performed. For example, if the first node 101 generates the reference configuration itself, step S2100 may not be performed.

[0206] In some embodiments, step S2100 may not be performed. For example, when the first node 101 actively sends the third message to the second node, step S2100 may not be performed.

[0207] Step S2101: The first node 101 determines a reference configuration.

[0208] In some embodiments, in a non-DC scenario, the first node 101 may be an S-MN or a C-MN.

[0209] In some embodiments, in a DC scenario, such as an NR-DC scenario, for an SCG LTM where the MCG does not change, the first node 101 may be an MN.

[0210] In the NR-DC scenario, for the MCG LTM released by the SCG, the first node 101 may be an S-MN or a C-MN.

[0211] In the NR-DC scenario, for the MCG LTM where the SCG does not change, the first node 101 may be an S-MN or a C-MN.

[0212] In some embodiments, the first node 101 may generate a reference configuration.

[0213] In some embodiments, the first node 101 may obtain a reference configuration from the second node 102 .

[0214] In some embodiments, in a non-DC scenario, the second node 102 may be a C-MN.

[0215] In some embodiments, in a DC scenario, such as an NR-DC scenario, for an SCG LTM where the MCG does not change, the second node 102 may be an S-SN or a C-SN.

[0216] In the NR-DC scenario, for the MCG LTM released by the SCG, the second node 102 may be a C-MN.

[0217] In the NR-DC scenario, for the MCG LTM whose SCG does not change, the second node 102 may be the S-SN.

[0218] In some embodiments, the first node 101 may generate a portion of the content in the reference configuration and obtain another portion of the content in the reference configuration from the second node 102 .

[0219] In some embodiments, in a non-DC scenario, the first node 101 may be an S-MN or a C-MN, and the second node 102 may be a C-MN.

[0220] In one example, in a non-DC scenario, the reference configuration only includes the MCG reference configuration, where the MCG reference configuration refers to the content associated with the MCG in the reference configuration.

[0221] In an example, in a non-DC scenario, when the first node 101 is an S-MN, the MCG reference configuration may be generated by the first node 101. The first node 101 determines a reference configuration, and the reference configuration only includes the MCG reference configuration generated by itself.

[0222] In an example, in a non-DC scenario, the first node 101 is an S-MN and may request the second node 102 to generate a reference configuration, where the second node 102 is a C-MN.

[0223] Exemplarily, the first node 101 (eg, S-MN) sends a third message to the second node 102 (eg, C-MN), where the third message is used to request a reference configuration.

[0224] Further, the second node 102 (C-MN) generates a reference configuration based on the third message. Specifically, the second node 102 (e.g., C-MN) generates an MCG reference configuration and sends a third response message to the first node 101 (e.g., S-MN), which includes the MCG reference configuration generated by the second node 102 (e.g., C-MN).

[0225] The first node 101 (eg, S-MN) determines a reference configuration based on the third response message. Specifically, the reference configuration only includes the MCG reference configuration.

[0226] In an example, in a non-DC scenario, the reference configuration may be generated only by the first node 101, and the reference configuration includes an MCG reference configuration, wherein the MCG reference configuration refers to the content associated with the MCG in the reference configuration.

[0227] In some embodiments, in a DC scenario, for example, in an NR-DC scenario, for an SCG LTM where the MCG does not change, the first node 101 may be an MN, and the second node 102 may be an S-SN or a C-SN.

[0228] In one example, in an NR-DC scenario, for an SCG LTM whose MCG remains unchanged, the reference configuration may include only an SCG reference configuration. The SCG reference configuration refers to the content associated with the SCG in the reference configuration. When the reference configuration includes only the SCG reference configuration, the first node 101 and the second node 102 continue to use the current MCG reference configuration by default. The MCG reference configuration refers to the content associated with the MCG in the reference configuration.

[0229] For example, in the NR-DC scenario, for the SCG LTM where the MCG has not changed, when the reference configuration may only include the SCG reference configuration, the first node 101 (MN) may send a third message to the second node 102 (e.g., S-SN or C-SN) to request the reference configuration. Specifically, the second node 102 (e.g., S-SN or C-SN) generates the SCG reference configuration based on the third message.

[0230] Further, the second node 102 (eg, S-SN or C-SN) sends a third response message to the first node 101 (eg, MN), which includes the SCG reference configuration generated by the second node 102 (S-SN or C-SN).

[0231] Exemplarily, in the NR-DC scenario, for the SCG LTM where the MCG is unchanged, when the reference configuration may only include the SCG reference configuration, the first node 101 (e.g., MN) may send the third message to the second node 102 (e.g., S-SN or C-SN) based on the fourth message sent by the third node 103. The third node 103 may be an S-SN.

[0232] Among them, if the second node 102 is also an S-SN, that is, the second node 102 and the third node 103 are the same node, the above process can be equivalent to the S-SN sending a fourth message to the MN, and the MN sending a third message to the S-SN based on the fourth message, so that the S-SN generates an SCG reference configuration based on the third message.

[0233] The first node 101 (eg, MN) determines a reference configuration, and the reference configuration only includes the SCG reference configuration generated by the second node 102 (eg, S-SN or C-SN).

[0234] In one example, in the NR-DC scenario, for an SCG LTM where the MCG remains unchanged, the reference configuration may include an MCG reference configuration and an SCG reference configuration. The MCG reference configuration refers to the content associated with the MCG in the reference configuration, and the SCG reference configuration refers to the content associated with the SCG in the reference configuration.

[0235] Accordingly, the first node 101 (e.g., MN) generates an MCG reference configuration. In addition, the first node 101 sends a third message to the second node 102 (e.g., S-SN or C-SN) to request a reference configuration. Specifically, the second node 102 (e.g., S-SN or C-SN) generates an SCG reference configuration based on the third message.

[0236] Further, the second node 102 (eg, S-SN or C-SN) sends a third response message to the first node 101 (eg, MN), which includes the SCG reference configuration generated by the second node 102 (eg, S-SN or C-SN).

[0237] For example, the first node 101 (MN) may receive a second message sent by the third node 103, where the second message is used to request the first node 101 (e.g., MN) to generate a reference configuration. Accordingly, the first node 101 (e.g., MN) generates an MCG reference configuration based on the second message. The third node 103 may be an S-SN.

[0238] Exemplarily, the first node 101 (e.g., MN) may receive a fourth message sent by the third node 103, where the fourth message is used to request the first node 101 (e.g., MN) to send a third message to the second node 102 (e.g., S-SN or C-SN). The third node 103 may be an S-SN.

[0239] The first node 101 (MN) determines a reference configuration, which includes an MCG reference configuration generated by itself and an SCG reference configuration generated by the second node 102 (eg, S-SN or C-SN).

[0240] In some embodiments, in a DC scenario, for example, in an NR-DC scenario, for an MCG LTM released by an SCG, the first node 101 may be an S-MN or a C-MN, and the second node 102 may be a C-MN.

[0241] In one example, in an NR-DC scenario, for an MCG LTM released by an SCG, the reference configuration only includes an MCG reference configuration, where the MCG reference configuration refers to the content associated with the MCG in the reference configuration.

[0242] In one example, in an NR-DC scenario, for an MCG LTM released by an SCG, when the first node 101 is an S-MN, an MCG reference configuration may be generated by the first node 101. The first node 101 determines a reference configuration, and the reference configuration only includes the MCG reference configuration generated by itself.

[0243] In one example, in the NR-DC scenario, for the MCG LTM released by the SCG, the first node 101 is the S-MN and can request the second node 102 to generate a reference configuration, and the second node 102 is the C-MN.

[0244] Exemplarily, the first node 101 (eg, S-MN) sends a third message to the second node 102 (eg, C-MN), where the third message is used to request a reference configuration.

[0245] Further, the second node 102 (e.g., C-MN) generates a reference configuration based on the third message. Specifically, the second node 102 (e.g., C-MN) generates an MCG reference configuration and sends a third response message to the first node 101 (e.g., S-MN), which includes the MCG reference configuration generated by the second node 102 (e.g., C-MN).

[0246] The first node 101 (eg, S-MN) determines a reference configuration based on the third response message. Specifically, the reference configuration only includes the MCG reference configuration.

[0247] In one example, in an NR-DC scenario, for an MCG LTM released by an SCG, when the first node 101 is a C-MN, an MCG reference configuration may be generated by the first node 101. The first node 101 determines a reference configuration, and the reference configuration only includes the MCG reference configuration generated by itself.

[0248] In some embodiments, in a DC scenario, for example, in an NR-DC scenario, for an MCG LTM in which the SCG is unchanged, the first node 101 may be an S-MN or a C-MN, and the second node 102 may be an S-MN.

[0249] In one example, in the NR-DC scenario, for the MCG LTM whose SCG has not changed, the reference configuration may only include the MCG reference configuration. The MCG reference configuration refers to the content associated with the MCG in the reference configuration. When the reference configuration only includes the MCG reference configuration, the first node 101 and the second node 102 continue to use the current SCG reference configuration by default. The SCG reference configuration refers to the content associated with the SCG in the reference configuration.

[0250] Exemplarily, in the NR-DC scenario, for the MCG LTM where the SCG has not changed, the reference configuration may only include the MCG reference configuration. When the first node 101 is the S-MN, the reference configuration may be generated by the first node 101, specifically, the MCG reference configuration.

[0251] The first node 101 determines a reference configuration, and the reference configuration only includes the MCG reference configuration.

[0252] Exemplarily, in the NR-DC scenario, for the MCG LTM where the SCG has not changed, the reference configuration may only include the MCG reference configuration. When the first node 101 is the S-MN, the S-MN may request the C-SN to generate the reference configuration. Specifically, the C-SN generates the MCG reference configuration.

[0253] The first node 101 (eg, S-SN) determines a reference configuration, which only includes the MCG reference configuration generated by the C-SN.

[0254] In one example, in an NR-DC scenario, for an MCG LTM whose SCG remains unchanged, the reference configuration may include an MCG reference configuration and an SCG reference configuration. The MCG reference configuration refers to the content associated with the MCG in the reference configuration, and the SCG reference configuration refers to the content associated with the SCG in the reference configuration.

[0255] Exemplarily, in the NR-DC scenario, for the MCG LTM where the SCG has not changed, when the reference configuration may include the MCG reference configuration and the SCG reference configuration, when the first node 101 is an S-MN, the first node 101 may generate the reference configuration, specifically, generate the MCG reference configuration. In addition, the first node 101 (e.g., S-MN) may send a third message to the second node 102 (e.g., S-SN) to request the reference configuration. Specifically, the second node 102 (e.g., S-SN) generates the SCG reference configuration based on the third message.

[0256] Further, the second node 102 (eg, S-SN) sends a third response message to the first node 101 (eg, S-MN), which includes the SCG reference configuration generated by the second node 102 (S-SN).

[0257] The first node 101 (eg, S-MN) determines a reference configuration, and the reference configuration includes an MCG reference configuration generated by the first node 101 (eg, S-MN) and an SCG reference configuration generated by the second node 102 (eg, S-SN).

[0258] Exemplarily, in the NR-DC scenario, for the MCG LTM where the SCG has not changed, when the reference configuration may include the MCG reference configuration and the SCG reference configuration, when the first node 101 is the S-MN, the first node 101 (e.g., S-MN) may request the C-SN to generate a reference configuration. Specifically, the C-SN generates the MCG reference configuration, and the C-SN sends the generated MCG reference configuration to the first node 101 (e.g., S-MN). In addition, the first node 101 (e.g., S-MN) may send a third message to the second node 102 (e.g., S-SN) to request the reference configuration. Specifically, the second node 102 (e.g., S-SN) generates the SCG reference configuration based on the third message.

[0259] Further, the second node 102 (eg, S-SN) sends a third response message to the first node 101 (eg, S-MN), which includes the SCG reference configuration generated by the second node 102 (eg, S-SN).

[0260] The first node 101 (eg, S-MN) determines a reference configuration, and the reference configuration includes an MCG reference configuration generated by a C-SN and an SCG reference configuration generated by a second node 102 (eg, S-SN).

[0261] In the above embodiment, the third message may be any of the following messages:

[0262] Handover Request message;

[0263] SN Addition Request message;

[0264] SN Modification Request message;

[0265] SN reconfiguration complete (SNReconfigurationComplete) message;

[0266] SN modification confirmation (SNModificationConfirm) message;

[0267] SN Change Confirm message;

[0268] Handover preparation information (HandoverRreprationInformation);

[0269] CG-configInfo;

[0270] The first Xn message is used for LTM request;

[0271] A first inter-node Radio Resource Control (inter-node RRC) message, where the first inter-node RRC message is used for LTM request.

[0272] In one example, the first Xn message may be an Xn message newly defined for LTM, which may be used for LTM request.

[0273] In one example, the first inter-node RRC message may be carried by an Xn message.

[0274] In an example, when the first node 101 is an S-MN and the second node 102 is a C-MN, the third message may be any one of a handover request message, a first Xn message, or a first inter-node RRC message.

[0275] In one example, when the first node 101 is an MN and the second node 102 is an SN, the third message can be any one of an SN addition request message, an SN modification request message, an SN reconfiguration completion message, an SN modification confirmation message, an SN change confirmation message, a first Xn message, or a first inter-node RRC message.

[0276] In the above embodiment, the third response message may be any of the following messages:

[0277] Handover Request Acknowledge message;

[0278] SN Addition Request Acknowledge message;

[0279] SN Modification Request Acknowledge message;

[0280] SN Modification Required message;

[0281] SN Change Required message;

[0282] Handover Command (handoverCommand);

[0283] CG-config;

[0284] CG-CadidateList;

[0285] The second Xn message is used for LTM request confirmation;

[0286] A first inter-node RRC message, where the first inter-node RRC message is used for an LTM request;

[0287] The second inter-node RRC message is used for LTM request confirmation.

[0288] In one example, the second Xn message may be an Xn message newly defined for LTM, which may be used for LTM request confirmation or LTM information transmission.

[0289] In one example, the second inter-node RRC message may be carried by an Xn message.

[0290] In an example, the third message (reference configuration request message) and the third response message (transmission of reference configuration) may be transmitted via an Xn message or via an inter-node RRC message.

[0291] For example, when Xn messages are used for transmission, the reference configuration request message and / or reference configuration message may be transmitted between the S-MN and the C-MN through the following messages:

[0292] The third message sent from the S-MN to the C-MN includes but is not limited to one or more of the following:

[0293] For example, HANDOVER REQUEST;

[0294] The first Xn message used for LTM request (or Xn message used for LTM information transmission).

[0295] Exemplarily, the third response message sent from the C-MN to the S-MN includes, but is not limited to, one or more of the following:

[0296] For example, HANDOVER REQUEST ACKNOWLEDGE;

[0297] The second Xn message used for LTM request confirmation (or the Xn message used for LTM information transmission).

[0298] Exemplarily, the third message and the fourth message may be transmitted between the MN and the SN through the following messages:

[0299] The messages sent by the MN to the SN include but are not limited to one or more of the following:

[0300] SN Addition Request;

[0301] SNModificationRequest;

[0302] SNReconfigurationComplete;

[0303] SNModificationConfirm;

[0304] SN ChangeConfirm;

[0305] The first Xn message used for LTM request (or Xn message used for LTM information transmission).

[0306] The messages sent by the SN to the MN include but are not limited to one or more of the following:

[0307] HandoverRequestAcknowledge;

[0308] SN Addition RequestAcknowledge;

[0309] SNModificationRequestAcknowledge;

[0310] SNModification Required;

[0311] SN ChangeRequired;

[0312] The first Xn message used for an LTM request (or an Xn message for an LTM information transmission).

[0313] Exemplarily, the first node 101 sends a third message to the second node 102, which includes an indication information, and the indication information can be an enumeration type. When the indication information is set to "true" or "request" or other specified values, or the third message includes the indication information, the second node 102 should generate a corresponding reference configuration based on the indication information.

[0314] For example, the third message includes an information unit of LTM configuration related information, including a reference configuration request indication, as shown in Table 1.

[0315] Table 1

[0316] For another example, the third message may include an LTM reference configuration request, as shown in Table 2.

[0317] Table 2

[0318] Exemplarily, the second node 102 may carry the generated reference configuration in the third response message, as shown in Table 3, for example.

[0319] Table 3

[0320] Alternatively, an information element (IE) can be included in the third message or the third response message (for example, the first Xn message or the second Xn message). This IE is used for reference information configuration. The content of this IE is shown in Table 4. The third response message can selectively include a reference configuration request indication or an LTM reference configuration.

[0321] Table 4

[0322] For example, for SCG LTM, that is, the transmission of reference configuration requests and / or reference configurations between MN and SN, in order to support subsequent primary and secondary cell addition / change (subsequent mobility CPAC, SCPAC), the transmission of reference configurations has been supported, and indication information (such as LTM indication information) can be added during the transmission process. The indication parameter (such as S-CPAC Reference Configuration Request) can also be used to indicate the request for LTM reference configuration.

[0323] Exemplarily, it is also transmitted through an inter-node RRC message (the inter-node RRC message is also transmitted by being included in the above-mentioned Xn message).

[0324] The reference configuration request and / or reference configuration may be transmitted between the S-MN and the C-MN via the following inter-node RRC messages:

[0325] The messages sent from the S-MN to the C-MN include but are not limited to one or more of the following:

[0326] Handover preparation information (HandoverPreparationInformation);

[0327] The first inter-node RRC message for LTM request (or inter-node RRC message for LTM information transmission).

[0328] The messages sent from the C-MN to the S-MN include but are not limited to one or more of the following:

[0329] Handover Command (HandoverCommand);

[0330] A second inter-node RRC message for LTM request confirmation (or an inter-node RRC message for LTM information transmission).

[0331] The reference configuration request and reference configuration can be transmitted between MN and SN through the following messages:

[0332] The messages sent by the MN to the SN include but are not limited to one or more of the following:

[0333] CG-ConfigInfo;

[0334] The first inter-node RRC message for LTM request (or inter-node RRC message for LTM information transmission).

[0335] The messages sent by the SN to the MN include but are not limited to one or more of the following:

[0336] CG-Config;

[0337] CG-CandidateList;

[0338] The first inter-node RRC message for LTM request.

[0339] Exemplarily, the specific implementation method is similar to including a reference configuration request and / or a reference configuration in an Xn message, as shown below:

[0340] For example, for SCG LTM, that is, the transmission of reference configuration between MN and SN, the transmission of reference configuration is currently supported, and indication information (such as LTM indication information) can be added to indicate that the corresponding parameters (such as scpac-ReferenceConfigurationSCG-r18) can also be used to indicate the reference configuration of the requested LTM.

[0341] The above is merely an exemplary description, and the present disclosure does not limit the content of the third message and the third response message.

[0342] In some embodiments, the second message is used to request the first node to send the first message to the second node. The first message is used to request the second node to generate a candidate configuration, and the first message includes any of the following:

[0343] First indication information, where the first indication information is used to instruct the second node to generate a complete candidate configuration;

[0344] The second indication information is used to instruct the second node to generate an incremental candidate configuration based on a reference configuration, where the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node.

[0345] In some embodiments, the MCG LTM and the SCG LTM have only one reference configuration, that is, the MCG LTM and the SCG LTM correspond to the same reference configuration.

[0346] In some embodiments, the MCG LTM corresponds to one reference configuration, and the SCG LTM corresponds to another reference configuration, that is, the MCG LTM and the SCG LTM correspond to different reference configurations.

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

[0348] In some embodiments, the first message is used to request the second node 102 to generate a mobility candidate configuration triggered by layer 1 or layer 2. The first message may include any of the following:

[0349] First indication information, where the first indication information is used to instruct the second node to generate a complete candidate configuration;

[0350] Second indication information, where the second indication information is used to instruct the second node to generate an incremental candidate configuration based on the reference configuration.

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

[0352] In some embodiments, the first message may further include at least one of the following:

[0353] Reference configuration;

[0354] The third indication information is used to request the second node to generate a candidate configuration for the first node or the LTM candidate cell.

[0355] In one example, the third indication information may occupy one bit. When the bit value of this bit is set to 1, it may be used to indicate that the second node 102 is requested to generate a candidate configuration for the first node. When the bit value of this bit is set to 0, it may be used to indicate that the second node 102 is requested to generate a candidate configuration for the LTM candidate cell, and vice versa.

[0356] In one example, when the first message includes a reference configuration, the reference configuration is associated with other candidate nodes other than the second node 102 .

[0357] Exemplarily, when the first node 101 is an S-MN and the second node 102 is a C-MN, the first message may include reference configurations generated by other C-MNs except the second node C-MN that generates the reference configuration.

[0358] Exemplarily, when the first node 101 is an MN and the second node 102 is a C-SN, the first message may include reference configurations generated by other C-SNs except the second node C-SN that generates the reference configuration.

[0359] In an example, the first message includes both the second indication information and the reference configuration determined by the first node 101 .

[0360] In one example, the first message includes first indication information.

[0361] In one example, the first message includes first indication information and third indication information.

[0362] In an example, the first message includes the second indication information, the reference configuration determined by the first node 101 and the third indication information.

[0363] The above description is merely an exemplary description, and the present disclosure does not limit the message content included in the first message.

[0364] In some embodiments, the type of the first message may be the same as the type of the third message, and details are not repeated here.

[0365] In an example, when the first message is an Xn message, the first indication information may be as shown in Table 5, for example.

[0366] Table 5

[0367] In an example, when the first message is an inter-node RRC message, the first indication information may be as follows:

[0368] Step S2103: The second node 102 generates a candidate configuration.

[0369] In some embodiments, the first message includes first indication information, and the second node 102 may generate a complete candidate configuration.

[0370] In some embodiments, the first message includes the second indication information and a reference configuration, and the second node 102 may generate an incremental candidate configuration based on the reference configuration.

[0371] In some embodiments, the first message does not include a reference configuration, and the second node 102 may generate a complete candidate configuration.

[0372] In some embodiments, the candidate configuration is a configuration portion of an RRC reconfiguration message associated with the candidate cell.

[0373] Step S2104 : The second node 102 sends a first response message to the first node 101 .

[0374] In some embodiments, the first response message includes the candidate configuration generated by the second node 102 .

[0375] In some embodiments, the first response message may also include first indication information or second indication information.

[0376] Exemplarily, the second node 102 may determine whether the candidate configuration generated or prepared for the terminal is a complete candidate configuration. If it is a complete candidate configuration, the first response message may include the first indication information. Otherwise, the first response message may include the second indication information, or the first response message may not include the integrity indication information (e.g., the first indication information and the second indication information).

[0377] In some embodiments, the first response message may be of the same type as the third response message, which will not be described in detail here.

[0378] 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.

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

[0380] 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.

[0381] 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.

[0382] In some embodiments, the information transmission method involved in the embodiments of the present disclosure may include at least one of steps S2100 to S2104. For example, step S2100 can be implemented as an independent embodiment, 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 S2102+S2103+S2104 can be implemented as an independent embodiment, and steps S2100 to S2104 can be implemented as independent embodiments, but are not limited thereto.

[0383] In some embodiments, step S2100 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the first node 101 generates a reference configuration on its own and / or the first node 101 proactively sends a third message to the second node, step S2100 may not be performed.

[0384] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second node 102 needs to generate a complete candidate configuration, step S2101 may not be performed.

[0385] 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 obtains the first message from an execution subject other than the first node, step S2102 may not be performed.

[0386] In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second node 102 does not need to generate a candidate configuration, step S2103 may not be performed.

[0387] 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 has provided the candidate configuration to the first node 101, step S2104 may not be performed.

[0388] In some embodiments, steps S2100 to S2104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0389] In some embodiments, the execution order of steps S2100 to S2104 is not limited.

[0390] In the above embodiment, the nodes for generating reference configurations are clearly defined, and reference configurations can be exchanged between nodes. It is also clear that nodes generate complete candidate configurations or incremental candidate configurations, thereby realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM configuration.

[0391] FIG2B is a schematic diagram of a method for generating information according to an embodiment of the present disclosure. As shown in FIG2B , the method can be performed by the first node 101 and / or the second node 102, and includes the following steps:

[0392] Step S2201: Generate a reference configuration.

[0393] In some embodiments, in a non-DC scenario, the first node 101 may be an S-MN or a C-MN, and the second node 102 may be a C-MN.

[0394] In some embodiments, the first node 101 (eg, an S-MN or a C-MN) may generate an MCG reference configuration.

[0395] In some embodiments, the first node 101 (eg, S-MN) may not generate the reference configuration, but the second node 102 (eg, C-MN) may generate the reference configuration.

[0396] In the non-DC scenario, the reference configuration is generated only by the first node 101 .

[0397] In some embodiments, in a DC scenario, such as an NR-DC scenario, for an SCG LTM where the MCG does not change, the first node 101 may be an MN, and the second node 102 may be an S-SN or a C-SN.

[0398] In some embodiments, the first node 101 (e.g., MN) can generate an MCG reference configuration. In addition, the second node 102 (e.g., S-SN or C-SN) can also generate a reference configuration. Specifically, the second node 102 (e.g., S-SN or C-SN) generates an SCG reference configuration. The final reference configuration includes an MCG reference configuration and an SCG reference configuration.

[0399] In some embodiments, the first node 101 (e.g., MN) may not generate the reference configuration, but instead the second node 102 (e.g., S-SN or C-SN) may generate the reference configuration. In this case, the reference configuration is generated only by the second node 102, i.e., the reference configuration only includes the SCG reference configuration.

[0400] In some embodiments, in a DC scenario, such as an NR-DC scenario, for an MCG LTM released by an SCG, the first node 101 may be an S-MN or a C-MN, and the second node 102 may be a C-MN.

[0401] In some embodiments, the first node 101 (eg, an S-MN or a C-MN) may generate an MCG reference configuration.

[0402] In some embodiments, the first node 101 (eg, S-MN) may not generate the reference configuration, but the second node 102 (eg, C-MN) may generate the reference configuration.

[0403] In the NR-DC scenario, for the MCG LTM released by the SCG, the reference configuration is only generated by the first node 101, that is, the reference configuration only includes the MCG reference configuration.

[0404] In some embodiments, in a DC scenario, such as an NR-DC scenario, for an MCG LTM where the SCG does not change, the first node 101 may be an S-MN or a C-MN, and the second node 102 may be an S-SN.

[0405] In some embodiments, the first node 101 (e.g., S-MN or C-MN) may generate an MCG reference configuration. In this case, the second node 102 (e.g., S-SN) does not need to generate a reference configuration. Accordingly, the reference configuration only includes the MCG reference configuration generated by the first node 101.

[0406] In some embodiments, the first node 101 (e.g., S-MN or C-MN) may generate an MCG reference configuration. At this time, the second node 102 (e.g., S-SN) generates an SCG reference configuration. Accordingly, the reference configuration includes the MCG reference configuration generated by the first node 101 and the SCG reference configuration generated by the second node 102.

[0407] In the above embodiment, the reference configuration may be generated by the first node or the second node, or by the first node and the second node, which clarifies the nodes for generating the reference configuration and improves the flexibility of generating the reference configuration.

[0408] FIG2C is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2C , the method may include the following steps:

[0409] Step S2301 : The third node 103 sends a second message and / or a fourth message to the first node 101 .

[0410] In some embodiments, the second message is used to request the first node 101 to generate a reference configuration.

[0411] In some embodiments, the fourth message is used to request the first node 101 to send the third message to the second node 102 .

[0412] In some embodiments, the third message is used to request a reference configuration.

[0413] In some embodiments, the third node 103 may be an S-SN in an NR-DC scenario.

[0414] The specific implementation method refers to step S2100 and will not be repeated here.

[0415] Step S2302: The first node 101 generates a reference configuration.

[0416] The specific implementation process can refer to the process of the first node 101 generating a reference configuration in steps S2101 and S2201, which will not be repeated here.

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

[0418] In some embodiments, the message type of the third message and the manner in which the request message is carried therein have been introduced in the aforementioned step S2101 and will not be repeated here.

[0419] Step S2304: The second node 102 generates a reference configuration.

[0420] The second node 102 may generate a reference configuration based on the third message. The specific implementation process may refer to the process of the second node 102 generating the reference configuration in steps S2101 and S2201, which will not be repeated here.

[0421] Step S2305 : The second node 102 sends a third response message to the first node 101 , wherein the third response message includes a reference configuration generated by the second node 102 .

[0422] In some embodiments, the message type of the third response message and the method of providing the reference configuration to the first node 101 have been introduced in the aforementioned step S2101 and will not be repeated here.

[0423] In some embodiments, steps S2301 to S2305 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0424] In some embodiments, the execution order of steps S2301 to S2305 is not limited.

[0425] In the above embodiment, the generated reference configuration can be transmitted between nodes, and the purpose of exchanging reference configurations between nodes is to improve the availability of the LTM configuration.

[0426] FIG2D is a flow chart of a method for determining information according to an embodiment of the present disclosure. As shown in FIG2D , the method may be performed by the first node 101 or the second node 102, and includes the following steps:

[0427] Step S2401: Determine integrity indication information of the candidate configuration.

[0428] In some embodiments, the first node 101 may determine whether the second node 102 is required to generate or prepare a complete candidate configuration for the terminal.

[0429] In an example, if the first node 101 determines that the second node 102 is required to generate or prepare a complete candidate configuration for the terminal, first indication information may be determined, where the first indication information is used to indicate a request to the second node to generate a complete candidate configuration.

[0430] In an example, if the first node 101 determines that the second node 102 is not required to generate or prepare a complete candidate configuration for the terminal, second indication information may be determined, where the second indication information is used to indicate a request for the second node to generate an incremental candidate configuration.

[0431] In some embodiments, the second node 102 may determine whether the candidate configuration generated or prepared for the terminal is a complete candidate configuration.

[0432] In one example, the second node 102 may determine the first indication information when generating or preparing a complete candidate configuration for the terminal, and determine the second indication information when generating or preparing an incomplete candidate configuration (or incremental candidate configuration) for the terminal.

[0433] In some embodiments, the first node 101 may determine whether the second node 102 is required to generate or prepare a complete candidate configuration for the terminal, and the second node 102 may determine whether the candidate configuration generated or prepared for the terminal is a complete candidate configuration.

[0434] In some embodiments, the first indication information and the second indication information may be indicated by a single integrity indication information. For example, when the integrity indication information is set to "true" or a first value, it is equivalent to the first indication information; and when it is set to "false" or a second value, it is equivalent to the second indication information. For specific implementation, please refer to the specific content of step S2102.

[0435] In the above embodiment, the node for determining the integrity indication information is clarified, thereby improving the availability of candidate configurations.

[0436] FIG2E is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2E , the method may include the following steps:

[0437] Step S2501: The first node 101 sends a first message to the second node 102, wherein the message includes integrity indication information.

[0438] In some embodiments, the first node 101 may include integrity indication information in the first message sent to the second node 102. The integrity indication information may be first indication information or second indication information. The specific implementation process is similar to step S2102 and will not be repeated here.

[0439] Step S2502: The second node 102 sends a first response message to the first node 101, which includes a candidate configuration and integrity indication information.

[0440] In some embodiments, the second node 102 may send integrity indication information to the first node 101 while sending the candidate configuration.

[0441] In some embodiments, step S2501 and step S2502 may be performed one by one, or both may be performed.

[0442] In some embodiments, the execution order of steps S2501 to S2502 is not limited.

[0443] In the above embodiment, integrity indication information can be transmitted between nodes, and availability is high.

[0444] 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:

[0445] Step S3100: Obtain the second message and / or the fourth message.

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

[0447] In some embodiments, the first node 101 obtains the second message and / or the fourth message determined according to a predefined rule.

[0448] In some embodiments, the first node 101 performs processing to obtain the second message and / or the fourth message.

[0449] In some embodiments, step S3100 is omitted, the first node 101 autonomously implements the functions indicated by the second message and / or the fourth message, or the first node 101 obtains the second message and / or the fourth message based on predefined rules or protocol agreements, or the above functions are default or default.

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

[0451] Step S3101: Determine a reference configuration.

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

[0453] Step S3102, sending the first message.

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

[0455] In some embodiments, the second node 102 sends the first message.

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

[0457] Step S3103: Obtain candidate configurations.

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

[0459] In some embodiments, the first node 101 obtains candidate configurations determined according to predefined rules.

[0460] In some embodiments, the first node 101 performs processing to obtain the candidate configuration.

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

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

[0463] In some embodiments, steps S3100 to S3103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0464] In some embodiments, the execution order of steps S3100 to S3103 is not limited.

[0465] In the above embodiment, the first node can serve as a node for generating a reference configuration, and can obtain the reference configuration generated by the second node from the second node. In addition, the first node can request the second node to generate a complete candidate configuration or an incremental candidate configuration, thereby realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM configuration.

[0466] 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:

[0467] Step S3201: Generate a reference configuration.

[0468] In some embodiments, the optional implementation of the second node 102 generating the reference configuration can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0469] Step S3202, obtain the first message.

[0470] 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.

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

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

[0473] In some embodiments, step S3202 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.

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

[0475] Step S3203: Generate candidate configurations.

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

[0477] Step S3204: Send a first response message including the candidate configuration.

[0478] In some embodiments, the second node 102 sends a first response message including the candidate configuration to the first node 101 .

[0479] In some embodiments, the first node 101 receives a first reply message including a candidate configuration.

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

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

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

[0483] In the above embodiment, the second node can serve as a node for generating a reference configuration and can provide the generated reference configuration to the first node. In addition, the second node can generate a complete candidate configuration or an incremental candidate configuration based on the request of the first node, thereby realizing LTM interaction between nodes, supporting the purpose of LTM configuration, and improving the availability of LTM configuration.

[0484] 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:

[0485] Step S3300: Send the second message and / or the fourth message.

[0486] In some embodiments, the third node 103 sends the second message and / or the fourth message to the first node 101 .

[0487] In some embodiments, the first node 101 receives the second message and / or the fourth message.

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

[0489] In the above embodiment, the third node can request the first node to generate a reference configuration, or request the first node to send a third request to the second node, thereby requesting the second node to generate a reference configuration. This clarifies the node that generates the reference configuration and improves the availability of the LTM configuration.

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

[0491] In the disclosed embodiments, a method for generating and transmitting a reference configuration for inter-CU LTM is proposed. First, the invention clarifies the generation of reference configurations for MCG LTM and SCG LTM, and how to transmit the reference configurations between a source node and candidate nodes, and between a primary node and a secondary node.

[0492] Taking into account that the candidate configuration can be a complete candidate configuration (that is, the configuration that needs to be applied to finally execute LTM does not need to be generated based on a reference configuration), the present invention also clarifies which nodes determine that the configuration corresponding to the candidate PSCell is a complete candidate configuration, and the transmission method of the corresponding candidate configuration indication information.

[0493] In the embodiment of the present disclosure, in order to support the incremental configuration of inter-CU LTM, the S-MN or S-SN generates a reference configuration, or the S-MN or S-SN sends an indication information to instruct the C-MN or C-SN to generate a reference configuration. After generating the reference configuration, the C-MN or C-SN sends the generated reference configuration to the MN through an Xn message or an inter-node RRC message. When the MN requests other C-MN / C-SN to prepare LTM for the UE, the MN carries the reference configuration, and the C-MN / C-SN generates a candidate configuration based on the reference configuration.

[0494] Secondly, the candidate configuration can be a complete configuration. Whether to generate a complete candidate configuration for a candidate PSCell can be determined by the S-MN or S-SN. That is, the request message for requesting LTM configuration carries an indication that instructs the C-MN / C-SN to generate a complete candidate configuration for the corresponding candidate PSCell. Alternatively, the C-MN / C-SN can determine whether to generate a complete candidate configuration for the candidate PSCell by carrying an indication in the response message containing the candidate configuration, indicating that the LTM candidate configuration is a complete candidate configuration.

[0495] Example 1: Generation of reference configuration.

[0496] Scenario 1: MCG LTM in a non-DC scenario.

[0497] Both S-MN and C-MN can generate reference configurations, which are represented by RRCReconfiguration messages. This reference configuration only includes MCG-related configurations and does not include SCG-related configurations.

[0498] The S-MN may send a request message to request the C-MN to generate a reference configuration.

[0499] Scenario 2: SCG LTM without MCG change in NR-DC.

[0500] The reference configuration can be jointly generated by the MN and the S-SN or C-SN. The MN generates the MCG part of the reference configuration, and the S-SN or C-SN generates the SCG part of the reference configuration. The reference configuration is represented by an RRCReconfiguration message.

[0501] The MN may request the S-SN or C-SN to generate a reference configuration.

[0502] Alternatively, the S-SN may request the MN to generate a reference configuration, or the S-SN may request the MN to initiate a request to the C-SN to request the C-SN to generate a reference configuration.

[0503] Scenario 3: SCG LTM (MCG LTM with SCG) released by SCG in the NR-DC scenario.

[0504] The generation of the reference configuration is the same as that in Scenario 1 and will not be repeated here.

[0505] Scenario 4: MCG LTM without SCG in the NR-DC scenario.

[0506] The reference configuration is jointly generated by the S-MN or C-MN and the S-SN. The S-MN or T-MN generates the MCG portion of the reference configuration, and the S-SN generates the SCG portion of the reference configuration. The reference configuration is represented by an RRCReconfiguration message.

[0507] The MN may request the S-SN and / or C-MN to generate a reference configuration.

[0508] Exemplarily, the reference configuration request message and the corresponding reference configuration may be applicable to the entire MCG or SCG, ie, the MCG LTM or SCG LTM has only one reference configuration.

[0509] For example, the reference configuration request message and the corresponding reference configuration may be applicable to a specific C-SN or C-MN, i.e., each C-MN and C-SN corresponds to a reference configuration. The reference configurations of different C-MNs and C-SNs may be the same or different.

[0510] Example 2, transmission of reference configuration.

[0511] Scenario 1: MCG LTM in a non-DC scenario.

[0512] Step 1: The S-MN generates a reference configuration, or sends a request message (third message) to request any C-MN to generate a reference configuration. After generating the reference configuration, the C-MN sends the reference configuration to the S-MN.

[0513] Step 2: The S-MN sends the reference configuration to the C-MN (other C-MNs except the C-MN generating the reference configuration may be excluded), requesting the C-MN to generate candidate configurations based on the reference configuration.

[0514] Scenario 2: SCG LTM without MCG change in NR-DC.

[0515] Step 1: MN receives the SCG reference configuration generated by S-SN or C-SN.

[0516] Step 2: The MN sends the reference configuration to the C-SN (other C-SNs except the C-SN generating the reference configuration may be excluded), requesting the C-SN to generate candidate configurations based on the reference configuration.

[0517] In step 2, the MN may only send the SCG reference configuration, and the C-SN may generate the SCG part of the candidate configuration based on this SCG reference configuration. The MN may determine whether to include the MCG part based on the received SCG reference configuration and the SCG part of the candidate configuration, based on the network implementation, and then generate the LTM reference configuration and one or more candidate configurations that are finally sent to the terminal.

[0518] Scenario 3: SCG LTM (MCG LTM with SCG) released by SCG in the NR-DC scenario.

[0519] The transmission of the reference configuration is the same as that in scenario 1 and is not described here.

[0520] Scenario 4: MCG LTM without SCG in the NR-DC scenario.

[0521] Step 1: S-MN receives the SCG reference configuration generated by S-SN or the MCG part of the reference configuration generated by S-MN, or sends a request message to request any C-MN to generate a reference configuration. C-MN sends the MCG part of the reference configuration to S-MN.

[0522] Step 2: The S-MN sends the reference configuration to the C-MN (other C-MNs except the C-MN generating the reference configuration may be excluded), requesting the C-MN to generate candidate configurations based on the reference configuration.

[0523] In step 2, the S-MN may only send one or more of the MCG part and the SCG part in the reference configuration. The C-MN determines the candidate configuration based on the MCG part of this reference configuration (which may include the MCG part and the SCG part. The C-MN may request the S-SN to provide the SCG part according to the existing process). The MN may determine the reference configuration based on the SCG and MCG parts of the received reference configuration, as well as the candidate configuration received from the C-MN, and then determine the LTM reference configuration and one or more candidate configurations finally sent to the UE.

[0524] The specific implementation method of reference information transmission is as follows:

[0525] The request and transmission of the reference configuration may be transmitted via an Xn message or an inter-node RRC message.

[0526] Transmitted via Xn messages:

[0527] The following messages may be used to transmit reference configuration requests and / or reference configurations between the S-MN and the T-MN:

[0528] The message sent from the S-MN to the T-MN includes but is not limited to one or more of the following: HANDOVER REQUEST or an Xn message for LTM request (or an Xn message for LTM information transmission) or other Xn messages.

[0529] The message sent from the T-MN to the S-MN includes but is not limited to one or more of the following: HANDOVER REQUEST ACKNOWLEDGE or an Xn message for LTM request confirmation (or an Xn message for LTM information transmission).

[0530] The MN and SN can transmit the reference configuration request and reference configuration through the following messages:

[0531] The message sent by the MN to the SN includes but is not limited to one or more of the following: SN ADDITION REQUEST, SN MODIFICATION REQUEST, SN RECONFIGURATION COMPLETE, SN MODIFICATION CONFIRM, SN CHANGE CONFIRM or an Xn message for LTM request (or an Xn message for LTM information transmission) and other Xn messages

[0532] The message sent by the SN to the MN includes but is not limited to one or more of the following: SN ADDITION REQUEST ACKNOWLEDGE, SN MODIFICATION REQUEST ACKNOWLEDGE, SN MODIFICATION REQUIRED, SN CHANGE REQUIRED or an Xn message for LTM request (or LTM information transmission) Xn message.

[0533] Exemplarily, the S-MN / S-SN (first node) sends an Xn message carrying a reference configuration request message to the C-MN / C-SN / S-MN (second node). The request message may be of an enumeration type. If the request message is configured as "true or Request or other specified value" or includes a request message, the second node needs to include the reference configuration of the LTM (at least the MCG part) in the corresponding response message, as shown in Table 1 or Table 2.

[0534] Exemplarily, the second node sends the generated reference configuration to the first node to notify the first node of the reference configuration requested by the first node, or the S-MN (third node) sends an Xn message carrying the reference configuration to the C-MN / C-SN (fourth node), requesting the C-MN to prepare a candidate configuration for the UE. The C-MN determines the candidate configuration based on the reference configuration (at least including the MCG part) and sends it to the S-MN through a corresponding response message, as shown in Table 3.

[0535] Exemplarily, an IE may be included in the Xn message, which is used for reference information configuration. The content of this IE is as follows. The corresponding Xn message may selectively include a reference configuration request indication or an LTM reference configuration, as shown in Table 4.

[0536] For example, for SCG LTM, that is, the transmission of reference configuration requests and / or reference configurations between MN and SN, in order to support SCPAC, which already supports the transmission of reference configurations, indication information (such as LTM indication) can be added. The indication parameter (S-CPAC Reference Configuration Request) can also be used to indicate the reference configuration of the requested LTM.

[0537] Transmitted through inter-node RRC message (inter-node RRC message is also transmitted by being included in the above Xn message).

[0538] The reference configuration request and / or reference configuration may be transmitted between the S-MN and the T-MN via the following inter-node RRC message.

[0539] The message sent from the S-MN to the T-MN includes but is not limited to one or more of the following: HandoverPreparationInformation or an inter-node RRC message for LTM request (or an inter-node RRC message for LTM information transmission) and other inter-node RRC messages.

[0540] The message sent from the T-MN to the S-MN includes but is not limited to one or more of the following: HandoverCommand or an inter-node RRC message for LTM request confirmation (or an inter-node RRC message for LTM information transmission) and other inter-node RRC messages.

[0541] The MN and SN can transmit the reference configuration request and reference configuration through the following messages:

[0542] The message sent by the MN to the SN includes but is not limited to one or more of the following: CG-ConfigInfo or an inter-node RRC message for LTM request (or an inter-node RRC message for LTM information transmission) and other inter-node RRC messages.

[0543] The message sent by the SN to the MN includes but is not limited to one or more of the following: CG-Config, CG-CandidateList or inter-node RRC messages such as inter-node RRC messages for LTM request (or inter-node RRC messages for LTM information transmission).

[0544] Exemplarily, the specific implementation method is similar to including the reference configuration request and / or reference configuration in the Xn message, as follows:

[0545] For example, for SCG LTM, that is, the transmission of reference configuration between MN and SN, in order to support SCPAC, which already supports the transmission of reference configuration, indication information (such as LTM indication) can be added to indicate that the corresponding parameter (scpac-ReferenceConfigurationSCG-r18) can also be used to indicate the reference configuration of the requested LTM.

[0546] Example 3: Determination and transmission of complete information indication of candidate configuration

[0547] Scenario 1: MCG LTM in a non-DC scenario.

[0548] The S-MN instructs one or more C-MNs (or one or more candidate PCells) to generate a complete candidate configuration. The S-MN sends a first message to the C-MN, where the first message includes information indicating whether to request the C-MN to generate a complete candidate configuration.

[0549] Implementation method 1: In the corresponding first message for requesting LTM configuration, indication information indicating candidate configuration complete information indication is carried, and the candidate configuration complete information indication may be for a certain C-MN or for a certain candidate PCell.

[0550] For example, the 1-bit indication information includes instructing the C-MN to generate a complete candidate configuration for each candidate PSCell corresponding to the C-MN, or the 1-bit indication information associated with the candidate PSCell includes instructing the C-MN to generate a complete candidate configuration for the candidate PSCell.

[0551] In implementation method 2, when the corresponding request message for requesting LTM configuration does not carry a reference configuration, when the C-MN receives the request message without a reference configuration, the C-MN generates a complete candidate configuration for the candidate cell.

[0552] The C-MN determines whether the candidate configuration corresponding to one or more candidate PCells corresponding to it is a complete candidate configuration. The C-MN includes indication information in the first response message sent to the S-MN, indicating that the corresponding candidate configuration is a complete candidate configuration.

[0553] Implementation method 1: In the corresponding first response message for sending LTM configuration, indication information including candidate configuration complete information indication is carried. The candidate configuration complete information indication may be for a certain C-MN or a certain candidate PCell.

[0554] Scenario 2: SCG LTM without MCG change in NR-DC.

[0555] The MN instructs one or more C-SNs (or one or more candidate PSCells) to generate a complete candidate configuration. The MN sends a second message to the C-SN, where the second message includes information indicating whether to request the C-SN to generate a complete candidate configuration.

[0556] Alternatively, the S-SN may request the MN or request one or more other C-SNs through the MN to generate a complete candidate configuration. The S-SN sends a third message to the MN, the third message including information indicating whether to request the C-SN to generate a complete candidate configuration.

[0557] The C-SN determines whether the candidate configurations corresponding to the one or more candidate PCells corresponding to it are complete candidate configurations. The C-SN includes indication information in a second response message sent to the MN, indicating that the corresponding candidate configuration is a complete candidate configuration.

[0558] The MN can indicate whether to request the corresponding C-SN to generate the LTM complete configuration by whether it has sent a message carrying the reference configuration. In other cases, explicit LTM integrity indication information is required for indication.

[0559] Scenario 3: MCG LTM with SCG release in the NR-DC scenario.

[0560] The implementation process is similar to that of Scenario 1 and will not be repeated here.

[0561] Scenario 4: MCG LTM without SCG in the NR-DC scenario.

[0562] The implementation process is similar to that of Scenario 1 and will not be repeated here.

[0563] The complete information of the specific candidate configuration indicates the implementation method of the transmission:

[0564] The transmission of the complete information indication of the candidate configuration may be transmitted through an Xn message or an inter-node RRC message. The specific Xn messages and inter-node RRC messages that may be used are similar to those for the transmission of the reference configuration.

[0565] An exemplary Xn message may be as shown in Table 5, for example.

[0566] An exemplary inter-node RRC message may be:

[0567] 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.

[0568] 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.

[0569] 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.

[0570] FIG4A is a schematic diagram of the structure of a first node proposed in an embodiment of the present disclosure. As shown in FIG4A , the first node 4100 may include: a processing module 4101 and a transceiver module 4102 .

[0571] In some embodiments, the above-mentioned processing module 4101 is configured to determine a reference configuration, which is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; wherein the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node.

[0572] In some embodiments, the above-mentioned transceiver module 4102 is configured to send a first message to the second node, and the first message is used to request the second node to generate a candidate configuration. The first message includes any one of the following items: first indication information, the first indication information is used to indicate the request for the second node to generate a complete candidate configuration; second indication information, the second indication information is used to indicate the request for the second node to generate an incremental candidate configuration based on the reference configuration.

[0573] Optionally, the processing module 4101 is used to execute at least one of the other steps (such as step S2101, but not limited thereto) executed by the first node 4100 in any of the above methods, which will not be described in detail here.

[0574] Optionally, the above-mentioned transceiver module 4102 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first node 4100 in any of the above methods (for example, step S2100, step S2102, step S2104, but not limited to these), which will not be repeated here.

[0575] FIG4B is a schematic diagram of the structure of a second node proposed in an embodiment of the present disclosure. As shown in FIG4B , the second node 4200 may include: a transceiver module 4201 .

[0576] In some embodiments, the above-mentioned transceiver module 4201 is configured to receive a first message sent by a first node, the first message is used to request the second node to generate a candidate configuration, the candidate configuration is triggered by layer 1 or layer 2, and the first message includes any one of the following items: first indication information, the first indication information is used to indicate the request for the second node to generate a complete candidate configuration; second indication information, the second indication information is used to indicate the request for the second node to generate an incremental candidate configuration based on the reference configuration; the reference configuration is generated by the first node or by the second node, or the reference configuration is generated by the first node and the second node.

[0577] Optionally, the above-mentioned transceiver module 4201 is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2102, step S2104, but not limited to this) performed by the second node 4200 in any of the above methods, which will not be repeated here.

[0578] In some embodiments, the second node 4200 may further include a processing module 4202 (not shown in FIG. 4B ).

[0579] Optionally, the processing module 4202 is used to execute at least one of the other steps (such as step S2103, but not limited thereto) executed by the second node 4200 in any of the above methods, which will not be described in detail here.

[0580] FIG4C is a schematic diagram of the structure of a third node proposed in an embodiment of the present disclosure. As shown in FIG4C , the third node 4300 may include: a transceiver module 4301 .

[0581] In some embodiments, the above-mentioned transceiver module 4301 is configured to send a second message to the first node, the second message is used to request the first node to generate a reference configuration, the reference configuration is used to determine the candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; and / or send a fourth message to the first node, the fourth message is used to request the first node to send a third message to the second node, the third message is used to request the reference configuration, the reference configuration is used to determine the candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2.

[0582] Optionally, the above-mentioned transceiver module 4301 is used to execute at least one of the communication steps such as sending and / or receiving (such as step S2100, but not limited to this) performed by the third node 4300 in any of the above methods, which will not be repeated here.

[0583] 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.

[0584] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules each 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.

[0585] Figure 5A is a schematic diagram of the structure of a communication device 5100 proposed in an embodiment of the present disclosure. Communication device 5100 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 5100 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.

[0586] As shown in Figure 5A, the communication device 5100 includes one or more processors 5101. The processor 5101 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 5100 is used to perform any of the above methods. Optionally, one or more processors 5101 are used to call instructions to enable the communication device 5100 to perform any of the above methods.

[0587] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2100, step S2102, step S2104, but not limited thereto), and the processor 5101 performs at least one of the other steps (e.g., step S2101, step S2103, 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, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

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

[0589] The communication device 5100 described in the above embodiment may be a network device, but the scope of the communication device 5100 described in the present disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. 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 or 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.

[0590] 5B is a schematic diagram of the structure of a chip 5200 according to an embodiment of the present disclosure. If the communication device 5100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 5200 shown in FIG5B , but the present disclosure is not limited thereto.

[0591] The chip 5200 includes one or more processors 5201. The chip 5200 is configured to execute any of the above methods.

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

[0593] In some embodiments, the interface circuit 5202 performs at least one of the communication steps (e.g., steps S2100, S2102, and S2104) of the aforementioned method. For example, the interface circuit 5202 performing the communication steps (e.g., steps S2100, S2102, and S2104) of the aforementioned method means that the interface circuit 5202 performs data exchange between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps (e.g., steps S2101 and S2103, but not limited thereto).

[0594] 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.

[0595] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 5100, causes the communication device 5100 to execute 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.

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

[0597] 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.

[0598] 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.

[0599] 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: Determining a reference configuration, which is used to determine a candidate configuration triggered by layer 1 or layer 2; wherein, the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node; Sending a first message to a second node, the first message being used to request the second node to generate the candidate configuration, and the first message includes any one of the following: First indication information, which is used to indicate a request for the second node to generate a complete candidate configuration; Second indication information, which is used to indicate a request for the second node to generate an incremental candidate configuration based on the reference configuration.

2. The method according to claim 1, wherein The reference configuration is common for non-complete candidate configurations of a set of configurations within the same cell group.

3. The method according to claim 1 or 2, characterized in that, When the reference configuration is generated by the first node, the reference configuration includes a master cell group (MCG) reference configuration.

4. The method according to claim 3, wherein The method further includes: Receiving a second message sent by a third node, the second message being used to request the first node to generate the reference configuration.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Sending a third message to the second node, the third message being used to request the reference configuration.

6. The method according to claim 5, wherein The determining the reference configuration includes: Receiving a third response message sent by the first node, and the third response message includes the reference configuration generated by the second node.

7. The method according to claim 5 or 6, characterized in that, The third message is any one of the following messages: Handover request message; Secondary node (SN) addition request message; SN modification request message; SN reconfiguration complete message; SM modification confirmation message; SN change confirmation message; Handover preparation information; Cell group configuration information; First Xn message, which is used for LTM request; RRC message between the first nodes, which is used for LTM request.

8. The method according to any one of claims 5 to 7, characterized in that, The third response message is any one of the following messages: Handover request confirmation message; SN addition request confirmation message; SN modification request confirmation message; SN modification requirement message; SN change requirement message; Handover command; Cell group configuration; Cell group candidate list; Second Xn message, which is used for LTM request confirmation; RRC message between the first nodes, which is used for LTM request; RRC message between the second nodes, which is used for LTM request confirmation.

9. The method according to any one of claims 5 - 8, characterized in that, The method further includes: Receiving a fourth message sent by a third node, the fourth message being used to request the first node to send the third message to the second node.

10. The method according to any one of claims 1-9, characterized in that, The reference configuration includes any one of the following: MCG reference configuration, which is generated by the first node or the second node; SCG reference configuration, which is generated by the second node; MCG reference configuration and SCG reference configuration, the MCG reference configuration is generated by the first node, and the SCG reference configuration is generated by the second node.

11. The method according to any one of claims 1-10, 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 reconfiguration complete message; SM modification confirmation message; SN change confirmation message; First Xn message for LTM request; First inter-node RRC message for LTM request.

12. The method according to any one of claims 1-11, characterized in that, The first message further includes at least one of the following: The reference configuration; Third indication information for requesting the second node to generate the candidate configuration for the first node or the LTM candidate cell.

13. The method according to any one of claims 1 to 12, characterized in that, The method further includes: Receiving a first response message sent by the second node, where the first response message includes the candidate configuration generated by the second node.

14. The method according to claim 13, wherein The first response message is any of the following messages: Handover request confirmation message; SN addition request confirmation message; SN modification request confirmation message; SN modification requirement message; SN change requirement message; Second Xn message for LTM request confirmation; Second inter-node RRC message for LTM request confirmation.

15. The method according to claim 13 or 14, characterized in that The first response message includes: Fourth indication information for indicating whether the candidate configuration generated by the second node is a complete candidate configuration.

16. 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, the first message for requesting the second node to generate a candidate configuration, the candidate configuration being triggered by layer 1 or layer 2, and the first message includes any of the following: First indication information for indicating to request the second node to generate a complete candidate configuration; Second indication information for indicating to request the second node to generate an incremental candidate configuration based on a reference configuration, the reference configuration being used to determine the candidate configuration; the reference configuration is generated by the first node or by the second node, or the reference configuration is generated by the first node and the second node.

17. The method according to claim 16, wherein The reference configuration is common for a set of non-complete candidate configurations within the same cell group.

18. The method according to claim 16 or 17, characterized in that, The method further includes: Receiving a third message sent by the first node, the third message for requesting the second node to generate the reference configuration; Generating the reference configuration; Sending a third response message to the first node, the third response message including the reference configuration generated by the second node.

19. The method according to claim 18, wherein The third message is any of the following messages: Handover request message; Secondary node SN addition request message; SN modification request message; SN modification confirmation message; SN change requirement message; First Xn message for LTM request; First inter-node RRC message for LTM request.

20. The method according to claim 18 or 19, characterized in that The third response message is any of the following messages: Handover request confirmation message; SN addition request confirmation message; SN modification request confirmation message; SN modification requirement message; SN change requirement message; Second Xn message for LTM request confirmation; Second inter-node RRC message for LTM request confirmation.

21. The method according to any one of claims 16 - 20, characterized in that, The reference configuration includes any of the following: MCG reference configuration, which is generated by the first node or the second node; SCG reference configuration, which is generated by the second node; MCG reference configuration and SCG reference configuration, where the MCG reference configuration is generated by the first node and the SCG reference configuration is generated by the second node.

22. The method according to any one of claims 16-21, 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 modification confirmation message; SN change requirement message; First Xn message, which is used for LTM request; First inter-node radio resource control RRC message, which is used for LTM request.

23. The method according to any one of claims 16-22, characterized in that, The first message further includes at least one of the following: The reference configuration; Third indication information, which is used to request the second node to generate the candidate configuration for the first node or the LTM candidate cell.

24. The method according to any one of claims 16-23, characterized in that, The method further includes any one of the following: The first indication information is included in the first message, and a complete candidate configuration is generated; The reference configuration is not included in the first message, and a complete candidate configuration is generated; The second indication information is included in the first message, and an incremental candidate configuration is generated based on the reference configuration.

25. The method according to any one of claims 16-24, characterized in that, The method further includes: Sending a first response message to the first node, where the first response message includes the candidate configuration generated by the second node.

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

27. The method according to claim 25 or 26, characterized in that, The first response message includes: Fourth indication information, which is used to indicate whether the candidate configuration generated by the second node is a complete candidate configuration.

28. An information transmission method, characterized in that, The method is executed by a third node and includes: Sending a second message to the first node, where the second message is used to request the first node to generate a reference configuration, and the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; and / or Sending a fourth message to the first node, where the fourth message is used to request the first node to send a third message to the second node, and the third message is used to request a reference configuration, and the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2.

29. The method according to claim 28, wherein The reference configuration is common for a set of non-complete candidate configurations within the same cell group.

30. A first node, characterized in that, Includes: A processing module, configured to determine a reference configuration, where the reference configuration is used to determine a candidate configuration, and the candidate configuration is triggered by layer 1 or layer 2; wherein, the reference configuration is generated by the first node or the second node, or the reference configuration is generated by the first node and the second node; A transceiver module, configured to send a first message to a second node, the first message being used to request the second node to generate the candidate configuration, and the first message including any one of the following: First indication information, the first indication information being used to indicate a request for the second node to generate a complete candidate configuration; Second indication information, the second indication information being used to indicate a request for the second node to generate an incremental candidate configuration based on the reference configuration.

31. A second node, characterized in that, Comprising: A transceiver module, configured to receive a first message sent by a first node, the first message being used to request the second node to generate a candidate configuration, the candidate configuration being triggered by layer 1 or layer 2, and the first message including any one of the following: First indication information, the first indication information being used to indicate a request for the second node to generate a complete candidate configuration; Second indication information, the second indication information being used to indicate a request for the second node to generate an incremental candidate configuration based on the reference configuration; The reference configuration is generated by the first node or by the second node, or the reference configuration is generated by the first node and the second node.

32. A third node, characterized in that, Comprising: A transceiver module, configured to send a second message to a first node, the second message being used to request the first node to generate a reference configuration, the reference configuration being used to determine a candidate configuration, the candidate configuration being triggered by layer 1 or layer 2; and / or Send a fourth message to the first node, the fourth message being used to request the first node to send a third message to the second node, the third message being used to request a reference configuration, the reference configuration being used to determine a candidate configuration, the candidate configuration being triggered by layer 1 or layer 2.

33. 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-15.

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

35. A third node, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the method for information transmission behavior according to claim 28 or 29.

36. 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-15, the second node is configured to implement the information transmission method according to any one of claims 16-27, and the third node is configured to implement the information transmission method according to claim 28 or 29.

37. A storage medium, wherein 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-15, 16-27, or 28-29.

Images