Communication method, communication device, communication system, storage medium and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium and a program product. The method comprises: a first device sending a first message, wherein the first message instructs a terminal to re-synchronize from a currently accessed first cell to a second cell, the first cell is managed by the first device, the second cell is managed by a second device, the configuration of the first cell is the same as the configuration of the second cell, and the first device and the second device move relative to the ground. In this way, the service performance of a network can be improved.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] Non-terrestrial Network (NTN) is a fifth-generation mobile communication technology (5G). th NTN (Network Transmission Network), a key technology introduced in 5G (5G Generation Mobile Communication Technology), provides wireless resources via satellites (or drones) instead of terrestrial base stations. NTN payloads are divided into transparent payloads and regenerative payloads. In the case of a transparent payload, the satellite amplifies and relays signals but does not have the ability to process information. In the case of a regenerative payload, such as gNB onboard, the satellite has the ability to process information onboard.

[0003] Summary of the Invention

[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0005] According to a first aspect of the present disclosure, a communication method is provided, performed by a first device, the method comprising: sending a first message, the first message instructing a terminal to resynchronize from a currently accessed first cell to a second cell, the first cell being managed by the first device, the second cell being managed by a second device, the configuration of the first cell being the same as the configuration of the second cell, and the first device and the second device moving relative to the ground.

[0006] According to a second aspect of the present disclosure, a communication method is provided, executed by a second device, the method comprising: receiving a sixth message sent by a third device; establishing or activating a second cell according to the sixth message; the configuration of the second cell being the same as that of a first cell; the first cell being a cell currently accessed by a terminal and managed by a first device; the first device and the second device moving relative to the ground; and the third device being stationary relative to the ground.

[0007] According to a third aspect of the present disclosure, a communication method is provided, performed by a third device, the method comprising: sending a second message to a first device, the second message instructing the first device to send a first message, the first message instructing a terminal to resynchronize from a currently accessed first cell to a second cell, the first cell being managed by the first device, the second cell being managed by a second device, the configuration of the first cell being the same as the configuration of the second cell, the first device and the second device moving relative to the ground, and the third device being stationary relative to the ground.

[0008] According to a fourth aspect of the present disclosure, a communication method is provided, executed by a terminal, the method comprising: receiving a first message; resynchronizing from a currently accessed first cell to a second cell according to the first message, wherein the first cell is managed by a first device and the second cell is managed by a second device, the configuration of the first cell is the same as the configuration of the second cell, and the first device and the second device move relative to the ground.

[0009] According to a fifth aspect of the present disclosure, a communication device is provided for performing the communication methods described in at least one of the first, second, third, and fourth aspects.

[0010] According to a sixth aspect of the present disclosure, a communication system is provided, including at least one of a first device, a second device, a third device, and a terminal, wherein the first device is configured to implement the communication method of the first aspect, the second device is configured to implement the communication method of the second aspect, the third device is configured to implement the communication method of the third aspect, and the terminal is configured to implement the communication method of the fourth aspect.

[0011] According to a seventh aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause at least one of the communication methods described in the first, second, third, and fourth aspects to be performed.

[0012] According to an eighth aspect of the present disclosure, a program product is provided, comprising at least one program and instructions, wherein when the program and instructions are executed by a communication device, the program and instructions implement the steps of the communication method described in at least one of the first, second, third, and fourth aspects.

[0013] By adopting the above technical solution, at least the following beneficial technical effects can be achieved:

[0014] The first device sends a first message instructing the terminal to resynchronize from the first cell under the currently accessed first device to the second cell under the second device. The first device and the second device are different devices moving relative to the ground. Since the configurations of the first cell and the second cell are identical, this method can reduce or avoid latency and signaling storms caused by the terminal switching from the first device to the second device, thereby improving network service performance. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

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

[0017] Figure 1B is an exemplary schematic diagram of the architecture of a non-terrestrial network provided according to an embodiment of the present disclosure.

[0018] Figure 1C is an exemplary schematic diagram of a transparent transmission mode provided according to an embodiment of the present disclosure.

[0019] Figure 1D is an exemplary schematic diagram of a regeneration mode provided according to an embodiment of the present disclosure.

[0020] Figure 1E is an exemplary schematic diagram of a gNB-DU-based regenerative satellite NG-RAN provided according to an embodiment of the present disclosure.

[0021] Figure 1F is an exemplary schematic diagram of a regenerative architecture provided according to an embodiment of the present disclosure.

[0022] Figure 1G is an exemplary schematic diagram of hard switching provided according to an embodiment of the present disclosure.

[0023] Figure 1H is an exemplary schematic diagram of a softswitch provided according to an embodiment of the present disclosure.

[0024] Figure 2A is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0025] Figure 2B is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0026] Figure 3 is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0027] Figure 4A is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0028] Figure 4B is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0029] Figure 5A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure.

[0030] Figure 5B is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure.

[0031] Figure 6A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure.

[0032] Figure 6B is a schematic diagram of a chip structure according to an embodiment of the present disclosure. Detailed Implementation

[0033] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0034] In a first aspect, embodiments of this disclosure propose a communication method executed by a first device, the method comprising: sending a first message, the first message instructing a terminal to resynchronize from a currently accessed first cell to a second cell, the first cell being managed by the first device, the second cell being managed by a second device, the configuration of the first cell being the same as the configuration of the second cell, and the first device and the second device moving relative to the ground.

[0035] In the above embodiment, the first device sends a first message instructing the terminal to resynchronize from the first cell under the currently accessed first device to the second cell under the second device. The first device and the second device are different devices moving relative to the ground. Since the configuration of the first cell is the same as that of the second cell, this method can reduce or avoid the latency and signaling storms caused by the terminal switching from the first device to the second device (cell handover), thereby improving network service performance.

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

[0037] Service time information of the first device;

[0038] Service information for the second device;

[0039] The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC);

[0040] The second instruction indicates whether to reset the Media Access Control (MAC).

[0041] In the above embodiments, the first message can indicate to the terminal at least one of the following: the service time information of the first device, the service information of the second device, whether to rebuild the RLC, and whether to reset the MAC. This facilitates the terminal in determining at least one of the following: the time to resynchronize from the first cell to the second cell, whether to rebuild the RLC in the case of resynchronization, and whether to reset the MAC in the case of resynchronization. This enables effective management of the terminal.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, prior to sending the first message, the process includes: receiving a second message sent by a third device, the second message instructing the first device to send the first message, the third device being stationary relative to the ground; wherein the second message includes at least one of the following:

[0043] The third instruction is used to indicate the content included in the first message;

[0044] The fourth indication is used to indicate the time when the first device sends the first message.

[0045] In the above embodiments, it is specified that the first device is controlled by a third device.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the second message is sent by the third device to the first device after sending a first request to the second device, the first request being used to request the second device to create a context for the terminal, wherein the first request includes a fifth indication, the fifth indication being used to instruct the second device to continue using at least one of the following:

[0047] The identifier assigned to the terminal by the first device;

[0048] The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device;

[0049] The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

[0050] In the above embodiments, the second device is controlled by the third device.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a third message sent by a third device, the third message including a second request for requesting the latest context of the terminal; and sending a fourth message to the third device for the third device to determine the latest context of the terminal.

[0052] In the above embodiments, the third device may request the latest context of the terminal from the first device to ensure information synchronization between the third device and the second device, thereby facilitating the protection of network service performance.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the third message further includes a third request, the third request being used to request the status information of the radio bearer of the terminal, the third request including at least one of the following:

[0054] The sixth indication is used to indicate that the radio bearer includes one or more of SRB and DRB;

[0055] The seventh indication is used to indicate that the status information includes one or more of RLC status information and MAC status information.

[0056] In the above embodiments, it is specified that a third device can request the status information of the terminal's wireless bearer from a first device.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: sending a fifth message to the third device, the fifth message being used by the third device to determine and send radio bearer status information of the terminal to the second device, the radio bearer status information of the terminal being used by the second device to receive or process at least one of data and signaling sent by the terminal when the terminal accesses the second cell;

[0058] The status information of the wireless bearer of the terminal includes at least one of the following:

[0059] Terminal identifier;

[0060] SRB logo,

[0061] DRB identification;

[0062] RLC status information;

[0063] MAC status information.

[0064] In the above embodiments, since the third device can send the terminal radio bearer status information obtained from the first device to the second device, the second device can continue to use the terminal radio bearer status information in the first device to receive or process data and signaling sent by the terminal even when the terminal is synchronized to the second cell. This enables the terminal to seamlessly switch cells. In other words, the terminal can assume that no cell handover has occurred when it resynchronizes from the first cell to the second cell.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the RLC status information includes at least one of the following:

[0066] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0067] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0068] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0069] The remaining time of the timeout timer is used to trigger a retransmission request.

[0070] In the above embodiments, the content of RLC status information is specified.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the MAC status information includes at least one of the following:

[0072] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0073] Lead time (TA);

[0074] Hybrid Automatic Repeat Request (HARQ) status.

[0075] In the above embodiments, the content of MAC status information is standardized.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: sending service information of the first device to a third device, the service information of the first device being used by the third device to determine the time to send a sixth message to the second device, the sixth message including at least one of the following:

[0077] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0078] The ninth instruction is used to instruct the second device to establish the second cell;

[0079] The tenth instruction is used to indicate the configuration of the second cell;

[0080] The eleventh instruction is used to instruct the activation of the second cell.

[0081] In the above embodiments, the first device and the second device are centrally controlled or managed by the third device. The first device may need to report its service information to the third device so that the third device can instruct the second device when to establish or activate the second cell.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments, the service information includes at least one of the following:

[0083] Mobile information;

[0084] Synchronize time information;

[0085] Service time information;

[0086] Service location information.

[0087] In the above embodiments, the content of the service information is standardized.

[0088] Secondly, this disclosure provides a communication method executed by a second device. The method includes: receiving a sixth message sent by a third device; establishing or activating a second cell according to the sixth message; the configuration of the second cell being the same as that of the first cell; the first cell being the cell currently accessed by the terminal and managed by the first device; the first device and the second device moving relative to the ground; and the third device being stationary relative to the ground.

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

[0090] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0091] The ninth instruction is used to instruct the second device to establish the second cell;

[0092] The tenth instruction is used to indicate the configuration of the second cell;

[0093] The eleventh instruction is used to instruct the activation of the second cell.

[0094] In conjunction with some embodiments of the second aspect, in some embodiments, establishing or activating the second cell according to the sixth message includes:

[0095] Establish the second DU; or,

[0096] Establish a second cell; or,

[0097] Activate the second cell.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a first request sent by the third device, creating a context for the terminal based on the first request, and continuing to use at least one of the following according to a fifth instruction in the first request:

[0099] The identifier assigned to the terminal by the first device;

[0100] The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device;

[0101] The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving radio bearer status information of the terminal sent by the third device; and, when the terminal accesses the second cell, receiving or processing at least one of data and signaling sent by the terminal based on the radio bearer status information of the terminal.

[0103] The status information of the wireless bearer of the terminal includes at least one of the following:

[0104] Terminal identifier;

[0105] SRB logo,

[0106] DRB identification;

[0107] RLC status information;

[0108] MAC status information.

[0109] In conjunction with some embodiments of the second aspect, in some embodiments, the RLC status information includes at least one of the following:

[0110] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0111] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0112] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0113] The remaining time of the timeout timer is used to trigger a retransmission request.

[0114] In conjunction with some embodiments of the second aspect, in some embodiments, the MAC status information includes at least one of the following:

[0115] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0116] Lead time (TA);

[0117] Hybrid Automatic Repeat Request (HARQ) status.

[0118] In some embodiments, in conjunction with the second aspect, the method further includes: sending service information of the second device to the third device, wherein the service information of the second device is used by the third device to determine the time to send the sixth message to the second device.

[0119] Thirdly, this disclosure provides a communication method executed by a third device. The method includes: sending a second message to a first device, the second message instructing the first device to send a first message, the first message instructing a terminal to resynchronize from a currently accessed first cell to a second cell, the first cell being managed by the first device, the second cell being managed by the second device, the configuration of the first cell being the same as the configuration of the second cell, the first device and the second device moving relative to the ground, and the third device being stationary relative to the ground.

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

[0121] Service time information of the first device;

[0122] Service information for the second device;

[0123] The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC);

[0124] The second instruction indicates whether to reset the Media Access Control (MAC).

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

[0126] The third instruction is used to indicate the content included in the first message;

[0127] The fourth indication is used to indicate the time when the first device sends the first message.

[0128] In conjunction with some embodiments of the third aspect, in some embodiments, prior to sending the second message to the first device, the method includes: sending a first request to the second device, the first request being used to request the second device to create a context for the terminal, wherein the first request includes a fifth indication, the fifth indication being used to instruct the second device to continue using at least one of the following:

[0129] The identifier assigned to the terminal by the first device;

[0130] The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device;

[0131] The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

[0132] In conjunction with some embodiments of the third aspect, in some embodiments, before sending the first request to the second device, the method includes: sending a third message to the first device, the third message including a second request, the second request being used to request the latest context of the terminal; receiving a fourth message sent by the first device, and determining the latest context of the terminal based on the fourth message.

[0133] In conjunction with some embodiments of the third aspect, in some embodiments, the third message further includes a third request, the third request being used to request the status information of the radio bearer of the terminal, the third request including at least one of the following:

[0134] The sixth indication is used to indicate that the radio bearer includes one or more of SRB and DRB;

[0135] The seventh indication is used to indicate that the status information includes one or more of RLC status information and MAC status information.

[0136] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: receiving a fifth message sent by the first device; determining and sending radio bearer status information of the terminal to the second device based on the fifth message, wherein the radio bearer status information of the terminal is used by the second device to receive or process at least one of data and signaling sent by the terminal when the terminal accesses the second cell;

[0137] The status information of the wireless bearer of the terminal includes at least one of the following:

[0138] Terminal identifier;

[0139] SRB logo,

[0140] DRB identification;

[0141] RLC status information;

[0142] MAC status information.

[0143] In conjunction with some embodiments of the third aspect, in some embodiments, the RLC status information includes at least one of the following:

[0144] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0145] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0146] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0147] The remaining time of the timeout timer is used to trigger a retransmission request.

[0148] In conjunction with some embodiments of the third aspect, in some embodiments, the MAC status information includes at least one of the following:

[0149] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0150] Lead time (TA);

[0151] Hybrid Automatic Repeat Request (HARQ) status.

[0152] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: sending a sixth message to the second device, the sixth message including at least one of the following:

[0153] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0154] The ninth instruction is used to instruct the second device to establish the second cell;

[0155] The tenth instruction is used to indicate the configuration of the second cell;

[0156] The eleventh instruction is used to instruct the activation of the second cell.

[0157] In conjunction with some embodiments of the third aspect, in some embodiments, the sending time of the sixth message is determined based on the service information sent by the first device and the service information sent by the second device;

[0158] Service information includes at least one of the following:

[0159] Sports information;

[0160] Synchronize time information;

[0161] Service time information;

[0162] Service location information.

[0163] Fourthly, embodiments of this disclosure propose a communication method executed by a terminal, the method comprising: receiving a first message; resynchronizing from a currently accessed first cell to a second cell according to the first message, wherein the first cell is managed by a first device and the second cell is managed by a second device, the configuration of the first cell is the same as the configuration of the second cell, and the first device and the second device move relative to the ground.

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

[0165] Service time information of the first device;

[0166] Service information for the second device;

[0167] The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC);

[0168] The second instruction indicates whether to reset the Media Access Control (MAC).

[0169] Fifthly, embodiments of this disclosure provide a communication device for performing the communication method described in any one of the first, second, third, and fourth aspects.

[0170] In a sixth aspect, embodiments of this disclosure provide a first device, which includes at least one of a transceiver module and a processing module; wherein the first device is used to perform an optional implementation of the first aspect.

[0171] In a seventh aspect, embodiments of this disclosure provide a second device, which includes at least one of a transceiver module and a processing module; wherein the second device is used to perform an optional implementation of the second aspect.

[0172] Eighthly, embodiments of this disclosure propose a third device, which includes at least one of a transceiver module and a processing module; wherein the third device is used to perform an optional implementation of the third aspect.

[0173] In a ninth aspect, embodiments of this disclosure provide a terminal, which includes at least one of a transceiver module and a processing module; wherein the terminal is used to execute an optional implementation of the fourth aspect.

[0174] In a tenth aspect, embodiments of this disclosure provide a first device, the first device comprising: one or more processors; wherein the terminal is configured to execute an optional implementation of the first aspect.

[0175] In one aspect, embodiments of this disclosure provide a second device, which includes one or more processors; wherein the terminal is used to execute an optional implementation of the second aspect.

[0176] In a twelfth aspect, embodiments of this disclosure provide a third device, which includes one or more processors; wherein the third device is used to perform an optional implementation of the third aspect.

[0177] In a thirteenth aspect, embodiments of this disclosure provide a terminal, which includes one or more processors; wherein the terminal is used to execute an optional implementation of the fourth aspect.

[0178] In a fourteenth aspect, embodiments of this disclosure provide a communication system comprising: a first device, a second device, a third device, and a terminal; wherein the first device is configured to perform the method described in the optional implementation of the first aspect, the second device is configured to perform the method described in the optional implementation of the second aspect, the third device is configured to perform the method described in the optional implementation of the third aspect, and the terminal is configured to implement the method described in the optional implementation of the fourth aspect.

[0179] In a fifteenth aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the optional implementations of the first, second, third, and fourth aspects.

[0180] In a sixteenth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, which, when executed by a communication device, causes the communication device to perform the method described in the optional implementations of the first, second, third, and fourth aspects.

[0181] On page seventeen, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the optional implementations of the first, second, third, and fourth aspects.

[0182] In an eighteenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first, second, third, and fourth aspects described above.

[0183] It is understood that the aforementioned communication equipment, communication system, first device, second device, third device, terminal, storage medium, program product, computer program, etc., are all used to execute the communication method proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0184] This disclosure provides a communication method, communication device, communication system, storage medium, and program product. In some embodiments, the terms communication method, information processing method, handover method, cell handover method, satellite handover method, network handover method, network migration method, and wireless link connection migration method can be used interchangeably.

[0185] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. 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. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0186] 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 scope of this disclosure.

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

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

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

[0190] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0191] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0192] 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. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

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

[0194] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0195] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device taking corresponding actions under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to have a judgment action when implementing it, nor do they mean that there must be other limitations.

[0196] 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”.

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

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

[0199] 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," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

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

[0201] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has 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., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0202] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

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

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

[0205] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0206] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 may include a terminal 101 and a network device 102, wherein the network device 102 may include at least one of a first device 1021, a second device 1022, and a third device 1023.

[0207] In some embodiments, terminal 101 includes, for example, 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, but is not limited thereto.

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

[0209] In some embodiments, network device 102 includes access network device. Access network device is, for example, a node or device that connects a terminal to a wireless network. Access 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), radio 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 Wi-Fi system.

[0210] Optionally, a base station may be, for example, a macro base station, a micro base station (also known as a small station), a relay station, an access point, a 5 / 6G base station or a future base station, a satellite, a drone, mobile access network equipment, a Transmitting and Receiving Point (TRP), a Transmitting Point (TP), a mobile switching center, or other equipment that performs base station functions in a communication system. This disclosure does not specifically limit the type of base station. For ease of description, in all embodiments of this disclosure, the apparatus that provides wireless communication functions for terminal devices is collectively referred to as a network device or a base station.

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

[0212] In some embodiments, a base station may include a Central Unit (CU) and a Distributed Unit (DU). The CU, also known as a Control Unit, allows for the separation of the base station's protocol layers, with some protocol layer functions residing in the CU and others in the DU. Optionally, the CU may also integrate some functions that have been moved down from the core network. The CU acts as a centralized management node, centrally controlling the DU. However, this is not the only possible approach.

[0213] In some embodiments, the first device and the second device are network devices including a DU, and the third device is a network device including a CU. The first device and the second device are centrally controlled by the third device.

[0214] 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 access 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.

[0215] 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 access 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.

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

[0217] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. 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.

[0218] 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, systems utilizing other communication methods, 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).

[0219] In some embodiments, as shown in FIG1B, the NTN network provides wireless resources to the terminal via satellite (or drone) instead of ground base stations.

[0220] In some embodiments, satellite signal processing can be divided into transparent transmission mode (i.e., transparent payload) and regenerative mode (i.e., regenerative payload). In transparent transmission mode, as shown in Figure 1C, the NTN ground station transmits the gNB signal to the satellite. The satellite converts the signal to its own frequency band and then transmits it to the UE. Aside from frequency conversion and signal amplification, the satellite does not demodulate the gNB signal, acting similarly to a repeater. In regenerative mode, as shown in Figure 1D, after the NTN ground station transmits the gNB signal to the satellite, the satellite demodulates and decodes the signal before re-encoding and modulating it (this process is regeneration) and then transmits the regenerated signal through its own frequency band. It should be noted that in Figures 1C and 1D, 5GCN refers to the 5G Core Network, the SRI interface is the Satellite Radio Interface, the NG interface is the interface between the Radio Access Network (RAN) and the 5G Core Network, and the N6 interface is the interface between the User Plane Functional Unit (UPF) and the External Data Network (DN).

[0221] In some embodiments, under regeneration mode, 3GPP also studies scenarios where only the distribution unit (DU) is deployed on a satellite.

[0222] In some embodiments, the NG-RAN logical architecture with CU-DU separation, as depicted in FIG1E, is used as the baseline for NTN scenarios.

[0223] In some embodiments, the satellite payload enables the regeneration of signals received from Earth.

[0224] In some embodiments, as shown in Figure 1E, the feeder link between the NTN gateway and the satellite uses a Satellite Radio Interface (SRI). The SRI transmits the F1 protocol.

[0225] In some embodiments, the satellite payload can provide inter-satellite links between satellites.

[0226] In some embodiments, SRIs are transport links; the logical interface F1 they transmit is specified by 3GPP.

[0227] In some embodiments, the NTN GW is a transport network layer node that supports all necessary transport protocols.

[0228] In some embodiments, DUs on different satellites can be connected to the same CU on the ground.

[0229] In some embodiments, if a satellite carries multiple DUs, the same SRI will transmit all corresponding F1 interface instances.

[0230] In some embodiments, the relationship between satellite altitude, orbit, and satellite coverage of some typical NTN networks is shown in Table 1 below.

[0231] Table 1

[0232] For example, as shown in Table 1, the altitude of low Earth orbit satellites is generally between 300 km and 1500 km, and the beam coverage range is between 100 km and 1000 km.

[0233] In some embodiments, the scenario shown in Figure 1F can be considered in the deployment of 6G satellite networks. For non-geosynchronous orbit regenerated payloads, frequent UE switching may occur due to frequent satellite handover. A possible solution is to support satellite handover and resynchronization through a regenerated architecture (airborne DU: no security issues because the Packet Data Convergence Protocol (PDCP) is in the CU).

[0234] In view of this, embodiments of this disclosure propose a communication method, communication device, communication system, storage medium, and program product. These can at least support satellite handover methods under a regenerative architecture, avoiding latency and signaling storms caused by handover.

[0235] The following describes the application scenarios of the embodiments of this disclosure. The embodiments of this disclosure can be applied to both hard-switch and soft-switch scenarios. As shown in Figure 1G, in a hard-switch scenario, the terminal is connected to either a source gNB or a target gNB. During the switch from the source gNB to the target gNB, communication is briefly interrupted. As shown in Figure 1H, in a soft-switch scenario, the terminal is connected to two or more gNBs. Switching gNBs does not require a change in the transmit / receive frequency, and communication is not interrupted.

[0236] 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 embodiment of the present disclosure relates to a communication method executed by a communication system 100, the method including:

[0237] In step S2101, the first device 1021 sends the service information of the first device to the third device 1023.

[0238] In some embodiments, the third device receives service information from the first device. For example, the third device receives service information sent by the first device. Optionally, the first device sends its own service information to the third device upon request. Optionally, the first device proactively reports its own service information to the third device (periodically).

[0239] In some embodiments, the service information of the first device may be carried in the F1 interface setup request sent by the first device to the third device. However, it is not limited to this.

[0240] In some embodiments, the first device moves relative to the ground. For example, the first device moves relative to the Earth. For example, the first device moves relative to a fixed reference point on the ground. Optionally, the first device is a non-ground-based mobile device. For example, it could be an aircraft, such as a satellite or drone in a non-geosynchronous orbit. Optionally, the first device can be a ground-based mobile device, such as a vehicle or ship.

[0241] In some embodiments, the first device includes at least a portion of the functionality of the DU. For example, the first device includes a DU.

[0242] In some embodiments, the name of the first device is not limited, and it may be, for example, a source DU, a first DU, a first satellite, a first access network device, a first mobile device, a first distributed unit, etc.

[0243] In some embodiments, the third device is stationary relative to the ground. For example, the third device is stationary relative to the Earth. For example, the third device is stationary relative to a fixed reference point on the ground.

[0244] Optionally, the third device can be a device that is stationary relative to the ground but moving relative to other reference coordinates. For example, it could be an aircraft, such as a satellite or drone in geosynchronous orbit. It should be understood that satellites and drones in geosynchronous orbit are stationary relative to the ground but moving relative to other reference coordinates such as the moon.

[0245] Optionally, the third device can be a stationary device on the ground, such as a controller, ground base station, tower, or ground site fixed to the ground. It should be understood that controllers, ground base stations, towers, and ground sites fixed to the ground are stationary relative to the ground.

[0246] In some embodiments, the third device includes at least a portion of the functionality of the CU. For example, the third device includes a CU.

[0247] In some embodiments, the name of the third device is not limited, and it may be, for example, CU, centralized controller, centralized unit, control unit, etc.

[0248] In some embodiments, the first device is controlled and managed by a third device.

[0249] In some embodiments, the service information of the first device is used to indicate service-related information of the first device. Optionally, the service information of the first device includes at least one of the following:

[0250] The movement information of the first device;

[0251] Synchronization time information of the first device;

[0252] Service time information for the first device;

[0253] The service location information of the first device.

[0254] The motion information of the first device is used to determine its trajectory and position at any given time. For example, assuming the first device is a first satellite, its motion information can be understood as its ephemeris information. The satellite's ephemeris information can include its parameters, such as orbital plane parameters and horizontal parameters. Orbital plane parameters include, for example, the square root of the semi-major axis, eccentricity, inclination at the reference time, longitude of the rising node, and perigee angle. Horizontal parameters include, for example, the mean anomaly of the reference time and the ephemeris reference time. Based on these satellite parameters, the satellite's position can be determined; that is, the satellite's ephemeris information is used to determine its position.

[0255] In some embodiments, the area where the first device provides network services can be further determined based on the location of the first device. When the first device provides network services to a certain area, terminals within that area can access the first device for communication. When the first device moves and no longer provides network services to that area, terminals within that area should access other devices for communication.

[0256] In some embodiments, the synchronization time information of the first device is used to indicate the time when the terminal synchronizes (accesses, switches) with the first device.

[0257] For example, when the first device provides network services to a certain area, the terminals in that area can synchronize uplink and / or downlink with the cells under the first device during the synchronization time period indicated by the first device.

[0258] In some embodiments, the service time information of the first device is used to indicate the time during which the first device provides network services.

[0259] For example, a terminal can access the first device for communication during the time period when the first device provides network services.

[0260] In some embodiments, the service location information of the first device is used to indicate which locations the first device can provide network services to.

[0261] For example, the terminal can determine whether its current location is within the range of the network services currently provided by the first device based on the service location information of the first device, thereby facilitating the terminal's decision on whether to access the first device to obtain network services.

[0262] In other words, based on the service information of the first device, it is possible to determine the time when the first device provides network services to a certain location, and the time when the terminal at that location synchronizes (accesses, switches) to the first device.

[0263] In some embodiments, step S2101 can be omitted, and the third device can determine the service information of the first device through pre-configuration information. The pre-configuration information may be, for example, Operation Administration and Maintenance (OAM) information.

[0264] In step S2102, the second device 1022 sends the service information of the second device to the third device 1023.

[0265] In some embodiments, the third device receives service information from the second device. For example, the third device receives service information sent by the second device. Optionally, the second device sends its own service information to the third device upon request. Optionally, the second device periodically and proactively reports its own service information to the third device.

[0266] In some embodiments, the service information of the second device may be carried in the F1 interface setup request sent by the second device to the third device. However, this is not the only possibility.

[0267] In some embodiments, the second device moves relative to the ground. For example, the second device moves relative to the Earth. For example, the second device moves relative to a fixed reference point on the ground. Optionally, the second device is a non-ground-based mobile device. For example, it could be an aircraft, such as a satellite or drone in a non-geosynchronous orbit. Optionally, the second device can be a ground-based mobile device, such as a vehicle or ship.

[0268] In some embodiments, the second device includes at least a portion of the functionality of the DU. For example, the second device includes the DU.

[0269] In some embodiments, the name of the second device is not limited, and it may be, for example, a target DU, a second DU, a second satellite, a second access network device, a second mobile device, a second distributed unit, etc.

[0270] In some embodiments, the second device is controlled and managed by a third device. That is, the third device can centrally control and manage the first and second devices.

[0271] In some embodiments, the service information of the second device is used to indicate service-related information of the second device. Optionally, the service information of the second device includes at least one of the following:

[0272] Movement information of the second device;

[0273] Synchronization time information of the second device;

[0274] Service time information for the second device;

[0275] Service location information for the second device.

[0276] The movement information of the second device is used to determine its trajectory and position at any given time. For example, assuming the second device is a second satellite, its movement information can be understood as its ephemeris information. The satellite's ephemeris information can include its parameters, such as orbital plane parameters and horizontal parameters. Orbital plane parameters include, for example, the square root of the semi-major axis, eccentricity, inclination at the reference time, longitude of the rising node, and perigee angle. Horizontal parameters include, for example, the mean anomaly of the reference time and the ephemeris reference time. Based on these satellite parameters, the satellite's position can be determined; that is, the satellite's ephemeris information is used to determine its position.

[0277] In some embodiments, the synchronization time information of the second device is used to indicate the time when the terminal synchronizes (accesses, switches) with the second device.

[0278] In some embodiments, the service time information of the second device is used to indicate the time during which the second device provides network services.

[0279] In some embodiments, the service location information of the second device is used to indicate which locations the second device can provide network services to.

[0280] In other words, based on the service information of the second device, it is possible to determine the time when the second device provides network services to a certain location, and the time when the terminal at that location synchronizes (accesses, switches) to the second device.

[0281] In some embodiments, step S2102 can be omitted, and the third device can determine the service information of the second device through pre-configuration information. The pre-configuration information may be, for example, OAM information.

[0282] In some embodiments, steps S2101 and S2102 may be executed periodically, at set times, or based on triggering conditions.

[0283] In some embodiments, the number of times steps S2101 and S2102 are executed is not limited. For example, steps S2101 and S2102 may be executed once or multiple times.

[0284] In some embodiments, the order of steps S2101 and S2102 with any of the subsequent steps S2103 to S2112 is not limited. For example, steps S2101 and S2102 may be performed before or after step S2103. For example, steps S2101 and S2102 may be performed before or after step S2111. However, this is not a limitation.

[0285] In step S2103, the third device 1023 sends a sixth message to the second device 1022.

[0286] In some embodiments, the second device receives a sixth message. For example, the second device receives a sixth message sent by a third device.

[0287] In some embodiments, the sixth message is used to instruct the second device to create or activate the second cell.

[0288] In some embodiments, the sixth message is used to instruct the second device to create or activate a second DU, wherein the second DU includes a second cell.

[0289] In some embodiments, the name of the sixth message is not limited, and it may be, for example, a cell creation instruction, a cell activation instruction, a DU creation or activation instruction, etc.

[0290] In some embodiments, the sixth message may be an F1 interface message. However, it is not limited to this.

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

[0292] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first DU, wherein the first DU includes a first cell and the second DU includes a second cell;

[0293] The ninth instruction is used to instruct the second device to establish a second cell;

[0294] The tenth instruction is used to indicate the configuration of the second cell;

[0295] The eleventh instruction is used to instruct the activation of the second cell.

[0296] In some embodiments, the configuration of the second cell includes at least one of the following: the identifier of the second cell, the supported PLMN, the Tracking Area Identifier (TAI), and the cell resource configuration.

[0297] In some embodiments, the sixth message may instruct the creation or activation of one or more second cells. Accordingly, the sixth message may include / instruct information required to create or activate one or more second cells.

[0298] It should be explained that the second cell is managed by the second device. The second DU includes the second cell, and the establishment of the second DU by the second device includes the establishment of the second cell. The first cell is managed by the first device, and the first DU of the first device includes the first cell. The configuration of the second DU is the same as the configuration of the first DU, which means that the configuration of the second cell is the same as the configuration of the first cell.

[0299] It should be noted that the configuration of the second cell indicated by the tenth instruction may be the configuration of the first cell obtained by the third device from the first device.

[0300] In some embodiments, the tenth instruction indicates the configuration of the second cell by indicating the configuration of the second DU. The configuration of the second DU may be the configuration of the first DU obtained by the third device from the first device.

[0301] It should be noted that, based on the content indicated by the sixth message, the second device is able to know which configuration of the second cell or second DU to establish or activate.

[0302] In some embodiments, the service information of the first device is used by the third device to determine the time to send the sixth message to the second device.

[0303] In some embodiments, the service information of the second device is used by the third device to determine the time to send the sixth message to the second device.

[0304] In some embodiments, the time at which the third device sends the sixth message to the second device is determined based on at least one of the service information of the first device and the service information of the second device.

[0305] In some embodiments, the third device determines the time when the terminal switches from the first device to the second device based on the service information of the first device and the service information of the second device, and the third device sends a sixth message to the second device before that time.

[0306] For example, assuming the first device is the first satellite and the second device is the second satellite, then the third device can send a sixth message to the second satellite before the terminal switches from the first satellite to the second satellite.

[0307] In step S2104, the second device 1022 establishes or activates the second cell according to the sixth message.

[0308] Optionally, the second device establishes a second DU based on the sixth message.

[0309] Optionally, the second device establishes a second cell based on the sixth message.

[0310] Optionally, the second device activates the second cell based on the sixth message.

[0311] In some embodiments, the sixth message includes the configuration of the second DU. The second device can create a second DU based on the configuration of the second DU, and creating the second DU includes creating a second cell.

[0312] In some embodiments, the sixth message includes the configuration of the second cell. The second device can create the second cell based on the configuration of the second cell.

[0313] In some embodiments, a cell with the same configuration as the second cell is pre-configured on the second device, and the second device can activate the cell to obtain an activated second cell.

[0314] It should be explained that cell establishment or activation refers to setting a geographical area covered by a base station to an available state so that terminals can connect to that area and communicate.

[0315] In step S2105, the second device 1022 sends cell update information to the third device 1023.

[0316] In some embodiments, the third device receives cell update information sent by the second device.

[0317] In some embodiments, cell update information is used to respond to a sixth message sent by a third device.

[0318] In some embodiments, cell update information is used to indicate the cell most recently created or activated by the second device. For example, the cell update information includes the ID of the second cell that was created or activated.

[0319] In some embodiments, the name of the cell update information is not limited, and it may be, for example, DU update information, response information, list of active cells, etc.

[0320] In some embodiments, cell update information can be sent via F1 interface messages.

[0321] In some embodiments, the second device may send cell update information to the third device after establishing or activating the second cell according to the sixth message, in response to the sixth message sent by the third device.

[0322] In step S2106, the third device 1023 sends a third message to the first device 1021.

[0323] In some embodiments, the first device receives a third message. For example, the first device receives a third message sent by a third device.

[0324] In some embodiments, the third message is used to request the latest context of the terminal.

[0325] In some embodiments, the third message includes a second request for requesting the latest context of the terminal.

[0326] In some embodiments, the name of the third message is not limited, and it may be, for example, a terminal context update information request, a context change information request, a context request, etc.

[0327] In step S2107, the first device 1021 sends a fourth message to the third device 1023.

[0328] In some embodiments, the third device receives a fourth message. For example, the third device receives a fourth message sent by the first device.

[0329] In some embodiments, the fourth message is a response of the first device to the third message.

[0330] In some embodiments, the fourth message is used by the third device to determine the latest context of the terminal.

[0331] For example, the fourth message includes the latest context of the terminal. For example, the fourth message includes updates / modifications to the terminal context. For example, the fourth message indicates that the terminal context has not been updated or modified.

[0332] In some embodiments, steps S2106 and S2107 are optional. For example, steps S2106 and S2107 may be omitted.

[0333] In some embodiments, steps S2106 and S2107 can be executed periodically, at set times, or based on triggering conditions.

[0334] In some embodiments, the number of times steps S2106 and S2107 are executed is not limited. For example, steps S2106 and S2107 may be executed once or multiple times.

[0335] In some embodiments, the order of steps S2106 and S2107 with any of steps S2101–S2105 and S2108–S2112 is not limited. For example, steps S2107 and S2108 may be executed before or after step S2103. For example, steps S2107 and S2108 may be executed before or after step S2111. However, this is not a limitation.

[0336] In step S2108, the third device 1023 sends a first request to the second device 1022.

[0337] In some embodiments, the second device receives the first request.

[0338] In some embodiments, the first request is used to request the second device to create a terminal context.

[0339] In some embodiments, the name of the first request is not limited, and it may be, for example, a context creation instruction or a directive.

[0340] Optionally, the first request includes a fifth instruction, which instructs the second device to continue using at least one of the following:

[0341] The identifier assigned to the terminal by the first device;

[0342] The SRB configuration corresponding to the terminal configured in the first device;

[0343] The first device is configured with the corresponding DRB configuration for the terminal.

[0344] In some embodiments, the SRB or DRB configuration corresponding to the terminal configured in the first device may include security-related information, such as a security key.

[0345] It should be explained that the identifier assigned to the terminal by the first device refers to the identifier assigned to the terminal under the service of the first device. For example, the identifier of the terminal may be C-RNTI.

[0346] The SRB configuration corresponding to the terminal configured by the first device refers to the SRB configuration information of the terminal under the service of the first device. The DRB configuration corresponding to the terminal configured by the first device refers to the DRB configuration information of the terminal under the service of the first device.

[0347] In step S2109, the second device 1022 sends a response message to the third device 1023.

[0348] In some embodiments, the third device receives response information. This response information is the second device's response to the first request. The response information may indicate whether the terminal context establishment was successful or failed.

[0349] In some embodiments, the name of the second message is not limited, and it may be, for example, a terminal context establishment feedback message.

[0350] In some embodiments, step S2109 can be omitted. If the third device does not receive a response from the second device within a certain period of time, the terminal context creation can be assumed to have succeeded or failed.

[0351] If the second device successfully establishes the terminal context, proceed to step S2110.

[0352] In step S2110, the third device 1023 sends a second message to the first device 1021.

[0353] In some embodiments, the first device receives a second message. For example, the first device receives a second message sent by a third device.

[0354] In some embodiments, the second message is used to instruct the first device to send the first message. Optionally, the second message includes at least one of the following:

[0355] The third instruction is used to indicate the content included in the first message;

[0356] The fourth instruction is used to indicate the time when the first device sends the first message.

[0357] Step S2111: The first device 1021 broadcasts the first message.

[0358] In some embodiments, the second device broadcasts the first message according to the second message. Optionally, the terminal 101 receives the first message.

[0359] In some embodiments, the first message instructs the terminal to resynchronize from the currently accessed first cell to the second cell.

[0360] In some embodiments, the first message instructs the terminal to resynchronize the information required to the second cell from the currently accessed first cell.

[0361] The first cell is managed by the first device, and the second cell is managed by the second device. The configurations of the first cell and the second cell are the same.

[0362] In some embodiments, the first message may be a system message. For example, the first message is a system message of type SIB19.

[0363] For example, the first message indicates or includes relevant information about the first device and / or the second device. Assuming the first and second devices are satellites, the first message could include messages indicating satellite-related information.

[0364] In some embodiments, the first message includes at least one of the following:

[0365] Service time information for the first device;

[0366] Service information for the second device;

[0367] The first instruction indicates whether to rebuild the RLC;

[0368] The second instruction indicates whether to reset the MAC address.

[0369] In some embodiments, the contents indicated by the first indication and the second indication can also be indicated simultaneously by a single indication. For example, assuming that the first device and the second device are satellites, the first message includes an indication of the satellite mode, which may include transparent transmission mode, regenerative mode, or DU onboard mode, etc. If the satellite mode indication in the first message is used to indicate regenerative mode or DU onboard mode, then after the UE performs resynchronization (i.e., synchronizes to the second cell), it needs to rebuild the RLC and / or reset the MAC.

[0370] In some embodiments, the service time information of the first device may include the remaining duration of service provided by the first device to the area where the terminal is currently located. Based on the service time information of the first device, the terminal can determine when it should synchronize and access the cell provided by other access network devices.

[0371] In step S2112, terminal 101 resynchronizes from the currently accessed first cell to the second cell according to the first message.

[0372] In some embodiments, the terminal resynchronizes according to the first message and can synchronize access to the second cell provided by the second device. If the first message includes a first indication indicating that the RLC needs to be rebuilt, then the terminal needs to rebuild the RLC after synchronization. If the first message includes a second indication indicating that the MAC needs to be reset, then the terminal needs to reset the MAC after synchronization.

[0373] In some embodiments, the first indication may be a type of resynchronization that requires the terminal to re-establish RLC.

[0374] In some embodiments, the second instruction may be a type of resynchronization that requires the terminal to perform a MAC reset.

[0375] It should be noted that the number of terminals is one or more. More easily understood is that the number of the first cell, second cell, first DU, second DU, etc., is one or more.

[0376] It should be noted that when a terminal resynchronizes from the first cell it is currently connected to to the second cell, i.e., in order to resynchronize with the second device, random access can be triggered via the second device through the PDCCH command. It should be explained that random access can be used for handover or for ordinary uplink / downlink synchronization.

[0377] In the embodiment shown in Figure 2A, the first device sends a first message instructing the terminal to resynchronize from the first cell under the currently accessed first device to the second cell under the second device. Here, the first device and the second device are different devices moving relative to the ground. Since the configuration of the first cell is the same as that of the second cell, this method can reduce or avoid latency and signaling storms caused by the terminal switching from the first device to the second device, thus improving network service performance. Furthermore, because the configurations of the first and second cells are identical, the terminal may perceive no cell handover during the switch from the first cell of the first device to the second cell of the second device (i.e., seamless handover), improving the user experience on the terminal side.

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

[0379] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

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

[0381] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

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

[0383] In some embodiments, the terms “eNB”, “gNB”, “base station”, “NG-RAN node”, “6G RAN”, and “DU” can be used interchangeably.

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

[0385] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc., from one subject to another passes through other subjects, it can be interpreted as the message being forwarded from one subject to another via other subjects, or it can be interpreted as the message being sent from one subject to another without passing through other subjects. For example, in step S2101, the first device sends its service information to the third device without being forwarded by the second device.

[0386] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2112. For example, step S2104 may be implemented as a separate embodiment, step S2111 may be implemented as a separate embodiment, step S2112 may be implemented as a separate embodiment, and steps S2111 and S2112 may be implemented as separate embodiments, but are not limited thereto.

[0387] In some embodiments, the order of any two steps S2101 to S2112 can be interchanged or they can be performed simultaneously. For example, the order of steps S2101 and S2102 can be interchanged or they can be performed simultaneously.

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

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

[0390] In some embodiments, steps S2101 to S2111 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0391] In some embodiments, steps S2101 to S2110 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0392] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0393] 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 embodiment of the present disclosure relates to a communication method executed by a communication system 100, the method including:

[0394] In step S2201, the third device 1023 sends a sixth message to the second device 1022.

[0395] The optional implementation of step S2201 can be found in the optional implementation of step S2103 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0396] In some embodiments, the second device receives a sixth message. For example, the second device receives a sixth message sent by a third device.

[0397] In some embodiments, the sixth message is used to instruct the second device to create or activate the second cell.

[0398] In some embodiments, the sixth message is used to instruct the second device to create or activate a second DU, wherein the second DU includes a second cell.

[0399] In some embodiments, the name of the sixth message is not limited, and it may be, for example, a cell creation instruction, a cell activation instruction, a DU creation or activation instruction, etc.

[0400] In some embodiments, the sixth message may be an F1 interface message. However, it is not limited to this.

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

[0402] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first DU, wherein the first DU includes a first cell and the second DU includes a second cell;

[0403] The ninth instruction is used to instruct the second device to establish a second cell;

[0404] The tenth instruction is used to indicate the configuration of the second cell;

[0405] The eleventh instruction is used to instruct the activation of the second cell.

[0406] In some embodiments, the configuration of the second cell includes at least one of the following: the identifier of the second cell, the supported PLMN, the Tracking Area Identifier (TAI), and the cell resource configuration.

[0407] In some embodiments, the sixth message may instruct the creation or activation of one or more second cells. Accordingly, the sixth message may include / instruct information required to create or activate one or more second cells.

[0408] It should be explained that the second cell is managed by the second device. The second DU includes the second cell, and the establishment of the second DU by the second device includes the establishment of the second cell. The first cell is managed by the first device, and the first DU of the first device includes the first cell. The configuration of the second DU is the same as the configuration of the first DU, which means that the configuration of the second cell is the same as the configuration of the first cell.

[0409] It should be noted that the configuration of the second cell indicated by the tenth instruction may be the configuration of the first cell obtained by the third device from the first device.

[0410] In some embodiments, the tenth instruction indicates the configuration of the second cell by indicating the configuration of the second DU. The configuration of the second DU may be the configuration of the first DU obtained by the third device from the first device.

[0411] It should be noted that, based on the content indicated by the sixth message, the second device is able to know which configuration of the second cell or second DU to establish or activate.

[0412] In some embodiments, the service information of the first device is used by the third device to determine the time to send the sixth message to the second device.

[0413] In some embodiments, the service information of the second device is used by the third device to determine the time to send the sixth message to the second device.

[0414] In some embodiments, the time at which the third device sends the sixth message to the second device is determined based on at least one of the service information of the first device and the service information of the second device.

[0415] In some embodiments, the third device determines the time when the terminal switches from the first device to the second device based on the service information of the first device and the service information of the second device, and the third device sends a sixth message to the second device before that time.

[0416] For example, assuming the first device is the first satellite and the second device is the second satellite, then the third device can send a sixth message to the second satellite before the terminal switches from the first satellite to the second satellite.

[0417] In step S2202, the second device 1022 establishes or activates the second cell according to the sixth message.

[0418] The optional implementation of step S2202 can be found in the optional implementation of step S2104 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0419] Optionally, the second device establishes a second DU based on the sixth message.

[0420] Optionally, the second device establishes a second cell based on the sixth message.

[0421] Optionally, the second device activates the second cell based on the sixth message.

[0422] In some embodiments, the sixth message includes the configuration of the second DU. The second device can create a second DU based on the configuration of the second DU, and creating the second DU includes creating a second cell.

[0423] In some embodiments, the sixth message includes the configuration of the second cell. The second device can create the second cell based on the configuration of the second cell.

[0424] In some embodiments, a cell with the same configuration as the second cell is pre-configured on the second device, and the second device can activate the cell to obtain an activated second cell.

[0425] It should be explained that cell establishment or activation refers to setting a geographical area covered by a base station to an available state so that terminals can connect to that area and communicate.

[0426] In step S2203, the second device 1022 sends cell update information to the third device 1023.

[0427] The optional implementation of step S2203 can be found in the optional implementation of step S2105 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0428] In some embodiments, the third device receives cell update information sent by the second device.

[0429] In some embodiments, cell update information is used to respond to a sixth message sent by a third device.

[0430] In some embodiments, cell update information is used to indicate the cell most recently created or activated by the second device. For example, the cell update information includes the ID of the second cell that was created or activated.

[0431] In some embodiments, the name of the cell update information is not limited, and it may be, for example, DU update information, response information, list of active cells, etc.

[0432] In some embodiments, cell update information can be sent via F1 interface messages.

[0433] In some embodiments, the second device may send cell update information to the third device after establishing or activating the second cell according to the sixth message, in response to the sixth message sent by the third device.

[0434] In step S2204, the third device 1023 sends a third message to the first device 1021.

[0435] The optional implementation of step S2204 can be found in the optional implementation of step S2106 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0436] In some embodiments, the first device receives a third message. For example, the first device receives a third message sent by a third device.

[0437] In some embodiments, the third message is used to request the latest context of the terminal.

[0438] In some embodiments, the third message includes a second request for requesting the latest context of the terminal.

[0439] In some embodiments, the name of the third message is not limited, and it may be, for example, a terminal context update information request, a context change information request, a context request, etc.

[0440] In some embodiments, where the first message instructs the terminal not to rebuild the RLC and / or not to reset the MAC, or where the first message does not include the first or second instruction, the third message further includes a third request for requesting the status information of the terminal's radio bearer. Optionally, the third request includes at least one of the following:

[0441] The sixth indication is used to indicate that the radio bearer includes one or more of SRBs and DRBs;

[0442] The seventh indication is used to indicate one or more of the status information, including RLC status information and MAC status information.

[0443] For example, if the first instruction in the first message explicitly indicates that the terminal does not rebuild the RLC, the third request includes a seventh instruction, which may instruct the first device to send the RLC status information of the terminal's radio bearer.

[0444] For example, if the first instruction in the first message explicitly indicates that the terminal does not reset the MAC, the third request includes a seventh instruction, which may instruct the first device to send the MAC status information of the terminal's radio bearer.

[0445] In some embodiments, the third request may be included in a message other than the third message. For example, the third request is sent separately by the third device to the first device via an F1 interface message.

[0446] In step S2205, the first device 1021 sends a fourth message to the third device 1023.

[0447] The optional implementation of step S2205 can be found in the optional implementation of step S2107 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0448] In some embodiments, the third device receives a fourth message. For example, the third device receives a fourth message sent by the first device.

[0449] In some embodiments, the fourth message is a response of the first device to the third message.

[0450] In some embodiments, the fourth message is used by the third device to determine the latest context of the terminal.

[0451] For example, the fourth message includes the latest context of the terminal. For example, the fourth message includes updates / modifications to the terminal context. For example, the fourth message indicates that the terminal context has not been updated or modified.

[0452] In some embodiments, steps S2204 and S2205 are optional. For example, steps S2204 and S2205 may be omitted.

[0453] In some embodiments, steps S2204 and S2205 may be executed periodically, at set times, or based on triggering conditions.

[0454] In some embodiments, the number of times steps S2204 and S2205 are executed is not limited. For example, steps S2204 and S2205 may be executed once or multiple times.

[0455] In some embodiments, the order of steps S2204 and S2205 with any of the steps S2201–S2203 and S2206–S2213 is not limited. For example, steps S2204 and S2205 may be executed before or after step S2203. For example, steps S2204 and S2205 may be executed before or after step S2211. However, this is not a limitation.

[0456] In step S2206, the third device 1023 sends a first request to the second device 1022.

[0457] The optional implementation of step S2206 can be found in the optional implementation of step S2108 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0458] In some embodiments, the second device receives the first request.

[0459] In some embodiments, the first request is used to request the second device to create a terminal context.

[0460] In some embodiments, the name of the first request is not limited, and it may be, for example, a context creation instruction or a directive.

[0461] Optionally, the first request includes a fifth instruction, which instructs the second device to continue using at least one of the following:

[0462] The identifier assigned to the terminal by the first device;

[0463] The SRB configuration corresponding to the terminal configured in the first device;

[0464] The first device is configured with the corresponding DRB configuration for the terminal.

[0465] In some embodiments, the SRB or DRB configuration corresponding to the terminal configured in the first device may include security-related information, such as a security key.

[0466] It should be explained that the identifier assigned to the terminal by the first device refers to the identifier assigned to the terminal under the service of the first device. For example, the identifier of the terminal may be C-RNTI.

[0467] The SRB configuration corresponding to the terminal configured by the first device refers to the SRB configuration information of the terminal under the service of the first device. The DRB configuration corresponding to the terminal configured by the first device refers to the DRB configuration information of the terminal under the service of the first device.

[0468] In step S2207, the second device 1022 sends a response message to the third device 1023.

[0469] The optional implementation of step S2207 can be found in the optional implementation of step S2109 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0470] In some embodiments, the third device receives response information. This response information is the second device's response to the first request. The response information may indicate whether the terminal context establishment was successful or failed.

[0471] In some embodiments, the name of the second message is not limited, and it may be, for example, a terminal context establishment feedback message.

[0472] In some embodiments, step S2109 can be omitted. If the third device does not receive a response from the second device within a certain period of time, the terminal context creation can be assumed to have succeeded or failed.

[0473] If the second device successfully establishes the terminal context, proceed to step S2208.

[0474] In step S2208, the third device 1023 sends a second message to the first device 1021.

[0475] The optional implementation of step S2208 can be found in the optional implementation of step S2110 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0476] In some embodiments, the first device receives a second message. For example, the first device receives a second message sent by a third device.

[0477] In some embodiments, the second message is used to instruct the first device to send the first message. Optionally, the second message includes at least one of the following:

[0478] The third instruction is used to indicate the content included in the first message;

[0479] The fourth instruction is used to indicate the time when the first device sends the first message.

[0480] In step S2209, the first device 1021 broadcasts the first message.

[0481] The optional implementation of step S2209 can be found in the optional implementation of step S2111 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0482] In some embodiments, the second device broadcasts the first message according to the second message. Optionally, the terminal 101 receives the first message.

[0483] In some embodiments, the first message instructs the terminal to resynchronize from the currently accessed first cell to the second cell.

[0484] In some embodiments, the first message instructs the terminal to resynchronize the information required to the second cell from the currently accessed first cell.

[0485] The first cell is managed by the first device, and the second cell is managed by the second device. The configurations of the first cell and the second cell are the same.

[0486] In some embodiments, the first message may be a system message. For example, the first message is a system message of type SIB19.

[0487] For example, the first message indicates or includes relevant information about the first device and / or the second device. Assuming the first and second devices are satellites, the first message could include messages indicating satellite-related information.

[0488] In some embodiments, the first message includes at least one of the following:

[0489] Service time information for the first device;

[0490] Service information for the second device;

[0491] The first instruction indicates whether to rebuild the RLC;

[0492] The second instruction indicates whether to reset the MAC address.

[0493] In some embodiments, the content indicated by the first instruction and the second instruction can also be indicated simultaneously by a single instruction.

[0494] In some embodiments, the service time information of the first device may include the remaining duration of service provided by the first device to the area where the terminal is currently located. Based on the service time information of the first device, the terminal can determine when it should synchronize and access the cell provided by other access network devices.

[0495] In step S2210, the first device 1021 sends a fifth message to the third device 1023.

[0496] In some embodiments, the third device receives the fifth message. For example, the third device receives the fifth message sent by the first device.

[0497] The fifth message is a response to the third request. The name of the fifth message is not limited; it can be, for example, a response message or a status message.

[0498] In some embodiments, the first device sends a fifth message to the third device in response to a third request. Optionally, the fifth message is used by the third device to determine the status information of the radio bearer of the terminal 101. Optionally, the status information of the terminal's radio bearer includes at least one of the following:

[0499] Terminal identifier;

[0500] SRB logo,

[0501] DRB identification;

[0502] RLC status information;

[0503] MAC status information.

[0504] For example, if a third request requires the first device to send the RLC status information of the terminal's SRB, the first device may send a fifth message to the third device, the fifth message including the RLC status information of the terminal's SRB.

[0505] For example, if a third request requires the first device to send the RLC status information of the terminal's DRB, the first device may send a fifth message to the third device, the fifth message including the RLC status information of the terminal's DRB.

[0506] For example, if a third request requires the first device to send the MAC status information of the terminal's SRB, the first device may send a fifth message to the third device, the fifth message including the MAC status information of the terminal's SRB.

[0507] For example, if a third request requires the first device to send the MAC status information of the terminal's DRB, the first device may send a fifth message to the third device, the fifth message including the MAC status information of the terminal's DRB.

[0508] In some embodiments, RLC status information includes at least one of the following:

[0509] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0510] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0511] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0512] The remaining time of the timeout timer is used to trigger a retransmission request.

[0513] For example, RLC status information includes the expected sequence number, first receive buffer information, and retransmission request list.

[0514] For example, RLC status information includes the expected sequence number, first receive buffer information, retransmission request list, and remaining timeout timer.

[0515] In some embodiments, the MAC status information includes at least one of the following:

[0516] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0517] Lead time (TA);

[0518] Hybrid Automatic Repeat Request (HARQ) status.

[0519] For example, MAC status information includes TA and HARQ status.

[0520] For example, MAC status information includes data segments that the MAC layer has received but have not yet been processed by the upper-layer protocol, as well as TA and HARQ statuses.

[0521] In step S2211, the third device 1023 sends the status information of the radio bearer of the terminal 101 to the second device according to the fifth message.

[0522] In some embodiments, the second device receives status information of the terminal's radio bearer. For example, the second device receives status information of the terminal's radio bearer sent by a third device.

[0523] In some embodiments, the second device receives at least one of the following from the terminal 101: RLC status information of the SRB, RLC status information of the DRB, MAC status information of the SRB, and MAC status information of the DRB, sent by the third device.

[0524] In step S2212, terminal 101 resynchronizes from the currently accessed first cell to the second cell according to the first message.

[0525] The optional implementation of step S2212 can be found in the optional implementation of step S2112 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0526] In some embodiments, the terminal resynchronizes according to the first message and can synchronize access to the second cell provided by the second device. If the first message includes a first indication indicating that RLC reconstruction is not required, then the terminal does not need to reconstruct the RLC after synchronization. If the first message includes a second indication indicating that MAC resetting is not required, then the terminal does not need to reset the MAC after synchronization.

[0527] In some embodiments, the first indication may be a type of resynchronization that does not require the terminal to re-establish RLC.

[0528] In some embodiments, the second indication may be a type of resynchronization that does not require the terminal to perform a MAC reset.

[0529] It should be noted that the number of terminals is one or more. More easily understood is that the number of first cell, second cell, first DU, second DU, etc., is one or more.

[0530] In the embodiment shown in Figure 2B, the first device sends a first message instructing the terminal to resynchronize from the first cell under the currently accessed first device to the second cell under the second device. The first device and the second device are different devices moving relative to the ground. Since the configuration of the first cell is the same as that of the second cell, this method can reduce or avoid latency and signaling storms caused by the terminal switching from the first device to the second device, thus improving network service performance. Furthermore, because the configurations of the first and second cells are identical, the terminal may perceive no cell handover (i.e., seamless handover) during the process of switching from the first cell of the first device to the second cell of the second device, improving the user experience on the terminal side.

[0531] In step S2213, the second device 1023 receives or processes at least one of the data and signaling sent by the terminal 101 based on the status information of the terminal 101.

[0532] In some embodiments, the second device receives or processes at least one of the data and signaling sent by the terminal based on the terminal's status information. Thus, after the terminal switches from the first device to the second device (synchronizing from the first cell to accessing the second cell), the terminal does not need to rebuild the RLC and / or reset the MAC. This can further reduce or avoid the latency and signaling storms caused by the terminal switching from the first device to the second device (synchronizing from the first cell to accessing the second cell).

[0533] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2213. For example, step S2202 may be implemented as an independent embodiment, step S2209 may be implemented as an independent embodiment, step S2210 may be implemented as an independent embodiment, step S2211 may be implemented as an independent embodiment, step S2212 may be implemented as an independent embodiment, step S2213 may be implemented as an independent embodiment, steps S2209 and S2212 may be implemented as independent embodiments, and steps S2210 and S2211 may be implemented as independent embodiments, but are not limited thereto.

[0534] In some embodiments, the order of any two steps S2201 to S2213 can be interchanged or they can be performed simultaneously. For example, the order of steps S2208 and S2210 can be interchanged or they can be performed simultaneously.

[0535] In some embodiments, steps S2201 and S2203 to S2213 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0536] In some embodiments, steps S2201 to S2208 and steps S2210 to S2213 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0538] In some embodiments, steps S2201 to S2210, S2212, and S2213 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0539] In some embodiments, steps S2201 to S2211 and step S2213 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0540] In some embodiments, steps S2201 to S2212 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0541] In some embodiments, steps S2201 to S2208, S2210, S2211, and S2213 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0543] In some embodiments, one or more of steps S2101 and S2102 in FIG2A may be included before or after any one or more of steps S2201 to S2213.

[0544] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0545] Figure 3 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3, the embodiment of the present disclosure relates to a communication method executed by a communication system 100, the method including:

[0546] In step S301, the third device 1023 sends a second message to the first device 1021.

[0547] Optionally, the second message instructs the first device to send the first message.

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

[0549] Service time information for the first device;

[0550] Service information for the second device;

[0551] The first instruction indicates whether to rebuild the RLC;

[0552] The second instruction indicates whether to reset the MAC address.

[0553] Optionally, the second message includes at least one of the following:

[0554] The third instruction is used to indicate the content included in the first message;

[0555] The fourth instruction is used to indicate the time when the first device sends the first message.

[0556] Optionally, before sending the second message to the first device, the method includes: sending a first request to the second device, the first request being used to request the second device to create a context for the terminal, wherein the first request includes a fifth indication, the fifth indication being used to instruct the second device to continue using at least one of the following:

[0557] The identifier assigned to the terminal by the first device;

[0558] The SRB configuration corresponding to the terminal configured in the first device;

[0559] The first device is configured with the corresponding DRB configuration for the terminal.

[0560] Optionally, before sending the first request to the second device, the method includes: sending a third message to the first device, the third message including a second request, the second request being used to request the latest context of the terminal; receiving a fourth message sent by the first device, and determining the latest context of the terminal based on the fourth message.

[0561] Optionally, the third message may also include a third request, which requests the status information of the terminal's radio bearer, and the third request includes at least one of the following:

[0562] The sixth indication is used to indicate that the radio bearer includes one or more of SRBs and DRBs;

[0563] The seventh indication is used to indicate one or more of the status information, including RLC status information and MAC status information.

[0564] Optionally, the method on the third device side further includes: receiving a fifth message sent by the first device; determining and sending the state information of the terminal's radio bearer to the second device based on the fifth message, wherein the state information of the terminal's radio bearer is used by the second device to receive or process at least one of the data and signaling sent by the terminal when the terminal accesses the second cell; wherein the state information of the terminal's radio bearer includes at least one of the following:

[0565] Terminal identifier;

[0566] SRB logo,

[0567] DRB identification;

[0568] RLC status information;

[0569] MAC status information.

[0570] Optionally, the RLC status information includes at least one of the following:

[0571] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0572] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0573] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0574] The remaining time of the timeout timer is used to trigger a retransmission request.

[0575] Optionally, the MAC status information includes at least one of the following:

[0576] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0577] Lead time (TA);

[0578] Hybrid Automatic Repeat Request (HARQ) status.

[0579] In step S302, the third device 1023 sends a sixth message to the second device 1022.

[0580] Optionally, the sixth message includes at least one of the following:

[0581] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0582] The ninth instruction is used to instruct the second device to establish a second cell;

[0583] The tenth instruction is used to indicate the configuration of the second cell;

[0584] The eleventh instruction is used to instruct the activation of the second cell.

[0585] Optionally, the sending time of the sixth message is determined based on the service information of the first device and the service information of the second device;

[0586] Service information includes at least one of the following:

[0587] Sports information;

[0588] Synchronize time information;

[0589] Service time information;

[0590] Service location information.

[0591] Step S303: The second device 1022 establishes or activates the second cell.

[0592] Optionally, the second device receives a sixth message sent by the third device and establishes or activates the second cell based on the sixth message.

[0593] Optionally, establishing or activating a second cell according to the sixth message includes: establishing a second DU; or, establishing the second cell; or, activating the second cell.

[0594] Optionally, the method on the second device side further includes: receiving a first request sent by a third device, creating a terminal context according to the first request, and continuing to use at least one of the following according to a fifth instruction in the first request:

[0595] The identifier assigned to the terminal by the first device;

[0596] The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device;

[0597] The first device is configured with the corresponding Data Radio Bearer (DRB) configuration for the terminal.

[0598] Optionally, the method on the second device side further includes: receiving the status information of the terminal's radio bearer sent by the third device; and, if the terminal accesses the second cell, receiving or processing at least one of the data and signaling sent by the terminal based on the status information of the terminal's radio bearer; wherein the status information of the terminal's radio bearer includes at least one of the following:

[0599] Terminal identifier;

[0600] SRB logo,

[0601] DRB identification;

[0602] RLC status information;

[0603] MAC status information.

[0604] Optionally, the RLC status information includes at least one of the following:

[0605] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0606] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0607] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0608] The remaining time of the timeout timer is used to trigger a retransmission request.

[0609] Optionally, the MAC status information includes at least one of the following:

[0610] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0611] Lead time (TA);

[0612] Hybrid Automatic Repeat Request (HARQ) status.

[0613] Optionally, the method on the second device side further includes: sending the service information of the second device to the third device.

[0614] Step S304, the first device 1021 sends the first message.

[0615] Optionally, the first message instructs the terminal to resynchronize from the currently accessed first cell to the second cell.

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

[0617] Service time information for the first device;

[0618] Service information for the second device;

[0619] The first instruction indicates whether to rebuild the RLC;

[0620] The second instruction indicates whether to reset the MAC address.

[0621] Optionally, before sending the first message, the method includes: receiving a second message sent by a third device, the second message instructing the first device to send the first message; wherein the second message includes at least one of the following:

[0622] The third instruction is used to indicate the content included in the first message;

[0623] The fourth indication is used to indicate the time when the first device sends the first message.

[0624] Optionally, the second message is sent by the third device to the first device after sending the first request to the second device. The first request is used to request the second device to create the context of the terminal, wherein the first request includes a fifth indication, which instructs the second device to continue using at least one of the following:

[0625] The identifier assigned to the terminal by the first device;

[0626] The SRB configuration corresponding to the terminal configured in the first device;

[0627] The DRB configuration corresponding to the terminal configured in the first device.

[0628] Optionally, the method performed by the first device further includes: receiving a third message sent by a third device, the third message including a second request, the second request being used to request the latest context of the terminal; and sending a fourth message to the third device, the fourth message being used by the third device to determine the latest context of the terminal.

[0629] Optionally, the third message may also include a third request, which requests the status information of the terminal's radio bearer, and the third request includes at least one of the following:

[0630] The sixth indication is used to indicate that the radio bearer includes one or more of SRBs and DRBs;

[0631] The seventh indication is used to indicate one or more of the status information, including RLC status information and MAC status information.

[0632] Optionally, the method executed by the first device further includes: sending a fifth message to a third device, the fifth message being used by the third device to determine and send the status information of the terminal's radio bearer to the second device, the status information of the terminal's radio bearer being used by the second device to receive or process at least one of the data and signaling sent by the terminal when the terminal accesses the second cell; wherein, the status information of the terminal's radio bearer includes at least one of the following:

[0633] Terminal identifier;

[0634] SRB logo,

[0635] DRB identification;

[0636] RLC status information;

[0637] MAC status information.

[0638] Optionally, the RLC status information includes at least one of the following:

[0639] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0640] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0641] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0642] The remaining time of the timeout timer is used to trigger a retransmission request.

[0643] Optionally, the MAC status information includes at least one of the following:

[0644] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0645] Lead time (TA);

[0646] Hybrid Automatic Repeat Request (HARQ) status.

[0647] Optionally, the method performed by the first device further includes: sending service information of the first device to the third device, wherein the service information of the first device is used by the third device to determine the time to send a sixth message to the second device, and the sixth message includes at least one of the following:

[0648] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0649] The ninth instruction is used to instruct the second device to establish a second cell;

[0650] The tenth instruction is used to indicate the configuration of the second cell;

[0651] The eleventh instruction is used to instruct the activation of the second cell.

[0652] Optionally, the service information includes at least one of the following:

[0653] Mobile information;

[0654] Synchronize time information;

[0655] Service time information;

[0656] Service location information.

[0657] In step S305, terminal 101 resynchronizes from the currently accessed first cell to the second cell according to the first message.

[0658] Optionally, the first cell is managed by the first device, and the second cell is managed by the second device.

[0659] Optionally, the configuration of the first cell is the same as that of the second cell.

[0660] Optionally, the first and second devices move relative to the ground, while the third device remains stationary relative to the ground.

[0661] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0662] In some embodiments, where the first device is DU1, the second device is DU2, DU1 and DU2 are deployed on different satellites, and the third device is CU, CU is deployed on the ground, the interaction process of the communication method of this disclosure includes at least one of the following steps:

[0663] Step 1, the establishment or activation of the logical DU (second DU) or cell (second cell), can ensure that the UE considers the cell unchanged after the satellite is switched.

[0664] Optionally, the CU instructs DU2 to establish or activate a cell on DU2 (DU1 and DU2 have cells with the same configuration) based on the cell configuration information on DU1.

[0665] Optionally, the CU receives information from satellites DU1 and DU2.

[0666] Optionally, the CU sends first information to DU2 based on satellite information. The first information is used to indicate the establishment of DU2, or to indicate that DU2 establishes or activates a second cell.

[0667] Optionally, the cell configurations in DU2 and DU1 are identical. DU2 can be a newly established logical DU, or the cells on DU2 can be newly established cells.

[0668] Step 2: Transmission and establishment of the UE context.

[0669] Optionally, the CU sends the UE context to DU2 and ensures that the UE's configuration remains unchanged on DU2. For example, the serving cell identifier and the corresponding Cell Radio Network Temporary Identify (C-RNTI) need to be consistent with the UE's configuration on DU1.

[0670] Step 3: Triggering and executing resynchronization.

[0671] Optionally, CU instructs DU1 to broadcast system information for resynchronization.

[0672] Step 4: After the terminal synchronizes with the new satellite, the protocol status is processed.

[0673] Optionally, if the system information indicates that the UE needs to reset the MAC and rebuild the RLC after synchronization, then the UE resets the MAC and rebuilds the RLC.

[0674] Optionally, if the system information does not indicate that the UE needs to reset the MAC and rebuild the RLC after synchronization, the UE will not reset the MAC and rebuild the RLC.

[0675] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0676] Figure 4A is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4A, the present disclosure relates to a communication method, which includes at least one of the following steps:

[0677] In step S4101a, the third device determines the information of the first satellite.

[0678] Alternatively, the third device may determine the information of the first satellite through pre-configuration (e.g., Operations and Maintenance (OAM)).

[0679] Optionally, a third device receives information from the first satellite from the first device. The first device is deployed on the first satellite.

[0680] Optionally, the first device (DU1) sends a first message (e.g., an F1 interface setup request message) to the third device (CU), wherein the first message includes information about the first satellite.

[0681] In some embodiments, the first device is a DU, the third device is a CU, and the first message may be an F1AP message, such as a DU configuration update message and / or an F1 establishment request message.

[0682] In some embodiments, the information of the first satellite includes at least one of the following:

[0683] Satellite ephemeris information;

[0684] Synchronize time information;

[0685] Service time information;

[0686] Service location information.

[0687] In step S4101b, the third device determines the information of the second satellite.

[0688] Alternatively, the third device may determine the information of the second satellite through pre-configuration (e.g., OAM).

[0689] Optionally, the third device receives information from the second satellite from the second device. The second device is deployed on the second satellite.

[0690] Optionally, the second device (DU1) sends a first message (e.g., an F1 interface setup request message) to the third device (CU), wherein the first message includes information about the second satellite.

[0691] Optionally, the second device is DU, the third device is CU, and the first message can be an F1AP message, such as a DU configuration update message and / or an F1 establishment request message.

[0692] Optionally, the information from the second satellite includes at least one of the following:

[0693] Satellite ephemeris information;

[0694] Synchronize time information;

[0695] Service time information;

[0696] Service location information.

[0697] In step S4102a, the third device instructs the second device to create or activate a cell.

[0698] For example, a third device sends a second message to a second device to instruct the creation or activation of a cell, wherein the second message includes first information. Optionally, the first information includes at least one of the following:

[0699] DU creation instruction, used to instruct the creation of a new DU;

[0700] Community creation instruction, used to instruct the creation of a new community;

[0701] Cell configuration information is used to indicate the cell configuration information corresponding to the new cell to be established, including but not limited to cell identifier, PLMN, air interface configuration (e.g., TDD, FDD configuration, bandwidth, frequency, etc.), and TAI. The cell configuration information is the same as the cell configuration in the first device. (The cell configuration information includes the configuration information of one or more cells).

[0702] Optionally, the cell activation indication information is used to indicate a cell that needs to be activated. In some embodiments, the cell that needs to be activated has been pre-configured on the second device, and the activation indication information is used to activate the configured cell.

[0703] Optionally, the third device determines when to send the second message based on the information from the first satellite and the second information. For example, the second message may be initiated before the satellite handover time is determined to activate or establish a new cell.

[0704] The second device performs at least one of the following operations based on the first information:

[0705] A new logical unit is established, and the configuration of the new logical unit is consistent with that of the logical unit serving the UE in the first device;

[0706] Establish one or more new cells, wherein the new cells are consistent with the cell configuration of the serving UE in the first device;

[0707] Activate one or more new cells, the new cells being consistent with the cell configuration of the serving UE in the first device.

[0708] In some embodiments, consistent logical unit configuration includes consistent cell configuration, which includes consistent cell identifier, PLMN, air interface configuration (e.g., TDD, FDD configuration, bandwidth, frequency, etc.), TAI, etc. That is, for the UE, the new cell is the same cell as the cell in the first device.

[0709] In step S4102b, after the second device completes cell activation or establishment, it sends a feedback message to the third device.

[0710] In step S4103, the third device obtains updated UE context information from the first device.

[0711] Step S4103 is optional.

[0712] In step S4104a, the third device sends a UE context establishment request to the second device. The UE context establishment request includes a UE identifier, which is an identifier assigned to the UE under the service of the first device, such as C-RNTI.

[0713] Optionally, the second device establishes a UE context according to the UE context establishment request, wherein the second device continues to use the UE's configuration information under the service of the first device, such as the configuration corresponding to C-RNTI, SRB, and DRB. SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer).

[0714] In some embodiments, the SRB or DRB configuration corresponding to the terminal configured in the first device may include security-related information, such as a security key.

[0715] In step S4104b, the second device sends a UE context establishment feedback message to the third device.

[0716] In step S4105, the third device instructs the first device to broadcast the first system information.

[0717] For example, a third device sends a second message to a first device to instruct the broadcast of first system information. Optionally, the second message includes at least one of the following:

[0718] The command to broadcast first system information is used to instruct the first device to broadcast first system information.

[0719] The information that the first system information needs to include, such as service time and information about the second satellite;

[0720] The first time is used to indicate the time when the first device broadcasts information from the first system.

[0721] Optionally, the second information is included in the F1AP message, such as the CU configuration update message.

[0722] In step S4106, the first device sends first system information based on the second information. The first system information is used to instruct the UE to resynchronize.

[0723] Optionally, the first system information includes at least one of the following:

[0724] Service time, such as the remaining service time of the first device;

[0725] Information from the second satellite;

[0726] The first indication is used to indicate that UE synchronization requires resetting the MAC and / or rebuilding the RLC;

[0727] In some embodiments, the first system information is SIB19.

[0728] In step S4107, the UE resynchronizes according to the first system information and can then access the cell provided by the second device. If the first system information includes a first indication, the UE needs to reset the MAC address and / or rebuild the RLC after synchronization.

[0729] Optionally, in some embodiments, the first indication may be a type of resynchronization that requires the UE to perform a MAC reset and / or RLC re-establishment.

[0730] In some embodiments, the first indication may be a satellite synchronization type, such as a resynchronizing satellite type that is a regenerable satellite.

[0731] In some embodiments, the first indication may include a MAC reset and / or an RLC reestablish indication.

[0732] In step S4108, the third device instructs the first device to release the UE context.

[0733] Optionally, the first device sends a UE context release complete message to the third device.

[0734] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0735] Figure 4B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 4B, the present disclosure relates to a communication method, which includes at least one of the following steps:

[0736] Step S4201: The third device sends a UE context modification message to the first device. The UE context modification message includes state request information, which is used to request the first device to transmit the corresponding RLC layer and / or MAC layer state on the UE's SRB and DRB.

[0737] The status request information includes at least one of the following:

[0738] Status request indication;

[0739] One or more of the SRB and DRB corresponding to the status request;

[0740] The protocol layer corresponding to the status request includes one or more of MAC and RLC;

[0741] The reporting time indicates when the status request was sent.

[0742] In some embodiments, the status request information may be a request for one UE or multiple UEs.

[0743] Before step S4201, there are one or more steps preceding step S4103 in Figure 4A.

[0744] Step S4202 is the same as steps S4104a and S4104b. It will not be described again here.

[0745] Step S4203 is the same as step S4105. It will not be described again here.

[0746] Step S4204 is the same as step S4106, except that step S4204 may not include the first indication. That is, the UE does not need to reset the MAC and / or rebuild the RLC after resynchronization.

[0747] In step S4205, the first device sends status information to the third device based on the status request information. The third device then sends the status information to the second device.

[0748] Optionally, the status information includes status information carried by one or more UEs, and each status information includes at least one of the following:

[0749] UE identifier;

[0750] Bearer identifier (e.g., SRB ID or DRB ID);

[0751] RLC layer status information;

[0752] MAC layer status information.

[0753] In some embodiments, RLC status information includes at least one of the following:

[0754] Expected Sequence Number: A sequence number used to indicate the next data segment that the RLC layer expects to receive;

[0755] Receive buffer information: Used to store data segments that have been received but have not yet been processed by the upper-layer protocol;

[0756] Retransmission request list: used to indicate the sequence numbers that require a retransmission;

[0757] Timeout timer remaining time: Used to trigger a retransmission request.

[0758] Optionally, RLC status information is included in the status report.

[0759] In some embodiments, MAC status information includes at least one of the following:

[0760] Receive buffer status;

[0761] TA (Time Lead Time);

[0762] HARQ status.

[0763] In some embodiments, status information can be transmitted via signaling or via the user plane.

[0764] In step S4206, the UE performs resynchronization according to step S4204 and accesses the second device. The second device receives and processes the UE's data and / or signaling based on the status information received in S4205.

[0765] In step S4107, the third device instructs the first device to release the UE context.

[0766] Optionally, the first device sends a UE context release complete message to the third device.

[0767] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0768] The embodiments in Figures 4A and 4B are solutions primarily based on the 4G network architecture, but they can also be applied to 5G, 6G, and future wireless networks. Therefore, terms such as "eNB," "gNB," "base station," "NG-RAN node," "6G RAN," and "DU" can be used interchangeably. Furthermore, in the embodiments of Figures 4A and 4B, the information numbering differs from that in the embodiments of Figures 2A to 3, but the function of the information indicates which piece of information in the embodiments of Figures 2A to 3 it is equivalent to.

[0769] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed 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, a first device, a second device, a third device, etc.) in any of the above methods.

[0770] 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 functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using 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 functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0771] 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. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is 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. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0772] Figure 5A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. Terminal 5100 is used to execute any of the above methods. In some embodiments, as shown in Figure 5A, terminal 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is used to receive a first message broadcast by a first device; the processing module 5102 is used to resynchronize from a currently accessed first cell to a second cell according to the first message, wherein the first cell is managed by a first device, the second cell is managed by a second device, the configuration of the first cell is the same as the configuration of the second cell, and the first device and the second device move relative to the ground.

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

[0774] Service time information of the first device;

[0775] Service information for the second device;

[0776] The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC);

[0777] The second instruction indicates whether to reset the Media Access Control (MAC).

[0778] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (e.g., steps S2101, S2102, S2103, S2105, S2106, S2107, S2108, S2109, S2110, S2111, S2112, S2201, S2203, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, but not limited thereto), which will not be elaborated here. Optionally, the above processing module is used to execute at least one of the other steps executed by the terminal 101 in any of the above methods (e.g., step S2104, step S2202, step S2213, but not limited thereto), which will not be elaborated here.

[0779] Figure 5B is a schematic diagram of a network device according to an embodiment of the present disclosure. The network device 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the network device may include at least one of a transceiver module 5201, a processing module 5202, etc.

[0780] In some embodiments, the network device is the first device.

[0781] Optionally, the transceiver module 5201 is used to send a first message, the first message instructing the terminal to resynchronize from the currently accessed first cell to the second cell, the first cell being managed by the first device, the second cell being managed by the second device, the configuration of the first cell being the same as the configuration of the second cell, and the first device and the second device moving relative to the ground.

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

[0783] Service time information of the first device;

[0784] Service information for the second device;

[0785] The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC);

[0786] The second instruction indicates whether to reset the Media Access Control (MAC).

[0787] Optionally, the transceiver module 5201 is configured to: receive a second message sent by a third device, the second message instructing the first device to send the first message, the third device being stationary relative to the ground; wherein the second message includes at least one of the following:

[0788] The third instruction is used to indicate the content included in the first message;

[0789] The fourth indication is used to indicate the time when the first device sends the first message.

[0790] Optionally, the second message is sent by the third device to the first device after sending a first request to the second device. The first request is used to request the second device to create a context for the terminal. The first request includes a fifth indication, which instructs the second device to continue using at least one of the following:

[0791] The identifier assigned to the terminal by the first device;

[0792] The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device;

[0793] The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

[0794] Optionally, the transceiver module 5201 is configured to: receive a third message sent by a third device, the third message including a second request, the second request being used to request the latest context of the terminal; and send a fourth message to the third device, the fourth message being used by the third device to determine the latest context of the terminal.

[0795] Optionally, the third message further includes a third request, the third request being used to request the status information of the terminal's radio bearer, the third request including at least one of the following:

[0796] The sixth indication is used to indicate that the radio bearer includes one or more of SRB and DRB;

[0797] The seventh indication is used to indicate that the status information includes one or more of RLC status information and MAC status information.

[0798] Optionally, the transceiver module 5201 is configured to: send a fifth message to the third device, wherein the fifth message is used by the third device to determine and send the status information of the radio bearer of the terminal to the second device, wherein the status information of the radio bearer of the terminal is used by the second device to receive or process at least one of the data and signaling sent by the terminal when the terminal accesses the second cell;

[0799] The status information of the wireless bearer of the terminal includes at least one of the following:

[0800] Terminal identifier;

[0801] SRB logo,

[0802] DRB identification;

[0803] RLC status information;

[0804] MAC status information.

[0805] Optionally, the RLC status information includes at least one of the following:

[0806] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0807] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0808] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0809] The remaining time of the timeout timer is used to trigger a retransmission request.

[0810] Optionally, the MAC status information includes at least one of the following:

[0811] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0812] Lead time (TA);

[0813] Hybrid Automatic Repeat Request (HARQ) status.

[0814] Optionally, the transceiver module 5201 is configured to: send service information of the first device to the third device, wherein the service information of the first device is used by the third device to determine the time to send a sixth message to the second device, the sixth message including at least one of the following:

[0815] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0816] The ninth instruction is used to instruct the second device to establish the second cell;

[0817] The tenth instruction is used to indicate the configuration of the second cell;

[0818] The eleventh instruction is used to instruct the activation of the second cell.

[0819] Optionally, the service information includes at least one of the following:

[0820] Mobile information;

[0821] Synchronize time information;

[0822] Service time information;

[0823] Service location information.

[0824] In some embodiments, the network device is a second device.

[0825] Optionally, the transceiver module 5201 is used to receive a sixth message sent by the third device; the processing module 5202 is used to establish or activate a second cell according to the sixth message, the configuration of the second cell is the same as the configuration of the first cell, the first cell is the cell currently accessed by the terminal and managed by the first device, the first device and the second device are moving relative to the ground, and the third device is stationary relative to the ground.

[0826] Optionally, the sixth message includes at least one of the following:

[0827] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0828] The ninth instruction is used to instruct the second device to establish the second cell;

[0829] The tenth instruction is used to indicate the configuration of the second cell;

[0830] The eleventh instruction is used to instruct the activation of the second cell.

[0831] Optionally, the processing module 5202 is used to: establish the second DU; or, establish the second cell; or, activate the second cell.

[0832] Optionally, the transceiver module 5201 is configured to receive a first request sent by the third device, create a context for the terminal based on the first request, and continue to use at least one of the following according to a fifth instruction in the first request:

[0833] The identifier assigned to the terminal by the first device;

[0834] The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device;

[0835] The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

[0836] Optionally, the transceiver module 5201 is configured to receive the status information of the radio bearer of the terminal sent by the third device; and, when the terminal accesses the second cell, to receive or process at least one of the data and signaling sent by the terminal according to the status information of the radio bearer of the terminal.

[0837] The status information of the wireless bearer of the terminal includes at least one of the following:

[0838] Terminal identifier;

[0839] SRB logo,

[0840] DRB identification;

[0841] RLC status information;

[0842] MAC status information.

[0843] Optionally, the RLC status information includes at least one of the following:

[0844] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0845] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0846] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0847] The remaining time of the timeout timer is used to trigger a retransmission request.

[0848] Optionally, the MAC status information includes at least one of the following:

[0849] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0850] Lead time (TA);

[0851] Hybrid Automatic Repeat Request (HARQ) status.

[0852] Optionally, the transceiver module 5201 is used to send the service information of the second device to the third device, and the service information of the second device is used by the third device to determine the time to send the sixth message to the second device.

[0853] In some embodiments, the network device is a third device.

[0854] Optionally, the transceiver module 5201 is used to send a second message to the first device. The second message instructs the first device to send a first message. The first message instructs the terminal to resynchronize from the currently accessed first cell to the second cell. The first cell is managed by the first device, and the second cell is managed by the second device. The configuration of the first cell is the same as the configuration of the second cell. The first device and the second device move relative to the ground, and the third device is stationary relative to the ground.

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

[0856] Service time information of the first device;

[0857] Service information for the second device;

[0858] The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC);

[0859] The second instruction indicates whether to reset the Media Access Control (MAC).

[0860] Optionally, the second message includes at least one of the following:

[0861] The third instruction is used to indicate the content included in the first message;

[0862] The fourth indication is used to indicate the time when the first device sends the first message.

[0863] Optionally, the transceiver module 5201 is configured to send a first request to the second device before sending the second message to the first device. The first request is configured to request the second device to create a context for the terminal. The first request includes a fifth indication, which instructs the second device to continue using at least one of the following:

[0864] The identifier assigned to the terminal by the first device;

[0865] The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device;

[0866] The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

[0867] Optionally, the transceiver module 5201 is configured to send a third message to the first device before sending the first request to the second device, the third message including a second request, the second request being used to request the latest context of the terminal; receive a fourth message sent by the first device, and determine the latest context of the terminal based on the fourth message.

[0868] Optionally, the third message further includes a third request, the third request being used to request the status information of the terminal's radio bearer, the third request including at least one of the following:

[0869] The sixth indication is used to indicate that the radio bearer includes one or more of SRB and DRB;

[0870] The seventh indication is used to indicate that the status information includes one or more of RLC status information and MAC status information.

[0871] Optionally, the transceiver module 5201 is configured to receive a fifth message sent by the first device; determine and send the status information of the radio bearer of the terminal to the second device according to the fifth message, wherein the status information of the radio bearer of the terminal is used by the second device to receive or process at least one of the data and signaling sent by the terminal when the terminal accesses the second cell;

[0872] The status information of the wireless bearer of the terminal includes at least one of the following:

[0873] Terminal identifier;

[0874] SRB logo,

[0875] DRB identification;

[0876] RLC status information;

[0877] MAC status information.

[0878] Optionally, the RLC status information includes at least one of the following:

[0879] Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive;

[0880] The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol.

[0881] A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested;

[0882] The remaining time of the timeout timer is used to trigger a retransmission request.

[0883] Optionally, the MAC status information includes at least one of the following:

[0884] The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol.

[0885] Lead time (TA);

[0886] Hybrid Automatic Repeat Request (HARQ) status.

[0887] Optionally, the transceiver module 5201 is configured to: send a sixth message to the second device, the sixth message including at least one of the following:

[0888] The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell;

[0889] The ninth instruction is used to instruct the second device to establish the second cell;

[0890] The tenth instruction is used to indicate the configuration of the second cell;

[0891] The eleventh instruction is used to instruct the activation of the second cell.

[0892] Optionally, the processing module 5202 is configured to determine the sending time of the sixth message based on the service information of the first device and the service information of the second device; the service information includes at least one of the following:

[0893] Sports information;

[0894] Synchronize time information;

[0895] Service time information;

[0896] Service location information.

[0897] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device 102 in any of the above methods (e.g., steps S2101, S2102, S2103, S2105, S2106, S2107, S2108, S2109, S2110, S2111, S2112, S2201, S2203, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, but not limited thereto), which will not be elaborated here. Optionally, the above processing module is used to execute at least one of the other steps (such as step S2104, step S2202, step S2213, but not limited thereto) executed by the network device 102 in any of the above methods, which will not be elaborated here.

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

[0899] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0900] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0901] Figure 6A is a schematic diagram of the structure of a communication device 6100 according to an embodiment of the present disclosure. The communication device 6100 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 6100 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.

[0902] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may 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. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0903] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2105, S2106, S2107, S2108, S2109, S2110, S2111, S2112, S2201, S2203, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2104, S2202, S2213, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0904] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.

[0905] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (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.

[0906] Figure 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. For cases where the communication device 6100 can be a chip or a chip system, the schematic diagram of the chip 6200 shown in Figure 6B can be referred to, but is not limited thereto.

[0907] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

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

[0909] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2105, S2106, S2107, S2108, S2109, S2110, S2111, S2112, S2201, S2203, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above method refers, for example, to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, chip 6200, memory 6203, or transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2104, S2202, S2213, but not limited thereto).

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

[0911] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0912] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0913] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, characterized in that, Performed by a first device, the method includes: Send a first message, which instructs the terminal to resynchronize from the currently accessed first cell to the second cell. The first cell is managed by the first device, and the second cell is managed by the second device. The configuration of the first cell is the same as that of the second cell. The first device and the second device move relative to the ground.

2. The method according to claim 1, characterized in that, The first message includes at least one of the following: Service time information of the first device; Service information for the second device; The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC); The second instruction indicates whether to reset the Media Access Control (MAC).

3. The method according to claim 1 or 2, characterized in that, Before sending the first message, the following is included: The first device receives a second message sent by a third device, the second message instructing the first device to send the first message, the third device being stationary relative to the ground; The second message includes at least one of the following: The third instruction is used to indicate the content included in the first message; The fourth indication is used to indicate the time when the first device sends the first message.

4. The method according to claim 3, characterized in that, The second message is sent by the third device to the first device after sending a first request to the second device. The first request is for requesting the second device to create a context for the terminal. The first request includes a fifth indication, which instructs the second device to continue using at least one of the following: The identifier assigned to the terminal by the first device; The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device; The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive a third message sent by a third device, the third message including a second request, the second request being used to request the latest context of the terminal; A fourth message is sent to the third device, the fourth message being used by the third device to determine the latest context of the terminal.

6. The method according to claim 5, characterized in that, The third message further includes a third request, which is used to request the status information of the radio bearer of the terminal, and the third request includes at least one of the following: The sixth indication is used to indicate that the radio bearer includes one or more of SRB and DRB; The seventh indication is used to indicate that the status information includes one or more of RLC status information and MAC status information.

7. The method according to claim 6, characterized in that, The method further includes: A fifth message is sent to the third device, the fifth message being used by the third device to determine and send the status information of the radio bearer of the terminal to the second device, the status information of the radio bearer of the terminal being used by the second device to receive or process at least one of the data and signaling sent by the terminal when the terminal accesses the second cell; The status information of the wireless bearer of the terminal includes at least one of the following: Terminal identifier; SRB logo, DRB identification; RLC status information; MAC status information.

8. The method according to claim 7, characterized in that, The RLC status information includes at least one of the following: Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive; The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol. A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested; The remaining time of the timeout timer is used to trigger a retransmission request.

9. The method according to claim 7 or 8, characterized in that, The MAC status information includes at least one of the following: The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol. Lead time (TA); Hybrid Automatic Repeat Request (HARQ) status.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: The service information of the first device is sent to the third device, and the service information of the first device is used by the third device to determine the time to send a sixth message to the second device, the sixth message including at least one of the following: The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell; The ninth instruction is used to instruct the second device to establish the second cell; The tenth instruction is used to indicate the configuration of the second cell; The eleventh instruction is used to instruct the activation of the second cell.

11. The method according to claim 2 or 10, characterized in that, Service information includes at least one of the following: Mobile information; Synchronize time information; Service time information; Service location information.

12. A communication method, characterized in that, Performed by a second device, the method includes: The terminal receives a sixth message from a third device and establishes or activates a second cell based on the sixth message. The configuration of the second cell is the same as that of the first cell. The first cell is the cell currently accessed by the terminal and managed by the first device. The first device and the second device are moving relative to the ground, while the third device is stationary relative to the ground.

13. The method according to claim 12, characterized in that, The sixth message includes at least one of the following: The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell; The ninth instruction is used to instruct the second device to establish the second cell; The tenth instruction is used to indicate the configuration of the second cell; The eleventh instruction is used to instruct the activation of the second cell.

14. The method according to claim 13, characterized in that, The step of establishing or activating the second cell according to the sixth message includes: Establish the second DU; or, Establish a second cell; or, Activate the second cell.

15. The method according to any one of claims 12-14, characterized in that, The method further includes: Receive a first request sent by the third device, create a context for the terminal based on the first request, and continue to use at least one of the following according to the fifth instruction in the first request: The identifier assigned to the terminal by the first device; The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device; The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

16. The method according to any one of claims 12-15, characterized in that, The method further includes: Receive the wireless bearer status information of the terminal sent by the third device; When the terminal accesses the second cell, it receives or processes at least one of the data and signaling sent by the terminal according to the status information of the terminal's radio bearer; The status information of the wireless bearer of the terminal includes at least one of the following: Terminal identifier; SRB logo, DRB identification; RLC status information; MAC status information.

17. The method according to claim 16, characterized in that, The RLC status information includes at least one of the following: Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive; The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol. A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested; The remaining time of the timeout timer is used to trigger a retransmission request.

18. The method according to claim 16 or 17, characterized in that, The MAC status information includes at least one of the following: The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol. Lead time (TA); Hybrid Automatic Repeat Request (HARQ) status.

19. The method according to any one of claims 12-18, characterized in that, The method further includes: The third device sends the service information of the second device to the third device, and the service information of the second device is used by the third device to determine the time to send the sixth message to the second device.

20. A communication method, characterized in that, Performed by a third device, the method includes: A second message is sent to the first device, the second message instructing the first device to send a first message, the first message instructing the terminal to resynchronize from the currently accessed first cell to the second cell, the first cell being managed by the first device, the second cell being managed by the second device, the configuration of the first cell being the same as the configuration of the second cell, the first device and the second device moving relative to the ground, and the third device being stationary relative to the ground.

21. The method according to claim 20, characterized in that, The first message includes at least one of the following: Service time information of the first device; Service information for the second device; The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC); The second instruction indicates whether to reset the Media Access Control (MAC).

22. The method according to claim 20 or 21, characterized in that, The second message includes at least one of the following: The third instruction is used to indicate the content included in the first message; The fourth indication is used to indicate the time when the first device sends the first message.

23. The method according to any one of claims 20-22, characterized in that, Before sending the second message to the first device, the following is included: A first request is sent to the second device, the first request being for requesting the second device to create a context for the terminal, wherein the first request includes a fifth indication, the fifth indication being for instructing the second device to continue using at least one of the following: The identifier assigned to the terminal by the first device; The signaling radio bearer (SRB) configuration corresponding to the terminal configured in the first device; The first device is configured with the data radio bearer (DRB) configuration corresponding to the terminal.

24. The method according to claim 23, characterized in that, Before sending the first request to the second device, the process includes: Send a third message to the first device, the third message including a second request, the second request being used to request the latest context of the terminal; The terminal receives a fourth message sent by the first device and determines the latest context of the terminal based on the fourth message.

25. The method according to claim 24, characterized in that, The third message further includes a third request, which is used to request the status information of the radio bearer of the terminal, and the third request includes at least one of the following: The sixth indication is used to indicate that the radio bearer includes one or more of SRB and DRB; The seventh indication is used to indicate that the status information includes one or more of RLC status information and MAC status information.

26. The method according to claim 25, characterized in that, The method further includes: Receive the fifth message sent by the first device; The fifth message determines and sends the status information of the terminal's radio bearer to the second device. The status information of the terminal's radio bearer is used by the second device to receive or process at least one of the data and signaling sent by the terminal when the terminal accesses the second cell. The status information of the wireless bearer of the terminal includes at least one of the following: Terminal identifier; SRB logo, DRB identification; RLC status information; MAC status information.

27. The method according to claim 26, characterized in that, The RLC status information includes at least one of the following: Expected sequence number, used to indicate the sequence number of the next data segment that the RLC layer expects to receive; The first receive buffer information is used to indicate data segments that the RLC layer has received but have not yet been processed by the upper layer protocol. A retransmission request list, used to indicate the sequence numbers for which retransmissions need to be requested; The remaining time of the timeout timer is used to trigger a retransmission request.

28. The method according to claim 26 or 27, characterized in that, The MAC status information includes at least one of the following: The second receive buffer information is used to indicate data segments that the MAC layer has received but have not yet been processed by the upper layer protocol. Lead time (TA); Hybrid Automatic Repeat Request (HARQ) status.

29. The method according to any one of claims 20-28, characterized in that, The method further includes: Send a sixth message to the second device, the sixth message including at least one of the following: The eighth instruction is used to instruct the second device to establish a second DU with the same configuration as the first distributed unit DU, wherein the first DU includes the first cell and the second DU includes the second cell; The ninth instruction is used to instruct the second device to establish the second cell; The tenth instruction is used to indicate the configuration of the second cell; The eleventh instruction is used to instruct the activation of the second cell.

30. The method according to claim 29, characterized in that, The sending time of the sixth message is determined based on the service information of the first device and the service information of the second device; Service information includes at least one of the following: Sports information; Synchronize time information; Service time information; Service location information.

31. A communication method, characterized in that, The method, executed by a terminal, includes: Upon receiving a first message, the device resynchronizes from the currently accessed first cell to the second cell based on the first message. The first cell is managed by a first device, and the second cell is managed by a second device. The configuration of the first cell is the same as that of the second cell. The first device and the second device move relative to the ground.

32. The method according to claim 31, characterized in that, The first message includes at least one of the following: Service time information of the first device; Service information for the second device; The first instruction is used to indicate whether to rebuild the Radio Link Control (RLC); The second instruction indicates whether to reset the Media Access Control (MAC).

33. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-11, 12-19, 20-30, 31, and 32.

34. A communication system, characterized in that, The device includes a first device, a second device, a third device, and a terminal, wherein the first device is configured to implement the communication method of any one of claims 1-11, the second device is configured to implement the communication method of any one of claims 12-19, the third device is configured to implement the communication method of any one of claims 20-30, and the terminal is configured to implement the communication method of any one of claims 31 and 32.

35. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication method of any one of claims 1-11, 12-19, 20-30, 31, and 32 is performed.

36. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method according to any one of claims 1-11, 12-19, 20-30, 31, and 32.

Images