Communication methods and devices, and communication system and storage medium

Abstract

The embodiments of the present disclosure relate to the technical field of communications. Disclosed are communication methods and apparatuses, and a computer-readable storage medium. A communication method comprises: a first node acquiring prediction-related information from a terminal; and sending a first message to a second node, wherein the first message comprises the prediction-related information. In the embodiments of the present disclosure, prediction-related information from a terminal is sent to a second node, so that the transmission of information for model prediction between nodes can be realized.

Description

Communication methods, devices, systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to a communication method, device, system, and storage medium. Background Technology

[0002] In mobile communication systems, to support terminal mobility and obtain timely information on the channel conditions of the terminal's serving cell and surrounding cells, network devices configure the terminal to perform radio resource management (RRM) measurements. During RRM measurements, the network device sends measurement configuration information to the terminal, which then performs in-frequency, out-of-frequency, or out-of-system measurements based on the configuration information and reports the measurements to the network device.

[0003] To better support terminal mobility, the transmission mechanisms associated with mobility operations need to be improved.

[0004] Summary of the Invention

[0005] This disclosure provides a communication method, device, system, and storage medium.

[0006] A first aspect of this disclosure provides a communication method, the method being executed by a first node, the method comprising:

[0007] Obtain prediction-related information from the terminal;

[0008] Send a first message to the second node, the first message including the prediction-related information.

[0009] A second aspect of this disclosure provides a communication method, the method being executed by a second node, the method comprising:

[0010] The system receives a first message sent by a first node, the first message including prediction-related information, which is obtained by the first node from the terminal.

[0011] A third aspect of this disclosure provides a communication method, the method being executed by a third node, the method comprising:

[0012] The receiving terminal sends an eighth message, which includes prediction-related information;

[0013] Send a third message to the first node, the third message including the prediction-related information;

[0014] The prediction-related information is forwarded from the first node to the second node.

[0015] A fourth aspect of this disclosure provides a first node, including:

[0016] The first transceiver module is used to acquire prediction-related information from the terminal and send a first message to the second node, the first message including the prediction-related information.

[0017] A fifth aspect of this disclosure provides a second node, including:

[0018] The second transceiver module is used to receive a first message sent by the first node, the first message containing prediction-related information, which is obtained by the first node from the terminal.

[0019] A sixth aspect of this disclosure provides a third node, including:

[0020] The third transceiver module is used to receive a sixth message sent by the terminal, the sixth message including prediction-related information, and to send a third message to the first node, the third message including the prediction-related information.

[0021] The prediction-related information is forwarded from the first node to the second node.

[0022] A seventh aspect of this disclosure provides a first node, including:

[0023] One or more processors;

[0024] The first node is used to execute the optional implementation of the first aspect described above.

[0025] An eighth aspect of this disclosure provides a second node, including:

[0026] One or more processors;

[0027] The second node is used to execute the optional implementation of the second aspect described above.

[0028] A ninth aspect of this disclosure provides a third node, including:

[0029] One or more processors;

[0030] The third node is used to execute the optional implementation of the aforementioned third aspect.

[0031] A tenth aspect of this disclosure provides a communication system including a first node and a second node, wherein the first node is configured to implement the method described in an optional embodiment of the first aspect, and the second node is configured to implement the method described in an optional embodiment of the second aspect.

[0032] According to an eleventh aspect of the present disclosure, a computer-readable storage medium is provided, wherein executable instructions are stored therein, which are loaded and executed by the processor to implement the method described in the optional embodiments of the first, second, or third aspects.

[0033] According to a twelfth aspect of the present disclosure, a computer program product is provided, the computer program product including a computer program that, when executed by a processor, implements the methods described in the optional embodiments of the first, second, or third aspects.

[0034] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

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

[0036] Figure 1 is a schematic diagram of a wireless communication system according to an exemplary embodiment;

[0037] Figure 2a is a flowchart illustrating a communication method according to an exemplary embodiment;

[0038] Figure 2b is a flowchart illustrating a communication method according to an exemplary embodiment;

[0039] Figure 2c is a flowchart illustrating a communication method according to an exemplary embodiment;

[0040] Figure 3a is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0041] Figure 3b is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0042] Figure 3c is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0043] Figure 4a is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0044] Figure 4b is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0045] Figure 5 is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0046] Figure 6a is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0047] Figure 6b is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0048] Figure 7a is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0049] Figure 7b is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0050] Figure 7c is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0051] Figure 7d is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0052] Figure 7e is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0053] Figure 7f is a flowchart illustrating the communication method according to an embodiment of this disclosure;

[0054] Figure 8a is a schematic diagram of the structure of the first node proposed in an embodiment of this disclosure;

[0055] Figure 8b is a schematic diagram of the structure of the second node proposed in an embodiment of this disclosure;

[0056] Figure 8c is a schematic diagram of the structure of the third node proposed in an embodiment of this disclosure;

[0057] Figure 9a is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0058] Figure 9b is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0059] This disclosure provides communication methods, devices, communication systems, and storage media.

[0060] In a first aspect, embodiments of this disclosure propose a communication method, which is executed by a first node, the method comprising:

[0061] Obtain prediction-related information from the terminal;

[0062] Send a first message to the second node, the first message including the prediction-related information.

[0063] In the above embodiments, by sending prediction-related information from the terminal to the second node, information for model prediction can be transmitted between nodes.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, obtaining prediction-related information from the terminal includes:

[0065] Receive a second message sent by the terminal, the second message including the prediction-related information; or...

[0066] The third message sent by the third node is received, the third message including the prediction-related information, wherein the prediction-related information is obtained by the third node from the terminal.

[0067] In the above embodiments, the first node can directly obtain prediction-related information from the terminal side or obtain prediction-related information from the third node, thereby adapting to more scenarios.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes prediction-related information from the second message; or, the first message includes prediction-related information from the third message, wherein the prediction-related information in the third message is prediction-related information obtained by the third node from the terminal.

[0069] In the above embodiments, the first node can forward the prediction-related information obtained from the terminal to the second node, or obtain the prediction-related information from the terminal to the third node, thereby adapting to more scenarios.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the prediction-related information includes: time information of the prediction results output by the prediction model on the terminal side.

[0071] In the above embodiments, the prediction-related information on the terminal side may include the time information of the prediction results output by the prediction model on the terminal side, which is beneficial for the network side to filter information.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes: a first Xn message or a first inter-node radio resource control (RRC) message.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, in response to a second message sent from the terminal that the prediction-related information is obtained, the first Xn message includes at least one of the following:

[0074] Switch request message

[0075] Add a request message to the secondary node SN;

[0076] SN modification request message; and

[0077] The first inter-node RRC message includes a handover preparation message;

[0078] In response to the third message obtained from the third node regarding the prediction-related information, the first Xn message includes at least one of the following:

[0079] Add a request message to the SN;

[0080] SN modification request message;

[0081] SN changes request message;

[0082] SN modification request reply message; and

[0083] The first inter-node RRC message includes cell group configuration messages.

[0084] In the above embodiments, the information used for model prediction can be transmitted between nodes through existing Xn messages or inter-node RRC messages, which can reduce the impact on network performance.

[0085] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes: a second Xn message or a second inter-node RRC message.

[0086] In conjunction with some embodiments of the first aspect, in some embodiments, the second Xn message or the second inter-node RRC message is used to transmit the prediction-related information between nodes, wherein the second inter-node RRC message is included in the second Xn message or included in the first Xn message.

[0087] In the above embodiments, by introducing Xn messages or inter-node RRC messages specifically for transmitting prediction-related information between nodes, the transmission of information for model prediction between nodes can be better realized.

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

[0089] Receive a fourth message sent by the second node, the fourth message including information related to the prediction model;

[0090] In response to the fourth message, perform one of the following operations:

[0091] Select the second node as the target node;

[0092] Select the second node as the candidate node;

[0093] A fifth message is sent to the second node, which is used to cancel the operation related to the handover.

[0094] In the above embodiments, the first node can determine whether the terminal is suitable to access the node based on the prediction model information fed back by the second node, and can prepare the cell selection configuration for the terminal based on the prediction information obtained from the terminal and the prediction model information obtained from the second node. From the perspective of the terminal, the signaling overhead of the terminal sending prediction information to the second node can be reduced.

[0095] In conjunction with some embodiments of the first aspect, in some embodiments, the information related to the prediction model includes at least one of the following:

[0096] The second node supports prediction functions;

[0097] The model information corresponding to the prediction functions supported by the second node.

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

[0099] Receive a sixth message sent by the second node, the sixth message including a first request message, used to request the first node to send prediction-related information from the terminal;

[0100] Sending the first message to the second node includes:

[0101] In response to the sixth message, the first message is sent to the second node.

[0102] In the above embodiments, the first node sends a message with prediction-related information from the terminal based on the request sent by the second node, and sends the requested prediction-related information to the second node, which can better meet the needs of the second node.

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

[0104] Send a seventh message to the second node, the seventh message including relevant information for the second node to prepare for mobility;

[0105] The sixth message is a response message to the seventh message.

[0106] In the above embodiments, the second node includes a request in its response message to the mobility request message to send prediction-related information from the terminal. This can reduce the impact on network performance. At the same time, it can enable the first node to provide the prediction-related information needed by the second node, thus better meeting the needs of the second node.

[0107] In conjunction with some embodiments of the first aspect, in some embodiments, the sixth message includes at least one of the following:

[0108] The first instruction information is used to instruct the first node to provide prediction-related information from the terminal;

[0109] The second instruction information is used to indicate the training data corresponding to the first prediction function required by the second node;

[0110] The third indication information is used to indicate the prediction result of the second prediction function on the terminal side required by the second node;

[0111] The fourth instruction information is used to indicate the input information required for model inference by the second node.

[0112] In conjunction with some embodiments of the first aspect, in some embodiments, the prediction result of the second prediction function on the terminal side includes at least one of the following:

[0113] Predicted results of a failed switchover;

[0114] Predicted cell-level measurement results;

[0115] Predicted beam-level measurement results;

[0116] Configuration of predicted measurement events;

[0117] Whether the predicted measurement events meet the corresponding configuration conditions;

[0118] The predicted and recommended optimal target cell;

[0119] The predicted recommended at least one candidate target cell.

[0120] In conjunction with some embodiments of the first aspect, in some embodiments, the prediction-related information from the terminal includes at least one of the following:

[0121] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0122] Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates;

[0123] Training data, which is used to train the prediction model on the second node side.

[0124] In conjunction with some embodiments of the first aspect, in some embodiments, the inference data includes at least one of the following:

[0125] The results output by the prediction model on the terminal side;

[0126] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0127] In conjunction with some embodiments of the first aspect, in some embodiments, the prediction-related information is used for at least one of the following prediction functions:

[0128] Predicting measurement results;

[0129] Switchover failure prediction;

[0130] Wireless link failure prediction;

[0131] Predicting measurement events.

[0132] In conjunction with some embodiments of the first aspect, in some embodiments, the prediction-related information is used to perform at least one of the following operations:

[0133] Optimized mobility operations;

[0134] Mobility configuration update;

[0135] Predictive model inference;

[0136] Predictive model training.

[0137] Secondly, embodiments of this disclosure propose a communication method, which is executed by a second node, the method comprising:

[0138] The system receives a first message sent by a first node, the first message including prediction-related information, which is obtained by the first node from the terminal.

[0139] In conjunction with some embodiments of the second aspect, in some embodiments, the prediction-related information is the prediction-related information reported by the terminal and obtained by the first node; or,

[0140] The prediction-related information is the prediction-related information sent by the third node and obtained by the first node, wherein the prediction-related information sent by the third node is the prediction-related information obtained by the third node from the terminal.

[0141] In conjunction with some embodiments of the second aspect, in some embodiments, the prediction-related information includes: time information of the prediction results output by the prediction model on the terminal side.

[0142] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes: a first Xn message or a first inter-node radio resource control (RRC) message.

[0143] In conjunction with some embodiments of the second aspect, in some embodiments, in response to a second message sent by the terminal from which the prediction-related information is obtained by the first node, the first Xn message includes at least one of the following:

[0144] Switch request message

[0145] Add a request message to the SN;

[0146] SN modification request message; and

[0147] The first inter-node RRC message includes a handover preparation message;

[0148] In response to the prediction-related information being obtained by the first node from a third message sent by the third node, the first Xn message includes at least one of the following:

[0149] Add a request message to the SN;

[0150] SN modification request message;

[0151] SN changes request message;

[0152] SN modification request reply message; and

[0153] The first inter-node RRC message includes cell group configuration messages.

[0154] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes: a second Xn message or a second inter-node RRC message.

[0155] In conjunction with some embodiments of the second aspect, in some embodiments, the second Xn message is used to transmit the prediction-related information between nodes, and the second inter-node RRC message is included in the second Xn message or included in the first Xn message.

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

[0157] A fourth message is sent to the first node, the fourth message including information related to the prediction model;

[0158] The fourth message is used to determine one of the following operations:

[0159] Select the second node as the target node;

[0160] Select the second node as the candidate node;

[0161] A fifth message is sent to the second node, which is used to cancel the operation related to the handover.

[0162] In conjunction with some embodiments of the second aspect, in some embodiments, the information related to the prediction model includes at least one of the following:

[0163] The second node supports prediction functions;

[0164] The model information corresponding to the prediction functions supported by the second node.

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

[0166] A sixth message is sent to the first node, the sixth message including a first request message, which requests the first node to send prediction-related information from the terminal;

[0167] The first message is a response message to the sixth message.

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

[0169] Receive a seventh message sent by the first node, the seventh message including relevant information for the second node to prepare mobility;

[0170] The sixth message is a response message to the seventh message.

[0171] In conjunction with some embodiments of the second aspect, in some embodiments, the sixth message includes at least one of the following:

[0172] The first instruction information is used to instruct the first node to provide prediction-related information from the terminal;

[0173] The second instruction information is used to indicate the training data corresponding to the first prediction function required by the second node;

[0174] The third indication information is used to indicate the prediction result of the second prediction function on the terminal side required by the second node;

[0175] The fourth instruction information is used to indicate the input information required for model inference by the second node.

[0176] In conjunction with some embodiments of the second aspect, in some embodiments, the prediction result of the second prediction function on the terminal side includes at least one of the following:

[0177] Predicted results of a failed switchover;

[0178] Predicted cell-level measurement results;

[0179] Predicted beam-level measurement results;

[0180] Configuration of predicted measurement events;

[0181] Whether the predicted measurement events meet the corresponding configuration conditions;

[0182] The predicted and recommended optimal target cell;

[0183] The predicted recommended at least one candidate target cell.

[0184] In conjunction with some embodiments of the second aspect, in some embodiments, the prediction-related information from the terminal includes at least one of the following:

[0185] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0186] Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates;

[0187] Training data, which is used to train the prediction model on the second node side.

[0188] In conjunction with some embodiments of the second aspect, in some embodiments, the inference data includes at least one of the following:

[0189] The results output by the prediction model on the terminal side;

[0190] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0191] In conjunction with some embodiments of the second aspect, in some embodiments, the prediction-related information is used for at least one of the following prediction functions:

[0192] Predicting measurement results;

[0193] Switchover failure prediction;

[0194] Wireless link failure prediction;

[0195] Predicting measurement events.

[0196] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: performing at least one of the following operations based on the prediction-related information:

[0197] Optimized mobility operations;

[0198] Mobility configuration updated;

[0199] Predictive model inference;

[0200] Predictive model training.

[0201] Thirdly, embodiments of this disclosure propose a communication method, which is executed by a third node, the method comprising:

[0202] The receiving terminal sends an eighth message, which includes prediction-related information;

[0203] Send a third message to the first node, the third message including the prediction-related information;

[0204] The prediction-related information is forwarded from the first node to the second node.

[0205] In conjunction with some embodiments of the third aspect, in some embodiments, the prediction-related information includes: time information of the prediction results output by the prediction model on the terminal side.

[0206] In conjunction with some embodiments of the third aspect, in some embodiments, the prediction-related information in the sixth message includes at least one of the following:

[0207] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0208] Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates;

[0209] Training data, which is used to train the prediction model on the second node side.

[0210] In conjunction with some embodiments of the third aspect, in some embodiments, the inference data includes at least one of the following:

[0211] The results output by the prediction model on the terminal side;

[0212] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0213] In conjunction with some embodiments of the third aspect, in some embodiments, the prediction-related information is used for at least one of the following prediction functions:

[0214] Predicting measurement results;

[0215] Switchover failure prediction;

[0216] Wireless link failure prediction;

[0217] Predicting measurement events.

[0218] In conjunction with some embodiments of the third aspect, in some embodiments, the prediction-related information is used to perform at least one of the following operations:

[0219] Optimized mobility operations;

[0220] Mobility configuration updated;

[0221] Predictive model inference;

[0222] Predictive model training.

[0223] Fourthly, embodiments of this disclosure provide a first node, comprising:

[0224] The first transceiver module is used to acquire prediction-related information from the terminal and send a first message to the second node, the first message including the prediction-related information.

[0225] Fifthly, embodiments of this disclosure provide a second node, comprising:

[0226] The second transceiver module is used to receive a first message sent by the first node, the first message containing prediction-related information, which is obtained by the first node from the terminal.

[0227] Sixthly, embodiments of this disclosure provide a third node, including:

[0228] The third transceiver module is used to receive a sixth message sent by the terminal, the sixth message including prediction-related information, and to send a third message to the first node, the third message including the prediction-related information.

[0229] The prediction-related information is forwarded from the first node to the second node.

[0230] In a seventh aspect, embodiments of this disclosure provide a first node, comprising:

[0231] One or more processors;

[0232] The first node is used to execute the optional implementation of the first aspect described above.

[0233] Eighthly, embodiments of this disclosure provide a second node, comprising:

[0234] One or more processors;

[0235] The second node is used to execute the optional implementation of the second aspect described above.

[0236] In a ninth aspect, embodiments of this disclosure provide a third node, comprising:

[0237] One or more processors;

[0238] The third node is used to execute the optional implementation of the aforementioned third aspect.

[0239] In a tenth aspect, embodiments of this disclosure provide a communication system including a first node and a second node, wherein the first node is used to implement the method described in the optional embodiments of the first aspect, and the second node is used to implement the method described in the optional embodiments of the second aspect.

[0240] In conjunction with some embodiments of the tenth aspect, in some embodiments, a third node is further included, wherein the third node is used to implement the method described in the alternative implementation of the third aspect.

[0241] Eleventhly, embodiments of this disclosure provide a computer-readable storage medium storing executable instructions that are loaded and executed by the processor to implement the methods described in the optional embodiments of the first, second, or third aspects.

[0242] In a twelfth aspect, embodiments of this disclosure provide a computer program product comprising a computer program that, when executed by a processor, implements the methods described in the optional embodiments of the first, second, or third aspects.

[0243] In a thirteenth aspect, embodiments of this disclosure provide a chip or chip system including processing circuitry for performing the method described in an optional implementation of the first or second aspect above.

[0244] Understandably, the aforementioned devices, communication equipment, communication systems, storage media, program products, and computer programs for random access are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. The communication equipment can be a terminal or a network device.

[0245] This disclosure provides communication methods, apparatus, devices, systems, and storage media.

[0246] In some embodiments, the terms communication method and information processing method, and for random access can be used interchangeably; the terms device for random access and information processing device, communication device, etc., can be used interchangeably; and the terms information processing system, communication system, etc., can be used interchangeably.

[0247] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of the embodiments disclosed. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0248] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0249] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the embodiments of this disclosure.

[0250] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0251] In the embodiments disclosed herein, "multiple" refers to two or more.

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

[0253] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.

[0254] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.

[0255] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. As another example, if the object being described is "information", then "first configuration" and "second configuration" can be the same information or different information, and their content can be the same or different.

[0256] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0257] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “in response to…”, “if…”, etc., can be used interchangeably.

[0258] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0259] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0260] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0261] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0262] In some embodiments, the access network device, core network device, or network device can be replaced by a terminal. For example, various embodiments of this disclosure can also be applied to structures that replace communication between the access network device, core network device, or network device and the terminal with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side").

[0263] For example, uplink channels and downlink channels can be replaced with side channels, and uplink links and downlink links can be replaced with side links.

[0264] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0265] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0266] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0267] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0268] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0269] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0271] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0272] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

[0273] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0274] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0275] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.

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

[0277] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0278] In some embodiments, the access network device may be a single device, multiple devices, or a group of devices, including all or part of a first network element, a second network element, etc. Network elements may be virtual or physical. Network devices may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0279] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. 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), or a Next Generation Core (NGC).

[0280] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0281] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0282] The embodiments disclosed herein can 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), 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, utilizing other systems for random access, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0283] Machine learning algorithms are one of the most important methods for implementing artificial intelligence technology. Machine learning can obtain models from large amounts of training data, and these models can then be used to predict events. In many fields, machine learning models can achieve very accurate predictions.

[0284] To support Layer 3 (L3) mobility, the network configures RRM measurements for the UE. Based on the measurement results reported by the UE, the network can trigger a handover (HO). Current L3 measurement reports can include both cell-level and beam-level measurement results. Based on the UE's measurement reports, the network can determine the target cell for handover and the optimal beam for the UE to access. After the target cell and / or beam are confirmed, a handover command (Reconfiguration with sync) is sent to the UE, carrying configuration information for the target cell. This configuration information may include bearer configuration, MAC configuration, and random access configuration. Upon receiving the handover command, the UE synchronizes with the target cell, initiates a random access procedure to access the target cell, and begins using the target cell's configuration.

[0285] In existing L3 handover mechanisms, handover is triggered and executed based on reported historical measurement results and / or measurement events, essentially a reactive (also known as a responsive) approach. This approach may perform well in low-mobility scenarios within existing macrocells, but it can encounter problems when UE mobility is high, in high-density deployment scenarios, or when there is mobility for both existing and future services (e.g., XR). Issues may arise, such as increased likelihood of handover failures, radio link failures, ping-pong handovers, throughput loss, or premature / late handover requests. To improve handover robustness, Conditional Handover (CHO) was introduced. To reduce downtime from frequent inter-cell handovers, L1 / L2 triggered Mobility Handover (LTM HO) was introduced. However, both of these mechanisms remain reactive.

[0286] The current research proposes AI-based mobility optimization schemes, including prediction of measurement results, prediction of handover failure (HO failure, HOF), and prediction of radio link failure (RLF). The prediction of measurement results includes both cell-level and beam-level prediction.

[0287] For mobility prediction, such as measurement result prediction, HOF prediction, RLF prediction, etc., it can currently support UE-side prediction models (UE-sided model) and network-side prediction models (NW-sided model).

[0288] For UE-sided models, the UE may need to report the prediction results of the UE-side prediction model to the network side to assist the network side in making handover decisions.

[0289] For NW-sided models, UEs may need to report some auxiliary information as input to the prediction model on the NW side. The prediction model on the NW side can make predictions based on the information reported by the UE and some information available on the NW side.

[0290] For network-side prediction models, the UE may need to participate in the model inference process, meaning the UE reports auxiliary information as input to the network-side prediction model. For UE-side prediction models, the UE may need to report the model inference results to the network side, requesting the network side to perform mobility optimization and configuration updates based on the model inference results.

[0291] In the current process, the UE can only directly report this information to the serving base station. For mobility procedures, the target base station (or candidate base station) also needs to know this information. On the one hand, the target base station (or candidate base station) can use this information to determine whether to accept the access request sent by the serving base station. On the other hand, the target base station (or candidate base station) can also optimize its configuration and perform mobility prediction based on prediction models after the UE accesses the network. However, there is currently no research on how to transmit information used for model prediction between nodes.

[0292] Based on the aforementioned wireless communication system, various embodiments of the communication method proposed in this disclosure will be described in detail below.

[0293] Figure 2a is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2a, the communication method is used in a communication system 100, and the method includes:

[0294] S201, Terminal 101 sends a second message to the first node.

[0295] In some embodiments, the second message includes prediction-related information.

[0296] In some embodiments, the first node may receive prediction-related information reported by the terminal.

[0297] Optionally, the first node can be the serving node (or network device) corresponding to the source cell before the terminal 101 switches.

[0298] For example, in a non-dual-connectivity (non-DC) scenario, the first node can be the source gNB, but it is not limited to this.

[0299] For example, in a dual-connectivity (DC) scenario, in response to mobility operations for the Master Cell group (MCG), the first node can be the source Master Node (MN); in response to mobility operations for the Secondary Cell group (SCG), the first node can be MN, but is not limited to this. The MCG includes one PCell (primary cell) or additionally includes one or more SCells (secondary cells). The SCG includes one PSCell (primary / secondary cell) or additionally includes one or more SCells.

[0300] In some embodiments, the prediction-related information may include at least one of the following:

[0301] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0302] Inference data, which is used by the second node to optimize mobility operations and / or update mobility configuration;

[0303] Training data, which is used to train the prediction model on the second node side.

[0304] In some embodiments, the terminal may send training data and inference data of the terminal-side prediction model to the first node, and may also send indication information indicating that the data comes from the terminal.

[0305] Optionally, the inference data may include: the output of the terminal-side prediction model, and may also include: auxiliary information from the terminal to assist the network-side prediction, such as: as input to the network-side prediction model.

[0306] In some embodiments, the prediction model can be an AI (Artificial Intelligence) / ML (Machine Learning) based model.

[0307] In some embodiments, the second node may be the serving node (or network device) corresponding to the target cell after the handover of terminal 101, or at least one candidate serving node corresponding to at least one candidate cell used to implement the handover of terminal 101.

[0308] For example, in a non-DC scenario, the second node can be a target gNB or a candidate gNB, but it is not limited to these. There can be one or more candidate gNBs, where "multiple" means more than one.

[0309] For example, in a DC scenario, in response to mobility operations for an MCG, the second node can be a target MN or a candidate MN; in response to mobility operations for a secondary cell group (SCG), the second node can be a target secondary node (SN) or a candidate SN, but is not limited to these. Here, there can be one or more candidate MNs and candidate SNs; "multiple" is understood as more than one.

[0310] In some embodiments, the inference data includes at least one of the following:

[0311] The results output by the prediction model on the terminal side;

[0312] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0313] Optionally, the inference data may include the prediction results output by the prediction model on the terminal side.

[0314] In some embodiments, the prediction result may include at least one of the following: a prediction result of HOF (HO failure, handover failure), a predicted cell-level measurement result, a predicted beam-level measurement result, and whether the predicted measurement event meets the measurement event configuration.

[0315] Optionally, the inference data may also include auxiliary information from the terminal.

[0316] In some embodiments, UE Assistance Information (UAI message) can be used as input information for model inference by the prediction model on the second node side.

[0317] In some embodiments, the prediction-related information can be used for at least one of the following prediction functions:

[0318] Predicting measurement results;

[0319] Switchover failure prediction;

[0320] Wireless link failure prediction;

[0321] Predicting measurement events.

[0322] Optionally, measurement result prediction may include cell-level measurement result prediction, beam-level measurement result prediction, etc., but is not limited to these.

[0323] S202, Send the first message to the second node.

[0324] In some embodiments, the first message includes prediction-related information.

[0325] In some embodiments, the first message includes prediction-related information from the second message.

[0326] In some embodiments, the first node sends the prediction-related information included in the second message to the second node.

[0327] Optionally, after the terminal switches from the first node to the second node, it can forward the prediction-related information obtained from the terminal 101 to the second node, thereby realizing the transmission of prediction-related information between nodes.

[0328] In some embodiments, the prediction-related information forwarded by the first node to the second node is the prediction-related information that the terminal 101 last sent to the first node.

[0329] In some embodiments, the prediction-related information includes: the timing information of the prediction results output by the prediction model on the terminal side.

[0330] In some embodiments, time information may include one or more points in time or one or more time ranges.

[0331] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “time range,” “duration,” “segment,” “time window,” “window,” and “time.”

[0332] Optionally, the terminal can report the time information of the prediction results output by the prediction model on the terminal side to the first node. The prediction-related information forwarded by the first node may include the time information of the prediction results output by the prediction model on the terminal side.

[0333] In some embodiments, the predicted relevant information is used to perform at least one of the following operations:

[0334] Optimized mobility operations;

[0335] Mobility configuration update;

[0336] Predictive model inference;

[0337] Predictive model training.

[0338] Optionally, after the terminal switches from the first node to the second node, the first node can forward the prediction-related information obtained from the terminal 101 to the second node, so that the second node can perform prediction model inference, training, or optimize and configure terminal mobility operations based on this information.

[0339] In some embodiments, prediction-related information is carried through information elements (IEs) or fields added to the first message.

[0340] In some embodiments, the first message may be a first Xn message or a first inter-node radio resource control (RRC) message.

[0341] In some embodiments, the first Xn message can be an existing Xn message.

[0342] Optionally, in the mobility operations of the MCG in both non-DC and DC scenarios, the first Xn message can be a handover request message.

[0343] In some embodiments, the first node forwards prediction-related information to the second node by including prediction-related information in the handover request message. Optionally, the prediction-related information can be included in a new IE or field added to the handover request message.

[0344] Optionally, in the mobility operation of the SCG in the DC scenario, the first Xn message can add a request message to the SN, or the SN can modify the request message.

[0345] In some embodiments, the first node forwards the prediction-related information to the second node by including prediction-related information in an SN Add Request Message or an SN Modify Request Message. Optionally, the prediction-related information may be carried in an IE or field newly added in the SN Add Request Message or in an IE or field newly added in the SN Modify Request Message.

[0346] In some embodiments, the first inter-node RRC message can be an existing inter-node RRC message.

[0347] Optionally, the RRC message between the first nodes can be a HandoverPreparationInformation message.

[0348] In some embodiments, the first node forwards prediction-related information to the second node by including prediction-related information in the handover preparation message. Optionally, the prediction-related information can be included in a new IE or field added to the handover preparation message.

[0349] In some embodiments, the first message may be a second Xn message or a second inter-node RRC message.

[0350] In some embodiments, the first message is used to transmit prediction-related information between nodes. Optionally, the first message can be a dedicated message for transmitting prediction-related information between nodes.

[0351] In some embodiments, the second Xn message is a newly introduced Xn message.

[0352] Optionally, prediction-related information can be carried in the IE or fields of the second Xn message.

[0353] In some embodiments, the second inter-node RRC message can be a newly introduced inter-node RRC message.

[0354] In some embodiments, the inter-node RRC message may be included in the second Xn message.

[0355] Optionally, the inter-node RRC message can be carried in the IE or field of the second Xn message, and the prediction-related information can be carried in the inter-node RRC message.

[0356] In some embodiments, the RRC message between the second nodes may be included in the first Xn message described above.

[0357] Optionally, the RRC message between the second nodes can be carried in the IE or field added in the first Xn message, and the prediction-related information can be carried in the RRC message between the second nodes.

[0358] Optionally, in the mobility operations of the MCG in both non-DC and DC scenarios, the first Xn message can be a handover request message. The first node forwards the prediction-related information to the second node by carrying an inter-node RRC message containing prediction-related information within the handover request message. Optionally, the inter-node RRC message can be carried in a newly added IE or field within the handover request message.

[0359] Optionally, in the SCG mobility operation under the DC scenario, the first Xn message can be an SN add request message, or an SN modify request message. The first node forwards the prediction-related information to the second node by carrying a second-node inter-RRC message containing prediction-related information in the SN add request message or the SN modify request message. Optionally, the second-node inter-RRC message can be carried in an IE or field newly added in the SN add request message, or in an IE or field newly added in the SN modify request message.

[0360] S203, The second node sends the fourth message to the first node.

[0361] In some embodiments, the fourth message includes information related to the prediction model.

[0362] In some embodiments, the second node sends information related to the prediction model to the first node.

[0363] In some embodiments, the first node sends information related to the prediction model to the second node.

[0364] In some embodiments, the information related to the prediction model includes at least one of the following:

[0365] The second node supports prediction functionality;

[0366] The second node supports the model information corresponding to the prediction functions.

[0367] In some embodiments, the model information corresponding to the prediction function supported by the second node can be the identifier of the prediction model, such as the index of the prediction model.

[0368] In some embodiments, the second node may send information to the first node about the prediction functions it supports.

[0369] In some embodiments, the second node may send to the first node which prediction models its supported prediction functions correspond to, and may carry the index of the prediction model.

[0370] S204. The first node responds to the fourth message and performs the relevant operations.

[0371] In some embodiments, the first node responds to the fourth message by performing one of the following operations:

[0372] Select the second node as the target node;

[0373] Select the second node as a candidate node;

[0374] Send a fifth message to the second node, which is used to cancel the handover-related operations.

[0375] In some embodiments, the fifth message may be a switch cancellation message, used to cancel the switch or PSCell addition or modification prepared by the second node. Optionally, the switch-related operations include the switch or PSCell addition or modification prepared by the second node.

[0376] In some embodiments, the first node may determine a candidate cell (or target cell) based on the received UE measurement results, and select a second node as a candidate or target node based on the candidate or target cell.

[0377] In some embodiments, if multiple candidate or target nodes are identified, but the UE has accessed other nodes, or if the first node evaluates that the UE is not suitable to access the second node, a handover cancellation message can be sent to the second node.

[0378] In some embodiments, prior to step S202, the method may further include:

[0379] S205, The first node receives the sixth message sent by the second node.

[0380] In some embodiments, the sixth message includes a first request message for requesting the first node to send prediction-related information from the terminal.

[0381] In some embodiments, the second node may request the first node to send prediction-related information from the terminal, and the first node may respond to the request of the second node by sending prediction-related information from the terminal to the second node.

[0382] In some embodiments, the sixth message includes at least one of the following:

[0383] The first instruction information is used to instruct the first node to provide prediction-related information from the terminal;

[0384] The second instruction information is used to indicate the training data corresponding to the first prediction function required by the second node;

[0385] The third indication information is used to indicate the prediction result of the second prediction function on the terminal side required by the second node;

[0386] The fourth instruction information is used to indicate the input information required for model inference by the second node.

[0387] In some embodiments, the second node may instruct the first node in the sixth message to provide prediction-related information from the terminal, and / or to indicate which prediction functions it needs training data for, and / or to indicate which prediction functions on the terminal side it needs prediction results for, and / or to indicate the input information it needs for model inference.

[0388] In some embodiments, the second node may instruct the first node in the sixth message to provide prediction-related information from the terminal, and to indicate the information included in the prediction-related information from the terminal. Optionally, the prediction-related information from the terminal may include at least one of: training data for some (or specific) prediction functions of the second node, prediction results for some (or specific) prediction functions on the terminal side, and input information required by the second node for model inference. Optionally, the input information required by the second node for model inference may be terminal auxiliary information.

[0389] In some embodiments, the first node provides the second node with corresponding prediction-related information based on the instructions in the sixth message.

[0390] In some embodiments, the prediction result of the second prediction function on the terminal side includes at least one of the following:

[0391] Predicted results of a failed switchover;

[0392] Predicted cell-level measurement results;

[0393] Predicted beam-level measurement results;

[0394] Configuration of predicted measurement events;

[0395] Whether the predicted measurement events meet the corresponding configuration conditions;

[0396] The predicted and recommended optimal target cell;

[0397] The predicted recommended at least one candidate target cell.

[0398] In some embodiments, the prediction results on the terminal side may include at least one of the following: prediction results of HOF (HO failure, handover failure), predicted cell-level and / or beam-level measurement results, configuration of predicted measurement events, whether the predicted measurement events meet the configuration, and the predicted recommended best target cell or at least one candidate target cell.

[0399] In some embodiments, prior to step S205, the method may further include:

[0400] S206. The second node receives the seventh message sent by the first node.

[0401] In some embodiments, the seventh message includes relevant information for the second node to prepare for mobility.

[0402] In some embodiments, the seventh message may be a mobility request message.

[0403] In some embodiments, the sixth message may be a response message to the seventh message.

[0404] In some embodiments, after the second node receives the mobility request message sent by the first node, the response message of the request message may include a first request message requesting the first node to send prediction-related information from the terminal. After receiving the first request message, the first node may send a first message to the second node, which includes prediction-related information from the terminal.

[0405] In some embodiments, the second node may also perform at least one of the following operations based on prediction-related information:

[0406] Optimized mobility operations;

[0407] Mobility configuration updated;

[0408] Predictive model inference;

[0409] Predictive model training.

[0410] In some embodiments, the second node obtains prediction-related information based on the first message sent by the first node.

[0411] In some embodiments, the second node may perform predictive model inference, training, or optimize and configure terminal mobility operations based on prediction-related information.

[0412] In some embodiments, mobility operations may include, but are not limited to, one or more of the following mobility operations: conventional switching HO, CHO, LTM, CLTM, etc.

[0413] Optionally, CHO refers to a handover performed by the UE when one or more handover execution conditions are met. After receiving the CHO configuration, the UE begins evaluating the execution conditions and stops evaluating them after performing a handover (including legacy handover and CHO). CHO is subject to the following criteria:

[0414] (1) CHO configuration includes CHO candidate cell configuration and execution conditions. Among them, an execution condition may contain one or two trigger conditions (e.g., CHO events A3 / A5).

[0415] Among them, CondEvent A3 (CHO event A3): The conditional reconfiguration candidate becomes better than PCell (primary cell) / PCells (primary cell group) by a certain offset.

[0416] Among them, CondEvent A5 (CHO event A5): PSCell (primary and secondary cells) becomes worse than absolute threshold 1, and the conditional reconfiguration candidate becomes better than another absolute threshold 2.

[0417] (2) If the UE receives a HO (without CHO configuration) command before any CHO execution conditions are met, the traditional HO procedure is executed, regardless of any previously received CHO configuration.

[0418] (3) When executing CHO, that is, from the time the UE starts synchronizing with the target gNB, the UE does not listen to the source gNB (e.g., the source gNB).

[0419] Optionally, LTM (L1 / L2 triggered mobility) refers to the gNB receiving an L1 measurement report from the UE and, based on the L1 measurement report, sending a cell handover command via MAC CE to change the UE's serving cell. The cell handover command indicates an LTM candidate configuration, which is an LTM candidate configuration previously prepared by the gNB and provided to the UE via RRC signaling. The UE then switches to the target configuration according to the cell handover command. The LTM process can be used to reduce mobility latency.

[0420] Optionally, CLTM is a condition-triggered LTM. A condition-triggered LTM can be called any one or more of Conditional LTM, CLTM, and C-LTM.

[0421] In some embodiments, in a DC scenario, the mobility operation of the MCG is used for MCG change, and may include, but is not limited to, one or more of the following mobility operations: HO, PSCell addition, PSCell change, CPAC (conditional PSCell addition or change), LTM, CHO with target SCG, CHO with candidate SCG(s), etc.

[0422] Optionally, CPAC can be divided into two types: CPA and CPC. CPC refers to the PSCell change performed by the UE when the execution conditions are met. When the UE receives the CPC configuration, it begins to evaluate the execution conditions, and stops evaluating the execution conditions once a PSCell change or PCell change is triggered.

[0423] Optionally, LTM can be divided into three types: MCG LTM (Master Cell group L1 / L2 triggered Mobility, L1 / L2 triggered handover of primary cell group mobility; MCG stands for Master Cell group), SCG LTM (Secondary Cell group L1 / L2 triggered Mobility, L1 / L2 triggered handover of secondary cell group mobility; SCG stands for Secondary Cell group), and / or LTM for MCG and SCG mobility.

[0424] Optionally, referring to Figure 2c, taking the traditional handover HO as an example of mobility operation, the handover process between gNBs may include:

[0425] In step 3-1, the UE performs measurement reporting based on the network device configuration [e.g., the mobility control information provided by the AMF (Access and Mobility Management Function) in 3-0].

[0426] In step 3-2, the source gNB determines the target cell (target gNB) to be handed over based on the measurement results reported by the UE;

[0427] In steps 3-6, the source gNB sends the handover command (RAN handover initiation, radio access network handover indication) configured for the target cell to the UE;

[0428] When the UE receives an RRC Reconfiguration message containing handover information, the UE will immediately execute the corresponding handover procedure according to the received RRC message.

[0429] In some embodiments, the names of information, etc., are not limited to those described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", and "data" can be used interchangeably.

[0430] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0431] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0432] In some embodiments, terms such as “in the case of,” “when,” “when,” “in response to,” and “if” can be used interchangeably.

[0433] The method involved in the embodiments of this disclosure may include at least one of steps S201 to S206. For example, steps S201 and S202 may be implemented as independent embodiments, steps S201, S202, and S203 may be implemented as independent embodiments, steps S201, S202, S203, and S204 may be implemented as independent embodiments, steps S201, S202, S203, and S205 may be implemented as independent embodiments, steps S201, S202, S203, S204, and S205 may be implemented as independent embodiments, but are not limited thereto.

[0434] In some embodiments, step S203 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0435] In some embodiments, step S204 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0436] In some embodiments, step S205 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0437] In some embodiments, step S206 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0438] Figure 2b is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2b, the communication method is used in a communication system 100, and the method includes:

[0439] S211, The third node sends a third message to the first node.

[0440] In some embodiments, the third message includes prediction-related information.

[0441] In some embodiments, the third message is prediction-related information obtained by the third node from the terminal.

[0442] In some embodiments, the third node can be the source SN in the mobility operation of the SCG in a DC scenario. Optionally, the first node can be the serving node corresponding to the source cell before the handover of terminal 101, for example, the first node is MN.

[0443] In some embodiments, the prediction-related information may include at least one of the following:

[0444] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0445] Inference data, which is used by the second node to optimize mobility operations and / or update mobility configuration;

[0446] Training data, which is used to train the prediction model on the second node side.

[0447] In some embodiments, the terminal may send training data and inference data of the terminal-side prediction model to the first node, and may also send indication information indicating that the data comes from the terminal.

[0448] Optionally, the inference data may include: the output of the terminal-side prediction model, and may also include: auxiliary information from the terminal to assist the network-side prediction, such as: as input to the network-side prediction model.

[0449] In some embodiments, the prediction model can be an AI (Artificial Intelligence) / ML (Machine Learning) based model.

[0450] In some embodiments, the second node may be the serving node corresponding to the target cell after the handover of terminal 101. Optionally, the second node may be the target SN in the mobility operation of SCG in a DC scenario.

[0451] In some embodiments, the inference data includes at least one of the following:

[0452] The results output by the prediction model on the terminal side;

[0453] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0454] Optionally, the inference data may include the prediction results output by the prediction model on the terminal side.

[0455] In some embodiments, the prediction result may include at least one of the following: a prediction result of HOF (HO failure, handover failure), a predicted cell-level measurement result, a predicted beam-level measurement result, and whether the predicted measurement event meets the measurement event configuration.

[0456] Optionally, the inference data may also include auxiliary information from the terminal.

[0457] In some embodiments, UE Assistance Information (UAI message) can be used as input information for model inference by the prediction model on the second node side.

[0458] In some embodiments, the prediction-related information can be used for at least one of the following prediction functions:

[0459] Predicting measurement results;

[0460] Switchover failure prediction;

[0461] Wireless link failure prediction;

[0462] Predicting measurement events.

[0463] Optionally, measurement result prediction may include cell-level measurement result prediction, beam-level measurement result prediction, etc., but is not limited to these.

[0464] In some embodiments, the prediction-related information forwarded by the third node to the first node is the prediction-related information that the terminal 101 last sent to the third node.

[0465] In some embodiments, the prediction-related information includes: the timing information of the prediction results output by the prediction model on the terminal side.

[0466] In some embodiments, time information may include one or more points in time or one or more time ranges.

[0467] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “time range,” “duration,” “segment,” “time window,” “window,” and “time.”

[0468] Optionally, the terminal can send the time information of the prediction results output by the prediction model on the terminal side to the third node. The prediction-related information sent by the third node to the first node may include the time information of the prediction results output by the prediction model on the terminal side.

[0469] In some embodiments, the predicted relevant information is used to perform at least one of the following operations:

[0470] Optimized mobility operations;

[0471] Mobility configuration updated;

[0472] Predictive model inference;

[0473] Predictive model training.

[0474] Optionally, after the terminal switches from the third node to the second node, the third node can forward the prediction-related information obtained from the terminal 101 from the first node to the second node, so that the second node can perform prediction model inference, training, or optimize and configure terminal mobility operations based on this information.

[0475] In some embodiments, prediction-related information is carried through information elements (IEs) or fields added in the third message.

[0476] In some embodiments, the third message may be a first Xn message or a first inter-node radio resource control (RRC) message.

[0477] In some embodiments, the first Xn message can be an existing Xn message.

[0478] Optionally, in the mobility operation of the SCG in the DC scenario, the first Xn message may include at least one of the following: SN add request message, SN modify request message, SN change request message, and SN modify request reply message.

[0479] In some embodiments, the third node forwards prediction-related information to the first node by adding a request message to the SN, or by the SN modifying the request message, or by the SN changing the request message, or by the SN modifying the request response message to include prediction-related information.

[0480] Optionally, the prediction-related information can be carried in the newly added IE or field in the SN add request message, or in the newly added IE or field in the SN modify request message, or in the newly added IE or field in the SN change request message, or in the newly added IE or field in the SN modify request reply message.

[0481] In some embodiments, the first inter-node RRC message can be an existing inter-node RRC message.

[0482] Optionally, the RRC message between the first nodes can be a cell group configuration message (CG-ConfigInfo).

[0483] In some embodiments, the third node forwards prediction-related information to the first node by including prediction-related information in the cell group configuration message. Optionally, the prediction-related information can be included in a newly added IE or field in the cell group configuration message.

[0484] In some embodiments, the third message may be a second Xn message or a second inter-node RRC message.

[0485] In some embodiments, the third message is used to transmit prediction-related information between nodes. Optionally, the third message can be a dedicated message for transmitting prediction-related information between nodes.

[0486] In some embodiments, the second Xn message is a newly introduced Xn message.

[0487] Optionally, prediction-related information can be carried in the IE or fields of the second Xn message.

[0488] In some embodiments, the second inter-node RRC message can be a newly introduced inter-node RRC message.

[0489] In some embodiments, the inter-node RRC message may be included in the second Xn message.

[0490] Optionally, the inter-node RRC message can be carried in the IE or field of the second Xn message, and the prediction-related information can be carried in the inter-node RRC message.

[0491] In some embodiments, the RRC message between the second nodes may be included in the first Xn message described above.

[0492] Optionally, the RRC message between the second nodes can be carried in the IE or field added in the first Xn message, and the prediction-related information can be carried in the RRC message between the second nodes.

[0493] Optionally, in the mobility operation of SCG in the DC scenario, the first Xn message can be an add request message for SN, or a modify request message for SN, or a change request message for SN, or a change request message for SN, or a change request reply message for SN. Then, the third node forwards the prediction-related information to the first node by carrying the second node inter-RRC message, which carries prediction-related information, in the add request message for SN, or a modify request message for SN, or a change request message for SN, or a change request reply message for SN.

[0494] Optionally, the RRC message between the second nodes can be carried in the newly added IE or field in the SN add request message, or in the newly added IE or field in the SN modify request message, or in the newly added IE or field in the SN change request message, or in the newly added IE or field in the SN modify request reply message.

[0495] In some embodiments, the following may be included before step S211:

[0496] S210, Terminal 101 sends the eighth message to the third node.

[0497] In some embodiments, the eighth message includes prediction-related information.

[0498] In some embodiments, after receiving the prediction-related information sent in the middle, the third node can send the prediction-related information to the first node.

[0499] S212, Send the first message to the second node.

[0500] In some embodiments, after receiving the prediction-related information sent by the third node, the first node forwards it to the second node.

[0501] In some embodiments, the first node sends prediction-related information included in a third message to the second node.

[0502] Optionally, in the mobility operation of SCG in the DC scenario, after the source SN receives the prediction-related information sent by the terminal, it sends the prediction-related information to the MN, and the MN forwards it to the target SN.

[0503] In some embodiments, prediction-related information is carried through information elements (IEs) or fields added to the first message.

[0504] In some embodiments, the first message may be a first Xn message or a first inter-node radio resource control (RRC) message.

[0505] In some embodiments, the first Xn message can be an existing Xn message.

[0506] Optionally, in the mobility operation of the SCG in the DC scenario, the first Xn message may include at least one of the following: SN add request message, SN modify request message, SN change request message, and SN modify request reply message.

[0507] In some embodiments, the first node forwards prediction-related information to the second node by adding a request message to the SN, or by the SN modifying the request message, or by the SN changing the request message, or by the SN modifying the request response message to include prediction-related information.

[0508] Optionally, the prediction-related information can be carried in the newly added IE or field in the SN add request message, or in the newly added IE or field in the SN modify request message, or in the newly added IE or field in the SN change request message, or in the newly added IE or field in the SN modify request reply message.

[0509] In some embodiments, the first inter-node RRC message can be an existing inter-node RRC message.

[0510] Optionally, the RRC message between the first nodes can be a cell group configuration message (CG-ConfigInfo).

[0511] In some embodiments, the first node forwards prediction-related information to the second node by including prediction-related information in the cell group configuration message. Optionally, the prediction-related information can be included in a newly added IE or field in the cell group configuration message.

[0512] In some embodiments, the first message may be a second Xn message or a second inter-node RRC message.

[0513] In some embodiments, the first message is used to transmit prediction-related information between nodes. Optionally, the first message can be a dedicated message for transmitting prediction-related information between nodes.

[0514] In some embodiments, the second Xn message is a newly introduced Xn message.

[0515] Optionally, prediction-related information can be carried in the IE or fields of the second Xn message.

[0516] In some embodiments, the second inter-node RRC message can be a newly introduced inter-node RRC message.

[0517] In some embodiments, the inter-node RRC message may be included in the second Xn message.

[0518] Optionally, the inter-node RRC message can be carried in the IE or field of the second Xn message, and the prediction-related information can be carried in the inter-node RRC message.

[0519] In some embodiments, the inter-node RRC message may be included in the first Xn message described above.

[0520] Optionally, the RRC message between the second nodes can be carried in the IE or field added in the first Xn message, and the prediction-related information can be carried in the RRC message between the second nodes.

[0521] Optionally, in the mobility operation of SCG in the DC scenario, the first Xn message can be an add request message for SN, or a modify request message for SN, or a change request message for SN, or a change request message for SN, or a change request reply message for SN. Then, the first node forwards the prediction-related information to the second node by carrying the inter-node RRC message between the second node in the add request message for SN, or the modify request message for SN, or the change request message for SN, or the change request reply message for SN. The inter-node RRC message between the second node carries prediction-related information.

[0522] Optionally, the RRC message between the second nodes can be carried in the newly added IE or field in the SN add request message, or in the newly added IE or field in the SN modify request message, or in the newly added IE or field in the SN change request message, or in the newly added IE or field in the SN modify request reply message.

[0523] S213, The second node sends the fourth message to the first node.

[0524] In some embodiments, the fourth message includes information related to the prediction model.

[0525] The optional implementation of step S213 can be found in the optional implementation of step S203 in Figure 2a, and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0526] S214. The first node responds to the fourth message and performs the relevant operations.

[0527] In some embodiments, the first node responds to the fourth message by performing one of the following operations:

[0528] Select the second node as the target node;

[0529] Select the second node as a candidate node;

[0530] Send a fifth message to the second node, which is used to cancel the handover-related operations.

[0531] The optional implementation of step S214 can be found in the optional implementation of step S204 in Figure 2a, and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0532] In some embodiments, prior to step S212, the method may further include:

[0533] S215, The first node receives the sixth message sent by the second node.

[0534] In some embodiments, the sixth message includes a first request message for requesting the first node to send prediction-related information from the terminal.

[0535] The optional implementation of step S215 can be found in the optional implementation of step S205 in Figure 2a, and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0536] In some embodiments, prior to step S215, the method may further include:

[0537] S216. The second node receives the seventh message sent by the first node.

[0538] In some embodiments, the seventh message includes relevant information for the second node to prepare for mobility.

[0539] In some embodiments, the seventh message may be a mobility request message.

[0540] In some embodiments, the sixth message may be a response message to the seventh message.

[0541] The optional implementation of step S216 can be found in the optional implementation of step S206 in Figure 2a, and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0542] In some embodiments, the second node may also perform at least one of the following operations based on prediction-related information:

[0543] Optimized mobility operations;

[0544] Mobility configuration updated;

[0545] Predictive model inference;

[0546] Predictive model training.

[0547] In some embodiments, in a DC scenario, the mobility operations of an SCG are used to change or add an SCG, and may include, but are not limited to, one or more of the following mobility operations: HO, PSCell addition, PSCell change, CPAC (conditional PSCell addition or change), LTM, CHO with target SCG, CHO with candidate SCG(s), etc.

[0548] In some embodiments, the names of information, etc., are not limited to those described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", and "data" can be used interchangeably.

[0549] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0550] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0551] In some embodiments, terms such as “in the case of,” “when,” “when,” “in response to,” and “if” can be used interchangeably.

[0552] The method involved in the embodiments of this disclosure may include at least one of steps S210 to S216. For example, steps S211 and S212 can be implemented as independent embodiments, steps S210, S211, S212, and S213 can be implemented as independent embodiments, steps S210, S211, S212, and S213 can be implemented as independent embodiments, steps S211, S212, S213, and S214 can be implemented as independent embodiments, and steps S211, S211, S212, S213, and S214 can be implemented as independent embodiments. Steps S212, S213, and S215 can be implemented as independent embodiments, as can steps S210, S211, S212, S213, and S215, as can steps S211, S212, S213, S214, and S215, as can steps S210, S211, S212, S213, S214, and S215, as can steps S211, S212, S213, S214, S215, and S216, but are not limited thereto.

[0553] In some embodiments, step S210 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0554] In some embodiments, step S213 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0555] In some embodiments, step S214 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0556] In some embodiments, step S215 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0557] In some embodiments, step S216 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0558] Figure 3a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3a, the communication method can be executed by a first node, and the method includes:

[0559] S301, Receive the second message sent by the terminal.

[0560] In some embodiments, the second message includes prediction-related information.

[0561] In some embodiments, the first node may receive prediction-related information reported by the terminal.

[0562] The optional implementation of step S301 can be found in the optional implementation of step S201 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0563] S302, Send the first message to the second node.

[0564] In some embodiments, the first message includes prediction-related information.

[0565] In some embodiments, the first message includes prediction-related information from the second message.

[0566] In some embodiments, the first node is the serving node corresponding to the source cell before the handover of terminal 101, the second node is the serving node corresponding to the target cell after the handover of terminal 101, or at least one candidate serving node corresponding to at least one candidate cell used to implement the handover of terminal 101.

[0567] Optionally, in a non-DC scenario, the first node can be the source gNB, and the second node can be the target gNB or a candidate gNB.

[0568] Optionally, in the mobility operation of MCG in the DC scenario, the first node can be the source MN, and the second node can be the target MN or a candidate MN.

[0569] Optionally, in the mobility operation of SCG in the DC scenario, the first node can be MN, and the second node can be the target SN or a candidate SN.

[0570] In some embodiments, the first message may be a first Xn message or a first inter-node RRC message.

[0571] In some embodiments, the first message may be a second Xn message or a second inter-node RRC message.

[0572] Optionally, the second Xn message is a new Xn message introduced specifically for transmitting prediction-related information between nodes.

[0573] Optionally, the second inter-node RRC message is a new RRC message introduced specifically for transmitting prediction-related information between nodes.

[0574] Optionally, the RRC message between the second nodes can be included in the second Xn message or the first Xn message.

[0575] Optionally, the first Xn message includes at least one of the following:

[0576] Switch request message

[0577] Add a request message to the secondary node SN;

[0578] SN modification request message.

[0579] Optionally, the RRC messages between the first nodes may include a handover preparation message.

[0580] The optional implementation of step S302 can be found in the optional implementation of step S202 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0581] In some embodiments, prior to step S302, the method may further include receiving a sixth message sent by the second node.

[0582] In some embodiments, the sixth message includes a first request message for requesting the first node to send prediction-related information from the terminal.

[0583] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S205 in Figure 2a, and other related parts in the embodiments involved in Figure 2a, which will not be repeated here.

[0584] In some embodiments, prior to step S302, the method may further include sending a seventh message to the second node.

[0585] In some embodiments, the seventh message includes relevant information for the second node to prepare for mobility.

[0586] In some embodiments, the seventh message may be a mobility request message.

[0587] In some embodiments, the sixth message may be a response message to the seventh message.

[0588] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S206 in Figure 2a, and other related parts in the embodiments involved in Figure 2a, which will not be repeated here.

[0589] S303, Receive the fourth message sent by the second node.

[0590] In some embodiments, the fourth message includes information related to the prediction model.

[0591] In some embodiments, the second node sends information related to the prediction model to the first node.

[0592] The optional implementation of step S303 can be found in the optional implementation of step S203 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0593] S304. In response to the fourth message, perform the relevant operation.

[0594] In some embodiments, the first node responds to the fourth message by performing one of the following operations:

[0595] Select the second node as the target node;

[0596] Select the second node as a candidate node;

[0597] Send a fifth message to the second node, which is used to cancel the handover-related operations.

[0598] The optional implementation of step S304 can be found in the optional implementation of step S204 in Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0599] The method involved in the embodiments of this disclosure may include at least one of steps S301 to S304. For example, steps S301 and S302 may be implemented as independent embodiments, and steps S301, S302 and S303 may be implemented as independent embodiments, but are not limited thereto.

[0600] In some embodiments, step S303 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0601] In some embodiments, step S304 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0602] Figure 3b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3b, the communication method can be executed by a first node, and the method includes:

[0603] S311, Receive the third message sent by the third node.

[0604] In some embodiments, the third message includes prediction-related information.

[0605] In some embodiments, the third message is prediction-related information obtained by the third node from the terminal.

[0606] In some embodiments, the third message may be a first Xn message or a first node RRC message.

[0607] Optionally, the first Xn message includes at least one of the following:

[0608] Add a request message to the SN;

[0609] SN modification request message;

[0610] SN changes request message;

[0611] SN modification request reply message.

[0612] Optionally, the RRC message between the first nodes can be a cell group configuration message.

[0613] In some embodiments, the third message may be a second Xn message or a second inter-node RRC message.

[0614] Optionally, the second Xn message is a new Xn message introduced specifically for transmitting prediction-related information between nodes.

[0615] Optionally, the second inter-node RRC message is a new RRC message introduced specifically for transmitting prediction-related information between nodes.

[0616] Optionally, the RRC message between the second nodes can be included in the second Xn message or the first Xn message.

[0617] The optional implementation of step S311 can be found in the optional implementation of step S211 in Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0618] In some embodiments, before step S311, the above method may further include: receiving an eighth message sent by the terminal.

[0619] In some embodiments, the eighth message includes prediction-related information.

[0620] The above-mentioned optional implementation methods can be found in the optional implementation methods of step S210 in Figure 2b, and other related parts in the embodiments involved in Figure 2b, which will not be repeated here.

[0621] S312, Send the first message to the second node.

[0622] In some embodiments, the first message includes prediction-related information.

[0623] In some embodiments, the first node sends prediction-related information included in a third message to the second node.

[0624] In some embodiments, during the mobility operation of an SCG in a DC scenario, the third node can be the source SN, the first node can be the MN, and the second node can be the target SN.

[0625] In some embodiments, the first message may be a first Xn message or a first inter-node RRC message.

[0626] In some embodiments, the first message may be a second Xn message or a second inter-node RRC message.

[0627] Optionally, the second Xn message is a new Xn message introduced specifically for transmitting prediction-related information between nodes.

[0628] Optionally, the second inter-node RRC message is a new RRC message introduced specifically for transmitting prediction-related information between nodes.

[0629] Optionally, the RRC message between the second nodes can be included in the second Xn message or the first Xn message.

[0630] Optionally, the first Xn message includes at least one of the following:

[0631] Add a request message to the SN;

[0632] SN modification request message;

[0633] SN changes request message;

[0634] SN modified request reply message.

[0635] Optionally, the RRC message between the first nodes can be a cell group configuration message.

[0636] In some embodiments, prior to step S312, the method may further include receiving a sixth message sent by the second node.

[0637] In some embodiments, the sixth message includes a first request message for requesting the first node to send prediction-related information from the terminal.

[0638] The optional implementations of step S312 can be found in step S205 of Figure 2a, the optional implementations of step S215 of Figure 2b, and other related parts in the embodiments involved in Figures 2a and 2b, which will not be repeated here.

[0639] In some embodiments, prior to step S312, the method may further include sending a seventh message to the second node.

[0640] In some embodiments, the seventh message includes relevant information for the second node to prepare for mobility.

[0641] In some embodiments, the seventh message may be a mobility request message.

[0642] In some embodiments, the sixth message may be a response message to the seventh message.

[0643] The above optional implementation methods can be found in the optional implementation methods of step S206 in Figure 2a and step S216 in Figure 2b, as well as other related parts in the embodiments involved in Figures 2a and 2b, which will not be repeated here.

[0644] S313, Receive the fourth message sent by the second node.

[0645] In some embodiments, the fourth message includes information related to the prediction model.

[0646] The optional implementation of step S313 can be found in step S203 of Figure 2a, the optional implementation of step S213 of Figure 2b, and other related parts in the embodiments involved in Figures 2a and 2b, which will not be repeated here.

[0647] S314. In response to the fourth message, perform the relevant operation.

[0648] In some embodiments, the first node responds to the fourth message by performing one of the following operations:

[0649] Select the second node as the target node;

[0650] Select the second node as a candidate node;

[0651] Send a fifth message to the second node, which is used to cancel the handover-related operations.

[0652] The optional implementation of step S314 can be found in step S204 of Figure 2a, the optional implementation of step S214 of Figure 2b, and other related parts in the embodiments involved in Figures 2a and 2b, which will not be repeated here.

[0653] The method involved in the embodiments of this disclosure may include at least one of steps S311 to S314. For example, steps S311 and S312 may be implemented as independent embodiments, and steps S311, S312 and S313 may be implemented as independent embodiments, but are not limited thereto.

[0654] In some embodiments, step S313 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0655] In some embodiments, step S314 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0656] Figure 3c is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3c, the communication method can be executed by a first node, and the method includes:

[0657] S321. Obtain prediction-related information from the terminal.

[0658] The optional implementations of step S321 can be found in the optional implementations of step S201 in Figure 2a, step S211 in Figure 2b, step S301 in Figure 3a, step S311 in Figure 3b, and other related parts in the embodiments involved in Figures 2a-2b and 3a-3b, which will not be repeated here.

[0659] In some embodiments, step S321 may include:

[0660] Receive a second message sent by the terminal, the second message including the prediction-related information; or...

[0661] The third message sent by the third node is received, the third message including the prediction-related information, wherein the prediction-related information is obtained by the third node from the terminal.

[0662] S322, Send the first message to the second node.

[0663] The optional implementations of step S322 can be found in step S202 of Figure 2a, step S212 of Figure 2b, step S302 of Figure 3a, step S312 of Figure 3b, and other related parts in the embodiments involved in Figures 2a-2b and 3a-3b, which will not be repeated here.

[0664] In some embodiments, the first message includes prediction-related information from the second message; or, the first message includes prediction-related information from the third message, wherein the prediction-related information in the third message is prediction-related information obtained by the third node from the terminal.

[0665] In some embodiments, the prediction-related information includes: time information of the prediction results output by the prediction model on the terminal side.

[0666] In some embodiments, the first message includes: a first Xn message or a first inter-node radio resource control (RRC) message.

[0667] In some embodiments, in response to a second message sent from a terminal that provides the prediction-related information, the first Xn message includes at least one of the following:

[0668] Switch request message

[0669] Add a request message to the secondary node SN;

[0670] SN modification request message; and

[0671] The first inter-node RRC message includes a handover preparation message;

[0672] In response to the third message obtained from the third node regarding the prediction-related information, the first Xn message includes at least one of the following:

[0673] Add a request message to the SN;

[0674] SN modification request message;

[0675] SN changes request message;

[0676] SN modification request reply message; and

[0677] The first inter-node RRC message includes cell group configuration messages.

[0678] In some embodiments, the first message includes: a second Xn message or a second inter-node RRC message.

[0679] In some embodiments, the second Xn message is used to transmit the prediction-related information between nodes, and the second inter-node RRC message is included in the second Xn message or included in the first Xn message.

[0680] In some embodiments, the method further includes: receiving a fourth message sent by the second node, the fourth message including information related to the prediction model; and, in response to the fourth message, performing one of the following operations:

[0681] Select the second node as the target node;

[0682] Select the second node as the candidate node;

[0683] A fifth message is sent to the second node, which is used to cancel the operation related to the handover.

[0684] The optional implementations of the above optional embodiments can be found in the optional implementations of steps S203 and S204 in FIG2a, steps S213 and S214 in FIG2b, steps S303 and S304 in FIG3a, steps S313 and S314 in FIG3b, and other related parts in the embodiments involved in FIG2a-2b and FIG3a-3b, which will not be repeated here.

[0685] In some embodiments, the information related to the prediction model includes at least one of the following:

[0686] The second node supports prediction functions;

[0687] The model information corresponding to the prediction functions supported by the second node.

[0688] In some embodiments, the method further includes: receiving a sixth message sent by the second node, the sixth message including first request information for requesting the first node to send prediction-related information from the terminal;

[0689] Then step S322 above may include: in response to the sixth message, sending the first message to the second node.

[0690] The optional implementations of the above optional embodiments can be found in the optional implementations of step S205 in FIG2a, step S215 in FIG2b, and other related parts in the embodiments involved in FIG2a and FIG2b, which will not be repeated here.

[0691] In some embodiments, the method further includes: sending a seventh message to the second node, the seventh message including relevant information for the second node to prepare mobility; wherein the sixth message is a response message to the seventh message.

[0692] The optional implementations of the above optional embodiments can be found in the optional implementations of step S206 in FIG2a, step S216 in FIG2b, and other related parts in the embodiments involved in FIG2a and FIG2b, which will not be repeated here.

[0693] In some embodiments, the sixth message includes at least one of the following:

[0694] The first instruction information is used to instruct the first node to provide prediction-related information from the terminal;

[0695] The second instruction information is used to indicate the training data corresponding to the first prediction function required by the second node;

[0696] The third indication information is used to indicate the prediction result of the second prediction function on the terminal side required by the second node;

[0697] The fourth instruction information is used to indicate the input information required for model inference by the second node.

[0698] In some embodiments, the prediction result of the second prediction function on the terminal side includes at least one of the following:

[0699] Predicted results of a failed switchover;

[0700] Predicted cell-level measurement results;

[0701] Predicted beam-level measurement results;

[0702] Configuration of predicted measurement events;

[0703] Whether the predicted measurement events meet the corresponding configuration conditions;

[0704] The predicted and recommended optimal target cell;

[0705] The predicted recommended at least one candidate target cell.

[0706] In some embodiments, the prediction-related information from the terminal includes at least one of the following:

[0707] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0708] Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates;

[0709] Training data, which is used to train the prediction model on the second node side.

[0710] In some embodiments, the inference data includes at least one of the following:

[0711] The results output by the prediction model on the terminal side;

[0712] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0713] In the above embodiments, the prediction-related information is used for at least one of the following prediction functions:

[0714] Predicting measurement results;

[0715] Switchover failure prediction;

[0716] Wireless link failure prediction;

[0717] Predicting measurement events.

[0718] In the above embodiments, the prediction-related information is used to perform at least one of the following operations:

[0719] Optimized mobility operations;

[0720] Mobility configuration updated;

[0721] Predictive model inference;

[0722] Predictive model training.

[0723] Figure 4a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4a, the method involved in this embodiment is executed by a second node, and the method includes:

[0724] S401, Receive the first message sent by the first node.

[0725] In some embodiments, the first message includes prediction-related information from the terminal.

[0726] The optional implementations of step S401 can be found in the optional implementations of step S202 in Figure 2a, step S212 in Figure 2b, step S302 in Figure 3a, step S312 in Figure 3b, and other related parts in the embodiments involved in Figures 2a-2b and 3a-3b, which will not be repeated here.

[0727] S402, Send the fourth message to the first node.

[0728] In some embodiments, the fourth message includes information related to the prediction model.

[0729] In some embodiments, the information related to the prediction model includes at least one of the following:

[0730] The second node supports prediction functions;

[0731] The model information corresponding to the prediction functions supported by the second node.

[0732] The optional implementations of the optional embodiments of step S402 can be found in the optional implementations of step S203 in FIG2a, step S213 in FIG2b, step S303 in FIG3a, step S313 in FIG3b, and other related parts in the embodiments involved in FIG2a-2b and FIG3a-3b, which will not be repeated here.

[0733] In some embodiments, the method further includes sending a sixth message to the first node.

[0734] In some embodiments, the sixth message includes a first request message for requesting the first node to send prediction-related information from the terminal.

[0735] The optional implementations of the above optional embodiments can be found in the optional implementations of step S205 in FIG2a, step S215 in FIG2b, and other related parts in the embodiments involved in FIG2a and FIG2b, which will not be repeated here.

[0736] In some embodiments, the method further includes: receiving a seventh message sent by the first node.

[0737] In some embodiments, the seventh message includes relevant information for the second node to prepare for mobility.

[0738] Optionally, the sixth message is a response message to the seventh message.

[0739] The optional implementations of the above optional embodiments can be found in the optional implementations of step S206 in FIG2a, step S216 in FIG2b, and other related parts in the embodiments involved in FIG2a and FIG2b, which will not be repeated here.

[0740] The method involved in the embodiments of this disclosure may include at least one of steps S401 to S402. For example, step S401 may be implemented as a standalone embodiment, but is not limited thereto.

[0741] In some embodiments, step S402 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0742] Figure 4b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4b, the method involved in this embodiment is executed by a second node, and the method includes:

[0743] S411, Receive the first message sent by the first node.

[0744] In some embodiments, the first message includes prediction-related information from the terminal.

[0745] In some embodiments, the first message includes prediction-related information, which is obtained by the first node from the terminal.

[0746] The optional implementations of step S411 can be found in step S202 of Figure 2a, step S212 of Figure 2b, step S302 of Figure 3a, step S312 of Figure 3b, and other related parts in the embodiments involved in Figures 2a-2b and 3a-3b, which will not be repeated here.

[0747] In some embodiments, the prediction-related information is the prediction-related information reported by the terminal and obtained by the first node; or,

[0748] The prediction-related information is the prediction-related information sent by the third node and obtained by the first node, wherein the prediction-related information sent by the third node is the prediction-related information obtained by the third node from the terminal.

[0749] In some embodiments, the prediction-related information includes: time information of the prediction results output by the prediction model on the terminal side.

[0750] In some embodiments, the first message includes: a first Xn message or a first inter-node radio resource control (RRC) message.

[0751] In some embodiments, in response to a second message sent by a terminal from which the prediction-related information is obtained by the first node, the first Xn message includes at least one of the following:

[0752] Switch request message

[0753] Add a request message to the SN;

[0754] SN modification request message; and

[0755] The first inter-node RRC message includes a handover preparation message;

[0756] In response to the prediction-related information being obtained by the first node from a third message sent by the third node, the first Xn message includes at least one of the following:

[0757] Add a request message to the SN;

[0758] SN modification request message;

[0759] SN changes request message;

[0760] SN modification request reply message; and

[0761] The first inter-node RRC message includes cell group configuration messages.

[0762] In some embodiments, the first message includes: a second Xn message or a second inter-node RRC message.

[0763] In some embodiments, the second Xn message is used to transmit the prediction-related information between nodes, and the second inter-node RRC message is included in the second Xn message or included in the first Xn message.

[0764] In some embodiments, the method further includes:

[0765] A fourth message is sent to the first node, the fourth message including information related to the prediction model;

[0766] The fourth message is used to determine one of the following operations:

[0767] Select the second node as the target node;

[0768] Select the second node as the candidate node;

[0769] A fifth message is sent to the second node, which is used to cancel the operation related to the handover.

[0770] The optional implementations of the above optional embodiments can be found in the optional implementations of step S203 in FIG2a, step S213 in FIG2b, step S303 in FIG3a, step S313 in FIG3b, and other related parts in the embodiments involved in FIG2a-2b and FIG3a-3b, which will not be repeated here.

[0771] In some embodiments, the information related to the prediction model includes at least one of the following:

[0772] The second node supports prediction functionality;

[0773] The model information corresponding to the prediction functions supported by the second node.

[0774] In some embodiments, the method further includes: sending a sixth message to the first node, the sixth message including first request information for requesting the first node to send prediction-related information from the terminal; wherein the first message is a response message to the sixth message.

[0775] The optional implementations of the above optional embodiments can be found in the optional implementations of step S205 in FIG2a and step S215 in FIG2b, as well as other related parts in the embodiments involved in FIG2a and FIG2b, which will not be repeated here.

[0776] In some embodiments, the method further includes: receiving a seventh message sent by the first node, the seventh message including relevant information for the second node to prepare mobility; wherein the sixth message is a response message to the seventh message.

[0777] The optional implementations of the above optional embodiments can be found in the optional implementations of step S206 in FIG2a and step S216 in FIG2b, as well as other related parts in the embodiments involved in FIG2a and FIG2b, which will not be repeated here.

[0778] In some embodiments, the sixth message includes at least one of the following:

[0779] The first instruction information is used to instruct the first node to provide prediction-related information from the terminal;

[0780] The second instruction information is used to indicate the training data corresponding to the first prediction function required by the second node;

[0781] The third indication information is used to indicate the prediction result of the second prediction function on the terminal side required by the second node;

[0782] The fourth instruction information is used to indicate the input information required for model inference by the second node.

[0783] In some embodiments, the prediction result of the second prediction function on the terminal side includes at least one of the following:

[0784] Predicted results of a failed switchover;

[0785] Predicted cell-level measurement results;

[0786] Predicted beam-level measurement results;

[0787] Configuration of predicted measurement events;

[0788] Whether the predicted measurement events meet the corresponding configuration conditions;

[0789] The predicted and recommended optimal target cell;

[0790] The predicted recommended at least one candidate target cell.

[0791] In some embodiments, the prediction-related information from the terminal includes at least one of the following:

[0792] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0793] Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates;

[0794] Training data, which is used to train the prediction model on the second node side.

[0795] In some embodiments, the inference data includes at least one of the following:

[0796] The results output by the prediction model on the terminal side;

[0797] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0798] In some embodiments, the method further includes: performing at least one of the following operations based on the first prediction-related information:

[0799] Optimized mobility operations;

[0800] Mobility configuration update;

[0801] Predictive model inference;

[0802] Predictive model training.

[0803] In the above embodiments, the prediction-related information is used for at least one of the following prediction functions:

[0804] Predicting measurement results;

[0805] Switchover failure prediction;

[0806] Wireless link failure prediction;

[0807] Predicting measurement events.

[0808] Figure 5 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 5, the method involved in this embodiment is executed by a third node, and the method includes:

[0809] S501, Receive the eighth message sent by the terminal.

[0810] In some embodiments, the eighth message includes prediction-related information.

[0811] The optional implementation of step S501 can be found in step S210 of Figure 2b and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0812] S502, Send the third message to the first node.

[0813] Optional implementations of step S502 can be found in step S212 of Figure 2b, step S311 of Figure 3b, and other related parts in the embodiments involved in Figures 2b and 3b, which will not be repeated here.

[0814] In some embodiments, the third message includes prediction-related information.

[0815] In some embodiments, the third message is prediction-related information obtained by the third node from the terminal.

[0816] In some embodiments, the prediction-related information is forwarded from the first node to the second node.

[0817] In some embodiments, the prediction-related information includes: time information of the prediction results output by the prediction model on the terminal side.

[0818] In some embodiments, the prediction-related information in the sixth message includes at least one of the following:

[0819] The fifth indication information is used to indicate that the prediction-related information comes from the terminal;

[0820] Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates;

[0821] Training data, which is used to train the prediction model on the second node side.

[0822] In some embodiments, the inference data includes at least one of the following:

[0823] The results output by the prediction model on the terminal side;

[0824] The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

[0825] In some embodiments, the prediction-related information is used for at least one of the following prediction functions:

[0826] Predicting measurement results;

[0827] Switchover failure prediction;

[0828] Wireless link failure prediction;

[0829] Predicting measurement events.

[0830] In some embodiments, the prediction-related information is used to perform at least one of the following operations:

[0831] Optimized mobility operations;

[0832] Mobility configuration updated;

[0833] Predictive model inference;

[0834] Predictive model training.

[0835] The method involved in the embodiments of this disclosure may include at least one of steps S501 to S502. For example, step S502 may be implemented as a separate embodiment, but is not limited thereto.

[0836] In some embodiments, step S501 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0837] Figure 6a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 6a, the method involved in this embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0838] S601, The first node receives the second message sent by the terminal.

[0839] The optional implementations of step S601 can be found in the optional implementations of step S201 in Figure 2a, step S301 in Figure 3a, and step S321 in Figure 3c, as well as other related parts in the embodiments involved in Figures 2a, 3a, and 3c, which will not be repeated here.

[0840] S602, The second node receives the second message sent by the first node.

[0841] Optional implementations of step S602 can be found in the optional implementations of step S202 in Figure 2a, step S212 in Figure 2b, step S302 in Figure 3a, step S312 in Figure 3b, step S322 in Figure 3c, step S401 in Figure 4a, step S411 in Figure 4b, and other related parts in the embodiments involved in Figures 2a-2b and 4a-4b, which will not be repeated here.

[0842] Figure 6b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 6b, the method involved in this embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0843] S611, The third node receives the eighth message sent by the terminal.

[0844] The optional implementation of step S611 can be found in the optional implementation of step S210 in Figure 2b, and other related parts in the embodiment involved in Figure 2b, which will not be repeated here.

[0845] S612, The first node receives the third message sent by the third node.

[0846] The optional implementations of step S612 can be found in the optional implementations of step S211 in Figure 2b, step S311 in Figure 3b, and step S321 in Figure 3c, as well as other related parts in the embodiments involved in Figures 2b, 3b, and 3c, which will not be repeated here.

[0847] S613, The second node receives the first message sent by the first node.

[0848] Optional implementations of step S613 can be found in the optional implementations of steps S202 in Figure 2a, S212 in Figure 2b, S302 in Figure 3a, S312 in Figure 3b, S322 in Figure 3c, S401 in Figure 4a, and S411 in Figure 4b, as well as other related parts in the embodiments involved in Figures 2a-2b and 4a-4b, which will not be repeated here.

[0849] In some embodiments, the above methods may include the methods described in the embodiments of the communication system side, terminal side, network equipment side, core network equipment side, etc., which will not be repeated here.

[0850] This disclosure also provides an optional implementation scheme, proposing a method for transmitting information for model prediction between nodes. During the mobility preparation process, the current serving node (which may correspond to the first node mentioned above) sends prediction-related information to the target node (which may correspond to the second node mentioned above). The target node can perform mobility management based on the prediction-related information sent by the serving node, select appropriate target cells and access beams for the UE, and generate corresponding target cell configurations.

[0851] 1. The first node receives prediction-related information sent by the terminal and forwards it to the second node. The second node can perform mobility optimization, AI inference, or model training based on the prediction-related information. The first node forwards the prediction-related information to the second node in one or more of the following ways:

[0852] 1.1 In non-DC scenarios, the first node is the source gNB and the second node is the target gNB (for mobility operations such as CHO, LTM, CLTM, the second node can be a candidate gNB). For mobility operations, there can be multiple second nodes.

[0853] 1.2 In DC scenarios:

[0854] 1.2.1 Mobility of MCG in DC scenario: The first node is the source MN, the second node is the target MN (or candidate MN), and the mobility is used for MCG change (i.e., Handover).

[0855] 1.2.2 SCG Mobility in DC Scenario: The first node is MN, and the second node is the target SN (or candidate SN). The mobility operation is used to change or add SCGs.

[0856] 1.2.2.1 For example, for SCG changes in a DC scenario, the prediction-related information sent by the first node MN to the target SN can come from the third node source SN. After receiving the prediction-related information sent by the UE, the third node source SN sends the prediction-related information to the first node MN, and the first node MN forwards it to the second node target SN.

[0857] Among them, the prediction-related information forwarded by the first node from the UE is the latest prediction-related information sent by the UE to the first node;

[0858] Among them, the prediction-related information from the UE that the third node forwards to the first node is the prediction-related information that the UE has just sent to the third node.

[0859] The prediction-related information may include the time information of the corresponding results output by the UE-side model.

[0860] Based on 1, the first node can send prediction-related information from the terminal through one or more of the following messages:

[0861] 2.1 Existing Xn messages (which can correspond to the first Xn message mentioned above) or existing inter-node RRC messages (which can correspond to the first inter-node RRC message mentioned above) can be used to transmit prediction-related information; the prediction-related information can be contained by defining a new IE or field.

[0862] 2.1.1Xn message:

[0863] 2.1.1.1 For MCG mobility in non-DC and DC scenarios, when the first node is the source gNB (source MN) and the second node is the target gNB (target MN), the prediction-related information can be carried in the handover request message, which is sent from the first node to the second node.

[0864] 2.1.1.2 For the mobility of SCG in DC scenario, when the first node is MN and the second node is target SN, the prediction-related information can be carried in the SN add request message (or SN modify request message), which is sent from the first node to the second node.

[0865] 2.1.1.3 For the mobility of SCG in DC scenario, the third node is the source SN and the first node is the MN. The prediction-related information can be carried in the SN change request message (or SN modification request reply message) and sent from the third node to the first node through the SN change request message (or SN modification request reply message).

[0866] 2.1.2 Carried in inter-node RRC messages

[0867] 2.1.2.1 For MCG mobility, the prediction-related information may be included in the HandoverPreparationInformation message.

[0868] 2.1.2.2 For SCG mobility, the prediction-related information may be included in the cell group configuration information (CG-ConfigInfo) sent by the MN to the SN (sent by the first node to the second node); the prediction-related information may be included in the (CG-Config) sent by the source SN to the MN.

[0869] 2.2 Introduce new Xn messages (which can correspond to the second Xn message mentioned above) or introduce new inter-node RRC messages (which can correspond to the second inter-node RRC message mentioned above) to transmit prediction-related information; the new messages are dedicated to the transmission of AI prediction-related information.

[0870] 2.2.1 A second Xn message (or a second inter-node RRC message) is introduced. The second Xn message (or the second inter-node RRC message) is used to transmit prediction-related information between nodes. The transmission direction of the second Xn message (or the second inter-node RRC message) can be any one or more of the following:

[0871] 2.2.1.1 From source node to target node, for example, the source node is the source NG-RAN node and the target node is the target NG-RAN node;

[0872] 2.2.1.2 From master node to slave node, for example, the master node is an M-NG-RAN node and the slave node is an S-NG-RAN node;

[0873] 2.2.1.3 From secondary node to primary node, for example, the secondary node is an S-NG-RAN node and the primary node is an M-NG-RAN node.

[0874] 2.2.2 The second inter-node RRC message can be included in the second Xn message or in an existing Xn message (switch request message, SN add request message, SN modify request message, SN change request message, SN modify request reply message).

[0875] 3. Based on either 1-2, when the second node receives a message from the first node containing prediction-related information from the terminal, the corresponding reply message may carry information related to the prediction model. This information may include any one or more of the following:

[0876] 3.1 Prediction functions supported by the second node.

[0877] 3.2 The corresponding AI prediction function supported by the second node and the corresponding model, such as the index of the prediction model.

[0878] Based on the information provided by the second node in the reply message, the first node can choose to use the second node as the target node (or candidate node) or send a switch cancellation message (or S-NODE RELEASE REQUEST) to the second node to cancel the switch or PSCell addition or modification prepared by the second node.

[0879] 4. Based on either 1-2, after the second node receives the mobility request message sent by the first node, it may include a request for prediction-related information from the terminal in the reply message or other Xn messages, requesting the first node to send prediction-related information from the terminal to the second node. The request for prediction-related information may include any one or more of the following information:

[0880] 4.1 Instruction information, indicating that the second node requires the first node to provide prediction-related information from the terminal.

[0881] 4.2 Instruction information, indicating that the second node needs training data for the corresponding prediction function, and optionally may include which training data from the terminal is needed.

[0882] 4.3 Instruction information, indicating the prediction results that the second node needs from the prediction function on the terminal side, and optionally including which prediction results are needed.

[0883] 4.3.1 For example, request the first node to forward the inference results of the terminal-side model;

[0884] 4.3.1.1 For example, the second node may request the first node to send the prediction results of HOF reported by the UE;

[0885] 4.3.1.2 For example, the second node may request the first node to send the predicted cell-level or beam-level measurement results reported by the UE;

[0886] 4.3.1.3 For example, the second node may request the first node to send the predicted measurement event fulfillment status and / or the corresponding measurement event configuration reported by the UE;

[0887] 4.3.1.4 For example, the second node may request the first node to send the predicted recommended best target cell or best target cell list reported by the UE.

[0888] 4.4 Instruction information, indicating the input information required for the second node to perform inference for the corresponding model, optionally including which information is required as inference input.

[0889] 4.4.1 For example, request the first node to forward the input information reported by the terminal for AI inference.

[0890] 5. Based on 3, after receiving the request information carrying prediction-related information, the first node sends the prediction-related information from the terminal to the second node.

[0891] 6. Based on any one of 1-5, the prediction-related information from the UE side mentioned in 1 includes one or more of the following:

[0892] 6.1 Indication information, indicating that the information comes from the UE side.

[0893] 6.1.1 For example, the inference result is indicated to be derived from the prediction model on the UE side.

[0894] 6.2 Inference data, which is used by the second node for mobility configuration and / or optimization, includes one or more of the following information.

[0895] 6.2.1 The inference output of the UE-side prediction model (including those directly reported by the UE to the first node, and / or those indirectly obtained by the first node from other nodes).

[0896] 6.2.2 UE-side information required for the network-side prediction model to perform AI inference, such as the input data required for inference, may include:

[0897] 6.2.2.1 Auxiliary information reported by the UE as input to the network-side prediction model (including information directly reported by the UE to the first node and / or information indirectly obtained by the first node from other nodes).

[0898] 6.3 Training data, which is used to train the AI ​​prediction model on the second node side, includes one or more of the following information.

[0899] 6.3.1 Training data collected by the UE and reported to the first node (including data directly reported by the UE to the first node and / or data indirectly obtained by the first node from other nodes).

[0900] 7. Based on any one of 1-6, the prediction-related information may include, but is not limited to, one or more of the following prediction functions:

[0901] 7.1 Measurement result prediction, such as cell-level measurement result prediction and beam-level measurement result prediction;

[0902] 7.2 Prediction of handover failure;

[0903] 7.3 Wireless link failure prediction;

[0904] 7.4 Measurement Event Prediction;

[0905] 7.5, etc.

[0906] In some embodiments, during the handover process based on scenario 1.1 above, the transmission of prediction-related information between nodes on the UE side can be achieved through the method shown in Figure 7a, specifically:

[0907] S70 and UE send a second message to the first node, reporting the prediction-related information.

[0908] The optional implementations of step S70 can be found in the optional implementations of step S201 in Figure 2a, step S301 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0909] Optionally, the second message can be a message used to report prediction-related information, such as a prediction-related information reporting message, but the message name is not limited to this.

[0910] S71. The first node sends a first message to the second node to transmit prediction-related information from the UE side.

[0911] The optional implementations of step S71 can be found in the optional implementations of step S202 in Figure 2a, step S302 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0912] Optionally, the first message can be an existing Xn message or an inter-node RRC message, or it can be a newly introduced Xn message or inter-node RRC message specifically used for transmitting prediction-related information between nodes. For example, the first message can be a handover request message.

[0913] Optionally, as described in Example 1: for handover (based on the scenario in 1.1 above, without considering the methods introduced in 3, 4, and 5 above), that is, when the source gNB sends a handover request message, it carries prediction-related information to the target gNB.

[0914] Optionally, the specific implementation process can be referred to Figure 7b, where step 0 is for the UE to send prediction-related information to the serving gNB. The UE can send prediction-related information to the serving gNB through PHY and MAC RRC layer messages.

[0915] In some embodiments, during the CHO and LTM processes based on the scenario described in 1.1 above, the transmission of prediction-related information between nodes on the UE side can be achieved through the method shown in Figure 7c. Specifically:

[0916] S72, the UE sends a second message to the first node, reporting the prediction-related information.

[0917] The optional implementations of step S72 can be found in the optional implementations of step S201 in Figure 2a, step S301 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0918] Optionally, the second message can be a message used to report prediction-related information, such as a prediction-related information reporting message, but the message name is not limited to this.

[0919] S73, the first node sends a first message to at least one second node to transmit prediction-related information from the UE side.

[0920] Optionally, the second node can be a candidate node. For example, the first node sends a first message to the second node 1 and the second node 2 respectively.

[0921] The optional implementations of step S73 can be found in the optional implementations of step S202 in Figure 2a and step S302 in Figure 3a, as well as other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0922] Optionally, the first message can be an existing Xn message or an inter-node RRC message, or it can be a newly introduced Xn message or an inter-node RRC message specifically used for transmitting prediction-related information between nodes. For example, the first message can be a handover request message or an LTM request message.

[0923] Optionally, as described in Example 2: consider CHO and LTM (based on the scenario in 1.1 above, without considering the methods introduced in 3, 4, and 5 above), that is, when the source gNB sends the handover request message, it carries prediction-related information to the candidate gNB. In the case of multiple candidate gNBs, the specific implementation process can be referred to Figure 7d.

[0924] In some embodiments, during the handover process based on scenario 1.1 above, the transmission of prediction-related information between nodes on the UE side can be achieved through the method shown in Figure 7e. Specifically:

[0925] S74, the UE sends a second message to the first node, reporting the prediction-related information.

[0926] The optional implementation of step S74 can be found in the optional implementation of step S201 in Figure 2a, step S301 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0927] Optionally, the second message can be a message used to report prediction-related information, such as a prediction-related information reporting message, but the message name is not limited to this.

[0928] S75, The first node sends the seventh message to the second node.

[0929] Optionally, the seventh message is a message used for the accurate handover and may include relevant information for the second node to prepare for mobility. For example, the seventh message may be a mobility request message or a handover request message.

[0930] The optional implementation of step S75 can be found in the optional implementation of step S206 in Figure 2a, and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0931] S76. The second node sends a sixth message to the first node to request prediction-related information from the UE side.

[0932] The optional implementation of step S76 can be found in the optional implementation of step S205 in Figure 2a, and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0933] S77. The first node sends a first message to the second node to transmit prediction-related information from the UE side.

[0934] The optional implementations of step S77 can be found in the optional implementations of step S202 in Figure 2a, step S302 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0935] Optionally, the first message can be an existing Xn message or an inter-node RRC message, or it can be a newly introduced Xn message or inter-node RRC message specifically used for transmitting prediction-related information between nodes. For example, a UE-side prediction-related information request confirmation message, but the message name is not limited to this.

[0936] Optionally, as described in Example 3: For the handover (based on the scenario in 1.1 above, consider the methods introduced in 4 and 5 above), after the source gNB sends the handover request message, the target gNB replies with a handover request reply message and sends an AI prediction information request message to the source gNB. After receiving this message, the source gNB sends AI prediction information to the target gNB.

[0937] Optionally, the specific implementation process can be referred to Figure 7f, where the messages in steps 1 and 2 are messages used for switching preparation, and the execution order of steps 5 and 6 and steps 3 and 4 is not constrained. The source gNB can execute steps 5 and 6 and steps 3 and 4 simultaneously.

[0938] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0939] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functions of some or all of the units or modules can be achieved through the design of the hardware circuits. The aforementioned hardware circuits can be understood as one or more processors. For example, in one implementation, the aforementioned hardware circuit is an application-specific integrated circuit (ASIC). The functions of some or all of the aforementioned units or modules are achieved through the design of the logical relationships between the components within the circuit. As another example, in another implementation, the aforementioned hardware circuit can be implemented through a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functions of some or all of the aforementioned units or modules.

[0940] All units or modules of the above devices can be implemented entirely through processor-invoked software, entirely through hardware circuits, or partially through processor-invoked software with the remainder implemented through hardware circuits. In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute 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 relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented using 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 configuring the hardware circuit 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 hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).

[0941] Figure 8a is a schematic diagram of the structure of the terminal proposed in an embodiment of this disclosure. As shown in Figure 8a, the first node may include at least one of a first transceiver module 711, a first processing module 712, etc.

[0942] In some embodiments, the first transceiver module 711 is used to acquire prediction-related information from the terminal and send a first message to the second node, the first message including the prediction-related information.

[0943] Optionally, the first transceiver module 711 is used to execute the steps related to transmitting and receiving signaling executed by the first node in any of the above methods, such as at least one of steps S201, S203, S205, and S206 shown in FIG2a, and steps S211, S213, S215, and S216 shown in FIG2b, which will not be described in detail here.

[0944] Optionally, the first processing module 712 is used to execute the information processing steps performed by the first node in any of the above methods, such as at least one of step S204 shown in FIG2a and step S214 shown in FIG2b, which will not be described in detail here.

[0945] Figure 8b is a schematic diagram of the network device proposed in an embodiment of this disclosure. As shown in Figure 8b, the second node includes at least one of a second transceiver module 721, a second processing module 722, etc.

[0946] In some embodiments, the second transceiver module 721 is used to receive a first message sent by the first node, the first message being prediction-related information, the prediction-related information being obtained by the first node from the terminal.

[0947] Optionally, the second transceiver module 721 is used to execute the steps related to transmitting and receiving signaling executed by the second node in any of the above methods, such as at least one of steps S203, S205, S206 shown in FIG2a, and steps S213, S215, S216 shown in FIG2b, which will not be described in detail here.

[0948] Figure 8c is a schematic diagram of the network device proposed in an embodiment of this disclosure. As shown in Figure 8c, the third node includes at least one of a third transceiver module 731, a third processing module 732, etc.

[0949] In some embodiments, the third transceiver module 731 is configured to receive a sixth message sent by the terminal, the sixth message including prediction-related information, and to send a third message to the first node, the third message including the prediction-related information.

[0950] The prediction-related information is forwarded from the first node to the second node.

[0951] Optionally, the third transceiver module 731 described above is used to execute the steps related to sending and receiving signaling executed by the third node in any of the above methods, such as step S210 shown in Figure 2b, which will not be described again here.

[0952] Figure 9a is a schematic diagram of the structure of the communication device 8100 proposed in an embodiment of this disclosure. The communication device 8100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 8100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0953] As shown in Figure 9a, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The processor 8101 is used to invoke instructions to cause the communication device 8100 to execute any of the above methods.

[0954] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., at least one of steps S201-S203, S205, S206 shown in FIG. 2a, and steps S210-S213, S215, S216 shown in FIG. 2b, but not limited thereto), and the processor 8101 performs at least one of other steps (e.g., at least one of step S204 shown in FIG. 2a, and step S214 shown in FIG. 2b, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

[0955] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may also be located outside the communication device 8100.

[0956] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

[0957] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0958] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in the embodiments of this disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 9a. 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 chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include storage components 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, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0959] Figure 9b is a schematic diagram of the structure of the chip 8200 according to an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the chip 8200 shown in Figure 9b, but it is not limited thereto.

[0960] Chip 8200 includes one or more processors 8201. Chip 8200 is used to perform any of the methods described above.

[0961] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Optionally, all or part of the memories 8203 may be located outside of chip 8200. Optionally, interface circuit 8202 is connected to memory 8203, and interface circuit 8202 can be used to receive data from memory 8203 or other devices, and interface circuit 8202 can be used to send data to memory 8203 or other devices. For example, interface circuit 8202 can read data stored in memory 8203 and send the data to processor 8201.

[0962] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., at least one of steps S201-S203, S205, S206 shown in FIG. 2a, and steps S210-S213, S215, S216 shown in FIG. 2b, but not limited thereto). The interface circuit 8202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 8202 performing data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of other steps (e.g., at least one of step S204 shown in FIG. 2a, and step S214 shown in FIG. 2b, but not limited thereto).

[0963] This disclosure also provides a program product that, when executed by the communication device 8100, causes the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0964] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0965] The technical solutions described in the embodiments of this disclosure can be combined arbitrarily without conflict.

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

[0967] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A communication method, characterized in that, The method is executed by the first node, and the method includes: Obtain prediction-related information from the terminal; Send a first message to the second node, the first message including the prediction-related information.

2. The method according to claim 1, characterized in that, The acquisition of prediction-related information from the terminal includes: Receive a second message sent by the terminal, the second message including the prediction-related information; or... The third message sent by the third node is received, the third message including the prediction-related information, wherein the prediction-related information is obtained by the third node from the terminal.

3. The method according to claim 2, characterized in that, The first message includes the prediction-related information in the second message; or, the first message includes the prediction-related information in the third message, wherein the prediction-related information in the third message is the prediction-related information obtained by the third node from the terminal.

4. The method according to claim 3, characterized in that, The prediction-related information includes: the time information of the prediction results output by the prediction model on the terminal side.

5. The method according to any one of claims 1-4, characterized in that, The first message includes: a first Xn message or a first inter-node radio resource control (RRC) message.

6. The method according to claim 5, characterized in that, In response to the second message obtained from the terminal regarding the prediction-related information, the first Xn message includes at least one of the following: Switch request message Add a request message to the secondary node SN; SN modification request message; and The first inter-node RRC message includes a handover preparation message; or In response to the third message obtained from the third node regarding the prediction-related information, the first Xn message includes at least one of the following: Add a request message to the SN; SN modification request message; SN changes request message; SN modification request reply message; and The first inter-node RRC message includes cell group configuration messages.

7. The method according to any one of claims 1-4, characterized in that, The first message includes: a second Xn message or a second inter-node RRC message.

8. The method according to claim 7, characterized in that, The second Xn message or the second inter-node RRC message is used to transmit the prediction-related information between nodes. The second inter-node RRC message is included in the second Xn message or is included in the first Xn message.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: Receive a fourth message sent by the second node, the fourth message including information related to the prediction model; In response to the fourth message, perform one of the following operations: Select the second node as the target node; Select the second node as the candidate node; A fifth message is sent to the second node, which is used to cancel the operation related to the handover.

10. The method according to claim 9, characterized in that, The information related to the prediction model includes at least one of the following: The second node supports prediction functionality; The model information corresponding to the prediction functions supported by the second node.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: Receive a sixth message sent by the second node, the sixth message including a first request message, used to request the first node to send prediction-related information from the terminal; Sending the first message to the second node includes: In response to the sixth message, the first message is sent to the second node.

12. The method according to claim 11, characterized in that, The method further includes: Send a seventh message to the second node, the seventh message including relevant information for the second node to prepare for mobility; The sixth message is a response message to the seventh message.

13. The method according to claim 11 or 12, characterized in that, The sixth message includes at least one of the following: The first instruction information is used to instruct the first node to provide prediction-related information from the terminal; The second instruction information is used to indicate the training data corresponding to the first prediction function required by the second node; The third indication information is used to indicate the prediction result of the second prediction function on the terminal side required by the second node; The fourth instruction information is used to indicate the input information required for model inference by the second node.

14. The method according to claim 13, characterized in that, The prediction result of the second prediction function on the terminal side includes at least one of the following: Predicted results of a failed switchover; Predicted cell-level measurement results; Predicted beam-level measurement results; Configuration of predicted measurement events; Whether the predicted measurement events meet the corresponding configuration conditions; The predicted and recommended optimal target cell; The predicted recommended at least one candidate target cell.

15. The method according to any one of claims 1-14, characterized in that, The prediction-related information from the terminal includes at least one of the following: The fifth indication information is used to indicate that the prediction-related information comes from the terminal; Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates; Training data, which is used to train the prediction model on the second node side.

16. The method according to claim 15, characterized in that, The inference data includes at least one of the following: The results output by the prediction model on the terminal side; The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

17. The method according to any one of claims 1-16, characterized in that, The prediction-related information is used in at least one of the following prediction functions: Predicting measurement results; Switchover failure prediction; Wireless link failure prediction; Predicting measurement events.

18. The method according to any one of claims 1-17, characterized in that, The prediction-related information is used to perform at least one of the following operations: Optimized mobility operations; Mobility configuration updated; Predictive model inference; Predictive model training.

19. A communication method, characterized in that, The method is executed by the second node, and the method includes: The system receives a first message sent by a first node, the first message including prediction-related information, which is obtained by the first node from the terminal.

20. The method according to claim 19, characterized in that, The prediction-related information is the prediction-related information reported by the terminal and obtained by the first node; or, The prediction-related information is the prediction-related information sent by the third node and obtained by the first node, wherein the prediction-related information sent by the third node is the prediction-related information obtained by the third node from the terminal.

21. The method according to claim 20, characterized in that, The prediction-related information includes: the time information of the prediction results output by the prediction model on the terminal side.

22. The method according to any one of claims 19-21, characterized in that, The first message includes: a first Xn message or a first inter-node radio resource control (RRC) message.

23. The method according to claim 22, characterized in that, In response to the second message sent by the terminal from which the prediction-related information is obtained by the first node, the first Xn message includes at least one of the following: Switch request message Add a request message to the SN; SN modification request message; and The first inter-node RRC message includes a handover preparation message; In response to the prediction-related information being obtained by the first node from a third message sent by the third node, the first Xn message includes at least one of the following: Add a request message to the SN; SN modification request message; SN changes request message; SN modification request reply message; and The first inter-node RRC message includes cell group configuration messages.

24. The method according to any one of claims 19-21, characterized in that, The first message includes: a second Xn message or a second inter-node RRC message.

25. The method according to claim 24, characterized in that, The second Xn message is used to transmit the prediction-related information between nodes. The second inter-node RRC message is included in the second Xn message or in the first Xn message.

26. The method according to any one of claims 19-25, characterized in that, The method further includes: A fourth message is sent to the first node, the fourth message including information related to the prediction model; The fourth message is used to determine one of the following operations: Select the second node as the target node; Select the second node as the candidate node; A fifth message is sent to the second node, which is used to cancel the operation related to the handover.

27. The method according to claim 26, characterized in that, The information related to the prediction model includes at least one of the following: The second node supports prediction functions; The model information corresponding to the prediction functions supported by the second node.

28. The method according to any one of claims 19-27, characterized in that, The method further includes: A sixth message is sent to the first node, the sixth message including a first request message, which requests the first node to send prediction-related information from the terminal; The first message is a response message to the sixth message.

29. The method according to claim 28, characterized in that, The method further includes: Receive a seventh message sent by the first node, the seventh message including relevant information for the second node to prepare mobility; The sixth message is a response message to the seventh message.

30. The method according to claim 28 or 29, characterized in that, The sixth message includes at least one of the following: The first instruction information is used to instruct the first node to provide prediction-related information from the terminal; The second instruction information is used to indicate the training data corresponding to the first prediction function required by the second node; The third indication information is used to indicate the prediction result of the second prediction function on the terminal side required by the second node; The fourth instruction information is used to indicate the input information required for model inference by the second node.

31. The method according to claim 30, characterized in that, The prediction result of the second prediction function on the terminal side includes at least one of the following: Predicted results of a failed switchover; Predicted cell-level measurement results; Predicted beam-level measurement results; Configuration of predicted measurement events; Whether the predicted measurement events meet the corresponding configuration conditions; The predicted and recommended optimal target cell; The predicted recommended at least one candidate target cell.

32. The method according to any one of claims 19-31, characterized in that, The prediction-related information from the terminal includes at least one of the following: The fifth indication information is used to indicate that the prediction-related information comes from the terminal; Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates; Training data, which is used to train the prediction model on the second node side.

33. The method according to claim 32, characterized in that, The inference data includes at least one of the following: The results output by the prediction model on the terminal side; The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

34. The method according to any one of claims 19-33, characterized in that, The prediction-related information is used in at least one of the following prediction functions: Predicting measurement results; Switchover failure prediction; Wireless link failure prediction; Predicting measurement events.

35. The method according to any one of claims 19-34, characterized in that, The method further includes: Based on the prediction-related information, perform at least one of the following operations: Optimized mobility operations; Mobility configuration update; Predictive model inference; Predictive model training.

36. A communication method, characterized in that, The method is executed by a third node, and the method includes: The receiving terminal sends an eighth message, which includes prediction-related information; Send a third message to the first node, the third message including the prediction-related information; The prediction-related information is forwarded from the first node to the second node.

37. The method according to claim 36, characterized in that, The prediction-related information includes: the time information of the prediction results output by the prediction model on the terminal side.

38. The method according to claim 36 or 37, characterized in that, The prediction-related information in the sixth message includes at least one of the following: The fifth indication information is used to indicate that the prediction-related information comes from the terminal; Inference data, which is used by the second node to perform mobility operation optimization and / or mobility configuration updates; Training data, which is used to train the prediction model on the second node side.

39. The method according to claim 38, characterized in that, The inference data includes at least one of the following: The results output by the prediction model on the terminal side; The input information required for the prediction model on the second node side to perform model inference is obtained from the terminal.

40. The method according to any one of claims 36-39, characterized in that, The prediction-related information is used in at least one of the following prediction functions: Predicting measurement results; Switchover failure prediction; Wireless link failure prediction; Predicting measurement events.

41. The method according to any one of claims 36-39, characterized in that, The prediction-related information is used to perform at least one of the following operations: Optimized mobility operations; Mobility configuration update; Predictive model inference; Predictive model training.

42. A first node, characterized in that, include: The first transceiver module is used to acquire prediction-related information from the terminal and send a first message to the second node, the first message including the prediction-related information.

43. A second node, characterized in that, include: The second transceiver module is used to receive a first message sent by the first node, the first message containing prediction-related information, which is obtained by the first node from the terminal.

44. A third node, characterized in that, include: The third transceiver module is used to receive a sixth message sent by the terminal, the sixth message including prediction-related information, and to send a third message to the first node, the third message including the prediction-related information. The prediction-related information is forwarded from the first node to the second node.

45. A first node, characterized in that, include: One or more processors; The first node is used to perform the method described in any one of claims 1 to 18.

46. ​​A second node, characterized in that, include: One or more processors; The second node is used to perform the method described in any one of claims 19 to 35.

47. A third node, characterized in that, include: One or more processors; The third node is used to perform the method described in any one of claims 36 to 41.

48. A communication system, characterized in that, include: A first node and a second node, wherein the first node is used to implement the method of any one of claims 1 to 18, and the second node is used to implement the method of any one of claims 19 to 35.

49. The system according to claim 38, characterized in that, Also includes: A third node, wherein the third node is used to implement the method of any one of claims 36 to 41.

50. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores executable instructions that are loaded and executed by a processor to implement the method as claimed in claims 1 to 18, or claims 19 to 35, or any one of claims 36 to 41.

51. A computer program product comprising a computer program that, when executed by a processor, implements the method of any one of claims 1-18, or the method of any one of claims 19-35, or the method of any one of claims 36-41.

Images