Information transmission method and apparatus, and storage medium

Abstract

The present disclosure provides an information transmission method and apparatus, and a storage medium. The method comprises: sending first information to a second node, wherein the first information is used for matching a first configuration, and the first configuration is triggered by layer 1 or layer 2. According to the present disclosure, LTM can be triggered on the basis of the first configuration when a candidate node is designated as a service node, thereby achieving the purpose of subsequent LTM and achieving high availability.

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 implement subsequent LTM, the embodiments of the present disclosure provide an information transmission method and device, and a storage medium.

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

[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 first information sent by a first node, where the first information is used to match a first configuration, where the first configuration is triggered by Layer 1 or Layer 2. According to a third aspect of an embodiment of the present disclosure, there is provided an information transmission method, which is executed by a third node and includes: sending a fourth message to the first node, where the fourth message is used to initiate a secondary cell group (SCG) LTM process; and receiving a fourth response message sent by the first node, where the fourth response message is used to indicate that the SCG LTM process has been completed.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a first node is provided, including: a transceiver module, configured to send first information to a second node, the first information being used to indicate matching a first configuration, and the first configuration being triggered by layer 1 or layer 2.

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

[0010] 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 fourth message to the first node, the fourth message being used to initiate a secondary cell group SCG LTM process; the transceiver module is also configured to receive a fourth response message sent by the first node, the fourth response message being used to indicate that the SCG LTM has been completed.

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

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

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

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

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

[0016] In the embodiment of the present disclosure, after the candidate node becomes a service node, LTM can be triggered based on the first configuration, thereby achieving the purpose of subsequent LTM and having high availability.

[0017] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0044] In a first aspect, embodiments of the present disclosure provide an information transmission method, performed by a first node, comprising: sending first information to a second node, the first information being used to match a first configuration, the first configuration being triggered by Layer 1 or Layer 2. In the above embodiment, after the candidate node becomes a serving node, LTM can be triggered based on the first configuration, thereby achieving the purpose of subsequent LTM and providing high availability.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the first node is a source master node S-MN, and the second node is a candidate master node C-MN; or the first node is a master node MN, and the second node is a candidate slave node C-SN.

[0046] In the above embodiment, the first node can be an S-MN or MN, and the second node can be a C-MN or C-SN. The first node sends the first information to the second node, so that after the second node becomes a service node from a candidate node, it can trigger LTM based on the first configuration, thereby achieving the purpose of subsequent LTM and high availability.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the first information is associated with other candidate nodes other than the second node.

[0048] In the above embodiment, the first information is associated with other candidate nodes besides the second node, which saves signaling resources of the first information and has high availability.

[0049] In combination with some embodiments of the first aspect, in some embodiments, sending the first information to the second node includes: sending the first information to the second node after completing the first preparation process with the second node, and the first preparation process is triggered by layer 1 or layer 2; or sending the first information to the second node when initiating the first preparation process with the second node, and the first preparation process is triggered by layer 1 or layer 2.

[0050] In the above embodiment, the first node can send the first information to the second node after completing the first preparation process with the second node, or can send the first information to the second node when initiating the first preparation process with the second node, thereby achieving the purpose of providing the first information to the second node (candidate node). When the second node subsequently becomes a service node, it can trigger LTM based on the first configuration, thereby achieving the purpose of subsequent LTM and having high availability.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the second message includes the first information, and the second message is used to match the first configuration after the first preparation process is completed.

[0052] In the above embodiment, the first node sends the second message including the first information to the second node, thereby achieving the purpose of sending the first information to the second node after completing the first preparation process with the second node, and having high availability.

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

[0054] In the above embodiment, the second message may be any of the above messages, so that the first information is provided to the second node through the second message, which is simple to implement and has high availability.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: receiving a second response message sent by the second node, the second response message is used to confirm the match of the first configuration, the second response message includes the candidate cell configuration and / or corresponding measurement configuration updated by the second node based on the first information, and the candidate cell configuration is triggered by layer 1 or layer 2.

[0056] In the above embodiment, the first node may receive a second response message returned by the second node, which may include the candidate cell configuration and / or corresponding measurement configuration updated by the second node based on the first information, to ensure that the nodes have a consistent understanding of the L candidate cell configuration.

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

[0058] In the above embodiment, the second response message can be any of the above messages, which is easy to implement and has high availability.

[0059] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: generating a first configuration, the first configuration including an updated candidate cell configuration generated by the second node, the candidate cell configuration being triggered by layer 1 or layer 2; and sending the first configuration to the terminal.

[0060] In the above embodiment, the first node may generate a first configuration including the updated candidate cell configuration generated by the second node, and send the first configuration to the terminal, thereby achieving the purpose of subsequent LTM and having high availability.

[0061] In combination with some embodiments of the first aspect, in some embodiments, the first message includes first information, and the first message is used to initiate a first preparation process.

[0062] In the above embodiment, the purpose of providing the first information to the second node when initiating the first preparation process with the second node is achieved, thereby ensuring subsequent LTM and high availability.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: receiving a first response message sent by the second node, the first response message is used to indicate the completion of the first preparation process, the first response message includes the candidate cell configuration and / or corresponding measurement configuration generated by the second node based on the first information, and the candidate cell configuration is triggered by layer 1 or layer 2; based on the first response message, sending a first configuration to the terminal, the first configuration includes the candidate cell configuration that the first node needs to provide to the terminal.

[0064] In the above embodiment, the second node may send a first response message to the first node, which includes a candidate cell configuration and / or a corresponding measurement configuration generated by the second node based on the first information. Based on the first response message, the first node may send a first configuration to the terminal, which includes a candidate cell configuration that the first node needs to provide to the terminal. The candidate cell configuration provided to the terminal may be the same as or different from the candidate cell configuration generated by the second node, thereby achieving the purpose of subsequent LTM.

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

[0066] The candidate cell configuration that needs to be provided to the terminal is different from the candidate cell configuration included in the first response message, and a third message is sent to the second node, where the third message is used to indicate at least one of the following: the candidate cell prepared for the terminal; the first configuration identifier; the matching relationship between the candidate cell prepared for the terminal and the first configuration identifier; and receiving the third response message sent by the second node.

[0067] In the above embodiment, if the LTM candidate cell configuration to be provided to the terminal is different from the candidate cell configuration included in the first response message, the first node can send the candidate cell to be provided to the terminal and the corresponding first configuration identifier to the second node to ensure the reliability of subsequent LTM.

[0068] In combination with some embodiments of the first aspect, in some embodiments, the third message is any one of the following messages: an SN modification request message; a third Xn message, the third Xn message is used for LTM update; a third inter-node RRC message, the third inter-node RRC message is used for LTM update.

[0069] In the above embodiment, the third message can be any of the above messages, which is easy to implement and has high availability.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the third response message is any one of the following messages: an SN modification request confirmation message; a fourth Xn message, the fourth Xn message is used for LTM update confirmation; a fourth inter-node RRC message, the fourth inter-node RRC message is used for LTM update confirmation.

[0071] In the above embodiment, the third response message may be any of the above messages, so that the second node can confirm that it has received the candidate cell configuration sent by the first node and provided to the terminal, thereby ensuring the reliability of subsequent LTM.

[0072] 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; an SN adding 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 the above embodiment, the first message may be any of the above messages, which improves the availability of subsequent LTM.

[0074] In combination with some embodiments of the first aspect, in some embodiments, the first response message is any one of the following messages: a handover request confirmation message; an SN add request confirmation message; a second Xn message, the second Xn message is used for LTM request confirmation; a second inter-node RRC message, the second inter-node RRC message is used for LTM request confirmation

[0075] In the above embodiment, the first response message may be any of the above messages, which improves the availability of subsequent LTM.

[0076] In combination with some embodiments of the first aspect, in some embodiments, the method also includes: receiving a fourth message sent by the third node, the fourth message is used to initiate the secondary cell group SCG LTM process; after receiving the second response message or the third response message sent by the second node, sending a fourth response message to the third node, the fourth response message is used to indicate that the SCG LTM has been completed.

[0077] In the above embodiment, the first information can be provided to the second node during the SCG LTM process initiated by the third node, thereby improving the availability of subsequent LTM in the SCG LTM process.

[0078] In combination with some embodiments of the first aspect, in some embodiments, the fourth message is an SN change request message, and / or the fourth response message is an SN change confirmation message.

[0079] In a second aspect, embodiments of the present disclosure provide an information transmission method, performed by a second node, comprising: receiving first information sent by a first node, the first information being used to match a first configuration, the first configuration being triggered by Layer 1 or Layer 2. In the above embodiment, the second node can receive the first information sent by the first node, thereby triggering LTM based on the first configuration after becoming a serving node, thereby achieving the purpose of subsequent LTM and providing high availability.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the first node is a source master node S-MN, and the second node is a candidate master node C-MN; or the first node is a master node MN, and the second node is a candidate slave node C-SN.

[0081] In combination with some embodiments of the second aspect, in some embodiments, the first information is associated with other candidate nodes other than the second node.

[0082] In combination with some embodiments of the second aspect, in some embodiments, receiving the first information sent by the first node includes: receiving the first information sent by the first node after completing the first preparation process with the first node, and the first preparation process is triggered by layer 1 or layer 2; or receiving the first information sent by the first node when initiating the first preparation process with the second node, and the first preparation process is triggered by layer 1 or layer 2.

[0083] In combination with some embodiments of the second aspect, in some embodiments, the second message includes the first information, and the second message is used to match the first configuration after the first preparation process is completed.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the second message is any one of the following messages: a switching request message; an SN adding 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.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: updating the generated candidate cell configuration based on the first information, determining the updated candidate cell configuration, and the candidate cell configuration is triggered by layer 1 or layer 2; sending a second response message to the first node, the second response message is used to confirm the match of the first configuration, and the second response message includes the updated candidate cell configuration and / or the corresponding measurement configuration.

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

[0087] In combination with some embodiments of the second aspect, in some embodiments, the first message includes first information, and the first message is used to initiate a first preparation process.

[0088] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: generating a candidate cell configuration based on the first information, the candidate cell configuration is triggered by layer 1 or layer 2; sending a first response message to the first node, the first response message is used to indicate the completion of the first preparation process, and the first response message includes the candidate cell configuration generated by the second node based on the first information.

[0089] 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 indicate at least one of the following: a candidate cell prepared for the terminal; a first configuration identifier; a matching relationship between the candidate cell prepared for the terminal and the first configuration identifier; and sending a third response message to the first node.

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

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

[0092] In combination with some embodiments of the second aspect, in some embodiments, the first message is any one of the following messages: a handover request message; an SN add request message.

[0093] 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 adding request confirmation message.

[0094] In the third aspect, an embodiment of the present disclosure proposes an information transmission method, which is executed by a third node, including: sending a fourth message to the first node, the fourth message is used to initiate the secondary cell group SCG LTM process; receiving a fourth response message sent by the first node, the fourth response message is used to indicate that the SCG LTM has been completed.

[0095] In combination with some embodiments of the third aspect, in some embodiments, the fourth message is an SN change request message, and / or the fourth response message is an SN change confirmation message.

[0096] In a fourth aspect, an embodiment of the present disclosure proposes a first node, comprising: a transceiver module, configured to send first information to a second node, the first information being used to match a first configuration, and the first configuration being triggered by layer 1 or layer 2. In a fifth aspect, an embodiment of the present disclosure proposes a second node, comprising: a transceiver module, configured to receive first information sent by a first node, the first information being used to match a first configuration, and the first configuration being triggered by layer 1 or layer 2. In a sixth aspect, an embodiment of the present disclosure proposes a third node, comprising: a transceiver module, configured to send a fourth message to the first node, the fourth message being used to initiate a secondary cell group SCG LTM process; and the transceiver module is further configured to receive a fourth response message sent by the first node, the fourth response message being used to indicate that the SCG LTM has been completed.

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

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

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

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

[0101] In the eleventh aspect, an embodiment of the present disclosure proposes a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute an information transmission method as described in any one of the first, second, or third aspects.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0122] 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 (e.g., a source gNB).

[0123] In some embodiments, in a dual connectivity (DC) scenario, such as an NR-DC scenario, the first node 101 may be a master node (MN).

[0124] 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 (e.g., C-gNB).

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

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

[0127] In some embodiments, the third node 103 may be a source node (Source-Secondary Nodes, S-SN) in a DC scenario.

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

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

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

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

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

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

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

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

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

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

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

[0139] 2. NR-NR Dual Connectivity

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

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

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

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

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

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

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

[0147] LTM supports the following scenarios:

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

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

[0150] -PCell changes in CA scenarios;

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

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

[0153] 4. LTM configuration:

[0154] LTM configures LTM configuration information through LTM configuration (such as LTM-Config).

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

[0156] LTM reference configuration;

[0157] One or more candidate cell configurations (for example, adding, modifying, or deleting candidate cell configurations through ltm-CandidateToReleaseList and ltm-CandidateToAddModList);

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

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

[0160] candidate configuration identifier;

[0161] Candidate cell identifier;

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

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

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

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

[0166] 5. LTM execution process:

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

[0168] The steps of LTM include:

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

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

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

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

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

[0174] When terminal-based timed advance (TA) measurement is configured, the terminal obtains the TA value of the candidate cell through measurement. The terminal performs early TA acquisition with the candidate cell at the request of the network before receiving the cell switching command. This is done by CFRA triggered by a physical downlink control channel (PDCCH) command from the source cell, and then the terminal sends a preamble to the indicated candidate cell. In order to minimize the data interruption of the source cell to the candidate cell due to CFRA, the terminal does not receive a random access response for TA value acquisition from the network, and indicates the TA value of the candidate cell in the cell switching command. The terminal does not maintain the TA timer of the candidate cell and relies on the network implementation to ensure the validity of the TA.

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

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

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

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

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

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

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

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

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

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

[0185] For inter-CU LTM in non-DC scenarios, we mainly discuss MCG LTM.

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

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

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

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

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

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

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

[0193] The cell switch command (Cell Switch Command) used to trigger LTM is sent by the current serving distributed unit (DU) to the terminal. To support subsequent LTM (subsequent LTM), each candidate DU needs to know the terminal's currently configured cells and the corresponding candidate configuration identifiers. This allows the candidate DU to trigger subsequent LTM based on this matching relationship after becoming a serving DU. Therefore, the present disclosure provides the following information transmission method, device, and storage medium. After a candidate node becomes a serving node, LTM can be triggered based on the existing LTM configuration, achieving the purpose of subsequent LTM with high availability.

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

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

[0196] In some embodiments, the fourth message may be used to initiate the SCG LTM.

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

[0198] SN change request (SNChangeRequired) message;

[0199] The fifth Xn message can be used to initiate SCG LTM.

[0200] Fifth inter-node Radio Resource Control (inter-node RRC) message: The fifth inter-node RRC message can be used to initiate SCG LTM.

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

[0202] In some embodiments, in a non-DC scenario, or in an NR-DC scenario with an MCG LTM released by an SCG or an SCG LTM triggered by an MN, step S2101 may not be performed.

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

[0204] In some embodiments, the first message is used to initiate a first preparation process, and the first preparation process is triggered based on layer 1 or layer 2.

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

[0206] Handover Request message;

[0207] SN AdditionRequest message;

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

[0209] The first inter-node RRC message is used for LTM request.

[0210] In one example, the first configuration is based on a layer 1 or layer 2 trigger.

[0211] Exemplarily, the first configuration may be equivalent to the LTM configuration. The relevant contents of the LTM configuration have been introduced in the above embodiment and will not be repeated here.

[0212] In an example, the first Xn message may be a new Xn message agreed upon by the protocol, and the message is used to request the first configuration.

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

[0214] In some embodiments, in a non-DC scenario, the first node 101 may be a source gNB, and the second node 102 may be a candidate gNB. The first message may be a handover request message, a first Xn message, or a first inter-node RRC message.

[0215] In some embodiments, in a DC scenario, such as an NR-DC scenario, the first node 101 may be an MN, and the second node 102 may be a C-SN. The first message may be an SN add request message, a first Xn message, or a first inter-node RRC message.

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

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

[0218] In some embodiments, the first response message is used to respond to the first message, which can be used to indicate the completion of the first preparation process.

[0219] The first response message can be any of the following messages:

[0220] Handover Request Acknowledge message;

[0221] SNAdditionRequestAcknowledge message;

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

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

[0224] In one example, the second Xn message may be a new Xn message agreed upon by the protocol, which is used for LTM request confirmation.

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

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

[0227] In some embodiments, the first node 101 receives the first response message and determines that the first preparation process is completed.

[0228] Step S2104: The first node 101 sends a second message to the second node 102, wherein the second message includes the first information.

[0229] In some embodiments, after receiving the first response messages sent by all second nodes 102 , the first node 101 sends a second message to the second node 102 .

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

[0231] Handover Request message;

[0232] SN modification request (SNModificationRequest) message;

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

[0234] The first inter-node RRC message is used for LTM request.

[0235] In some embodiments, the first information may be used to indicate at least one of the following:

[0236] candidate cells;

[0237] a first configuration identifier;

[0238] A matching relationship between the candidate cell and the first configuration identifier.

[0239] Exemplarily, the first information may include a candidate cell identifier to indicate the candidate cell. The candidate cell may be a candidate cell when LTM triggers cell switching.

[0240] For example, the first information may include a first configuration identifier, and the first configuration may be triggered by layer 1 or layer 2. The first configuration may be equivalent to the LTM configuration. The LTM configuration has been introduced in the above embodiment and will not be repeated here.

[0241] Exemplarily, the first information may include a matching relationship between the candidate cell identifier and the first configuration identifier, for example, candidate cell #1 corresponds to first configuration #1 and first configuration #2, and candidate cell #2 corresponds to first configuration #1, first configuration #3, first configuration #4...

[0242] Illustratively, the first information may include a combination of two or three of the above items.

[0243] Illustratively, the first information may also include other content, which is not limited in this disclosure.

[0244] Exemplarily, the candidate cell indicated by the first information and / or the first configuration identifier indicated by the first information is associated with other candidate nodes other than the second node.

[0245] Exemplarily, the first information may include candidate cells prepared by other candidate nodes for the terminal and / or a first configuration identifier corresponding to the candidate cells.

[0246] The other candidate nodes may be all candidate nodes except the second node that prepare candidate cells for the terminal, or may be any one or more candidate nodes except the second node that prepare candidate cells for the terminal.

[0247] The candidate cells prepared for the terminal include at least one of the following:

[0248] The candidate cell that the candidate node has prepared for the terminal;

[0249] For other candidate cells except the first cell, the first message may be the candidate cells indicated by the first message.

[0250] Exemplarily, the candidate cells prepared for the terminal may include candidate cells that all candidate nodes have prepared for the terminal.

[0251] Exemplarily, the first message may indicate the global cell identifier of the first cell, such as the target cell ID. For example, the first node 101 is the source gNB, the second node 102 is the candidate gNB#1, and the first node 101 sends a first message to the second node 102. The first message includes candidate cell identifiers and / or first configuration identifiers associated with candidate gNB#2, candidate gNB#3, and the like. For example, candidate gNB#2 is associated with candidate cells#2 to#4, and candidate gNB#2 is associated with first configuration#2. Candidate gNB#3 is associated with candidate cells#5 to#7, and candidate gNB#3 is associated with first configuration#1.

[0252] When the first node 101 is an MN and the second node 102 is a C-SN, the candidate cell indicated by the first information and / or the first configuration identifier are associated with other C-SNs in a manner similar to the above process and will not be repeated here.

[0253] Exemplarily, the first information may also include all candidate cell identifiers to be configured by the first node 101 for the terminal, the first configuration identifier, and a matching relationship between the two.

[0254] Exemplarily, the first information may also include identifiers of candidate cells other than the first cell, the first configuration identifier, and a matching relationship between the two. The first cell may be the cell indicated by the first message, for example, the first message includes the cell identifier of the first cell.

[0255] In some embodiments, the candidate cell, the first configuration identifier, and the matching relationship between the two may be represented by an LTM configuration identifier matching table.

[0256] In one example, the LTM configuration identifier matching table may contain a maximum of Y elements, where Y is the maximum number of candidate gNBs that can be configured. Each element corresponds to a candidate gNB identifier and a group of candidate cells and the first configuration identifier or LTM configuration identifier corresponding to the candidate cell, as shown in Table 1.

[0257] Table 1

[0258] In an example, the LTM configuration identifier matching table may contain at most X elements, where X is the maximum number of configurable cells, and each element corresponds to a candidate cell and the first configuration identifier or LTM configuration identifier corresponding to the candidate cell, as shown in Table 2.

[0259] Table 2

[0260] In one example, the first information may be transmitted via an inter-node RRC message, such as including a candidate cell identifier and a corresponding LTM configuration identifier of the candidate cell in a CG-ConfigInfo message (which may also include other relevant information, such as candidate cell measurement results, etc.).

[0261] In an example, LTM related information may be included in the SN add request message or the SN modify request message, as shown in Table 3.

[0262] Table 3

[0263] In this information, the MN and SN transmit the candidate SN list by referencing, for example, candidateCellInfoListMN and / or candidateCellListCPC in CG-ConfigInfo. There is no corresponding LTM configuration identifier in these two information. The first configuration identifier associated with the LTM candidate cell can be added to this information:

[0264] For candidateCellInfoListMN, it corresponds to a group of measurement results associated with different frequencies, and each measurement result associated with a different frequency contains a group of cell measurement results, as follows. Therefore, a first configuration identifier can be added to the measurement result corresponding to each cell to associate it with the LTM candidate cell.

[0265] For candidateCellListCPC, it corresponds to a list of cells associated with different frequencies. Each element associated with a different frequency includes the PCI of a group of cells. Therefore, the PCI of each cell in each group of cells can be associated with the first configuration identifier.

[0266] The specific implementation process is not limited in this disclosure.

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

[0268] In some embodiments, the second response message includes the candidate cell configuration and / or the corresponding measurement configuration updated by the second node 102 based on the first information. The candidate cell configuration is triggered based on layer 1 or layer 2.

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

[0270] Handover Request Acknowledge message;

[0271] SN Modification Request Acknowledge message;

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

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

[0274] Step S2106: The first node 101 generates a first configuration.

[0275] In some embodiments, the first configuration generated by the first node 101 includes the candidate cell configuration generated by the second node 102 .

[0276] In some embodiments, the first configuration generated by the first node 101 includes at least one of the following:

[0277] Reference configuration;

[0278] one or more candidate cell configurations (e.g., candidate cell configurations generated by the second node 102);

[0279] CSI resource configuration.

[0280] In some embodiments, considering that different nodes generate first configuration identifiers corresponding to candidate cells, the following solutions may be adopted:

[0281] Solution 1: The third node 103, such as S-SN, can generate a corresponding candidate configuration identifier for the candidate configuration of the SCG LTM candidate cell. When the first node 101 is the MN, the MN follows the candidate configuration identifier, generates a first configuration for the terminal, and sends it to the terminal.

[0282] Solution 2: When the first node 101 is an MN, the first node generates a corresponding candidate configuration identifier for the candidate configuration of the SCG LTM candidate cell and informs the third node 103. The third node can trigger the initial SCGLTM based on the candidate configuration identifier generated by the first node.

[0283] Solution 3, the second node 102 is the C-SN, the second node 102 generates a candidate configuration identifier corresponding to the candidate cell it prepares, and sends it to the first node 101 (MN) through an SN add response message, and then the MN sends it to the S-SN and other candidate SNs.

[0284] Step S2107: The first node 101 sends a first configuration to the terminal.

[0285] In some embodiments, the first node 101 sends an RRC reconfiguration message to the terminal, where the message includes the first configuration generated by the first node 101 .

[0286] Step S2108 : The terminal sends an RRC reconfiguration completion message to the first node 101 .

[0287] In some embodiments, after updating the first configuration stored in itself, the terminal sends an RRC reconfiguration completion message to the first node 101 .

[0288] Step S2109 : The first node 101 sends a fourth response message to the third node 103 .

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

[0290] SN Change Confirm message;

[0291] The sixth Xn message can be used for SCG LTM confirmation.

[0292] The sixth inter-node RRC message, the sixth inter-node RRC message can be used for SCG LTM confirmation.

[0293] In some embodiments, in a non-DC scenario, or in an NR-DC scenario with an MCG LTM released by an SCG or an SCG LTM triggered by an MN, step S2109 may not be performed.

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

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

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

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

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

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

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

[0301] 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 sends the first response message to other execution entities, step S2103 may not be executed.

[0302] In some embodiments, steps S2104 to S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the first node 101 has already sent the first information to the second node 102 via the first message, steps S2104 to S2105 may not be performed.

[0303] In some embodiments, steps S2106 to S2108 are optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when other nodes provide the LTM configuration to the terminal, steps S2106 to S2108 may not be performed.

[0304] In some embodiments, step S2109 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, in a non-DC scenario, or in an NR-DC scenario with an MCG LTM released by an SCG or an SCG LTM triggered by an MN, step S2109 may not be performed.

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

[0306] In some embodiments, the execution order of steps S2101 to S2109 is not limited.

[0307] In the above embodiment, the first node can send the first information to the second node after completing the LTM preparation process with the second node, wherein the first information can be used to indicate the LTM candidate cell and / or the corresponding first configuration identifier. After becoming a service node, the second node can determine the first configuration corresponding to the LTM candidate cell based on the first information, and trigger LTM based on the first configuration, thereby achieving the purpose of subsequent LTM and having high availability.

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

[0309] Step S2201: The third node 103 sends a fourth message to the first node 101.

[0310] In some embodiments, the implementation of step S2201 is similar to that of step S2101 and will not be repeated here.

[0311] Step S2202: The first node 101 sends a first message to the second node 102, wherein the message includes first information.

[0312] In some embodiments, the first message is used to initiate the LTM preparation process.

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

[0314] Handover Request message;

[0315] SN AdditionRequest message;

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

[0317] The first inter-node RRC message is used for LTM request.

[0318] In one example, the first Xn message may be a new Xn message agreed upon by the protocol, which is used for LTM request.

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

[0320] In some embodiments, in a non-DC scenario, the first node 101 may be a source gNB, and the second node 102 may be a candidate gNB. The first message may be a handover request message, a first Xn message, or a first inter-node RRC message.

[0321] In some embodiments, in a DC scenario, such as an NR-DC scenario, the first node 101 may be an MN, and the second node 102 may be a C-SN. The first message may be an SN add request message, a first Xn message, or a first inter-node RRC message.

[0322] In some embodiments, the first information may be used to indicate at least one of the following:

[0323] candidate cells;

[0324] a first configuration identifier;

[0325] The matching relationship between the candidate cell and the first configuration identifier.

[0326] Exemplarily, the first information may include a candidate cell identifier to indicate the candidate cell.

[0327] Exemplarily, the first information may include a first configuration identifier.

[0328] Exemplarily, the first information may include a matching relationship between the candidate cell identifier and the first configuration identifier.

[0329] Illustratively, the first information may include a combination of two or three of the above items.

[0330] Illustratively, the first information may also include other content, which is not limited in this disclosure.

[0331] Exemplarily, the candidate cell indicated by the first information and / or the first configuration identifier indicated by the first information is associated with other candidate nodes other than the second node.

[0332] Exemplarily, the first information may include candidate cells prepared for the terminal in other candidate nodes and / or a first configuration identifier corresponding to the candidate cells.

[0333] The other candidate nodes may be all candidate nodes except the second node that prepare candidate cells for the terminal, or may be any one or more candidate nodes except the second node that prepare candidate cells for the terminal.

[0334] The candidate cells prepared for the terminal sent by the first node 101 to the second node 102 when initiating the first preparation process are different from the candidate cells prepared for the terminal sent by the first node 101 to the second node 102 after the LTM preparation process is completed. The first preparation process is triggered by layer 1 or layer 2.

[0335] In the embodiment of the present disclosure, the candidate cells prepared for the terminal and provided to the second node when the first preparation process is initiated may include, but are not limited to, at least one of the following:

[0336] The candidate cell that the candidate node has prepared for the terminal;

[0337] The first node, such as the source node, plans to have the candidate node prepare a cell. Exemplarily, the first information may also include all LTM candidate cell identifiers, LTM candidate configuration identifiers, and a matching relationship between the two that the first node 101 wants to configure for the terminal.

[0338] Exemplarily, the first information may also include LTM candidate cell identifiers other than the first cell, LTM candidate configuration identifiers, and a matching relationship between the two. The first cell may be the cell indicated by the first message, for example, the first message includes the cell identifier of the first cell.

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

[0340] In some embodiments, the first response message is used to respond to the first message, and the first response message can be used to indicate that the first preparation process has been completed. The first response message can be any of the following messages:

[0341] Handover Request Acknowledge message;

[0342] SNAdditionRequestAcknowledge message;

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

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

[0345] In one example, the second Xn message may be a new Xn message agreed upon by the protocol, which is used for LTM request confirmation.

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

[0347] In some embodiments, the first response message includes the candidate cell configuration and / or the corresponding measurement configuration generated by the second node 102 based on the first information.

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

[0349] Step S2204: The first node 101 generates a first configuration that needs to be provided to the terminal.

[0350] In some embodiments, the first configuration includes a candidate cell configuration, wherein the candidate cell configuration included in the first configuration may be the same as or different from the candidate cell configuration generated by the second node 102 .

[0351] If the candidate cell configuration included in the first configuration is different from the candidate cell configuration generated by the second node 102, the following steps S2204 to S2205 are performed.

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

[0353] In some embodiments, when the candidate cell identifier (or LTM candidate cell identifier list) provided to the terminal is different from the candidate cell identifier (or LTM candidate cell identifier list) included in the first response message, the first node 101 sends a third message to the second node 102. The third message may include but is not limited to at least one of the following:

[0354] Candidate cells prepared for the terminal;

[0355] a first configuration identifier;

[0356] A matching relationship between the candidate cells prepared for the terminal and the first configuration identifier.

[0357] The candidate cell configuration includes the above-mentioned candidate cell identifier.

[0358] In some embodiments, the third message is any one of the following messages:

[0359] SN modification request message;

[0360] The third Xn message is used for LTM update;

[0361] The third inter-node RRC message is used for LTM update.

[0362] In some embodiments, the candidate cells prepared for the terminal, the first configuration identifier, and the matching relationship between the two can be represented by an LTM configuration identifier matching table.

[0363] In one example, the LTM configuration identifier matching table can contain a maximum of Y elements, where Y is the maximum number of candidate gNBs that can be configured. Each element corresponds to a candidate gNB identifier and a group of candidate cells and the LTM configuration identifier corresponding to the candidate cells, as shown in Table 1.

[0364] In an example, the LTM configuration identifier matching table may contain at most X elements, where X is the maximum number of configurable LTM cells, and each element corresponds to a candidate cell and the LTM configuration identifier corresponding to the candidate cell, as shown in Table 2.

[0365] In one example, the third message may be an inter-node RRC message, such as a CG-ConfigInfo message including the prepared LTM candidate cell identifier and the corresponding LTM configuration identifier of the candidate cell (and may also include other relevant information, such as candidate cell measurement results, etc.).

[0366] In an example, the SN modification request message may include LTM related information, such as shown in Table 3.

[0367] Step S2206 : The second node 102 sends a third response message to the first node 101 .

[0368] In some embodiments, after the second node 102 updates its own stored LTM candidate cell configuration, it sends a third response message to the first node 101 .

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

[0370] SN modification request confirmation message;

[0371] The fourth Xn message is used for LTM update confirmation;

[0372] The fourth inter-node RRC message is used for LTM update confirmation.

[0373] Step S2207: The first node 101 sends a first configuration to the terminal.

[0374] In some embodiments, the first node 101 sends an RRC reconfiguration message to the terminal, which includes the first configuration generated by the first node 101.

[0375] Step S2208 : The terminal sends an RRC reconfiguration completion message to the first node 101 .

[0376] In some embodiments, after updating the first configuration stored in itself, the terminal sends an RRC reconfiguration completion message to the first node 101 .

[0377] Step S2209 : The first node 101 sends a fourth response message to the third node 103 .

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

[0379] SN Change Confirm message;

[0380] The sixth Xn message can be used for SCG LTM confirmation.

[0381] The sixth inter-node RRC message, the sixth inter-node RRC message can be used for SCG LTM confirmation.

[0382] In some embodiments, in a non-DC scenario, or in an NR-DC scenario with an MCG LTM released by an SCG or an SCG LTM triggered by an MN, step S2109 may not be performed.

[0383] In some embodiments, the information transmission method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2209. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, steps S2201+S2202 can be implemented as an independent embodiment, step S2203 can be implemented as an independent embodiment, steps S2201 to S2203 can be implemented as independent embodiments, step S2204 can be implemented as an independent embodiment, steps S2205+S2206 can be implemented as independent embodiments, steps S2207+S2208 can be implemented as independent embodiments, steps S2207+S2208+S2209 can be implemented as independent embodiments, and steps S2201 to S2209 can be implemented as independent embodiments, but are not limited thereto.

[0384] In some embodiments, steps S2201 to S2209 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0385] In some embodiments, the execution order of steps S2201 to S2209 is not limited.

[0386] In the above embodiment, when initiating an LTM preparation process with the second node, the first node may send first information to the second node. The first information may be used to indicate an LTM candidate cell and / or a corresponding first configuration identifier. The second node may then generate an LTM candidate cell configuration based on the first information. Consequently, after the second node becomes a serving node, LTM is triggered based on the first configuration, achieving the purpose of subsequent LTM and providing high availability.

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

[0388] Step S3101, obtain the fourth message.

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

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

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

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

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

[0394] Step S3102, sending the first message.

[0395] In some embodiments, the first node 101 may send a first message to the second node 102 .

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

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

[0398] Step S3103: Obtain a first response message.

[0399] In some embodiments, the first node 101 may obtain the first response message from the second node 102, but is not limited thereto. The first response message may also be received from other entities.

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

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

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

[0403] In some embodiments, the optional implementation of step S3103 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.

[0404] Step S3104: Send a second message including the first information.

[0405] In some embodiments, the first node 101 may send a second message to the second node 102 .

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

[0407] In some embodiments, the optional implementation of step S3104 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.

[0408] Step S3105: Obtain a second response message.

[0409] In some embodiments, the second response message includes the candidate cell configuration and / or the corresponding measurement configuration updated by the second node 102 based on the first information.

[0410] The first node 101 may obtain the second response message from the second node 102, but is not limited thereto. The first node 101 may also receive a second response message sent by another entity.

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

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

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

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

[0415] Step S3106: Generate a first configuration.

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

[0417] Step S3107: Send the first configuration.

[0418] In some embodiments, the first node 101 may send the first configuration to the terminal.

[0419] In some embodiments, the terminal receives the first configuration.

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

[0421] Step S3108: Obtain RRC reconfiguration completion message.

[0422] In some embodiments, the first node 101 may obtain the RRC reconfiguration completion message from the terminal, but is not limited thereto, and may also receive the RRC reconfiguration completion message sent by other entities.

[0423] In some embodiments, the first node 101 obtains an RRC reconfiguration complete message determined according to a predefined rule.

[0424] In some embodiments, the first node 101 performs processing to obtain the RRC reconfiguration completion message.

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

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

[0427] Step S3109: Send a fourth response message.

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

[0429] In some embodiments, the third node 103 receives the fourth reply message.

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

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

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

[0433] In the above embodiment, the first node may send the first information to the second node after completing the LTM preparation process with the second node, thereby improving the availability of subsequent LTM.

[0434] 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 first node 101. The method includes:

[0435] Step S3201, obtain the fourth message.

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

[0437] Step S3202: Send a first message including first information.

[0438] In some embodiments, the first node 101 sends a first message to the second node 102 , wherein the message includes first information.

[0439] In some embodiments, the second node 102 receives the first message, thereby obtaining the first information.

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

[0441] Step S3203: Obtain a first response message.

[0442] In some embodiments, the first response message includes the candidate cell configuration and / or the corresponding measurement configuration generated by the second node 102 based on the first information.

[0443] In some embodiments, the first node 101 may obtain the first response message from the second node 102, but is not limited thereto. The first response message may also be received from other entities.

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

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

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

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

[0448] Step S3204: Generate a first configuration that needs to be provided to the terminal.

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

[0450] Step S3205: Send the third message.

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

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

[0453] Step S3206, obtain the third response message.

[0454] In some embodiments, the first node 101 may obtain the third response message from the second node 102, but is not limited thereto. The first node 101 may also receive a third response message sent by another entity.

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

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

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

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

[0459] Step S3207: Send the first configuration.

[0460] In some embodiments, the first node 101 sends an RRC reconfiguration message to the terminal, which includes the LTM configuration generated by the first node 101.

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

[0462] Step S3208: Obtain RRC reconfiguration completion message.

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

[0464] Step S3209: Send a fourth response message.

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

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

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

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

[0469] In the above embodiment, the first node may send the first information to the second node when initiating and completing the LTM preparation process with the second node, thereby improving the availability of subsequent LTM.

[0470] 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 second node 102. The method includes:

[0471] Step S3301, obtain the first message.

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

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

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

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

[0476] In some embodiments, the optional implementation of step S3301 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.

[0477] Step S3302: Send a first response message.

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

[0479] In some embodiments, the optional implementation of step S3302 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.

[0480] Step S3303: Obtain a second message, which includes the first information.

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

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

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

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

[0485] In some embodiments, the optional implementation of step S3303 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.

[0486] Step S3304: Send a second response message.

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

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

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

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

[0491] In the above embodiment, the second node can receive the first information sent by the first node after completing the LTM preparation process, thereby achieving the purpose of subsequent LTM and having high availability.

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

[0493] Step S3401: Obtain a first message, which includes first information.

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

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

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

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

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

[0499] Step S3402: Send a first response message.

[0500] In some embodiments, the first response message includes the LTM candidate cell configuration and / or corresponding measurement configuration generated by the second node 102 based on the first information.

[0501] In some embodiments, the second node 102 may send a first response message to the first node 101 .

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

[0503] Step S3403, obtain the third message.

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

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

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

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

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

[0509] Step S3404: Send a third response message.

[0510] In some embodiments, the second node 102 may send a third response message to the first node 101 .

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

[0512] In some embodiments, steps S3401 to S3404 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0513] In some embodiments, the execution order of steps S3401 to S3404 is not limited.

[0514] In the above embodiment, the second node can receive the first information sent by the first node when initiating the LTM preparation process, thereby achieving the purpose of subsequent LTM and having high availability.

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

[0516] Step S3501: Send the fourth message.

[0517] In some embodiments, the third node 103 may send a fourth message to the first node 101 .

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

[0519] Step S3502: Obtain the fourth response message.

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

[0521] In some embodiments, the third node 103 obtains a fourth response message determined according to a predefined rule.

[0522] In some embodiments, the third node 103 performs processing to obtain the fourth response message.

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

[0524] In some embodiments, the optional implementation of step S3502 can refer to the optional implementation of step S2109 in Figure 2A and other related parts of the embodiment involved in Figure 2A, or refer to the optional implementation of step S2209 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0525] In some embodiments, steps S3501 to S3502 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0526] In some embodiments, the execution order of steps S3501 to S3502 is not limited.

[0527] In the above embodiment, the first information can be provided to the second node during the SCG LTM process initiated by the third node, thereby improving the availability of subsequent LTM in the SCG LTM process.

[0528] For the SCG LTM initiated by the MN, the LTM can be triggered by the following two methods:

[0529] Method 1: For example, as shown in FIG4A , the MN-DU sends a Cell Switch Command to the terminal to trigger the initial LTM. When the terminal accesses the LTM candidate cell, the DU of the candidate SN where the candidate cell is located sends a Cell Switch Command to trigger the subsequent LTM.

[0530] Method 2: For example, as shown in FIG4B , the MN-DU sends a Cell Switch Command to the terminal to trigger the initial LTM and subsequent LTM, regardless of which candidate SN the terminal currently accesses.

[0531] For method 2, the MN always knows the corresponding relationship between the LTM candidate cells and the LTM candidate configuration identifiers, so there is no need to send the LTM candidate cells and the matching relationship between the candidate cells and the first configuration identifier to the candidate SN.

[0532] For method 1, when the terminal accesses the corresponding candidate SN, the candidate SN needs to trigger subsequent LTM, so the candidate SN needs to know the LTM candidate cells prepared by other candidate SNs for the UE and their matching relationship with the LTM candidate configuration identifier.

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

[0534] The present invention proposes a method for transmitting LTM configuration matching information that can be used to support subsequent LTM. After becoming a serving node, a candidate node can trigger LTM based on the existing configuration without RRC reconfiguration. In addition to preparing LTM candidate configurations for candidate cells associated with the candidate nodes, the source node and the candidate node also need to exchange LTM candidate cells prepared by other candidate nodes and LTM candidate configuration identifiers associated with the LTM candidate cells. In this way, the candidate node can trigger subsequent LTM without configuration update after UE access.

[0535] In the embodiment of the present disclosure, for scenario 1, MCG LTM in a non-DC scenario.

[0536] Transmit LTM candidate cells, LTM configuration identifiers, and the matching relationship between candidate cells and LTM configuration identifiers between the source gNB and the candidate gNB.

[0537] In Solution 1, after the source gNB and the candidate gNB complete the LTM preparation process, the source gNB sends the candidate cell identifier to be configured for the terminal and its corresponding LTM configuration identifier to the candidate gNB.

[0538] Solution 2: When the source gNB initiates an LTM preparation request to the candidate gNB, the source gNB sends the candidate cell identifier to be configured for the terminal and its corresponding LTM configuration identifier to the candidate gNB.

[0539] Scenario 2: SCG LTM triggered by the mobile node in the NR-DC scenario.

[0540] The LTM candidate cells, the LTM configuration identifier, and the matching relationship between the candidate cells and the LTM configuration identifier are transmitted between the MN and the T-SN.

[0541] Solution 1: After the MN and the candidate SN complete the LTM preparation process, the MN sends the candidate cell identifier to be configured for the UE and its corresponding LTM configuration identifier to the candidate SN.

[0542] Solution 2: When the MN initiates an LTM preparation request to the candidate SN, the MN sends one or more candidate cell identifiers to be provided to the terminal and their corresponding LTM configuration identifiers to the candidate SN. After the candidate SN completes the LTM preparation process, if the LTM candidate cell list prepared by the candidate SN is different from the candidate cell list to be provided by the MN to the UE, the MN sends the prepared LTM candidate cells and their corresponding configuration IDs to the candidate SN.

[0543] Scenario 2: SCG LTM triggered by SN in NR-DC scenario.

[0544] The LTM candidate cells, LTM configuration identifiers, and the matching relationship between the candidate cells and the LTM configuration identifiers are transmitted between the MN and the S-SN, taking into account that different nodes generate the LTM candidate configuration identifiers corresponding to the LTM candidate cells. The following solutions are possible:

[0545] Solution 1: The S-SN generates a corresponding LTM candidate configuration identifier for the LTM candidate configuration of the SCG LTM candidate cell. The MN generates an LTM configuration to be sent to the terminal based on this identifier.

[0546] Solution 2: The MN generates a corresponding LTM candidate configuration identifier for the LTM candidate configuration of the SCG LTM candidate cell and informs the S-SN. The S-SN triggers the initial SCG LTM based on this LTM candidate configuration identifier.

[0547] Solution 3: The candidate SN generates an LTM candidate configuration identifier corresponding to the candidate cell it has prepared, and sends it to the MN through an SN add response message, which then is sent by the MN to the S-SN and other candidate SNs.

[0548] Example 1, for MCG LTM (candidate cell is candidate PCell)

[0549] In Solution 1, after the first node 101 (source gNB) and the second node 102 (candidate gNB) complete the LTM preparation process, the source gNB sends one or more LTM candidate cells to be configured for the terminal, the LTM configuration identifier, and the matching relationship between the LTM candidate cells and the LTM configuration identifier to the candidate gNB (the candidate cells may also be referred to as candidate target cells). This process is shown in Figure 4C and includes the following steps:

[0550] In step S4301, the source gNB sends a first message (e.g., a handover request message) to the candidate gNB, and the candidate gNB generates a corresponding LTM candidate cell configuration based on the first message.

[0551] In step S4302, the candidate gNB sends a first response message to the source gNB, such as a handover request confirmation message, which includes the LTM candidate cell configuration.

[0552] In step S4303, after receiving the first response messages from all candidate gNBs, the source gNB determines the candidate cells to be configured for the terminal and their corresponding LTM configuration identifiers, and sends a second message to the candidate gNBs, which includes the first information.

[0553] Exemplarily, the first information is used to indicate at least one of the following:

[0554] LTM candidate cells;

[0555] LTM configuration identifier;

[0556] The matching relationship between LTM candidate cells and LTM configuration identifiers.

[0557] The candidate cell refers to identification information of the candidate cell, such as a global cell identifier (eg, Cell Global Identifier).

[0558] Exemplarily, the second message may be a handover request message, or a new message for LTM information transmission and update.

[0559] Exemplarily, the candidate cell and its corresponding LTM configuration identifier sent through the second message may be one or more of the following:

[0560] Candidate cells corresponding to other candidate gNBs and their corresponding LTM configuration identifiers;

[0561] All candidate cells to be configured for the UE and their corresponding LTM configuration identifiers;

[0562] Other candidate cells except the first cell indicated in the first message and their corresponding LTM configuration identifiers.

[0563] In some embodiments, the first information may be represented by an LTM configuration identifier matching table, such as shown in Table 1 or Table 2 above.

[0564] Step S4304: The candidate gNB sends a second response message to the source gNB.

[0565] The candidate gNB receives the second message carrying the first information from the source gNB, determines based on the second message whether to update the corresponding candidate cell configuration, and then sends a second response message to the source gNB. The response message may include the updated LTM candidate cell configuration.

[0566] Step S4305: After receiving the second response message sent by the candidate gNB, the source gNB generates an LTM configuration including the LTM candidate cell configuration and sends it to the terminal.

[0567] In step S4306, after receiving the LTM configuration, the terminal sends an RRC connection reconfiguration complete message to the source gNB.

[0568] Solution 2: When the source gNB initiates an LTM preparation request to the candidate gNB, the source gNB sends one or more candidate cells to be provided to the terminal and their corresponding LTM configuration identifiers to the candidate gNB. After the candidate gNB completes the LTM preparation process, if the LTM candidate cell list prepared by the candidate gNB is different from the candidate cell list to be provided to the terminal by the source gNB, the source gNB sends the prepared LTM candidate cells and their corresponding LTM configuration identifiers to the candidate gNB, as shown in Figure 4D, including the following steps:

[0569] In step S4401, the source gNB sends a first message (e.g., a handover request message) to the candidate gNB, including first information. The candidate gNB generates a corresponding candidate cell configuration based on the request message from the source gNB.

[0570] In step S4402, the candidate gNB sends a first response message to the source gNB, such as a handover request confirmation message, which includes the LTM candidate cell configuration generated by the candidate gNB based on the first information.

[0571] In step S4403, after receiving the first response messages from all candidate gNBs, the source gNB determines the candidate cells to be configured for the terminal and their corresponding LTM configuration identifiers. The source gNB can initiate the LTM modification process through a third message.

[0572] If the candidate cell list sent by the candidate gNB differs from the candidate cell list to be offered to the terminal, for example when not all candidate cells to be offered are accepted by the candidate gNB, the source gNB may initiate the LTM information modification / transmission procedure to inform the candidate gNB about the updated list of candidate cells prepared in other candidate gNBs.

[0573] The source gNB may determine to accept the candidate cell and / or its corresponding LTM configuration identifier to the candidate gNB or send the rejected candidate cell and / or its corresponding LTM configuration identifier to the candidate gNB through a third message.

[0574] Step S4404: The candidate gNB sends a third response message to the source gNB.

[0575] In step S4405, the source gNB generates an LTM configuration including the LTM candidate cell configuration and sends it to the terminal.

[0576] In step S4406, after receiving the LTM configuration, the terminal sends an RRC connection reconfiguration complete message to the source gNB.

[0577] Example 2, inter-CU SCG LTM (candidate cell is candidate PSCell)

[0578] For inter-CU SCG LTM, the participation of the MN is required. Therefore, the configuration information of the SCG LTM is always sent to the terminal through the MN, that is, the LTM configuration generated by the MN is sent to the terminal.

[0579] Scenario 2.1: MN initiates SCG LTM (e.g., MN initiated SCG LTM with MN involvement).

[0580] For the SCG LTM initiated by the MN, the LTM can be triggered by the following two methods:

[0581] Method 1: The MN-DU sends a Cell Switch Command to the terminal to trigger the initial LTM. When the terminal accesses the LTM candidate cell, the DU of the C-SN where the candidate cell is located sends a Cell Switch Command to trigger the subsequent LTM.

[0582] Method 2: The MN-DU sends a Cell Switch Command to the terminal to trigger the initial LTM and subsequent LTM, regardless of which C-SN the terminal is currently connected to.

[0583] For method 2, the MN always knows the corresponding relationship between the LTM candidate cells and the LTM candidate configuration identifiers, so there is no need to send the LTM candidate cells and the matching relationship between the candidate cells and the LTM configuration identifiers to the candidate SN.

[0584] For method 1, when the terminal accesses the corresponding C-SN, the C-SN needs to trigger subsequent LTM. Therefore, the C-SN needs to know the LTM candidate cells prepared by other C-SNs for the terminal and their correspondence with the LTM candidate configuration identifiers.

[0585] This is similar to the transmission of LTM candidate cells and corresponding LTM candidate configuration identifiers between the source gNB and the candidate gNB in ​​MCG LTM. There are also two possible solutions:

[0586] Solution 1: After the MN and the candidate SN complete the LTM preparation process, the MN sends the candidate target cell identifier to be configured for the terminal and its corresponding LTM configuration identifier to the candidate SN.

[0587] Solution 2: When the MN initiates an LTM preparation request to the candidate SN, the MN sends one or more candidate cell identifiers to be provided to the terminal and their corresponding LTM configuration identifiers to the C-SN.

[0588] After the C-SN completes the LTM preparation process, if the LTM candidate cell list prepared by the C-SN is different from the candidate cell list to be provided by the MN to the terminal, the MN sends the prepared LTM candidate cells and their corresponding configuration identifiers to the C-SN.

[0589] The detailed steps are similar to the process of transmitting LTM candidate cells and their corresponding LTM configuration identifiers between the source gNB and the candidate gNB during the MCG LTM process. For SCG LTM solution 1, as shown in Figure 4E, the following steps are included:

[0590] Step S4501: The MN sends a first message (SN add request message) to the C-SN, and the C-SN generates a corresponding LTM candidate cell configuration based on the first message.

[0591] In solution 1, the first message does not include the first information.

[0592] Step S4502: The C-SN sends a first response message (SN add request confirmation message) to the MN.

[0593] In solution 1, the first response message includes the LTM candidate cell configuration.

[0594] Step S4503: The MN carries an LTM candidate cell list prepared by other candidate SNs in an SN modification request message, which includes an LTM candidate cell ID and its corresponding LTM configuration identifier.

[0595] Step S4504: The candidate SN updates the LTM candidate cell related configuration based on this, and sends it to the MN via an SN modification request ACK message.

[0596] The subsequent steps are similar to MCG LTM and will not be described in detail.

[0597] Scheme 2 for SCG LTM, as shown in FIG4F , includes the following steps:

[0598] Step S4601: The MN sends a first message (SN add request message) to the C-SN, and the C-SN generates a corresponding LTM candidate cell configuration based on the first message.

[0599] In solution 2, the first message includes first information.

[0600] Step S4602: The C-SN sends a first response message (SN add request confirmation message) to the MN.

[0601] In solution 2, the first response message includes the LTM candidate cell configuration generated by the second node 102 based on the first information.

[0602] In step S4603, if the LTM candidate cell list prepared by the candidate SN is different from the candidate cell list that the MN will provide to the UE, the MN will send the prepared LTM candidate cells and their corresponding configuration identifiers to the candidate SN via an SN Modify Request message (third message). In step S4604, the candidate SN sends an SN Modify Request Confirmation message (third Reply message) to the MN.

[0603] The subsequent steps are similar to MCG LTM and will not be described in detail.

[0604] The first information may also be transmitted through the following examples:

[0605] Through inter-node RRC message transmission, for example, the CG-ConfigInfo message includes the candidate cell identifier and the LTM configuration identifier corresponding to the candidate cell (it may also include other relevant information, such as candidate cell measurement results, etc.), as shown in Table 3.

[0606] In this information, the MN and SN transmit the candidate SN list by referencing candidateCellInfoListMN and candidateCellListCPC in CG-ConfigInfo, but there is no corresponding LTM configuration identifier in these two information. Therefore, the LTM configuration identifier associated with the LTM candidate cell needs to be added to this information:

[0607] In the existing process, candidateCellInfoListMN corresponds to a set of measurement results associated with different frequencies. Each measurement result associated with a different frequency contains a set of cell measurement results, as follows. Therefore, it is necessary to add an LTM configuration identifier to the measurement result corresponding to each cell to associate it with the LTM candidate cell.

[0608] In the existing process, candidateCellListCPC corresponds to a list of cells associated with different frequencies. Each element associated with a different frequency includes a PCI of a group of cells. Therefore, the PCI of each cell in each group of cells needs to be included.

[0609] Scenario 2.2: SN initiated SCG LTM (SN initiated SCG LTM with MN involvement).

[0610] For SN-initiated SCG LTM, compared to scenario 2.1, the source SN initiates the SCG LTM process by sending an SN Change Required message to the mobile node. The subsequent process is similar to scenario 2.1. Therefore, in steps S4702 to S4705 in Figure 4G , the process of transmitting candidate small cells and corresponding LTM configuration identifiers between the mobile node and the candidate SN is similar to scenario 2.1 and is not described in detail here. The following description focuses on steps S4701 and S4708.

[0611] Step S4701: The S-SN sends a fourth message (SN change request message) to the MN.

[0612] The fourth message may include one or more LTM candidate cell identifiers recommended by the S-SN. The S-SN sends one or more recommended C-SNs to the MN, each C-SN corresponding to a set of LTM candidate cell identifiers. The relevant information for requesting LTM also includes an LTM candidate configuration identifier corresponding to each LTM candidate cell. Based on the identifiers, the MN generates the corresponding LTM configuration. The recommended LTM candidate cells and corresponding candidate configuration identifiers may be implemented in one or more of the following ways:

[0613] The MN sends the first information to the C-SN through the first message (or the second message), and indicates in the first message (or the second message) that the first information is used to indicate the LTM candidate cell or cell list.

[0614] The inter-node RRC message is sent to the C-SN via an inter-node RRC message. The inter-node RRC message may be carried in the first message (or the second message) and sent to the C-SN.

[0615] Step S4708: After the MN receives the third response message from the C-SN, the MN sends a fourth response message, such as an SN Change Confirm message, to the S-SN to inform the S-SN of the LTM candidate cells prepared by the C-SN.

[0616] The SN Change Confirm message contains one or more T-SNs for which LTM configurations are prepared, along with a list of corresponding SCG LTM candidate cells. The SN Change Confirm message also contains the LTM candidate configuration identifier corresponding to each LTM candidate cell. In the LTM configuration sent by the mobile node to the terminal, each LTM candidate cell corresponds to a corresponding LTM candidate configuration identifier.

[0617] The solution for transmitting LTM candidate cells and LTM candidate configurations in the SN change Required message and SN change confirm message can be seen in the solution in Scenario 2.1.

[0618] In the above SCG LTM process, since the S-SN needs to trigger the initial SCG LTM and the candidate SN triggers the subsequent SCG LTM, who generates the LTM candidate configuration identifier? The following schemes can be used:

[0619] Solution 1: The S-SN generates a corresponding LTM candidate configuration identifier for the LTM candidate configuration of the SCG LTM candidate cell. The MN generates the LTM configuration according to this identifier and sends it to the UE.

[0620] Solution 2: The MN generates a corresponding LTM candidate configuration identifier for the LTM candidate configuration of the SCG LTM candidate cell and informs the S-SN. The S-SN triggers the initial SCG LTM based on this LTM candidate configuration identifier.

[0621] Solution 3: The candidate SN generates an LTM candidate configuration identifier corresponding to the candidate cell it has prepared, and sends it to the MN through an SN add response message. The MN then sends it to the S-SN through step 8 above and to other candidate SNs through step 4.

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

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

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

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

[0626] In some embodiments, the transceiver module 5101 is configured to send first information to the second node, where the first information is used to match a first configuration, and the first configuration is triggered by layer 1 or layer 2.

[0627] Optionally, the above-mentioned transceiver module 5101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first node 5100 in any of the above methods (for example, step S2101, step S2102, step S2103, step S2104, step S2105, step S2107, step S2108, step S2109, step S2201, step S2202, step S2203, step S2205, step S2206, step S2207, step S2208, step S2209, but not limited to these), which will not be repeated here.

[0628] In some embodiments, the first node 5100 may further include a processing module 5102 (not shown in FIG. 5A ).

[0629] Optionally, the processing module 5102 is used to execute at least one of the other steps (such as step S2106 and step S2204, but not limited thereto) executed by the first node 5100 in any of the above methods, which will not be repeated here.

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

[0631] In some embodiments, the transceiver module 5201 is configured to receive first information sent by a first node, where the first information is used to match a first configuration, and the first configuration is triggered by layer 1 or layer 2. Optionally, the transceiver module 5201 is configured to execute at least one of the communication steps such as sending and / or receiving performed by the second node 5200 in any of the above methods (for example, step S2102, step S2103, step S2104, step S2105, step S2202, step S2203, step S2205, and step S2206, but not limited thereto), which will not be further described herein.

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

[0633] In some embodiments, the transceiver module 5201 is configured as the first node to send a fourth message, where the fourth message is used to initiate a secondary cell group SCG LTM process.

[0634] The transceiver module 5201 is further configured to receive a fourth response message sent by the first node, where the fourth response message is used to indicate that the SCG LTM has been completed.

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

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

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

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

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

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

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

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

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

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

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

[0646] In some embodiments, the interface circuit 6202 performs at least one of the communication steps of sending and / or receiving in the above method (e.g., step S2101, step S2102, step S2103, step S2104, step S2105, step S2107, step S2108, step S2109, step S2201, step S2202, step S2203, step S2205, step S2206, step S2207, step S2208, step S2209, but not limited thereto). The interface circuit 6202 performing the communication steps of sending and / or receiving in the above method, for example, means that the interface circuit 6202 performs data exchange between the processor 6201, chip 6200, memory 6203, or transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps (e.g., step S2106, step S2204, but not limited thereto).

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

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

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

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

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

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

Claims

1. An information transmission method, characterized in that, The method is executed by a first node and includes: Sending first information to a second node, where the first information is used to match a first configuration triggered by layer 1 or layer 2.

2. The method according to claim 1, wherein The first node is a source master node S-MN, and the second node is a candidate master node C-MN; or The first node is a master node MN, and the second node is a candidate secondary node C-SN.

3. The method according to claim 1 or 2, characterized in that, The first information is associated with other candidate nodes other than the second node.

4. The method according to any one of claims 1 to 3, characterized in that The sending of the first information to the second node includes: After completing a first preparation process with the second node, sending the first information to the second node, where the first preparation process is triggered by layer 1 or layer 2; or When initiating the first preparation process with the second node, sending the first information to the second node, where the first preparation process is triggered by layer 1 or layer 2.

5. The method according to claim 4, wherein The second message includes the first information, and the second message is used to match the first configuration after the first preparation process is completed.

6. The method according to claim 5, wherein The second message is any of the following messages: Handover request message; SN modification request message; First Xn message, where the first Xn message is used for LTM request; First inter-node RRC message, where the first inter-node RRC message is used for LTM request.

7. The method according to claim 5 or 6, characterized in that, The method further includes: Receiving a second response message sent by the second node, where the second response message is used for matching confirmation of the first configuration, and the second response message includes an updated candidate cell configuration and / or corresponding measurement configuration of the second node based on the first information, and the candidate cell configuration is triggered by layer 1 or layer 2.

8. The method according to claim 7, wherein The second response message is any of the following messages: Handover request confirmation message; SN modification request confirmation message; Second Xn message, where the second Xn message is used for LTM request confirmation; Second inter-node RRC message, where the second inter-node RRC message is used for LTM request confirmation.

9. The method according to any one of claims 5 - 8, characterized in that The method further includes: Generating the first configuration, where the first configuration includes an updated candidate cell configuration generated by the second node, and the candidate cell configuration is triggered by layer 1 or layer 2; Sending the first configuration to the terminal.

10. The method according to claim 4, wherein The first message includes the first information, and the first message is used to initiate the first preparation process.

11. The method according to claim 10, characterized in that, The method further includes: Receiving a first response message sent by the second node, where the first response message is used to indicate completion of the first preparation process, and the first response message includes a candidate cell configuration and / or corresponding measurement configuration generated by the second node based on the first information, and the candidate cell configuration is triggered by layer 1 or layer 2; Based on the first response message, sending the first configuration to the terminal, where the first configuration includes the candidate cell configuration that the first node needs to provide to the terminal.

12. The method according to claim 11, wherein The method further includes: If the candidate cell configuration to be provided to the terminal is different from the candidate cell configuration included in the first response message, sending a third message to the second node, where the third message is used to indicate at least one of the following: Candidate cells prepared for the terminal; First configuration identifier; Matching relationship between the candidate cells prepared for the terminal and the first configuration identifier; Receive the third response message sent by the second node.

13. The method according to claim 12, wherein The third message is any of the following messages: SN modification request message; The third Xn message, which is used for LTM update; The third inter-node RRC message, which is used for LTM update.

14. The method according to claim 12 or 13, characterized in that, The third response message is any of the following messages: SN modification request confirmation message; The fourth Xn message, which is used for LTM update confirmation; The fourth inter-node RRC message, which is used for LTM update confirmation.

15. The method according to any one of claims 5-14, characterized in that, The first message is any of the following messages: Handover request message; SN addition request message; The first Xn message, which is used for LTM request; The first inter-node RRC message, which is used for LTM request.

16. The method according to any one of claims 5 to 15, characterized in that, The first response message is any of the following messages: Handover request confirmation message; SN addition request confirmation message; The second Xn message, which is used for LTM request confirmation; The second inter-node RRC message, which is used for LTM request confirmation.

17. The method according to any one of claims 4-16, characterized in that, The method further includes: Receiving a fourth message sent by a third node, where the fourth message is used to initiate a secondary cell group (SCG) LTM process; After receiving the second response message or the third response message sent by the second node, sending a fourth response message to the third node, where the fourth response message is used to indicate that the SCG LTM has been completed.

18. The method according to claim 17, wherein The fourth message is an SN change request message, and / or the fourth response message is an SN change confirmation message.

19. An information transmission method, characterized in that, The method is executed by a second node and includes: Receiving first information sent by a first node, where the first information is used to match a first configuration triggered by layer 1 or layer 2.

20. The method according to claim 19, characterized in that, The first node is a source master node (S-MN), and the second node is a candidate master node (C-MN); or The first node is a master node (MN), and the second node is a candidate secondary node (C-SN).

21. The method according to claim 19 or 20, characterized in that, The first information is associated with other candidate nodes other than the second node.

22. The method according to any one of claims 19-21, characterized in that, The receiving the first information sent by the first node includes: After completing a first preparation process with the first node, receiving the first information sent by the first node, where the first preparation process is triggered by layer 1 or layer 2; or Receiving the first information sent by the first node when initiating a first preparation process with the second node, where the first preparation process is triggered by layer 1 or layer 2.

23. The method according to claim 22, wherein The first information is included in a second message, and the second message is used to match the first configuration after the first preparation process is completed.

24. The method according to claim 23, wherein The second message is any of the following messages: Handover request message; SN addition request message; The first Xn message, which is used for LTM request; The first inter-node RRC message, which is used for LTM request.

25. The method according to claim 23 or 24, characterized in that The method further includes: Based on the first information, updating the generated candidate cell configuration to determine the updated candidate cell configuration, where the candidate cell configuration is triggered by layer 1 or layer 2. Send a second response message to the first node, where the second response message is used for matching confirmation of the first configuration, and the updated candidate cell configuration and / or corresponding measurement configuration are included in the second response message.

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

27. The method according to claim 22, wherein The first information is included in the first message, and the first message is used to initiate the first preparation process.

28. The method according to claim 27, wherein The method further includes: Generate a candidate cell configuration based on the first information, where the candidate cell configuration is triggered by layer 1 or layer 2; Send a first response message to the first node, where the first response message is used to indicate completion of the first preparation process, and the candidate cell configuration generated by the second node based on the first information is included in the first response message.

29. The method according to claim 28, wherein The method further includes: Receive a third message sent by the first node, where the third message is used to indicate at least one of the following: Candidate cells prepared for the terminal; First configuration identifier; Matching relationship between the candidate cells prepared for the terminal and the first configuration identifier; Send a third response message to the first node.

30. The method according to claim 29, wherein The third message is any one of the following messages: SN modification request message; Third Xn message, where the third Xn message is used for LTM update; Third inter-node RRC message, where the third inter-node RRC message is used for LTM update.

31. The method according to claim 29 or 30, characterized in that, The third response message is any one of the following messages: SN modification request confirmation message; Fourth Xn message, where the fourth Xn message is used for LTM update confirmation; Fourth inter-node RRC message, where the fourth inter-node RRC message is used for LTM confirmation.

32. The method according to any one of claims 22-31, characterized in that, The first message is any one of the following messages: Handover request message; SN addition request message .

33. The method according to any one of claims 22-32, characterized in that, The first response message is any one of the following messages: Handover request confirmation message; SN addition request confirmation message.

34. An information transmission method, characterized in that, The method is executed by a third node and includes: Send a fourth message to the first node, where the fourth message is used to initiate a secondary cell group (SCG) LTM process; Receive a fourth response message sent by the first node, where the fourth response message is used to indicate that the SCG LTM has been completed.

35. The method according to claim 34, characterized in that, The fourth message is an SN change request message, and / or the fourth response message is an SN change confirmation message.

36. A first node, characterized in that, Includes: A transceiver module, configured to send first information to a second node, where the first information is used to match a first configuration, and the first configuration is triggered by layer 1 or layer 2.

37. A second node, characterized in that, Includes: A transceiver module, configured to receive first information sent by a first node, where the first information is used to match a first configuration, and the first configuration is triggered by layer 1 or layer 2.

38. A third node, characterized in that, Includes: A transceiver module, configured to send a fourth message to the first node, where the fourth message is used to initiate a secondary cell group (SCG) LTM process; The transceiver module is further configured to receive the fourth response message sent by the first node, where the fourth response message is used to indicate that the SCG LTM has been completed.

39. A first node, characterized in that, Includes: One or more processors; Wherein, the processor is configured to execute the information transmission method according to any one of claims 1-18.

40. A second node, characterized in that, Comprising: One or more processors; Wherein, the processor is configured to execute the method of the information transmission behavior according to any one of claims 19-33.

41. A third node, characterized in that, Comprising: One or more processors; Wherein, the processor is configured to execute the method of the information transmission behavior according to claim 34 or 35.

42. 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-18, the second node is configured to implement the information transmission method according to any one of claims 19-33, and the third node is configured to implement the information transmission method according to claim 34 or 35.

43. A storage medium storing instructions, characterized in that, When the instruction runs on the communication device, the communication device is caused to execute the information transmission method according to any one of claims 1-18, 19-33, or 34-35.

Images