Communication method, communication device and communication system

Abstract

The invention provides a communication method, communication equipment and a communication system, and relates to the technical field of communication. The method comprises the following steps: a first node at an NTN side sends first information to a second node; wherein the first information is used for transmitting context information of the terminal. The context information of the terminal is stored in the node of the ground network, the terminal in the RRCINACTIVE state under the coverage of a non-GEO satellite is supported to be recovered to the RRCCONNECTED state, the process that the terminal initiates RNA is reduced, and the frequent terminal context acquisition process is avoided.

Description

A communication method, communication device and communication system Technical Field

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

[0002] Non-terrestrial networks (NTNs) are an important technology introduced by 5G, which provide wireless resources through satellites (or drones, etc.) instead of terrestrial base stations.

[0003] Summary of the Invention

[0004] This disclosure proposes a communication method, communication device, and communication system that, by storing the terminal's context information in a node of a terrestrial network, enables a terminal in a non-geostationary orbit (non-GEO) satellite coverage area to return to a connected radio resource control (RRC) state, thereby reducing the process of the terminal initiating network area registration (RNA) and avoiding frequent terminal context acquisition processes.

[0005] A first aspect of this disclosure provides a communication method executed by a first node on the NTN side, the method comprising: sending first information to a second node on the terrestrial network (TN) side; wherein the first information is used to transmit context information of a terminal.

[0006] A second aspect of this disclosure provides a communication method executed by a second node, the method comprising: receiving first information sent by a first node on an NTN side; wherein the first information is used to transmit context information of a terminal.

[0007] A third aspect of this disclosure provides a communication method executed by a third node on the NTN side, the method comprising: receiving a second request sent by a terminal; wherein the second request is used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0008] A fourth aspect of this disclosure provides a communication method executed by a terminal, the method comprising: sending a second request to a third node on the NTN side; wherein the second request is used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0009] A fifth aspect embodiment of this disclosure provides a communication method, comprising: a first node on an NTN side sending first information to a second node, the first information being used to transmit context information of a terminal; the second node sending second information to the first node, the second information being used to confirm that the second node has successfully received the context information of the terminal, the second information including a first identifier and node information of the second node, the first identifier being an identifier assigned to the terminal by the second node; the first node sending an RRC release message to the terminal according to the second information, the terminal entering an RRC_INACTIVE state according to the RRC release message; the terminal determining that it needs to recover to an RRC_CONNECTED state, sending a second request to a third node on the NTN side currently serving the terminal, the second request being used to request recovery from the RRC_INACTIVE state to the RRC_CONNECTED state, the second request including the first identifier and node information of the second node; the third node sending a first request to the second node according to the second request, the first request being used to request obtaining the context information of the terminal; the second node sending the context information of the terminal to the third node according to the first request, the context information being used by the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0010] A sixth aspect of this disclosure provides a communication device applied to a first node on an NTN side, comprising: a transceiver module configured to send first information to a second node; wherein the first information is used to transmit context information of a terminal.

[0011] A seventh aspect embodiment of this disclosure provides a communication apparatus applied to a second node, comprising: a transceiver module configured to receive first information sent by a first node on an NTN side; wherein the first information is used to transmit context information of a terminal.

[0012] An eighth aspect embodiment of this disclosure provides a communication apparatus applied to a third node on an NTN side, comprising: a transceiver module configured to receive a second request sent by a terminal; wherein the second request is used to request a return from an RRC_INACTIVE state to an RRC_CONNECTED state.

[0013] A ninth aspect embodiment of this disclosure provides a communication apparatus applied to a terminal, comprising: a transceiver module configured to send a second request to a third node on an NTN side; wherein the second request is used to request a return from an RRC_INACTIVE state to an RRC_CONNECTED state.

[0014] A tenth aspect embodiment of this disclosure provides a communication device, including: one or more processors; wherein the processors are configured to perform the method as described in the first aspect embodiment, or the method as described in the second aspect embodiment, or the method as described in the third aspect embodiment, or the method as described in the fourth aspect embodiment.

[0015] The eleventh aspect of this disclosure provides a communication system, including: a first node, a second node, a third node on the NTN side, and a terminal; the first node performs the method as described in the first aspect embodiment, the second node performs the method as described in the second aspect embodiment, the third node performs the method as described in the third aspect embodiment, and the terminal performs the method as described in the fourth aspect embodiment.

[0016] A twelfth aspect embodiment of this disclosure provides a computer storage medium storing computer-executable instructions; when executed by a processor, the computer-executable instructions are capable of implementing the methods described in the first aspect embodiment, the second aspect embodiment, the third aspect embodiment, or the fourth aspect embodiment.

[0017] The thirteenth aspect of this disclosure provides a computer program product, wherein the computer program product stores a computer program; after being executed by a processor, the computer program is able to implement the methods described in the first aspect embodiment, or the second aspect embodiment, or the third aspect embodiment, or the fourth aspect embodiment.

[0018] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description

[0019] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

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

[0021] Figure 2 is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

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

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

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

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

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

[0027] Figure 8 is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0028] Figure 9 is a block diagram of a communication device according to an embodiment of the present disclosure;

[0029] Figure 10 is a block diagram of a communication device according to an embodiment of the present disclosure;

[0030] Figure 11 is a block diagram of a communication device according to an embodiment of the present disclosure;

[0031] Figure 12 is a block diagram of a communication device according to an embodiment of the present disclosure;

[0032] Figure 13 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure;

[0033] Figure 14 is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0034] The embodiments of this disclosure are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure. It should be noted that, unless otherwise specified, the embodiments of this disclosure and the features in the embodiments can be combined with each other.

[0035] For ease of understanding, the terminology used in the embodiments of this disclosure will be introduced first.

[0036] 1. Non-terrestrial Network (NTN)

[0037] NTN is a key technology introduced in 5G, providing wireless resources through network devices such as satellites or drones instead of terrestrial base stations. Depending on how the satellite processes the signal, it can be divided into transparent transmission mode and regeneration mode. In transparent transmission mode, the NTN ground station transmits the signal from the network device (gNB) to the satellite. The satellite converts the signal to its own frequency band before transmitting it to the terminal (UE). Aside from frequency conversion and signal amplification, the satellite does not demodulate the gNB signal, acting as a repeater. In regeneration mode, after the NTN ground station transmits the gNB signal to the satellite, the satellite first 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.

[0038] Table 1 below shows the satellite altitude, orbit, and coverage area of ​​a typical NTN network:

[0039] Table 1

[0040] 2. Radio Resource Control (RRC) Inactive (RRC_INACTIVE) and Radio Resource Control Connected (RRC_CONNECTED) states

[0041] In mobile communication systems, especially 5G NR (New Radio) systems, the Radio Resource Control (RRC) layer is responsible for managing the connection and configuration of the radio interface. RRC defines several different states to describe the relationship between the terminal and the network. Two key states are the RRC_INACTIVE state and the RRC_CONNECTED state.

[0042] In the RRC_INACTIVE state, a "lightweight" connection exists between the terminal and the network. The terminal has completed the initial access procedure and may have performed authentication and security settings, but a complete connection has not yet been established for data transmission. In the RRC_CONNECTED state, a complete connection is established between the UE and the network, enabling data exchange.

[0043] When a terminal needs to send data or receives a paging message, it transitions from the RRC_INACTIVE state to the RRC_CONNECTED state. These states are designed to improve system efficiency and response speed while reducing unnecessary resource consumption.

[0044] This disclosure presents a communication method, communication device, and communication system.

[0045] In a first aspect, embodiments of this disclosure propose a communication method executed by a first node on the NTN side, the method comprising: sending first information to a second node; wherein the first information is used to transmit context information of the terminal.

[0046] The technical solution provided in this disclosure supports the recovery of terminals in the RRC_INACTIVE state to the RRC_CONNECTED state under non-GEO satellite coverage by storing the terminal's context information in the nodes of the terrestrial network, thereby reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0047] In conjunction with some embodiments of the first aspect, the context information is used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0048] In conjunction with some embodiments of the first aspect, the first information includes the context information.

[0049] In conjunction with some embodiments of the first aspect, the context information includes at least one of the following:

[0050] Core network information for the terminal being served;

[0051] The terminal's access layer (AS) security information;

[0052] The AS context of the terminal;

[0053] The terminal's session information.

[0054] In conjunction with some embodiments of the first aspect, the second node includes at least one of the following:

[0055] Access network equipment;

[0056] Core network equipment.

[0057] In conjunction with some embodiments of the first aspect, the first information is used to redirect the context of the terminal.

[0058] In conjunction with some embodiments of the first aspect, the first information is used to instruct the second node to save the context information of the terminal.

[0059] In conjunction with some embodiments of the first aspect, the method further includes: determining that it is necessary to instruct the terminal in the RRC_CONNECTED state to enter the RRC_INACTIVE state.

[0060] In conjunction with some embodiments of the first aspect, the method further includes: receiving second information sent by the second node; wherein the second information is used to confirm that the second node has successfully received the context information of the terminal.

[0061] In some embodiments of the first aspect, the second information is a response to the first information.

[0062] In conjunction with some embodiments of the first aspect, the second information is used to instruct the second node to agree to the request for terminal context redirection.

[0063] In conjunction with some embodiments of the first aspect, the second information is used to instruct the second node to agree to save the context information of the terminal.

[0064] In conjunction with some embodiments of the first aspect, the second information includes a first identifier, which is an identifier assigned by the second node to the terminal.

[0065] In conjunction with some embodiments of the first aspect, the first identifier is used to obtain the context information of the terminal.

[0066] In conjunction with some embodiments of the first aspect, the first identifier includes at least one of the following:

[0067] Inactive wireless network temporary identifier (I-RNTI);

[0068] System Temporary User Identity (S-TMSI).

[0069] In conjunction with some embodiments of the first aspect, the method further includes: sending a Radio Resource Control (RRC) release message to the terminal in the RRC_CONNECTED state;

[0070] The RRC release message includes at least one of the following:

[0071] The first identifier;

[0072] The node information of the second node.

[0073] In conjunction with some embodiments of the first aspect, sending the first information to the second node includes: sending the first information to the second node before sending the RRC release message to the terminal.

[0074] In conjunction with some embodiments of the first aspect, the method further includes: sending third information to the second node; wherein the third information is used to notify the second node that the terminal has entered the RRC_INACTIVE state.

[0075] Secondly, embodiments of this disclosure propose a communication method executed by a second node, the method comprising: receiving first information sent by a first node on the NTN side; wherein the first information is used to transmit context information of the terminal.

[0076] The technical solution provided in this disclosure supports the recovery of terminals in the RRC_INACTIVE state to the RRC_CONNECTED state under non-GEO satellite coverage by storing the terminal's context information in the nodes of the terrestrial network, thereby reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0077] In conjunction with some embodiments of the second aspect, the context information is used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0078] In conjunction with some embodiments of the second aspect, the first information includes the context information of the terminal.

[0079] In conjunction with some embodiments of the second aspect, the context information of the terminal includes at least one of the following:

[0080] Core network information for the terminal being served;

[0081] The terminal's AS security information;

[0082] The AS context of the terminal;

[0083] The terminal's session information.

[0084] In conjunction with some embodiments of the second aspect, the second node includes at least one of the following:

[0085] Access network equipment;

[0086] Core network equipment.

[0087] In conjunction with some embodiments of the second aspect, the first information is used to redirect the context of the terminal.

[0088] In conjunction with some embodiments of the second aspect, the first information is used to instruct the second node to save the context information of the terminal.

[0089] In conjunction with some embodiments of the second aspect, the method further includes: sending second information to the first node; wherein the second information is used to confirm that the second node has successfully received the context information of the terminal.

[0090] In some embodiments of the second aspect, the second information is a response to the first information.

[0091] In conjunction with some embodiments of the second aspect, the second information is used to instruct the second node to agree to the request for terminal context redirection.

[0092] In conjunction with some embodiments of the second aspect, the second information is used to instruct the second node to agree to save the context information of the terminal.

[0093] In conjunction with some embodiments of the second aspect, the second information includes a first identifier, which is an identifier assigned by the second node to the terminal.

[0094] In conjunction with some embodiments of the second aspect, the first identifier is used to obtain the context information of the terminal.

[0095] In conjunction with some embodiments of the second aspect, the first identifier includes at least one of the following:

[0096] I-RNTI;

[0097] S-TMSI.

[0098] In conjunction with some embodiments of the second aspect, the method further includes: receiving a first request sent by a third node on the NTN side; wherein the first request is used to request to obtain context information of the terminal.

[0099] In conjunction with some embodiments of the second aspect, the first request includes the first identifier.

[0100] In conjunction with some embodiments of the second aspect, the method further includes: sending the terminal's context information to the third node according to the first request.

[0101] In conjunction with some embodiments of the second aspect, the method further includes: initiating a path conversion process based on the context information of the terminal.

[0102] In conjunction with some embodiments of the second aspect, the method further includes: receiving third information sent by the first node;

[0103] The third information is used to notify the second node that the terminal has entered the RRC_INACTIVE state.

[0104] Thirdly, embodiments of this disclosure propose a communication method executed by a third node on the NTN side, the method comprising: receiving a second request sent by a terminal; wherein the second request is used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0105] The technical solution provided in this disclosure supports the recovery of terminals in the RRC_INACTIVE state to the RRC_CONNECTED state under non-GEO satellite coverage by storing the terminal's context information in the nodes of the terrestrial network, thereby reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0106] In conjunction with some embodiments of the third aspect, the second request includes at least one of the following:

[0107] The node information of the second node;

[0108] The first identifier is an identifier assigned to the terminal by the second node.

[0109] In conjunction with some embodiments of the third aspect, the first identifier is used to obtain the context information of the terminal.

[0110] In conjunction with some embodiments of the third aspect, the first identifier includes at least one of the following:

[0111] I-RNTI;

[0112] S-TMSI.

[0113] In conjunction with some embodiments of the third aspect, the method further includes: sending a first request to the second node based on the node information; wherein the first request is used to request the acquisition of the context information of the terminal.

[0114] In conjunction with some embodiments of the third aspect, the context information is used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0115] In conjunction with some embodiments of the third aspect, the first request includes the first identifier.

[0116] In conjunction with some embodiments of the third aspect, the method further includes: receiving context information of the terminal sent by the second node.

[0117] Fourthly, embodiments of this disclosure propose a communication method executed by a terminal, the method comprising: sending a second request to a third node on the NTN side; wherein the second request is used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0118] The technical solution provided in this disclosure supports the recovery of terminals in the RRC_INACTIVE state to the RRC_CONNECTED state under non-GEO satellite coverage by storing the terminal's context information in the nodes of the terrestrial network, thereby reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0119] In conjunction with some embodiments of the fourth aspect, the second request includes at least one of the following:

[0120] The node information of the second node;

[0121] The first identifier is an identifier assigned to the terminal by the second node.

[0122] In conjunction with some embodiments of the fourth aspect, the first identifier is used to obtain the context information of the terminal.

[0123] In conjunction with some embodiments of the fourth aspect, the first identifier includes at least one of the following:

[0124] I-RNTI;

[0125] S-TMSI.

[0126] In conjunction with some embodiments of the fourth aspect, before sending the second request to the third node on the NTN side, the method further includes: receiving a Radio Resource Control (RRC) release message sent by the first node on the NTN side; and switching from the RRC_CONNECTED state to the RRC_INACTIVE state according to the RRC release message;

[0127] The RRC release message includes at least one of the following:

[0128] The first identifier;

[0129] The node information of the second node.

[0130] Fifthly, this disclosure provides a communication method comprising: a first node on the NTN side sending first information to a second node, the first information being used to transmit context information of a terminal; the second node sending second information to the first node, the second information being used to confirm that the second node has successfully received the context information of the terminal, the second information including a first identifier and node information of the second node, the first identifier being an identifier assigned to the terminal by the second node; the first node sending an RRC release message to the terminal according to the second information, the terminal entering the RRC_INACTIVE state according to the RRC release message; the terminal determining that it needs to recover to the RRC_CONNECTED state, sending a second request to a third node on the NTN side currently serving the terminal, the second request being used to request recovery from the RRC_INACTIVE state to the RRC_CONNECTED state, the second request including the first identifier and node information of the second node; the third node sending a first request to the second node according to the second request, the first request being used to request obtaining the context information of the terminal; the second node sending the context information of the terminal to the third node according to the first request, the context information being used by the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0131] In a sixth aspect, embodiments of this disclosure provide a communication device applied to a first node on the NTN side, the device comprising: a transceiver module configured to send first information to a second node; wherein the first information is used to transmit context information of a terminal.

[0132] In a seventh aspect, embodiments of this disclosure provide a communication device applied to a second node, the device comprising: a transceiver module configured to receive first information sent by a first node on the NTN side; wherein the first information is used to transmit context information of a terminal.

[0133] Eighthly, embodiments of this disclosure provide a communication device applied to a third node on the side of a non-terrestrial network (NTN), the device comprising: a transceiver module configured to receive a second request sent by a terminal; wherein the second request is used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0134] In a ninth aspect, embodiments of this disclosure provide a communication device applied to a terminal, the device comprising: a transceiver module configured to send a second request to a third node on the NTN side; wherein the second request is used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0135] In a tenth aspect, this disclosure provides a communication device, which may be a first node, a second node, a third node, or a terminal, comprising: one or more processors; wherein the processor of the first node is configured to execute the method described in the first aspect embodiment, the processor of the second node is configured to execute the method described in the second aspect embodiment, the processor of the third node is configured to execute the method described in the third aspect embodiment, and the processor of the terminal is configured to execute the method described in the fourth aspect embodiment.

[0136] Eleventhly, this disclosure provides a communication system comprising: a first node, a second node, a third node, and a terminal; the first node performs the method described in the first aspect embodiment, the second node performs the method described in the second aspect embodiment, the first node performs the method described in the third aspect embodiment, and the terminal performs the method described in the fourth aspect embodiment.

[0137] In a twelfth aspect, embodiments of this disclosure provide a computer storage medium storing computer-executable instructions; when executed by a processor, the computer-executable instructions are able to implement the methods described in the first aspect embodiment, the second aspect embodiment, the third aspect embodiment, or the fourth aspect embodiment.

[0138] In a thirteenth aspect, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, can implement the methods described in the first aspect embodiment, the second aspect embodiment, the third aspect embodiment, or the fourth aspect embodiment.

[0139] In a fourteenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect embodiment, or the second aspect embodiment, or the third aspect embodiment, or the fourth aspect embodiment.

[0140] In a fifteenth 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 in the first, second, third, or fourth aspect embodiments.

[0141] It is understood that the aforementioned nodes, terminals, communication systems, storage media, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0142] This disclosure provides a communication method, communication device, and communication system. In some embodiments, the terms "communication method" can be substituted for "information processing method," "information sending method," and "information receiving method," and the terms "communication device" can be substituted for "information processing device," "information sending device," and "information receiving device," and the terms "information processing system," "communication system," "information sending system," and "information receiving system" can be substituted for each other.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] 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", "client", and "narrowband Internet of Things (NB-IoT) device" can be used interchangeably.

[0159] 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 that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., also referred to as 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, uplink link, downlink link, etc., can be replaced with sidelink link.

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

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

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

[0163] In some embodiments, the threshold mentioned in this embodiment may be a numerical value, a constant, or some fixed value.

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

[0165] In some embodiments, "eNB" and "gNB", "base station", "NG-RAN node", and "6G RAN" can be used interchangeably.

[0166] In some embodiments, "Mobility Management Entity (MME)" can be interchanged with "Core Network (CN)," "Access and Mobility Management Function (AMF)," "Session Management Function (SMF)," "6G CN," etc.

[0167] In some embodiments, "Service Gateway (SGW)" can be interchanged with "User Plane Function (UPF)".

[0168] In some embodiments, “bearer” can be interchanged with “Protocol Data Unit (PDU) Session”, “Evolved Radio Access Bearer (E-RAB)”, “Evolved Packet System (EPS) Bearer”, and “Quality of Service Flow”.

[0169] In some embodiments, "Next Generation Application Protocol (NGAP)" can be used interchangeably with "S1 Application Protocol (S1AP)".

[0170] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0171] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0172] The communication methods, communication equipment, and communication systems provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0173] Figure 1 shows a structural diagram of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the system architecture may include a first node 11, a second node 12, a third node 13, and a terminal 14.

[0174] In some embodiments, the first node 11, the second node 12, and the third node 13 may refer to key components in the communication network, or nodes in the communication network, which may be responsible for data transmission, exchange, routing, or signal processing, etc.

[0175] In some embodiments, the first node 11 may be a network device. In some examples, the first node 11 may specifically be a network device on the NTN side. For example, the first node 11 may be a communication node on a satellite or a communication node on an aircraft.

[0176] In some embodiments, the second node 12 may be a network device. In some examples, the second node 12 may specifically be a network device on the TN side, such as an access network device or a core network device of a terrestrial network. In some examples, the second node 12 may specifically be a communication node on the NTN side. For example, the second node 12 may be a communication node deployed on a geostationary orbit satellite, or it may be a communication node deployed in the same orbit as the first node.

[0177] In some embodiments, the third node 13 may be a network device. In some examples, the third node 13 may specifically be a network device on the NTN side, such as a communication node on a satellite or an aircraft. In some examples, the third node 13 is different from the first node 11.

[0178] In some examples, a network device can be an entity on the network side used to transmit or receive signals. For example, a network device can be a base station, a core network node, or a server. Specifically, a network device can be a communication satellite, an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of this disclosure do not limit the specific technology or device form used in the network device. The network device provided in the embodiments of this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure, the protocol layer of a network device, such as a base station, can be separated. Some 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, which is centrally controlled by the CU.

[0179] In some examples, terminal 14 may be referred to as a terminal device, user equipment, mobile station (MS), mobile terminal device (MT), NB-IoT terminal, etc. Terminal 14 can also be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality device, an augmented reality device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of this disclosure do not limit the specific technology or device form adopted by terminal 14.

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

[0181] The following embodiments of this disclosure can be applied to the communication system shown in FIG1, or some of the subjects, but are not limited thereto. The subjects shown in FIG1 are illustrative. The communication system may include all or some of the subjects in FIG1, or may include other subjects other than those in FIG1. ​​The number and form of each subject are arbitrary. The connection relationship between the subjects is illustrative. The subjects may not be connected to each other or may be connected in any way. The connection may be direct or indirect, wired or wireless.

[0182] The embodiments disclosed herein can be applied to satellite communications, 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 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).

[0183] In non-geostationary orbit (non-GEO) satellite systems, as satellites move, base stations on those satellites also move. For a terminal in the RRC_INACTIVE state, if it needs to return to the RRC_CONNECTED state, and the satellite currently serving the terminal may be far away from the satellite with the terminal's context, with no inter-satellite link or being unreachable between the two satellites, the base station on the satellite currently serving the terminal cannot trigger the terminal to return from the RRC_INACTIVE state to the RRC_CONNECTED state based on the terminal's context.

[0184] To address the aforementioned issues, the technical solution provided in this embodiment stores the terminal's context information at a node in the terrestrial network. This ensures that even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the node in the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to return to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0185] Furthermore, to illustrate the specific execution process of the above-described communication system, Figure 2 shows a schematic diagram of a communication method according to an embodiment of this disclosure. The method, applied to the above-described communication system, as shown in Figure 2, may include the following steps:

[0186] Step S201: The first node sends the first information to the second node.

[0187] In some embodiments, the second node receives the first information sent by the first node.

[0188] In some embodiments, the first information can be used to transmit context information of the terminal. For example, the first node uses the first information to indicate the context information of the terminal to the second node. In some examples, the first information may include the context information of the terminal.

[0189] In some embodiments, the first node may be a communication node on the NTN side. In some examples, the first node may be a communication node on a satellite, or a communication node on an aircraft, etc. For example, the first node may be a base station on a satellite.

[0190] In some embodiments, the second node may be a communication node on the TN side. In some examples, the second node may be an access network device and / or a core network device of the terrestrial network. For example, the second node may be a terrestrial base station or a core network node, such as an Access and Mobility Management Function (AMF). As another example, if the second node includes both access network devices and core network devices of the terrestrial network, the first node may send first information to both the access network device and the core network device respectively, for transmitting the terminal's context information to both devices. The terminal's context information may be stored in both the access network device and the core network device, and subsequently obtained from either the access network device or the core network device for restoring the RRC_CONNECTED state.

[0191] In some embodiments, the second node may be a communication node on the NTN side. In some examples, the second node may be a communication node deployed on a geostationary orbit satellite, or it may be a communication node deployed in the same orbit as the first node.

[0192] In some embodiments, the terminal's context information can be used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0193] In some embodiments, the context information of the terminal may include at least one of the following A to D:

[0194] A. Core network information of the service terminal, such as node information and / or address information of the core network.

[0195] B. Terminal AS security information, such as Key NG-RAN Star, Next Hop Chaining Count, etc.

[0196] C. Terminal AS context, such as RRC context.

[0197] D. Terminal session information, such as Protocol Data Unit (PDU) session-related information.

[0198] In some embodiments, the first information can be used to redirect the context of the terminal. For example, the anchor node of the terminal can be changed from a first node to a second node.

[0199] In some embodiments, the first information may be used to instruct the second node to save the context information of the terminal.

[0200] In some embodiments, the first node may determine that it needs to instruct a terminal in the RRC_CONNECTED state to enter the RRC_INACTIVE state. To do this, it may send an RRC release message to the terminal, causing the terminal to enter the RRC_INACTIVE state. In some examples, before sending the RRC release message to the terminal in the RRC_CONNECTED state, the first node sends first information to the second node.

[0201] For example, when the first node decides to allow a terminal in the RRC_CONNECTED state to enter the RRC_INACTIVE state, before sending an RRC release message to the terminal in the RRC_CONNECTED state, the first node sends first information to the second node, wherein the first information is used to transmit the terminal's context information.

[0202] In some embodiments, after the terminal enters the RRC_INACTIVE state but before receiving an RRC recovery request and / or downlink data from the terminal, the first node can send first information to the second node to ensure that the node containing the terminal's context remains within a certain coverage area. For example, if a satellite moves to a new coverage area, the terminal's context information can be relayed on the satellite.

[0203] Step S202: The second node sends the second information to the first node.

[0204] In some embodiments, the first node receives second information sent by the second node.

[0205] In some embodiments, the second information can be used to confirm that the second node has successfully received the terminal's context information.

[0206] In some embodiments, the second information may be a response to the first information.

[0207] In some embodiments, the second information may be used to instruct the second node to agree to the request for terminal context redirection.

[0208] In some embodiments, the second information may be used to instruct the second node to agree to save the terminal's context information.

[0209] In some embodiments, the second information may include a first identifier, which may be an identifier assigned to the terminal by the second node.

[0210] In some embodiments, the first identifier can be used to obtain the context information of a terminal. In some examples, the second node can store the context information of each terminal, and other nodes can obtain the context information of the terminal corresponding to the first identifier by sending a request with the first identifier to the second node. The second node can then query using the first identifier to find the context information of the corresponding terminal and return it to the requesting node.

[0211] In some embodiments, the first identifier may include at least one of the following:

[0212] Temporary Identifier for Inactive Wireless Network (I-RNTI); Temporary System Identifier for Users (S-TMSI).

[0213] In some embodiments, the second node initiates a path conversion process based on the terminal's context information. For example, the second node sends a path conversion request to the core network node and subsequently receives a confirmation message for the path conversion request.

[0214] Step S203: The first node sends an RRC release message to the terminal in the RRC_CONNECTED state.

[0215] In some embodiments, the terminal receives an RRC release message sent by the first node.

[0216] In some embodiments, the RRC release message can be used to cause a terminal in the RRC_CONNECTED state to change to the RRC_INACTIVE state.

[0217] In some embodiments, the RRC release message includes at least one of the following:

[0218] The first identifier; the node information of the second node, such as the identifier and / or IP address of the second node.

[0219] In some embodiments, the identifier of the second node may be a satellite identifier or an identifier used to indicate a satellite orbit.

[0220] In some embodiments, the first node may send third information to the second node, and correspondingly, the second node receives the third information sent by the first node. This third information can be used to notify the second node that the terminal has entered the RRC_INACTIVE state.

[0221] Step S204: The terminal enters the RRC_INACTIVE state according to the RRC release message.

[0222] Step S205: The terminal determines that it needs to return to the RRC_CONNECTED state and sends a second request to the third node currently serving the terminal.

[0223] For example, when a terminal needs to send uplink data or receives a paging message (such as when the network needs to send downlink data), it can be determined that it needs to return to the RRC_CONNECTED state.

[0224] In some embodiments, the third node receives a second request sent by the terminal.

[0225] In some embodiments, the third node may be a communication node on the NTN side. In some examples, the third node is different from the first node.

[0226] In some embodiments, the second request is used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0227] In some embodiments, the second request includes at least one of the following:

[0228] The node information of the second node; the first identifier.

[0229] Step S206: The third node sends the first request to the second node according to the second request.

[0230] In some embodiments, the second node receives a first request sent by the third node.

[0231] In some embodiments, the first request may be used to request the acquisition of context information of the terminal.

[0232] In some embodiments, the first request may include a first identifier.

[0233] In some embodiments, the third node determines the second node based on the node information of the second node in the second request, and sends the first request to the second node.

[0234] Step S207: The second node sends the terminal's context information to the third node according to the first request.

[0235] In some embodiments, the third node receives context information of the terminal sent by the second node.

[0236] In some embodiments, the second node obtains the context information of the terminal based on the first identifier in the first request and sends the context information of the terminal to the third node. In some examples, the context information is used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0237] The communication method involved in this embodiment may include at least one of steps S201 to S203. For example, step S201, step S202, step S203, step S204, step S205, step S206, and step S207 may be implemented as independent embodiments. Alternatively, some or all of the steps S201 to S207 may be combined as independent embodiments, and this embodiment does not limit this.

[0238] The technical solution provided in this embodiment stores the terminal's context information in the nodes of the terrestrial network. This way, even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the nodes of the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to restore to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0239] To illustrate the specific execution process of the first node, Figure 3 shows a flowchart of a communication method according to an embodiment of this disclosure. The execution of the first node may include the following steps.

[0240] Step S301: The first node sends the first information to the second node.

[0241] In some embodiments, the second node receives the first information sent by the first node.

[0242] In some embodiments, the first information is used to transmit the context information of the terminal.

[0243] In some embodiments, the terminal's context information is used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0244] In some embodiments, the first information includes the terminal's context information.

[0245] In some embodiments, the context information of the terminal includes at least one of the following A to D:

[0246] A. Core network information of the service terminal;

[0247] B. Terminal AS security information;

[0248] C. The AS context of the terminal;

[0249] D. Terminal session information.

[0250] In some embodiments, the second node includes at least one of the following:

[0251] Access network equipment; core network equipment.

[0252] In some embodiments, the first information may be used to redirect the context of the terminal.

[0253] In some embodiments, the first information can be used to instruct the second node to save the terminal's context information.

[0254] In some embodiments, the first node determines that it is necessary to instruct the terminal in the RRC_CONNECTED state to enter the RRC_INACTIVE state.

[0255] In some embodiments, before the first node sends an RRC release message to the terminal, the first node sends first information to the second node.

[0256] Step S302: The first node receives the second information sent by the second node;

[0257] The second information can be used by the first node to confirm that the second node has successfully received the terminal's context information.

[0258] In some embodiments, the second information may be a response to the first information.

[0259] In some embodiments, the second information is used to indicate that the second node agrees to the request for terminal context redirection.

[0260] In some embodiments, the second information is used to indicate that the second node agrees to save the terminal's context information.

[0261] In some embodiments, the second information may include a first identifier, which may be an identifier assigned to the terminal by the second node.

[0262] In some embodiments, the first identifier is used to obtain the context information of the terminal.

[0263] In some embodiments, the first identifier includes at least one of the following:

[0264] I-RNTI; S-TMSI.

[0265] Step S303: The first node sends an RRC release message to the terminal in the RRC_CONNECTED state.

[0266] In some embodiments, the terminal receives an RRC release message and enters the RRC_CONNECTED state according to the RRC release message.

[0267] In some embodiments, the RRC release message includes at least one of the following:

[0268] First identifier; second node information.

[0269] In some embodiments, the first node may send third information to the second node.

[0270] The third piece of information is used to notify the second node that the terminal has entered the RRC_INACTIVE state.

[0271] For a detailed description of the specific examples in this embodiment, please refer to the corresponding descriptions of the embodiments in Figures 1 and 2, which will not be repeated here.

[0272] The communication method involved in this embodiment may include at least one of steps S301 to S302. For example, step S301 may be implemented as a standalone embodiment, and step S302 may be implemented as a standalone embodiment. Alternatively, some or all of the steps in steps S301 to S302 may be combined as a standalone embodiment, and this embodiment does not limit this.

[0273] The technical solution provided in this embodiment stores the terminal's context information in the nodes of the terrestrial network. This way, even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the nodes of the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to restore to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0274] Figure 4 shows a flowchart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4, the method is applied to the execution of a second node and may include the following steps.

[0275] Step S401: The second node receives the first information sent by the first node.

[0276] In some embodiments, the first node sends first information to the second node.

[0277] In some embodiments, the first information is used to transmit the context information of the terminal.

[0278] In some embodiments, the terminal's context information can be used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0279] In some embodiments, the first information includes the terminal's context information.

[0280] In some embodiments, the context information of the terminal includes at least one of the following A to D:

[0281] A. Core network information of the service terminal;

[0282] B. Terminal AS security information;

[0283] C. The terminal's AS context;

[0284] D. Terminal session information.

[0285] In some embodiments, the second node includes at least one of the following:

[0286] Access network equipment; core network equipment.

[0287] In some embodiments, the first information is used to redirect the context of the terminal.

[0288] In some embodiments, the first information is used to instruct the second node to save the terminal's context information.

[0289] Step S402: The second node sends the second information to the first node.

[0290] In some embodiments, the second information is used to confirm that the second node has successfully received the context information of the terminal.

[0291] In some embodiments, the second information is a response to the first information.

[0292] In some embodiments, the second information is used to indicate that the second node agrees to the request for terminal context redirection.

[0293] In some embodiments, the second information is used to indicate that the second node agrees to save the terminal's context information.

[0294] In some embodiments, the second information includes a first identifier, which may be an identifier assigned to the terminal by the second node.

[0295] In some embodiments, the first identifier is used to obtain the context information of the terminal.

[0296] In some embodiments, the first identifier includes at least one of the following:

[0297] I-RNTI; S-TMSI.

[0298] In some embodiments, the second node receives a first request sent by the third node on the NTN side.

[0299] In some embodiments, the first request is used to request the acquisition of the terminal's context information.

[0300] In some embodiments, the first request includes a first identifier.

[0301] In some embodiments, the second node sends the terminal's context information to the third node in response to the first request.

[0302] In some embodiments, the second node initiates a path conversion process based on the context information of the terminal.

[0303] In some embodiments, the second node receives third information sent by the first node; wherein the third information is used to notify the second node that the terminal has entered the RRC_INACTIVE state.

[0304] For specific examples in this embodiment, please refer to the corresponding descriptions of the embodiments in Figures 1 to 3, which will not be repeated here.

[0305] The communication method involved in this embodiment may include at least one of steps S401 to S402. For example, step S401 may be implemented as a standalone embodiment, and step S402 may be implemented as a standalone embodiment. In addition, some or all of the steps in steps S401 to S402 may be combined as a standalone embodiment, and this embodiment does not limit this.

[0306] The technical solution provided in this embodiment stores the terminal's context information in the nodes of the terrestrial network. This way, even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the nodes of the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to restore to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0307] Figure 5 shows a flowchart of a communication method according to an embodiment of the present disclosure. As shown in Figure 5, the method is applied to a third node and may include the following steps.

[0308] Step S501: The third node receives the second request sent by the terminal.

[0309] In some embodiments, the third node may be a node of the current service terminal.

[0310] In some embodiments, the terminal sends a second request to the third node.

[0311] In some embodiments, the second request can be used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0312] In some embodiments, the second request includes at least one of the following:

[0313] The node information of the second node;

[0314] The first identifier is the identifier assigned to the terminal by the second node.

[0315] In some embodiments, the first identifier is used to obtain the context information of the terminal.

[0316] In some embodiments, the first identifier includes at least one of the following:

[0317] I-RNTI; S-TMSI.

[0318] Step S502: The third node sends the first request to the second node according to the second request.

[0319] In some embodiments, the second node receives a first request sent by the third node.

[0320] In some embodiments, the first request may be used to request the acquisition of context information of the terminal.

[0321] In some embodiments, the third node sends a first request to the second node based on the node information of the second node.

[0322] In some embodiments, the first request may include a first identifier.

[0323] Step S503: The third node receives the terminal context information sent by the second node.

[0324] In some embodiments, the terminal's context information is used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state. For example, a third node triggers the terminal's recovery from the RRC_INACTIVE state to the RRC_CONNECTED state based on the terminal's context information.

[0325] For specific examples in this embodiment, please refer to the corresponding descriptions of the embodiments in Figures 1 to 4, which will not be repeated here.

[0326] The communication method involved in this embodiment may include at least one of steps S501 to S502. For example, step S501 may be implemented as a standalone embodiment, step S502 may be implemented as a standalone embodiment, and step S504 may be implemented as a standalone embodiment. In addition, some or all of the steps in steps S501 to S504 may be combined as a standalone embodiment, and this embodiment does not limit this.

[0327] The technical solution provided in this embodiment stores the terminal's context information in the nodes of the terrestrial network. This way, even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the nodes of the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to restore to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0328] Figure 6 shows a flowchart of a communication method according to an embodiment of the present disclosure. As shown in Figure 6, the method is applied to a terminal and may include the following steps.

[0329] Step S601: The terminal sends a second request to the third node on the NTN side.

[0330] In some embodiments, the third node may be a node of the current service terminal.

[0331] In some embodiments, the second request can be used to request a return from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0332] In some embodiments, the second request includes at least one of the following:

[0333] The node information of the second node;

[0334] The first identifier may be an identifier assigned to the terminal by the second node.

[0335] In some embodiments, the first identifier is used to obtain the context information of the terminal.

[0336] In some embodiments, the first identifier includes at least one of the following:

[0337] I-RNTI; S-TMSI.

[0338] In some embodiments, before sending a second request to a third node on the NTN side, the terminal receives an RRC release message sent by a first node on the NTN side; and switches from the RRC_CONNECTED state to the RRC_INACTIVE state according to the RRC release message.

[0339] In some examples, the RRC release message includes at least one of the following:

[0340] First identifier; second node information.

[0341] For specific examples in this embodiment, please refer to the corresponding descriptions of the embodiments in Figures 1 to 5, which will not be repeated here.

[0342] The technical solution provided in this embodiment stores the terminal's context information in the nodes of the terrestrial network. This way, even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the nodes of the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to restore to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0343] Figure 7 shows a flowchart of a communication method according to an embodiment of the present disclosure. A terminal (UE) accesses a first node, which may be a base station on a satellite (Serving gNB (LEO1)). As shown in Figure 7, the method includes:

[0344] Step 701: When the first node decides to let the UE enter the RRC_INACTIVE state, the first node sends the first information to the second node.

[0345] In some embodiments, the first information is used to transmit the UE's context information.

[0346] In some embodiments, the second node may be a ground-based base station (Anchor gNB(onground)).

[0347] In some embodiments, the first information is used to redirect the UE's context, that is, to change the UE's anchor node from the first node to the second node.

[0348] In some embodiments, the first information is used to instruct the second node to save the UE's context information.

[0349] In some embodiments, the first information includes UE context information, which includes at least one of the following:

[0350] Core network information serving the UE, such as core network node information and / or address information;

[0351] UE's AS security information, such as Key NG-RAN Star and Next Hop Chaining Count;

[0352] The UE's AS context, for example, RRC context;

[0353] UE session-related information, such as PDU session-related information.

[0354] Step 702: The second node sends the second information to the first node.

[0355] In some embodiments, the second information can be used to confirm the context of the receiving UE.

[0356] In some embodiments, the second information may be a response to the first information.

[0357] In some embodiments, the second information is used to instruct the second node to agree to the UE context redirection request.

[0358] In some embodiments, the second information is used to indicate that the second node agrees to save the context of the UE.

[0359] In some embodiments, the second information includes a first identifier.

[0360] In some embodiments, the first identifier is an identifier assigned to the UE by the second node.

[0361] In some embodiments, the first identifier may be I-RNTI.

[0362] In some embodiments, the first identifier is used to obtain UE context information.

[0363] In steps 703 to 704, the second node initiates a path conversion process based on the UE context information.

[0364] For example, the second node sends a path conversion request to the core network (CN) and then receives a request response from the CN.

[0365] Step 705: The first node sends an RRC release message to the UE, wherein the RRC release message includes a first identifier received from the second node.

[0366] Step 706: The first node sends the third message to the second node.

[0367] In some embodiments, the third information is used to notify the second node UE to enter the RRC_INACTIVE state.

[0368] When the UE subsequently accesses a third node, such as a base station on a satellite (New Serving gNB(LEO2)), during the process of recovering from the RRC_INACTIVE state to the RRC_CONNECTED state, the terminal can send an RRC connection recovery request with the first identifier (such as I-RNTI) to the third node.

[0369] For specific examples in this embodiment, please refer to the corresponding descriptions of the embodiments in Figures 1 to 6, which will not be repeated here.

[0370] The communication method involved in this embodiment may include at least one of steps S701 to S706. For example, step S701, step S702, step S703, step S704, step S705, and step S706 may be implemented as independent embodiments. Alternatively, some or all of the steps in S701 to S706 may be combined as independent embodiments, and this embodiment does not limit this.

[0371] The technical solution provided in this embodiment stores the terminal's context information in the nodes of the terrestrial network. This way, even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the nodes of the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to restore to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

[0372] Figure 8 shows a flowchart of a communication method according to an embodiment of the present disclosure. A terminal (UE) accesses a first node, which may be a base station on a satellite (Serving gNB (LEO1)). As shown in Figure 8, the method includes:

[0373] Step 801: When the first node decides to let the UE enter the RRC_INACTIVE state, the first node sends the first information to the second node.

[0374] In some embodiments, the first information is used to transmit the UE's context information.

[0375] In some embodiments, the second node can be a ground-based core network node (CN (onground)). For example, AMF, etc.

[0376] In some embodiments, the first information is used to instruct the second node to save the UE context.

[0377] In some embodiments, the first information includes UE context information, which includes at least one of the following:

[0378] UE's AS security information, such as Key NG-RAN Star and Next Hop Chaining Count;

[0379] The UE's AS context, for example, RRC context.

[0380] Step 802: The second node sends the second information to the first node.

[0381] In some embodiments, the second information is used to confirm the context of the receiving UE.

[0382] In some embodiments, the second information may be a response to the first information.

[0383] In some embodiments, the second information is used to indicate that the second node agrees to save the context of the UE.

[0384] In some embodiments, the second information includes a first identifier.

[0385] In some embodiments, the first identifier is an identifier assigned to the UE by the second node.

[0386] In some embodiments, the first identifier may be S-TMSI

[0387] In some embodiments, the first identifier is used to obtain UE context information.

[0388] Step 803: The first node sends an RRC release message to the UE.

[0389] In some embodiments, the RRC release message includes a first identifier received from the second node and / or the node information of the second node.

[0390] In some embodiments, the node information of the second node may be the identifier and / or IP address information of the core network node.

[0391] Step 804: The first node sends the third information to the second node.

[0392] In some embodiments, the third information is used to notify the second node UE to enter the RRC_INACTIVE state.

[0393] Step 805: If it is necessary to send uplink data and / or receive downlink data (such as receiving a paging message sent by the network side), the UE sends a fourth message to the third node, namely the RRC resumerequest message (equivalent to the second request mentioned above), to trigger the recovery to the RRC_CONNECTED state.

[0394] In some embodiments, the third node is the base station of the currently serving UE (New Serving gNB(LEO2)). The fourth information is used to request the restoration of the RRC connection.

[0395] In some embodiments, the third node is located on a satellite.

[0396] In some embodiments, the fourth information includes node information of the second node and / or the first identifier.

[0397] Step 806: The third node sends the fifth information (equivalent to the first request mentioned above) to the second node based on the fourth information.

[0398] In some embodiments, the fifth piece of information is used to obtain the UE context.

[0399] In some embodiments, the fifth information includes a first identifier.

[0400] Step 807: The second node sends UE context information to the third node.

[0401] Step 808: The third node performs the terminal's RRC connection recovery process based on the UE context information.

[0402] For specific examples in this embodiment, please refer to the corresponding descriptions of the embodiments in Figures 1 to 7, which will not be repeated here.

[0403] The communication method involved in this embodiment may include at least one of steps S801 to S808. For example, step S801, step S802, step S803, step S804, step S805, step S806, step S807, and step S808 may be implemented as independent embodiments. Alternatively, some or all of the steps in S801 to S808 may be combined as independent embodiments, and this embodiment does not limit this.

[0404] The technical solution provided in this embodiment stores the terminal's context information in the nodes of the terrestrial network. This way, even if the base station on the satellite moves, the base station on the satellite currently serving the terminal can still obtain the terminal's context information through the nodes of the terrestrial network. This enables the terminal in the RRC_INACTIVE state under non-GEO satellite coverage to restore to the RRC_CONNECTED state, reducing the process of the terminal initiating RNA and avoiding frequent terminal context acquisition processes.

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

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

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

[0408] Figure 9 is a schematic diagram of the structure of a communication device applied to a first node according to an embodiment of this disclosure. As shown in Figure 9, it includes a transceiver module 61. In some embodiments, the transceiver module 61 is used to perform at least one of the communication steps (e.g., steps S301 to S302, but not limited thereto) performed by the first node in any of the above methods, which will not be described in detail here.

[0409] Figure 10 is a schematic diagram of the structure of a communication device applied to a second node according to an embodiment of this disclosure. As shown in Figure 10, it may include a transceiver module 71. In some embodiments, the transceiver module 71 is used to perform at least one of the communication steps (e.g., steps S401 to S402, but not limited thereto) performed by the second node in any of the above methods, which will not be described in detail here.

[0410] Figure 11 is a schematic diagram of the structure of a communication device applied to a third node according to an embodiment of this disclosure. As shown in Figure 11, it includes a transceiver module 81. In some embodiments, the transceiver module 81 is used to perform at least one of the communication steps (e.g., steps S501 to S503, but not limited thereto) performed by the third node in any of the above methods, which will not be described in detail here.

[0411] Figure 12 is a schematic diagram of the structure of a communication device applied to a terminal according to an embodiment of this disclosure. As shown in Figure 12, it may include a transceiver module 91. In some embodiments, the transceiver module 91 is used to perform at least one of the communication steps (e.g., step S602, but not limited thereto) performed by the terminal in any of the above methods, which will not be described in detail here.

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

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

[0414] As shown in Figure 13, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 can be used to execute any of the above methods. Optionally, one or more processors 8101 can be used to invoke instructions to cause the communication device 8100 to execute any of the above methods.

[0415] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceivers 8102 perform the communication steps such as sending and / or receiving in the above method, and the processor 8101 performs at least one of the other steps. 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, sending unit, transmitter, sending circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0416] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Optionally, all or part of the memories 8103 may be located outside the communication device 8100. In an optional embodiment, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memories 8102, and the interface circuits 8104 can be used to receive data from the memories 8102 or other devices, and can be used to send data to the memories 8102 or other devices. For example, the interface circuits 8104 can read data stored in the memories 8102 and send the data to the processor 8101.

[0417] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in this disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG13. The communication device may be a standalone device or may be 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 and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0418] Figure 14 is a schematic diagram of the structure of chip 8200 according to an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of chip 8200 shown in Figure 14, but it is not limited thereto.

[0419] Chip 8200 includes one or more processors 8201. Chip 8200 is used to perform any of the above methods.

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

[0421] In some embodiments, the interface circuit 8202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 8202 performing the communication steps, such as sending and / or receiving, in the above-described method refers to the interface circuit 8202 performing data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of the communication method steps described above.

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

[0423] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 8100, cause the communication device 8100 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.

[0424] This disclosure also provides a program product that, when executed by the communication device 8100, causes the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0425] 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, The method, executed by the first node on the non-terrestrial network (NTN) side, includes: Send the first message to the second node; The first information is used to transmit the context information of the terminal.

2. The method according to claim 1, characterized in that, The context information is used by the terminal to recover from the Radio Resource Control (RRC) inactive state (RRC_INACTIVE) to the Radio Resource Control (RRC_CONNECTED) connected state.

3. The method according to any one of claims 1 to 2, characterized in that, The first information includes the context information.

4. The method according to any one of claims 1 to 3, characterized in that, The context information includes at least one of the following: Core network information for the terminal being served; The terminal's access layer (AS) security information; The AS context of the terminal; The terminal's session information.

5. The method according to any one of claims 1 to 4, characterized in that, The second node includes at least one of the following: Access network equipment; Core network equipment.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive the second information sent by the second node; The second information is used to confirm that the second node has successfully received the context information of the terminal.

7. The method according to claim 6, characterized in that, The second information includes a first identifier, which is an identifier assigned to the terminal by the second node.

8. The method according to claim 7, characterized in that, The first identifier is used to obtain the context information of the terminal.

9. The method according to claim 8, characterized in that, The first identifier includes at least one of the following: Inactive wireless network temporary identifier I-RNTI; System Temporary User Identity (S-TMSI).

10. The method according to any one of claims 7 to 9, characterized in that, The method further includes: Send a Radio Resource Control (RRC) release message to the terminal that is in the RRC_CONNECTED state; The RRC release message includes at least one of the following: The first identifier; The node information of the second node.

11. The method according to claim 10, characterized in that, Sending the first information to the second node includes: Before sending the RRC release message to the terminal, the first information is sent to the second node.

12. The method according to any one of claims 10 to 11, characterized in that, The method further includes: Send the third message to the second node; The third information is used to notify the second node that the terminal has entered the RRC_INACTIVE state.

13. A communication method, characterized in that, Executed by the second node, the method includes: Receive the first message sent by the first node on the non-terrestrial network (NTN) side; The first information is used to transmit the context information of the terminal.

14. The method according to claim 13, characterized in that, The context information is used by the terminal to recover from the Radio Resource Control (RRC) inactive state (RRC_INACTIVE) to the Radio Resource Control (RRC_CONNECTED) connected state (RRC_CONNECTED).

15. The method according to any one of claims 13 to 14, characterized in that, The first information includes the context information of the terminal.

16. The method according to any one of claims 13 to 15, characterized in that, The context information of the terminal includes at least one of the following: Core network information for the terminal being served; The terminal's access layer (AS) security information; The AS context of the terminal; The terminal's session information.

17. The method according to any one of claims 13 to 16, characterized in that, The second node includes at least one of the following: Access network equipment; Core network equipment.

18. The method according to any one of claims 13 to 17, characterized in that, The method further includes: Send the second message to the first node; The second information is used to confirm that the second node has successfully received the context information of the terminal.

19. The method according to claim 18, characterized in that, The second information includes a first identifier, which is an identifier assigned to the terminal by the second node.

20. The method according to claim 19, characterized in that, The first identifier is used to obtain the context information of the terminal.

21. The method according to any one of claims 19 to 20, characterized in that, The first identifier includes at least one of the following: Inactive wireless network temporary identifier I-RNTI; System Temporary User Identity (S-TMSI).

22. The method according to any one of claims 19 to 21, characterized in that, The method further includes: Receive a first request sent by a third node on the NTN side, wherein the first request includes the first identifier and the first request is used to request to obtain the context information of the terminal; The terminal's context information is sent to the third node according to the first request.

23. The method according to any one of claims 13 to 22, characterized in that, The method further includes: Receive the third information sent by the first node; The third information is used to notify the second node that the terminal has entered the RRC_INACTIVE state.

24. A communication method, characterized in that, The method, executed by a third node on the non-terrestrial network (NTN) side, includes: The receiving terminal sends a second request; The second request is used to request a return from the Radio Resource Control inactive RRC_INACTIVE state to the Radio Resource Control connected RRC_CONNECTED state.

25. [Amended according to Rule 26, 12.09.2024] The method according to claim 24, characterized in that, The second request includes at least one of the following: The node information of the second node; The first identifier is an identifier assigned to the terminal by the second node.

26. The method according to claim 25, characterized in that, The method further includes: A first request is sent to the second node based on the node information, wherein the first request includes the first identifier, and the first request is used to request the acquisition of the context information of the terminal; Receive the context information of the terminal sent by the second node.

27. A communication method, characterized in that, The method, executed by a terminal, includes: Send a second request to the third node on the non-terrestrial network NTN side; The second request is used to request a return from the Radio Resource Control inactive RRC_INACTIVE state to the Radio Resource Control connected RRC_CONNECTED state.

28. The method according to claim 27, characterized in that, The second request includes at least one of the following: The node information of the second node; The first identifier is an identifier assigned to the terminal by the second node.

29. The method according to claim 28, characterized in that, Before sending the second request to the third node on the NTN side, the method further includes: Receive the Radio Resource Control (RRC) release message sent by the first node on the NTN side; According to the RRC release message, the state switches from RRC_CONNECTED to RRC_INACTIVE. The RRC release message includes at least one of the following: The first identifier; The node information of the second node.

30. A communication method, characterized in that, include: The first node on the non-terrestrial network (NTN) side sends first information to the second node, and the first information is used to transmit the terminal's context information; The second node sends second information to the first node. The second information is used to confirm that the second node has successfully received the context information of the terminal. The second information includes a first identifier and node information of the second node. The first identifier is an identifier assigned to the terminal by the second node. The first node sends a Radio Resource Control (RRC) release message to the terminal based on the second information, and the terminal enters the Radio Resource Control inactive (RRC_INACTIVE) state based on the RRC release message. The terminal determines that it needs to return to the Radio Resource Control (RRC) connection RRC_CONNECTED state, and sends a second request to the third node on the NTN side currently serving the terminal. The second request is used to request to return from the RRC_INACTIVE state to the RRC_CONNECTED state. The second request includes the first identifier and the node information of the second node. The third node sends a first request to the second node according to the second request, the first request being used to request the acquisition of the terminal's context information; The second node sends the terminal's context information to the third node according to the first request. The context information is used for the terminal to recover from the RRC_INACTIVE state to the RRC_CONNECTED state.

31. A communication device, characterized in that, The device, applied to the first node on the non-terrestrial network (NTN) side, includes: The transceiver module is configured to send first information to the second node; wherein the first information is used to transmit the context information of the terminal.

32. A communication device, characterized in that, Applied to the second node, the device includes: The transceiver module is configured to receive first information sent by a first node on the non-terrestrial network (NTN) side; wherein the first information is used to transmit the terminal's context information.

33. A communication device, characterized in that, The device, applied to a third node on the non-terrestrial network (NTN) side, includes: The transceiver module is configured to receive a second request sent by the terminal; wherein the second request is used to request a return from the Radio Resource Control inactive RRC_INACTIVE state to the Radio Resource Control connected RRC_CONNECTED state.

34. A communication device, characterized in that, Applied to a terminal, the device includes: The transceiver module is configured to send a second request to a third node on the non-terrestrial network (NTN) side; wherein the second request is used to request a return from the Radio Resource Control (RRC) inactive state (RRC_INACTIVE) to the Radio Resource Control (RRC) connected state (RRC_CONNECTED).

35. A communication system, characterized in that, include: The first node on the non-terrestrial network NTN side is configured to implement the method of any one of claims 1 to 12; The second node is configured to implement the method of any one of claims 13 to 23; The third node on the NTN side is configured to implement the method of any one of claims 24 to 26; The terminal is configured to implement the method of any one of claims 27 to 29.

36. A communication device, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 1 to 29.

37. A computer storage medium, wherein, The computer storage medium stores computer-executable instructions; when executed by a processor, the computer-executable instructions can implement the method of any one of claims 1 to 29.

38. A computer program product comprising a computer program that, when executed by a processor, enables the implementation of the method according to any one of claims 1 to 29.

Images