Communication methods, communication apparatuses, network device, communication system and storage medium

Abstract

The present disclosure relates to communication methods, communication apparatuses, a network device, a communication system, and a storage medium. A method comprises: detecting that a satellite link is unavailable; and executing one of the following: storing data, and instructing a first core network element to store data, wherein the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and the satellite. In respect of communication systems supporting satellite access, the present disclosure achieves satellite operations of data storage and forwarding.

Description

Communication method, communication device, network equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies, and in particular to a communication method, a communication device, a network device, a communication system, and a storage medium. Background Art

[0002] The evolution of telecommunications network technology has integrated non-terrestrial network (NTN) technologies and supported satellite access. This allows terminals to access the core network and conduct services via satellite access networks. However, due to issues such as insufficient satellite deployments and limited coverage, satellite access networks may not provide continuous satellite connectivity. This discontinuous satellite connectivity occurs when the connection between the satellite and the terminal or between the satellite and the ground station is intermittent.

[0003] Summary of the Invention

[0004] For satellite access, a regenerative architecture—where at least the base station functionality is deployed on the satellite—requires support for delay-tolerant services, even with discontinuous satellite connectivity. This requires the satellite to support store-and-forward (S&F) data functionality, allowing data to be stored on the satellite in the event of a connection interruption and forwarded when the connection is restored. Implementing S&F functionality is a pressing issue.

[0005] The embodiments of the present disclosure provide a communication method, a communication apparatus, a network device, a communication system, and a storage medium, thereby implementing a store and forward satellite operation of data storage and forwarding for a communication system supporting satellite access.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a first network element and includes: detecting that a satellite link is unavailable; performing one of the following: storing data; instructing the first core network network element to store data; wherein the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and a satellite.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a first core network network element and includes: receiving second information, the second information being used to indicate storage of downlink data sent to a terminal at a first time, wherein the second information is determined based on the time when a feeder link between the satellite and the ground station is unavailable.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a core network, wherein the core network includes a first core network network element and a second core network network element; the method includes: the second core network network element detects that a satellite link is unavailable; the second core network network element executes one of the following: storing data; instructing the first core network network element to store data; wherein the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and a satellite.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a communication device is proposed, including: a processing module for detecting that a satellite link is unavailable; performing one of the following: storing data; instructing a first core network network element to store data; wherein the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and a satellite.

[0010] According to the fifth aspect of an embodiment of the present disclosure, a communication device is proposed, including: a transceiver module for receiving second information, the second information being used to indicate the storage of downlink data sent to the terminal at a first time, wherein the second information is determined based on the time when the feeder link between the satellite and the ground station is unavailable.

[0011] According to the sixth aspect of an embodiment of the present disclosure, a network device is proposed, comprising: one or more processors; one or more memories for storing instructions; wherein the processor is used to call instructions so that the network device executes a method as described in any one of the first and second aspects.

[0012] According to the seventh aspect of the embodiment of the present disclosure, a communication system is proposed, including: a first network element, configured to implement the method as described in the first aspect; and a first core network network element, configured to implement the method as described in the second aspect.

[0013] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, wherein the storage medium stores instructions, wherein when the instructions are executed by a network device, they can execute the method described in any one of the first and second aspects.

[0014] According to a ninth aspect of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a network device, the method according to any one of the first and second aspects is performed.

[0015] The technical solution provided by the embodiments of the present disclosure is for a satellite system in a regeneration mode to realize the position identification of a terminal.

[0016] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

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

[0019] FIG1B is a schematic diagram of a satellite communication system architecture based on transparent transmission payload according to an embodiment of the present disclosure.

[0020] FIG1C is a schematic diagram of a satellite communication system based on regenerative payload according to an embodiment of the present disclosure.

[0021] FIG2A is a schematic diagram illustrating normal or default satellite operation according to an embodiment of the present disclosure.

[0022] FIG2B is a schematic diagram illustrating the operation of a store and forward satellite according to an embodiment of the present disclosure.

[0023] 3A to 3D are exemplary interaction diagrams illustrating a communication method according to an embodiment of the present disclosure.

[0024] 4A and 4B are schematic diagrams showing an architecture of a satellite communication system according to an embodiment of the present disclosure.

[0025] 5A to 5F are schematic diagrams showing an implementation flow of a first network element executing a communication method according to an embodiment of the present disclosure.

[0026] FIG6A and FIG6B are schematic diagrams showing an implementation flow of a first core network element executing a communication method according to an embodiment of the present disclosure.

[0027] FIG7A and FIG7B are another flow chart showing a communication method executed by a first network element side according to an embodiment of the present disclosure.

[0028] FIG8 is another flowchart illustrating a communication method executed by a first core network element side according to an embodiment of the present disclosure.

[0029] 9A and 9B are schematic structural diagrams of a communication device according to an embodiment of the present disclosure.

[0030] FIG10A is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0031] FIG10B is a schematic structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] Embodiments of the present disclosure provide a communication method, a communication apparatus, a network device, a communication system, and a storage medium.

[0033] In a first aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a first network element, and the method includes: detecting that a satellite link is unavailable; executing one of the following: storing data; instructing the first core network network element to store data; wherein the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and a satellite.

[0034] In the embodiment of the present disclosure, after detecting that the feeder link or service link is unavailable, the first network element stores data and / or instructs the first core network network element to store data. In this way, when the satellite connection is interrupted, the data can still be stored at the satellite or core network, so that when the satellite connection is restored, the stored data can be forwarded, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0035] In some possible implementations, the unavailability of the satellite link is determined based on first information, the first information including at least one of the following: ephemeris information associated with the satellite; time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

[0036] In some possible implementations, when the first network element is a first access network element, after detecting that the satellite link is unavailable, storing data includes at least one of the following: storing uplink data sent by the terminal; and storing downlink data sent to the terminal.

[0037] In the disclosed embodiment, the first access network element can store uplink data sent by the terminal after detecting that the feeder link is unavailable, and / or can store downlink data sent to the terminal after detecting that the service link is unavailable. In this way, even if the satellite connection is interrupted, the data can still be stored at the satellite, so that the stored data can be forwarded when the satellite connection is restored, thereby implementing store-and-forward satellite operations and deploying delay-tolerant services.

[0038] In some possible implementations, when the first network element is a second core network element and the first network element is deployed on a satellite, after detecting that the satellite link is unavailable, storing data includes: storing uplink data sent by the terminal.

[0039] In the disclosed embodiment, the satellite-based secondary core network element can store uplink data sent by the terminal after detecting that the feeder link is unavailable. This allows uplink data to be stored at the satellite even if the satellite connection is interrupted, allowing the stored data to be forwarded when the satellite connection is restored. This enables store-and-forward satellite operations and allows for delay-tolerant services.

[0040] In some possible implementations, the first network element is the second core network element, and after detecting that the satellite link is unavailable, instructing the first core network element to store data includes: sending second information, where the second information is used to instruct the first core network element to store the downlink data sent to the terminal at the first time, wherein the second information is determined based on the time when the feeder link is unavailable.

[0041] In the disclosed embodiment, after detecting that the feeder link is unavailable, the second core network element can instruct the first core network element to store downlink data sent to the terminal. This allows the first core network element to store data even if the satellite connection is interrupted, allowing the stored downlink data to be forwarded when the satellite connection is restored. This enables store-and-forward satellite operations and allows for delay-tolerant services.

[0042] In some possible implementations, the second information is carried in the first message, and the first message is used to release the connection between the first network element and the first core network element.

[0043] In some possible implementations, the first message further carries third information, where the third information is used to indicate that the reason for releasing the connection is that the feeder link is unavailable.

[0044] In some possible implementations, when the first network element is a second core network element and is deployed on the ground, after detecting that the satellite link is unavailable, storing data includes: storing downlink data sent to the terminal.

[0045] In the disclosed embodiment, a second core network element on the ground can store downlink data sent to a terminal after detecting that the feeder link is unavailable. This allows data to be stored at the second core network element even if the satellite connection is interrupted, allowing the stored downlink data to be forwarded when the satellite connection is restored. This enables store-and-forward satellite operations and allows for delay-tolerant services.

[0046] In some possible implementations, after detecting that the satellite link is unavailable, the method further includes: detecting that the satellite link is available; performing one of the following: sending stored data; and instructing the first core network element to send the stored data.

[0047] In the embodiment of the present disclosure, after detecting that the feeder link or service link is available, the first network element forwards the stored data and / or instructs the first core network network element to forward the stored data. In this way, when the satellite connection is restored, the data stored when the feeder link or service link is unavailable is forwarded, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0048] In some possible embodiments, the availability of the satellite link is determined based on first information, wherein the first information includes at least one of the following: ephemeris information associated with the satellite; time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

[0049] In some possible implementations, when the first network element is a first access network element and the satellite link is a feeder link, after determining that the satellite link is available, the method further includes: sending the stored uplink data to the second core network element.

[0050] In the embodiment of the present disclosure, after detecting that the feeder link is available, the first access network network element forwards the stored uplink data to the second core network network element to continue the uplink data transmission. In this way, when the satellite connection is restored, the uplink data stored when the feeder link is unavailable is forwarded, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0051] In some possible implementations, when the first network element is a first access network element and the satellite link is a service link, after determining that the satellite link is available, the method further includes: sending the stored downlink data to the terminal.

[0052] In the embodiment of the present disclosure, after detecting that the service link is available, the first access network element forwards the stored downlink data to the terminal to continue the downlink data transmission. In this way, when the satellite connection is restored, the downlink data stored when the service link is unavailable is forwarded, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0053] In some possible implementations, when the first network element is a second core network element and the first network element is deployed on a satellite, after determining that the satellite link is available, the method further includes: sending the stored uplink data to the first core network element.

[0054] In the disclosed embodiment, after detecting that the feeder link is available, the second core network element on board the satellite forwards the stored uplink data to the first core network element to continue the uplink data transmission. In this way, when the satellite connection is restored, the uplink data stored when the feeder link is unavailable is forwarded, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0055] In some possible implementations, when the first network element is a second core network element and is deployed on the ground, after determining that the satellite link is available, the method further includes: sending the stored downlink data to the first access network element.

[0056] In the embodiment of the present disclosure, after detecting that the feeder link is available, the second core network network element on the ground forwards the stored downlink data to the first access network network element to continue downlink data transmission. In this way, when the satellite connection is restored, the downlink data stored when the feeder link is unavailable is forwarded, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0057] In some possible implementations, when the first network element is the second core network element, after determining that the satellite link is available, instructing the first core network element to send stored data includes: sending a second message, where the second message is used to establish a connection between the first core network element and the second core network element, and the connection is used to receive downlink data stored in the first core network element.

[0058] In the embodiment of the present disclosure, after detecting that the feeder link is available, the second core network network element instructs the first core network network element to forward the stored downlink data to continue downlink data transmission. In this way, when the satellite connection is restored, the downlink data stored at the first core network network element when the feeder link is unavailable is forwarded, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0059] In the second aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a first core network network element, and the method includes: receiving second information, the second information being used to indicate the storage of downlink data sent to the terminal at a first time, wherein the second information is determined based on the time when the feeder link between the satellite and the ground station is unavailable.

[0060] In some possible implementations, the second information is carried in the first message, and the first message is used to release the connection between the second core network element and the first core network element.

[0061] In some possible implementations, the first message further carries third information, where the third information is used to indicate that the reason for releasing the connection is that the feeder link is unavailable.

[0062] In some possible implementations, the method includes: receiving a second message, where the second message is used to establish a connection between the second core network element and the first core network element; and after the connection is established, sending the stored downlink data to the first network element.

[0063] In some possible implementations, after receiving the second information, the method further includes: receiving downlink data; and storing the downlink data within a first time.

[0064] In a third aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a core network, wherein the core network includes a first core network network element and a second core network network element; the method includes: the second core network network element detects that a satellite link is unavailable; the second core network network element executes one of the following: storing data; instructing the first core network network element to store data; wherein the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and a satellite.

[0065] In some possible implementations, the unavailability of the satellite link is determined based on first information, the first information including at least one of the following: ephemeris information associated with the satellite; time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

[0066] In some possible implementations, when the second core network element is deployed on a satellite, after the second core network element detects that the satellite link is unavailable, the second core network element storing data includes: the second core network element storing uplink data sent by the terminal.

[0067] In some possible implementations, after detecting that the satellite link is unavailable, the second core network element instructs the first core network element to store data, including: the second core network element sends second information, and the second information is used to instruct the first core network element to store the downlink data sent to the terminal at the first time, wherein the second information is determined based on the time when the feeder link is unavailable.

[0068] In some possible implementations, the second information is carried in the first message, and the first message is used to release the connection between the first network element and the first core network element.

[0069] In some possible implementations, the first message further carries third information, where the third information is used to indicate that the reason for releasing the connection is that the feeder link is unavailable.

[0070] In some possible implementations, when the second core network element is deployed on the ground, after the second core network element detects that the satellite link is unavailable, the second core network element storing data includes: the second core network element storing downlink data sent to the terminal.

[0071] In some possible implementations, after the second core network element detects that the satellite link is unavailable, the method further includes: detecting that the satellite link is available; performing one of the following: sending stored data; and instructing the first core network element to send the stored data.

[0072] In some possible embodiments, the availability of the satellite link is determined based on first information, wherein the first information includes at least one of the following: ephemeris information associated with the satellite; time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

[0073] In some possible implementations, when the second core network element is deployed on a satellite, after the second core network element determines that the satellite link is available, the method further includes: the second core network element sending the stored uplink data to the first core network element.

[0074] In some possible implementations, when the second core network element is deployed on the ground, after the second core network element determines that the satellite link is available, the method further includes: sending the stored downlink data to the first access network element.

[0075] In some possible implementations, the second core network element instructs the first core network element to send stored data, including: the second core network element sends a second message, the second message is used to establish a connection between the first core network element and the second core network element, and the connection is used to receive downlink data stored by the first core network element.

[0076] In a fourth aspect, an embodiment of the present disclosure proposes a communication device, which is applied to a first network element, and the device includes: a processing module, which is used to detect that a satellite link is unavailable; execute one of the following: store data; instruct the first core network network element to store data; wherein the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and a satellite.

[0077] In some possible implementations, the unavailability of the satellite link is determined based on first information, the first information including at least one of the following: ephemeris information associated with the satellite; time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

[0078] In some possible implementations, when the first network element is a first access network element, after detecting that the satellite link is unavailable, storing data includes at least one of the following: storing uplink data sent by the terminal; and storing downlink data sent to the terminal.

[0079] In some possible implementations, when the first network element is a second core network element and the first network element is deployed on a satellite, the processing module is configured to store uplink data sent by the terminal after detecting that the satellite link is unavailable.

[0080] In some possible embodiments, the device includes: a transceiver module; when the first network element is a second core network element, the transceiver module is used to send second information after the processing module detects that the satellite link is unavailable, and the second information is used to instruct the first core network element to store the downlink data sent to the terminal at the first time, wherein the second information is determined based on the time when the feeder link is unavailable.

[0081] In some possible implementations, the second information is carried in the first message, and the first message is used to release the connection between the first network element and the first core network element.

[0082] In some possible implementations, the first message further carries third information, where the third information is used to indicate that the reason for releasing the connection is that the feeder link is unavailable.

[0083] In some possible implementations, when the first network element is a second core network element and is deployed on the ground, the processing module is configured to store downlink data sent to the terminal after detecting that the satellite link is unavailable.

[0084] In some possible implementations, the processing module is configured to detect that the satellite link is available after detecting that the satellite link is unavailable; and perform one of the following: sending the stored data; and instructing the first core network element to send the stored data.

[0085] In some possible embodiments, the availability of the satellite link is determined based on first information, wherein the first information includes at least one of the following: ephemeris information associated with the satellite; time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

[0086] In some possible embodiments, the device includes: a transceiver module; when the first network element is a first access network network element and the satellite link is a feeder link, the transceiver module is used to send the stored uplink data to the second core network network element after the satellite link of the processing module is available.

[0087] In some possible implementations, the device includes: a transceiver module; when the first network element is a first access network network element and the satellite link is a service link, the transceiver module is used to send the stored downlink data to the terminal after the processing module satellite link is available.

[0088] In some possible implementations, the device includes: a transceiver module; when the first network element is a second core network element and the first network element is deployed on a satellite, the transceiver module is used to send the stored uplink data to the first core network element after the satellite link of the processing module is available.

[0089] In some possible embodiments, the device includes: a transceiver module; when the first network element is a second core network element and the first network element is deployed on the ground, the transceiver module is used to send the stored downlink data to the first access network element after the satellite link of the processing module is available.

[0090] In some possible embodiments, the device includes: a transceiver module; when the first network element is a second core network element, the transceiver module is used to send a second message after the satellite link of the processing module is available, and the second message is used to establish a connection between the first core network element and the second core network element, and the connection is used to receive downlink data stored in the first core network element.

[0091] In the fifth aspect, an embodiment of the present disclosure proposes a communication device, including: a transceiver module for receiving second information, the second information being used to indicate the storage of downlink data sent to the terminal at a first time, wherein the second information is determined based on the time when the feeder link between the satellite and the ground station is unavailable.

[0092] In some possible implementations, the second information is carried in the first message, and the first message is used to release the connection between the second core network element and the first core network element.

[0093] In some possible implementations, the first message further carries third information, where the third information is used to indicate that the reason for releasing the connection is that the feeder link is unavailable.

[0094] In some possible implementations, the transceiver module is further used to receive a second message, where the second message is used to establish a connection between the second core network element and the first core network element; after the connection is established, the stored downlink data is sent to the first network element.

[0095] In some possible implementations, the device includes: a processing module; a transceiver module, configured to receive downlink data after receiving the second information; and a processing module, configured to store the downlink data within a first time.

[0096] In the sixth aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; one or more memories for storing instructions; wherein the processor is used to call instructions so that the network device executes a method as described in any one of the first and second aspects and their possible implementations.

[0097] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, including: a first network element, configured to implement the method as described in the first aspect and any one of its possible implementation methods; a first core network network element, configured to implement the method as described in the second aspect and any one of its possible implementation methods.

[0098] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions, wherein when the instructions are executed by a network device, they can execute the method as described in any one of the first aspect and the second aspect and their possible implementations.

[0099] In a seventh aspect, embodiments of the present disclosure provide a storage medium storing instructions that, when executed on a network device, cause the communication device to execute the method of any one of the first aspect, the second aspect, and the embodiments thereof.

[0100] In an eighth aspect, an embodiment of the present disclosure proposes a computer program product. When the computer program product is executed by a communication device, the network device executes a method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

[0101] In a ninth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a network device, enables the network device to execute a method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

[0102] It is understandable that the above-mentioned communication devices, network devices, communication systems, storage media, computer program products, and computer programs are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0103] The present disclosure provides a communication method, communication device, network equipment, communication system, and storage medium. In some embodiments, the terms communication method, store-and-forward method, and information processing method are interchangeable. The terms terminal, network equipment, communication device, and information processing device are interchangeable. The terms communication system, satellite communication system, and information processing system are interchangeable.

[0104] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. Unless there is any contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementations in a certain embodiment can be arbitrarily combined. In addition, the embodiments can be arbitrarily combined. For example, some or all of the steps of different embodiments can be arbitrarily combined. For another example, a certain embodiment can be arbitrarily combined with the optional implementations of other embodiments.

[0105] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0106] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0107] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

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

[0110] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0111] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is similar when there are more branches such as A, B, C, etc.

[0112] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0113] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0114] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0115] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

[0116] 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", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0117] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network devices, core network devices, etc.).

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

[0119] 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 the like may be used interchangeably.

[0120] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by sidelinks. The sidelink can also be replaced by a sidelink.

[0121] 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, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

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

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

[0124] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0125] As shown in FIG1A , which is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure, the communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0126] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal 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, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0127] In some embodiments, the access network device 102, for example, is a node or device that accesses the terminal to the wireless network, and may include at least one of an evolved node B (eNB), a next generation eNB (ng-eNB), a next generation node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.

[0128] In some embodiments, the technical solution of the present disclosure can be applied to the open radio access network (Open RAN) architecture. In this case, the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0129] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0130] In some embodiments, the core network device 103 may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of one or more network elements. The network elements may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC) network, a 5G core (5GC) network, and a next generation core (NGC) network.

[0131] In some embodiments, the core network may be an EPC network in a 4G system. In this case, the access network device 102 may be, for example, an eNB.

[0132] In some embodiments, the core network device 103 may include a first core network element, such as a serving gateway (S-GW) or a packet data gateway (PDN-GW).

[0133] In some embodiments, the first core network element may be used for functions such as user plane processing, routing and forwarding of data packets, and its name is not limited thereto.

[0134] In some embodiments, the core network device 103 may include a second core network element, such as a mobility management entity (MME).

[0135] In some embodiments, the second core network element can be used for user mobility management, bearer management, user authentication, S-GW selection, etc., and its name is not limited thereto.

[0136] In some embodiments, the core network may be a 5G 5G network in a 5G system. In this case, the access network device 102 may be, for example, a gNB.

[0137] In some embodiments, the core network device 103 may include a first core network element, such as a user plane function (UPF).

[0138] In some embodiments, the first core network network element may be used for routing and forwarding core network user plane data packets, and its name is not limited thereto.

[0139] In some embodiments, the core network device 103 may include a second core network element, such as a session management function (SMF) or an access mobility function (AMF).

[0140] In some embodiments, the second core network element may be used to process user services, and its name is not limited thereto.

[0141] In some embodiments, each network element in the core network device 103 may also be referred to as a network device, a network function, a network entity, etc., without limitation to the name.

[0142] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0143] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or some of the entities in the communication system 100 , but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system 100 may include all or some of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities are arbitrary. The entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0144] The embodiments of the present disclosure may be applied to long term evolution (LTE), LTE-advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, international mobile telecommunications-advanced (IMT-advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (reg 802.20, ultra-wideband (UWB), Bluetooth (registered trademark), public land mobile network (PLMN) networks, device-to-device (D2D) systems, machine-to-machine (M2M) systems, Internet of Things (IoT) systems, vehicle-to-everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0145] The various embodiments of the present disclosure may be applicable to non-terrestrial networks (NTNs), including networks or network segments that utilize transmission equipment relay nodes or base stations carried on airborne or space-based vehicles, and any network involving non-terrestrial flying objects. For example, NTNs may include satellite communication networks and high altitude platform systems (HAPs). In the embodiments of the present disclosure, a satellite communication NTN is used as an example for illustration.

[0146] With the development of communication technology, satellite communication technology is considered an important aspect of the future development of wireless communication technology. Communication systems that support satellite access technology (such as 4G and 5G networks) can also be called satellite communication networks. In this communication network, terminals can access the core network (such as EPC and 5GC) through the satellite access network and conduct business. However, due to the insufficient number of satellite deployments, satellite access networks may have problems such as limited coverage. Therefore, satellites may not be able to provide continuous connection services. This discontinuous satellite connection includes interruptions in the service connection between the satellite and the terminal or the feeder connection between the satellite and the ground station.

[0147] In some embodiments, the connection between the satellite and the terminal may also be referred to as a service link, and the connection between the satellite and the ground station may also be referred to as a feeder link.

[0148] In some embodiments, the satellite communication network may have two different architectures: a satellite communication network architecture based on transparent payloads (i.e., transparent mode) and a satellite communication network architecture based on regenerative payloads (i.e., regenerative mode).

[0149] In some embodiments, as shown in FIG1B , FIG1B is a schematic diagram illustrating a satellite communication system architecture based on transparent transmission payloads according to an embodiment of the present disclosure. In this satellite communication system architecture, the core network is described as the EPC. Of course, the core network can also be 5GC or other evolved versions of the core network, which is not specifically limited in this embodiment of the present disclosure. In transparent transmission mode, eNB 20 is deployed on the ground, and satellite 10 performs the radio frequency functions of eNB 20.

[0150] In some embodiments, as shown in FIG1C , FIG1C is a schematic diagram illustrating a satellite communication system architecture based on a regenerative payload according to an embodiment of the present disclosure. In this satellite communication system architecture, the core network is still described as the EPC. Of course, the core network can also be 5GC or other evolved versions of the core network, which is not specifically limited in this embodiment of the present disclosure. In regenerative mode, at least eNB 20 is deployed on satellite 10.

[0151] In some embodiments, handling discontinuous coverage of the service link when the satellite is in transparent transmission mode may include enhancing terminal mobility and power saving techniques when the satellite provides discontinuous coverage. However, when the satellite is in regeneration mode, handling discontinuous coverage of the feeder link has not yet been technically clarified to support terminal services.

[0152] In some embodiments, to provide delay-tolerant communication services, satellite communication systems support store-and-forward (S&F) functionality. Store-and-forward (S&F) operation is an operating mode of a communication system with satellite access (i.e., a satellite communication system). This allows the communication system to provide a certain level of service (e.g., storing and forwarding data) when satellite connectivity is intermittent or temporarily unavailable. For example, this allows for communication services to terminals within satellite coverage without requiring simultaneous connection to a ground segment feeder link.

[0153] In some embodiments, the operation mode of the satellite communication system based on the transparent mode or the regeneration mode described above can be described as normal or default satellite operation.

[0154] In some embodiments, as shown in FIG2A , FIG2A is a schematic diagram illustrating normal or default satellite operation according to an embodiment of the present disclosure. In the "normal / default satellite operation" mode, the interaction of signaling and data transmission between the terminal and the remote terrestrial network (TN) via the satellite requires that the service link and the feeder link are simultaneously active. Therefore, when the terminal interacts with the satellite via the service link, a continuous, end-to-end connection path exists between the terminal, the satellite, and the terrestrial network.

[0155] In some embodiments, as shown in Figure 2B, Figure 2B is a schematic diagram of the storage and forwarding satellite operation shown in accordance with an embodiment of the present disclosure. Compared with the above-mentioned "normal / default satellite operation" mode, under the "S&F satellite operation" mode, the interaction of end-to-end signaling or data transmission is processed as a combination of two steps that are not executed at the same time (such as steps A and B in Figure 2B). In step A, signaling or data transmission is interactively performed between the terminal and the satellite. At this time, the satellite may not be connected to the ground network (that is, the satellite can use the service link when there is no available feeder link connection). In step B, a connection is established between the satellite and the ground network (that is, a feeder link is established), so that communication can be carried out between the satellite and the ground network. Therefore, the satellite moves from being connected to the terminal in step A to being connected to the ground network in step B.

[0156] In some embodiments, support for S&F satellite operations is particularly applicable to non-geostationary satellite orbit (NGSO) satellites providing delay-tolerant or non-real-time IoT satellite services.

[0157] A regenerative architecture for satellite access, where at least the base station functionality is deployed on the satellite, allows for delay-tolerant services to be delivered even with discontinuous satellite connectivity. This requires the satellite to support store-and-forward (S&F) data capabilities, allowing data to be stored on the satellite in the event of a connection interruption and forwarded when the connection is restored. Implementing S&F satellite operations is a pressing issue.

[0158] In order to solve the above problems, the embodiments of the present disclosure provide a communication method, a communication apparatus, a network device, a communication system and a storage medium to implement the above-mentioned S&F satellite operation for a communication system supporting satellite access.

[0159] As shown in Figure 3A, Figure 3A is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is executed by the above-mentioned communication system 100. The above-mentioned communication method includes steps S3101 to S3117.

[0160] In the embodiments of the present disclosure, the core network is taken as EPC as an example for description.

[0161] In some embodiments, the EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW, and the second core network element is an MME.

[0162] In some embodiments, an access network is described as an E-UTRAN. A first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0163] In some embodiments, as shown in Figure 4A, which is a schematic diagram of an architecture of a satellite communication system according to an embodiment of the present disclosure, both the S-GW and the MME are deployed on the ground.

[0164] In one embodiment, the connection between the onboard eNB and the MME via the ground station is an S1-MME connection.

[0165] In one embodiment, the connection between the MME and the S-GW is an S11-U connection.

[0166] In some embodiments, the satellite link may include a service link and a feeder link.

[0167] In the embodiment of the present disclosure, the first network element may be one of the second core network element and the first access network element.

[0168] The following describes the data transmission process initiated by a mobile terminal (MO).

[0169] In step S3101, the terminal sends uplink data.

[0170] In some embodiments, the eNB receives uplink data.

[0171] In some embodiments, the uplink data is encrypted and encapsulated in a non-access stratum (NAS) protocol data unit (PDU). The NAS PDU also carries an EPS bearer ID (EBI).

[0172] In some embodiments, the terminal is in an EPS connection management idle (ECM-IDLE) state. The terminal triggers a radio resource control (RRC) connection establishment process. In one example, the terminal sends an RRC connection request message (RRCConnectionRequest) or a radio resource control early data request (RRCEarlyDataRequest) message to the eNB. The RRC message carries a NAS PDU.

[0173] In some embodiments, if header compression is supported, the terminal may apply header compression before encapsulating the encrypted uplink data into a NAS PDU.

[0174] In some embodiments, the terminal may further carry NAS release assistance information in the NAS PDU. The NAS release assistance information is used to indicate whether further uplink data transmission (i.e., transmission of uplink data) or downlink data transmission (i.e., transmission of downlink data) is not expected, or to indicate that only a single downlink data transmission (e.g., an acknowledgment message or response message for the uplink data) is expected after the transmission of the uplink data.

[0175] In some embodiments, after step S3101, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. In this case, step S3102 is executed.

[0176] In step S3102, the eNB detects that the feeder link is unavailable.

[0177] In some embodiments, the satellite link is a feeder link between the satellite and a ground station.

[0178] In some embodiments, after receiving uplink data, the eNB detects that the feeder link is unavailable. The feeder link being unavailable means that the connection between the satellite and the ground station is disconnected.

[0179] In some embodiments, the eNB detecting that the feeder link is unavailable can be understood as the eNB detecting that the feeder link is unavailable at the current moment. In this case, the feeder link has been interrupted and the connection between the satellite and the ground station has been disconnected.

[0180] In some embodiments, the eNB detecting that the feeder link is unavailable can be understood as the eNB detecting that the feeder link is unavailable at a future time. In this case, the feeder link is about to be interrupted, and the connection between the satellite and the ground station is about to be disconnected.

[0181] In some embodiments, the eNB detects that the feeder link is unavailable based on information A. In one embodiment, information A may be pre-configured or sent to the eNB by operation administration and maintenance (OAM). In this case, the first information is information A.

[0182] In some embodiments, information A may include at least one of satellite-associated ephemeris information and time information determined based on the satellite's ephemeris information. The time information determined based on the ephemeris information may be used to indicate when the feeder link is available and / or when the satellite link is unavailable. In one example, information A may indicate a period during which the feeder link is available or a time when the feeder link is available. In another example, information A may indicate a period during which the feeder link is unavailable or a time when the feeder link is unavailable.

[0183] In some embodiments, the time information determined based on the satellite's ephemeris information can be derived from the ephemeris information associated with the satellite. Based on this information, the eNB can determine when the satellite is available to connect to the ground station, the duration of the feeder link, and when the satellite loses connection with the ground station, thereby detecting whether the feeder link is available or unavailable.

[0184] In step S3103, the eNB stores the uplink data.

[0185] In some embodiments, the eNB stores uplink data after detecting that the feeder link is unavailable.

[0186] In some embodiments, when a terminal uses a satellite access supporting the S&F function, the eNB may store uplink data based on an S&F quota granted to the terminal.

[0187] In step S3104, the eNB detects whether the feeder link is available.

[0188] In some embodiments, the satellite link is a feeder link between the satellite and a ground station.

[0189] In some embodiments, after determining that the feeder link is unavailable, the eNB may continue to detect the feeder link. In one example, the eNB may monitor the feeder link or periodically detect the feeder link.

[0190] In some embodiments, the eNB detecting that the feeder link is available can be understood as the eNB detecting that the feeder link is available at the current moment. In this case, the feeder link is established and the satellite is connected to the ground station.

[0191] In some embodiments, the eNB detecting that the feeder link is available can be understood as the eNB detecting that the feeder link is available at a future time. In this case, the feeder link is about to be established and the satellite is about to be connected to the ground station.

[0192] In some embodiments, the eNB detects, based on information A, that the feeder link is available.

[0193] In step S3105 , the eNB sends uplink data.

[0194] In some embodiments, the MME receives uplink data.

[0195] In some embodiments, after detecting that the feeder link is available, the eNB sends its stored uplink data to the MME to continue uplink data transmission. In one example, the eNB sends the uplink data to the MME via an S1-AP message. In one example, the S1-AP message can be an S1-AP Initial UE message. In one example, if the eNB receives an RRCEarlyDataRequest message in step S3101, the eNB can include an "Early Data Transfer Session (EDT Session)" indication in the S1-AP Initial UE message.

[0196] In some embodiments, after receiving uplink data, ie, NAS PDU, the MME detects the integrity of the NAS PDU and decrypts the uplink data contained in the NAS PDU.

[0197] In some embodiments, if header compression is applied to a packet data network (PDN) connection, the MME may decompress the header.

[0198] In some embodiments, after step S3105, if the connection between the S-GW and the MME is not established, a connection between the MME and the S-GW is established, and steps S3106 to S3107 are executed. Otherwise, step S3108 is executed.

[0199] In step S3106, the MME sends a second message.

[0200] In some embodiments, the S-GW receives the second message.

[0201] In some embodiments, the second message is used to request establishment of a connection between the MME and the S-GW, such as an S11-U connection. In one example, the third message may be a modify bearer request message.

[0202] In some embodiments, the MME sends a modify bearer request message for each PDN connection to the S-GW to request establishment of an S11-U connection.

[0203] In some embodiments, the modify bearer request message may include: an MME address and an MME tunnel endpoint identifier (TEID) of downlink data.

[0204] In step S3107, the S-GW sends a third message.

[0205] In some embodiments, the MME receives the third message.

[0206] In some embodiments, the third message is a confirmation message or a response message of the second message. In one example, the third message can be a modify bearer response message.

[0207] In some embodiments, after the S11-U connection is established, the S-GW sends a modify bearer response message to the MME.

[0208] In some embodiments, the modify bearer response message may include: an S-GW address and an S-GW TEID of uplink data.

[0209] In step S3108, the MME sends uplink data.

[0210] In some embodiments, the S-GW receives uplink data.

[0211] In some embodiments, if the NAS release assistance information sent by the terminal indicates that no further downlink data transmission (i.e., downlink data transmission) is desired, then after step S3106, it means that all application layer data interaction has been completed via uplink data. In this case, steps S3109 to S3117 can be skipped. Otherwise, steps S3109 to S3117 are executed.

[0212] In step S3109, the S-GW sends downlink data.

[0213] In some embodiments, the MME receives downlink data.

[0214] In some embodiments, the S-GW sends the stored downlink data.

[0215] In some embodiments, after step S3109, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. In this case, step S3110 is executed.

[0216] In step S3110 , the MME detects that the feeder link is unavailable.

[0217] In some embodiments, the satellite link is a feeder link between the satellite and a ground station.

[0218] In some embodiments, after receiving the downlink data, the MME detects that the feeder link is unavailable. The feeder link being unavailable means that the connection between the satellite and the ground station is disconnected.

[0219] In some embodiments, the MME detecting that the feeder link is unavailable can be understood as the MME detecting that the feeder link is unavailable at the current moment. In this case, the feeder link has been interrupted, and the connection between the satellite and the ground station has been disconnected.

[0220] In some embodiments, the MME detecting that the feeder link is unavailable can be understood as the MME detecting that the feeder link is unavailable at a future time. In this case, the feeder link is about to be interrupted, and the connection between the satellite and the ground station is about to be disconnected.

[0221] In some embodiments, the MME detects that the feeder link is unavailable based on information B. In one embodiment, information B may be preconfigured or sent to the MME by the eNB or OAM. In this case, the first information is information B.

[0222] In some embodiments, information B may include at least one of satellite-associated ephemeris information and time information determined based on the satellite's ephemeris information. The time information determined based on the ephemeris information may be used to indicate when the feeder link is available and / or when the satellite link is unavailable. In one example, information B may indicate a period during which the feeder link is available or a time when the feeder link is available. In another example, information B may indicate a period during which the feeder link is unavailable or a time when the feeder link is unavailable.

[0223] In some embodiments, the time information determined based on the satellite's ephemeris information can be derived from the ephemeris information associated with the satellite. Based on this information, the MME can determine when the satellite can connect to the ground station, the duration of the feeder link, and when the satellite loses connection with the ground station, thereby detecting whether the feeder link is available or unavailable.

[0224] In step S3111, the MME stores the downlink data.

[0225] In some embodiments, the MME stores the downlink data after detecting that the feeder link is unavailable.

[0226] In some embodiments, when the terminal uses a satellite access supporting the S&F function, the MME may store downlink data based on the S&F quota authorized to the terminal.

[0227] In step S3112, the MME detects that the feeder link is available.

[0228] In some embodiments, the satellite link is a feeder link between the satellite and a ground station.

[0229] In some embodiments, after determining that the feeder link is unavailable, the MME may continue to detect the feeder link. In one example, the MME may monitor the feeder link or periodically detect the feeder link.

[0230] In some embodiments, the MME detecting that the feeder link is available can be understood as the MME detecting that the feeder link is available at the current moment. In this case, the feeder link is established and the satellite is connected to the ground station.

[0231] In some embodiments, the MME detecting that the feeder link is available can be understood as the MME detecting that the feeder link is available at a future time. In this case, the feeder link is about to be established and the satellite is about to be connected to the ground station.

[0232] In some embodiments, the MME detects, based on information B, that the feeder link is available.

[0233] In step S3113, the MME sends downlink data.

[0234] In some embodiments, the eNB receives downlink data.

[0235] In some embodiments, after receiving the downlink data, the MME encrypts and integrity-protects the downlink data. It then forwards the downlink data to the eNB. In one example, the MME encapsulates the downlink data in a NAS PDU and sends it to the eNB via an S1-AP message.

[0236] In some embodiments, if the NAS release assistance information in the NAS PDU is received together with the uplink data in step S3101, and the NAS release assistance information indicates that further downlink data is expected, then after step S3110, it means that the next downlink data packet after sending the NAS release assistance information is the last data packet of the application layer data exchange. In this case, the MME sends a terminal context release command (such as UE Context Release Command) through the S1-AP message immediately after sending the S1-AP message to instruct the eNB to release the RRC connection after successfully sending the downlink data to the UE.

[0237] In some embodiments, after step S3113, the connection between the terminal and the satellite is disconnected or about to be disconnected, and the service link is unavailable. In this case, step S3114 is executed.

[0238] In step S3114, the eNB detects that the serving link is unavailable.

[0239] In some embodiments, the satellite link is a serving link between the satellite and the terminal.

[0240] In some embodiments, after receiving downlink data, the eNB detects that the service link is unavailable. The service link being unavailable means that the connection between the satellite and the terminal is disconnected.

[0241] In some embodiments, the eNB detecting that the service link is unavailable can be understood as the eNB detecting that the service link is unavailable at the current moment. In this case, the service link has been interrupted and the connection between the satellite and the terminal has been disconnected.

[0242] In some embodiments, the eNB detecting that the service link is unavailable can be understood as the eNB detecting that the service link is unavailable at a future time. In this case, the service link is about to be interrupted, and the connection between the satellite and the terminal is about to be disconnected.

[0243] In some embodiments, the eNB detects that the serving link is unavailable according to information A. In one embodiment, the information A may be pre-configured or sent to the MME by the OAM.

[0244] In step S3115, the eNB stores the downlink data.

[0245] In some embodiments, the eNB stores downlink data after detecting that the serving link is unavailable.

[0246] In some embodiments, when a terminal uses a satellite access supporting the S&F function, the eNB may store downlink data based on an S&F quota granted to the terminal.

[0247] In step S3116, the eNB detects that the serving link is available.

[0248] In some embodiments, the satellite link is a serving link between the satellite and the terminal.

[0249] In some embodiments, after determining that the serving link is unavailable, the eNB may continue to detect the serving link. In one example, the eNB may monitor the serving link or periodically detect the serving link.

[0250] In some embodiments, the eNB detecting that the service link is available can be understood as the eNB detecting that the service link is available at the current moment. In this case, the service link is established and the terminal is connected to the eNB.

[0251] In some embodiments, the eNB detecting that the service link is available can be understood as the eNB detecting that the service link is available at a future time. In this case, the service link is about to be established and the terminal is about to be connected to the eNB.

[0252] In some embodiments, the eNB detects, based on information A, that the feeder link is available.

[0253] In step S3117, the eNB sends downlink data.

[0254] In some embodiments, the terminal receives downlink data.

[0255] In some embodiments, the uplink data is encrypted and encapsulated in a NAS PDU. The NAS PDU also carries an EPS bearer ID (EBI).

[0256] In some embodiments, the NAS PDU is carried in an RRC message and sent. In one example, the RRC message may be an RRC downlink data message or an RRC early data complete message.

[0257] In some embodiments, after the eNB receives the S1-AP message from the MME, if the S1-AP message carries an end indication of no further data, the eNB may send an RRC EarlyDataComplete message.

[0258] In some embodiments, if the MME sends a UE Context Release Command immediately after the S1-AP message, the eNB releases the RRC connection after the downlink data transmission of the NAS PDU to the terminal is completed.

[0259] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3117. For example, the combination of steps S3101 to S3105 can be implemented as an independent embodiment. For example, the combination of steps S3109 to S3113 can be implemented as an independent embodiment. For example, the combination of steps S3114 to S3117 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3105 and step S3108 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3108 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3105, steps S3108 to S3113, and step S3117 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3113 and step S3117 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3105 and steps S3108 to S3117 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3117 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3102, steps S3108 to S3113, and step S3117 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3102 and steps S3108 to S3117 can be implemented as an independent embodiment. For example, steps S3101 to S3113 and step S3117 can be implemented as independent embodiments. For example, steps S3101 to S3117 can be implemented as independent embodiments. It should be noted that one or more steps from steps S3101 to S3117 may constitute a possible independent embodiment, but are not limited to this.

[0260] In some embodiments, steps S3106 to S3107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0261] In some embodiments, steps S3114 to S3116 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0262] As shown in Figure 3B, Figure 3B is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is executed by the above-mentioned communication system 100. The above-mentioned communication method includes steps S3201 to S3220.

[0263] In the embodiments of the present disclosure, the core network is taken as EPC as an example for description.

[0264] In some embodiments, the EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW, and the second core network element is an MME.

[0265] In some embodiments, the access network is described as E-UTRAN. A first access network element in E-UTRAN is an access network element deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0266] In some embodiments, as shown in FIG4B , which is a schematic diagram of an architecture of a satellite communication system according to an embodiment of the present disclosure, the S-GW is deployed on the ground. The MME is deployed on a satellite, in which case the MME may also be referred to as a satellite-borne MME.

[0267] In one embodiment, the connection between the onboard MME and the S-GW is an S11-U connection.

[0268] In one embodiment, the connection between the eNB and the MME is an S1-MME connection.

[0269] In some embodiments, the satellite link may include a service link and a feeder link.

[0270] In the embodiment of the present disclosure, the first network element may be one of the second core network element and the first access network element.

[0271] The following describes the data transmission process initiated by the terminal (MO).

[0272] In step S3201, the terminal sends uplink data.

[0273] The optional implementation of step S3201 can refer to the optional implementation of step S3101 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0274] In step S3202, the eNB sends uplink data.

[0275] The optional implementation of step S3202 can refer to the optional implementation of step S3105 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0276] In some embodiments, after step S3202, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. In this case, step S3103 is executed.

[0277] In step S3203, the MME detects that the feeder link is unavailable.

[0278] In some embodiments, the satellite link is a feeder link between the satellite and a ground station.

[0279] In some embodiments, after receiving the downlink data, the MME detects that the feeder link is unavailable. The feeder link being unavailable means that the connection between the satellite and the ground station is disconnected.

[0280] In some embodiments, the MME detecting that the feeder link is unavailable can be understood as the MME detecting that the feeder link is unavailable at the current moment. In this case, the feeder link has been interrupted, and the connection between the satellite and the ground station has been disconnected.

[0281] In some embodiments, the MME detecting that the feeder link is unavailable can be understood as the MME detecting that the feeder link is unavailable at a future time. In this case, the feeder link is about to be interrupted, and the connection between the satellite and the ground station is about to be disconnected.

[0282] In some embodiments, the MME detects that the feeder link is unavailable based on information B. In one embodiment, information B may be preconfigured or sent to the MME by the eNB or OAM. In this case, the first information is information B.

[0283] In some embodiments, information B may include at least one of satellite-associated ephemeris information and time information determined based on the satellite's ephemeris information. The time information determined based on the ephemeris information may be used to indicate when the feeder link is available and / or when the satellite link is unavailable. In one example, information B may indicate a period during which the feeder link is available or a time when the feeder link is available. In another example, information B may indicate a period during which the feeder link is unavailable or a time when the feeder link is unavailable.

[0284] In some embodiments, the time information determined based on the satellite's ephemeris information can be derived from the ephemeris information associated with the satellite. Based on this information, the MME can determine when the satellite can connect to the ground station, the duration of the feeder link, and when the satellite loses connection with the ground station, thereby detecting whether the feeder link is available or unavailable.

[0285] In step S3204, the MME stores the uplink data.

[0286] In some embodiments, the MME stores uplink data after detecting that the feeder link is unavailable.

[0287] In some embodiments, when the terminal uses a satellite access supporting the S&F function, the MME may store downlink data based on the S&F quota authorized to the terminal.

[0288] In some embodiments, after receiving the NAS PDU, the MME detects the integrity of the NAS PDU and decrypts the uplink data contained in the NAS PDU.

[0289] In some embodiments, if header compression is applied to the PDN connection, the MME may decompress the header.

[0290] In step S3205 , the MME detects that the feeder link is available.

[0291] The optional implementation of step S3205 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0292] In some embodiments, after step S3205, if no connection is established between the S-GW and the MME, a connection is established between the MME and the S-GW, and steps S3206 to S3207 are executed.

[0293] In step S3206, the MME sends a second message.

[0294] The optional implementation of step S3206 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0295] In step S3207, the S-GW sends a third message.

[0296] The optional implementation of step S3207 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0297] In step S3208, the MME sends uplink data.

[0298] In some embodiments, the S-GW receives uplink data.

[0299] In some embodiments, after detecting that the feeder link is available, the MME sends the uplink data stored in itself to the S-GW to continue uplink data transmission.

[0300] In some embodiments, if the NAS release assistance information sent by the terminal indicates that no further downlink data transmission (i.e., downlink data transmission) is desired, then after step S3208, it means that all application layer data interaction has been completed via uplink data. In this case, the following steps S3209 to S3220 can be skipped. Otherwise, step S3209 is executed.

[0301] In step S3209, the MME detects that the feeder link is unavailable.

[0302] The optional implementation of step S3209 can refer to the optional implementation of step S3110 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0303] In some embodiments, in step S3209 , when the MME detects that the feeder link is about to become unavailable, the MME executes step S3210 .

[0304] In step S3210, the MME sends the second information.

[0305] In some embodiments, the S-GW receives the second information.

[0306] In some embodiments, the second information is used to instruct the S-GW to store the downlink data sent to the terminal at the first time. In one example, the second information may be downlink buffering duration time information.

[0307] In some embodiments, the second information is determined based on the time during which the feeder link is unavailable. In one example, the MME determines information B based on satellite ephemeris information or time information determined based on the satellite ephemeris information, and then determines the second information based on information B. The MME then sends the second information to the S-GW to ensure that downlink data can be stored at the S-GW during the period during which the feeder link is unavailable. In one example, the first time can be a time period or a moment.

[0308] In some embodiments, the second information may be carried in the first message and sent to request the release of the connection between the MME and the S-GW, such as the S11-U connection. In one example, the first message is a release bearer request message.

[0309] In some embodiments, the first message may further carry third information, and the third information may be used to indicate that the reason for the connection release is that the feeder link is unavailable.

[0310] In some embodiments, after receiving the first message, the S-GW sends an acknowledgment message or a response message of the first message to the MME. In one embodiment, the acknowledgment message or the response message of the first message may be a release bearer response message.

[0311] In step S3211, the S-GW stores the downlink data.

[0312] In some embodiments, the S-GW stores downlink data during the period when the feeder link is unavailable.

[0313] In some embodiments, the S-GW stores the downlink data within a first time indicated by the downlink buffering duration information.

[0314] In step S3212, the MME detects that the feeder link is available.

[0315] The optional implementation of step S3212 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0316] In step S3213, the MME sends a second message.

[0317] The optional implementation of step S3213 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0318] In step S3214, the S-GW sends a third message.

[0319] The optional implementation of step S3214 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0320] In step S3215, the S-GW sends downlink data.

[0321] In some embodiments, the MME receives downlink data.

[0322] In some embodiments, the S-GW sends the stored downlink data.

[0323] In step S3216, the MME sends downlink data.

[0324] In some embodiments, the eNB receives downlink data.

[0325] In some embodiments, after receiving the downlink data, the MME encrypts and integrity-protects the downlink data. It then forwards the downlink data to the eNB. In one example, the MME encapsulates the downlink data in a NAS PDU and sends it to the eNB via an S1-AP message.

[0326] In some embodiments, the configuration information in the MME indicates that the eNB supports confirmation of downlink NAS PDU, and confirmation of downlink NAS PDU is enabled in the subscription information of the terminal. At this time, the MME indicates in the S1-AP message that the eNB is requested to confirm.

[0327] In some embodiments, if the NAS release assistance information in the NAS PDU is received together with the uplink data in step S3101, and the NAS release assistance information indicates that further downlink data is expected, then after step S3110, it means that the next downlink data packet after sending the NAS release assistance information is the last data packet of the application layer data exchange. In this case, the MME sends a UE Context Release Command via an S1-AP message immediately after sending the S1-AP message to instruct the eNB to release the RRC connection after successfully sending the downlink data to the UE.

[0328] In some embodiments, after step S3215, the connection between the terminal and the satellite is disconnected or about to be disconnected, and the service link is unavailable. In this case, step S3217 is executed.

[0329] In step S3217, the eNB detects that the serving link is unavailable.

[0330] The optional implementation of step S3217 can refer to the optional implementation of step S3114 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0331] In step S3218, the eNB stores the downlink data.

[0332] The optional implementation of step S3218 can refer to the optional implementation of step S3115 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0333] In step S3219, the eNB detects that the serving link is available.

[0334] The optional implementation of step S3219 can refer to the optional implementation of step S3116 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0335] In step S3220, the eNB sends downlink data.

[0336] The optional implementation of step S3220 can refer to the optional implementation of step S3117 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0337] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3220. For example, the combination of steps S3203 to S3205 and step S3208 can be implemented as an independent embodiment. For example, the combination of steps S3209 to S3212 and step S3215 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3205 and step S3208 can be implemented as an independent embodiment. For example, the combination of steps S3217 to S32208 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3208 can be implemented as an independent embodiment. For example, the combination of steps S3209 to S3212, steps S3215 to S3216, and step S3220 can be implemented as an independent embodiment. For example, the combination of steps S3209 to S3216 and step S3220 can be implemented as an independent embodiment. For example, the combination of steps S3209 to S3212 and steps S3215 to S3220 can be implemented as an independent embodiment. For example, the combination of steps S3209 to S3220 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3205, steps S3208 to S3212, steps S3215 to S3216, and step S3220 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3212, steps S3215 to S3216, and step S3220 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3205, steps S3208 to S3216, and step S3220 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3216 and step S3220 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3205 and steps S3208 to S3220 can be implemented as independent embodiments. For example, the combination of steps S3201 to S3220 can be implemented as independent embodiments. It should be noted that one or more steps from steps S3201 to S3220 may constitute an independent embodiment, but are not limited to this.

[0338] In some embodiments, steps S3206 to S3207 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0339] In some embodiments, steps S3213 to S3214 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0340] As shown in Figure 3C, Figure 3C is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is executed by the above-mentioned communication system 100. The above-mentioned communication method includes steps S3301 to S3317.

[0341] In the embodiments of the present disclosure, the core network is taken as EPC as an example for description.

[0342] In some embodiments, the EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW, and the second core network element is an MME.

[0343] In some embodiments, the access network is described using E-UTRAN as an example. The first access network element in E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-based eNB. In some embodiments, as shown in FIG4B , the S-GW is deployed on the ground. The MME is deployed on the satellite, in which case the MME may also be referred to as a satellite-based MME.

[0344] In one embodiment, the connection between the onboard MME and the S-GW via the ground station is an S11-U connection.

[0345] In one embodiment, the connection between the eNB and the MME is an S1-MME connection.

[0346] In some embodiments, the satellite link may include a service link and a feeder link.

[0347] In the embodiment of the present disclosure, the first network element may be one of the second core network element and the first access network element.

[0348] The following describes the data transmission process received by a mobile terminated (MT) terminal.

[0349] In step S3301, the S-GW receives downlink data.

[0350] In some embodiments, the terminal is connected to the EPS and is in an idle state (ECM-IDLE).

[0351] In step S3302, the S-GW sends a fourth message.

[0352] In some embodiments, the MME receives the fourth message.

[0353] In some embodiments, the fourth message is used to indicate the arrival of downlink data at the terminal. In one example, the fourth message may be a downlink data notification message. In one example, the downlink data notification message may carry parameters such as allocation and retention priority (ARP) and EBI.

[0354] In some embodiments, when the S-GW receives downlink data for a terminal (such as downlink data packetization, downlink control signaling, etc.), if the S-GW context information indicates that there is no downlink user plane TEID pointing to the MME, the S-GW stores the downlink data and identifies which MME is currently serving the terminal. The S-GW then sends a fourth message to the MME that has a control plane connection with the terminal to notify the MME of the arrival of the downlink data of the terminal.

[0355] In some embodiments, after the S-GW notifies the MME that the downlink data has arrived, the connection between the satellite and the ground station is about to be disconnected and the feeder link is unavailable.

[0356] In step S3303, the MME detects that the feeder link is unavailable.

[0357] The optional implementation of step S3303 can refer to the optional implementation of step S3110 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0358] In step S3304, the MME sends the second information.

[0359] In some embodiments, the S-GW receives the second information.

[0360] In some embodiments, the second information is used to instruct the S-GW to store the downlink data sent to the terminal at the first time. In one example, the second information may be downlink buffering duration time information.

[0361] In some embodiments, the second information is determined based on the time during which the feeder link is unavailable. In one embodiment, the MME determines information B based on satellite ephemeris information or time information determined based on the satellite ephemeris information, and then determines the second information based on information B. The MME then sends the second information to the S-GW to ensure that downlink data can be stored at the S-GW during the period during which the feeder link is unavailable. In one example, the first time can be a period of time or a moment in time.

[0362] In some embodiments, the second information may be carried in a fifth message. In some embodiments, the fifth message is a confirmation message or a response message of the fourth message. In one example, the fifth message may be an acknowledgment message (downlink data notification ack) of the downlink data notification message.

[0363] In some embodiments, after step S3304, the connection between the satellite and the ground station is disconnected and the feeder link is unavailable. In this case, step S3305 is executed.

[0364] In step S3305, the S-GW stores the downlink data.

[0365] The optional implementation of step S3305 can refer to the optional implementation of step S3211 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0366] In step S3306, the MME detects that the feeder link is available.

[0367] The optional implementation of step S3306 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0368] In step S3307, the MME sends a sixth message.

[0369] In some embodiments, the terminal registered with the MME receives the sixth message through the eNB.

[0370] In some embodiments, the sixth message is used to page the terminal to notify the terminal of the arrival of downlink data.

[0371] In step S3308, the terminal sends the seventh message.

[0372] In some embodiments, the eNB receives the seventh message.

[0373] In some embodiments, the seventh message is used to establish a control plane connection. In one example, the seventh message may be a control plane service request message. Here, the seventh message is a NAS message.

[0374] In some embodiments, the seventh message is carried in an RRC message and sent to the eNB. In one example, the RRC message may be an RRCConnectionRequest message, and the fourth message may be a ControlPlaneServiceRequest message.

[0375] In some embodiments, the seventh message does not trigger the MME to establish a data radio bearer, and the MME may immediately send the downlink data it receives using the NAS PDU to the eNB.

[0376] In step S3309, the eNB sends an eighth message.

[0377] In some embodiments, the MME receives the eighth message.

[0378] In some embodiments, the eighth message is the seventh message forwarded by the eNB. In one example, the eighth message may be a control plane service request message.

[0379] In some embodiments, the eNB sends the eighth message to the MME via an S1-AP message. In one example, the S1-AP message may be an S1-AP initial UE message.

[0380] In step S3310, the MME sends a second message.

[0381] The optional implementation of step S3310 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0382] In step S3311, the S-GW sends a third message.

[0383] The optional implementation of step S3311 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0384] In step S3312, the S-GW sends downlink data.

[0385] The optional implementation of step S3312 can refer to the optional implementation of step S3109 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0386] In step S3313, the MME sends downlink data.

[0387] The optional implementation of step S3313 can refer to the optional implementation of step S3113 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0388] In some embodiments, after step S3313, the connection between the terminal and the satellite is disconnected or about to be disconnected, and the service link is unavailable. In this case, step S3314 is executed.

[0389] In step S3314, the eNB detects that the serving link is unavailable.

[0390] The optional implementation of step S3314 can refer to the optional implementation of step S3114 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0391] In step S3315, the eNB stores the downlink data.

[0392] The optional implementation of step S3315 can refer to the optional implementation of step S3115 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0393] In step S3316, the eNB detects that the serving link is available.

[0394] The optional implementation of step S3316 can refer to the optional implementation of step S3116 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0395] In step S3317, the eNB sends downlink data.

[0396] The optional implementation of step S3317 can refer to the optional implementation of step S3117 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0397] In some embodiments, after S3316, the RRC connection remains, at which point NAS PDUs can be used to transmit further uplink and downlink data. In one example, the terminal sends a NAS PDU encapsulated with uplink data to the eNB via an RRC message. The eNB then sends the NAS PDU to the MME via an S1-AP message. Upon receiving the NAS PDU, the MME checks its integrity, decrypts the uplink data contained in the NAS PDU, and then sends it to the S-GW.

[0398] In some embodiments, if there is no data transmission for a period of time, the eNB initiates an S1 release procedure or a connection suspension procedure, and the terminal enters the ECM_IDLE state.

[0399] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3317. For example, the combination of steps S3303 to S3307 can be implemented as an independent embodiment. For example, the combination of steps S3314 to S3317 can be implemented as an independent embodiment. For example, the combination of steps S3301 to S3309, steps S3312 to S3313, and step S3317 can be implemented as an independent embodiment. For example, the combination of steps S3301 to S3302, steps S3307 to S3313, and step S3317 can be implemented as an independent embodiment. For example, the combination of steps S3301 to S3302, steps S3307 to S3309, and steps S3312 to S3317 can be implemented as an independent embodiment. For example, the combination of steps S3301 to S3317 can be implemented as an independent embodiment. It should be noted that one or more steps from step S3301 to step S3317 may constitute an independent embodiment, but are not limited thereto.

[0400] In some embodiments, steps S3303 to S3306 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0401] In some embodiments, steps S3310 to S3311 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0402] In some embodiments, steps S3314 to S3316 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0403] As shown in Figure 3D, Figure 3D is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is executed by the above-mentioned communication system 100. The above-mentioned communication method includes steps S3401 to S3417.

[0404] In the embodiments of the present disclosure, the core network is taken as EPC as an example for description.

[0405] In some embodiments, the EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW, and the second core network element is an MME.

[0406] In some embodiments, an access network is described as an E-UTRAN. A first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0407] In some embodiments, as shown in FIG4A , both the S-GW and the MME are deployed on the ground.

[0408] In one embodiment, the connection between the onboard eNB and the MME via the ground station is an S1-MME connection.

[0409] In one embodiment, the connection between the MME and the S-GW is an S11-U connection.

[0410] In some embodiments, the satellite link may include a service link and a feeder link.

[0411] In the embodiment of the present disclosure, the first network element may be one of the second core network element and the first access network element.

[0412] The following describes the data transmission process received by the terminal (MT).

[0413] In step S3401, the S-GW receives downlink data.

[0414] In some embodiments, the terminal is connected to the EPS and is in an idle state (ECM-IDLE).

[0415] In step S3402, the S-GW sends a fourth message.

[0416] The optional implementation of step S3402 can refer to the optional implementation of step S3302 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0417] In step S3403, the MME sends a fifth message.

[0418] In some embodiments, the S-GW receives the fifth message.

[0419] In some embodiments, the fifth message is an acknowledgment message or a response message of the fourth message. In one example, the fifth message may be a downlink data notification ack message.

[0420] In step S3404, the MME sends a second message.

[0421] The optional implementation of step S3404 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0422] In step S3405, the S-GW sends a third message.

[0423] The optional implementation of step S3405 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0424] In step S3406, the S-GW sends downlink data.

[0425] The optional implementation of step S3406 can refer to the optional implementation of step S3109 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0426] In some embodiments, after step S33406, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. In this case, step S3407 is executed.

[0427] In step S3407, the MME detects that the feeder link is unavailable.

[0428] The optional implementation of step S3407 can refer to the optional implementation of step S3110 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0429] In step S3408, the MME stores the downlink data.

[0430] The optional implementation of step S3408 can refer to the optional implementation of step S3111 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0431] In step S3409, the MME detects that the feeder link is available.

[0432] The optional implementation of step S3409 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0433] In step S3410, the MME sends a sixth message.

[0434] The optional implementation of step S3410 can refer to the optional implementation of step S3306 in Figure 3C and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0435] In step S3411, the terminal sends the seventh message.

[0436] The optional implementation of step S3411 can refer to the optional implementation of step S3307 in Figure 3C and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0437] In step S3412, the eNB sends an eighth message.

[0438] The optional implementation of step S3412 can refer to the optional implementation of step S3308 in Figure 3C and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0439] In step S3413, the MME sends downlink data.

[0440] The optional implementation of step S3413 can refer to the optional implementation of step S3113 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0441] In some embodiments, after step S3413, the connection between the terminal and the satellite is disconnected or about to be disconnected, and the service link is unavailable. In this case, step S3414 is executed.

[0442] In step S3414, the eNB detects that the serving link is unavailable.

[0443] The optional implementation of step S3414 can refer to the optional implementation of step S3114 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0444] In step S3415, the eNB stores the downlink data.

[0445] The optional implementation of step S3415 can refer to the optional implementation of step S3115 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0446] In step S3416, the eNB detects that the serving link is available.

[0447] The optional implementation of step S3416 can refer to the optional implementation of step S3116 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0448] In step S3417, the eNB sends downlink data.

[0449] The optional implementation of step S3417 can refer to the optional implementation of step S3117 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0450] In some embodiments, after S3417, the RRC connection remains, at which point NAS PDUs can be used to transmit further uplink and downlink data. In one example, the terminal sends a NAS PDU encapsulated with uplink data to the eNB via an RRC message. The eNB then sends the NAS PDU to the MME via an S1-AP message. Upon receiving the NAS PDU, the MME checks its integrity, decrypts the uplink data contained in the NAS PDU, and then sends it to the S-GW.

[0451] In some embodiments, if there is no data transmission for a period of time, the eNB initiates an S1 release procedure or a connection suspension procedure, and the terminal enters the ECM_IDLE state.

[0452] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3417. For example, the combination of steps S3407 to S3409 can be implemented as an independent embodiment. For example, the combination of steps S3414 to S3416 can be implemented as an independent embodiment. For example, the combination of steps S3401 to S3408 can be implemented as an independent embodiment. For example, the combination of steps S3401 to S3413 and step S3417 can be implemented as an independent embodiment. For example, the combination of steps S3401 to S3406, steps S3410 to S3413, and step S3417 can be implemented as an independent embodiment. For example, the combination of steps S3401 to S3406, steps S3410, to S3417 can be implemented as an independent embodiment. For example, the combination of steps S3401 to S3413 and step S3417 can be implemented as an independent embodiment. For example, the combination of step S3401 to step S3417 can be implemented as an independent embodiment. It should be noted that one or more steps in step S3401 to step S3417 may constitute a possible independent embodiment, but are not limited thereto.

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

[0454] In some embodiments, steps S3407 to S3409 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0455] In some embodiments, steps S3415 to S3417 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0457] In some embodiments, terms such as "release," "suspend," "pause," and "suspend" may be used interchangeably.

[0458] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0459] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0460] In some embodiments, the terms "carry", "include", "contain", "encapsulate", etc. can be used interchangeably.

[0461] In some embodiments, the terms "bearer", "radio bearer", "connection", "resource" and the like may be used interchangeably.

[0462] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0463] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

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

[0465] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0466] As shown in Figure 5A, Figure 5A is a schematic diagram of an implementation flow of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method, which is performed by a first network element. The above communication method includes steps S5101 to S5110.

[0467] In some embodiments, the first network element may be the first access network element in the above embodiment. In one example, the access network is E-UTRAN, and the first access network element is an eNB.

[0468] In some embodiments, the first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0469] In one example, taking the core network as EPC, the EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW, and the second core network element is an MME.

[0470] In some embodiments, the satellite link may include a service link and a feeder link.

[0471] In some embodiments, for a data transmission process initiated by a terminal (MO), the first network element executes steps S5101 to S5110.

[0472] In step S5101, uplink data is received.

[0473] The optional implementation of step S5101 can refer to the optional implementation of step S3101 in Figure 3A, and other related parts of the embodiment involved in Figure 3A, which will not be repeated here.

[0474] In some embodiments, after step S5101, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. In this case, step S5102 is executed.

[0475] In step S5102, it is detected that the feeder link is unavailable.

[0476] The optional implementation of step S5102 can refer to the optional implementation of step S3102 in Figure 3A, and other related parts of the embodiment involved in Figure 3A, which will not be repeated here.

[0477] In step S5103, the uplink data is stored.

[0478] The optional implementation of step S5103 can refer to the optional implementation of step S3103 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0479] In step S5104, it is detected whether the feeder link is available.

[0480] The optional implementation of step S5104 can refer to the optional implementation of step S3104 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0481] In step S5105, uplink data is sent.

[0482] The optional implementation of step S5103 can refer to the optional implementation of step S3103 in Figure 3A, the optional implementation of step S3205 in Figure 3B, and other related parts in the embodiments involved in Figures 3A and 3B, which will not be repeated here.

[0483] In step S5106, downlink data is received.

[0484] The optional implementation of step S5106 can refer to the optional implementation of step S3113 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0485] In some embodiments, after step S5106, the connection between the terminal and the satellite is disconnected or about to be disconnected, and the service link is unavailable. In this case, step S5107 is executed.

[0486] In step S5107, it is detected that the service link is unavailable.

[0487] The optional implementation of step S5107 can refer to the optional implementation of step S3114 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0488] In step S5108, the downlink data is stored.

[0489] The optional implementation of step S5108 can refer to the optional implementation of step S3115 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0490] In step S5109, it is detected that the service link is available.

[0491] The optional implementation of step S5109 can refer to the optional implementation of step S3116 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0492] In step S5110, downlink data is sent.

[0493] The optional implementation of step S5110 can refer to the optional implementation of step S3117 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0494] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5110. For example, the combination of steps S5101 to S5105 can be implemented as an independent embodiment. For example, the combination of steps S5106 to S5110 can be implemented as an independent embodiment. For example, the combination of steps S5101 to S5105 and step S5110 can be implemented as an independent embodiment. For example, the combination of steps S5101, S5106 to S5110 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S5101 to S5110 may form a possible independent embodiment, but are not limited to this.

[0495] In some embodiments, steps S5102 to S5104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0496] In some embodiments, steps S5107 to S5109 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0497] As shown in Figure 5B, Figure 5B is a schematic diagram of an implementation flow of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method, which is performed by a first network element. The above communication method includes steps S5201 to S5208.

[0498] In some embodiments, the first network element may be the first access network element in the above embodiment. In one example, the access network is E-UTRAN, and the first access network element is an eNB.

[0499] In some embodiments, the first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0500] In one example, taking the core network as EPC, the EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW, and the second core network element is an MME.

[0501] In some embodiments, the satellite link may include a service link.

[0502] In some embodiments, for a data transmission process received by a terminal (MT), the first network element executes steps S5201 to S5208.

[0503] In step S5201, the sixth message is forwarded.

[0504] The optional implementation of step S5201 can refer to the optional implementation of step S3307 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0505] In step S5202, the seventh message is received.

[0506] The optional implementation of step S5202 can refer to the optional implementation of step S3308 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0507] In step S5203, the eighth message is sent.

[0508] The optional implementation of step S5203 can refer to the optional implementation of step S3309 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0509] In step S5204, downlink data is received.

[0510] The optional implementation of step S5204 can refer to the optional implementation of step S3113 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0511] In some embodiments, after step S5204, the connection between the terminal and the satellite is disconnected or about to be disconnected, and the service link is unavailable. In this case, step S5202 is executed.

[0512] In step S5205 , it is detected that the service link is unavailable.

[0513] The optional implementation of step S5205 can refer to the optional implementation of step S3114 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0514] In step S5206, the downlink data is stored.

[0515] The optional implementation of step S5206 can refer to the optional implementation of step S3115 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0516] In step S5207, it is detected that the service link is available.

[0517] The optional implementation of step S5207 can refer to the optional implementation of step S3116 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0518] In step S5208, downlink data is sent.

[0519] The optional implementation of step S5208 can refer to the optional implementation of step S3117 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0520] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5201 to S5208. For example, the combination of steps S5205 to S5208 can be implemented as an independent embodiment. For example, the combination of steps S5201 to S5204 and step S5208 can be implemented as an independent embodiment. For example, the combination of steps S5201 to S5208 and step S5113 can be implemented as an independent embodiment. It should be noted that one or more steps from steps S5201 to S5208 may constitute a possible independent embodiment, but are not limited to this.

[0521] As shown in Figure 5C, Figure 5C is a schematic diagram of an implementation process of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method, which is performed by a first network element. The above communication method includes steps S5301 to S5309.

[0522] In some embodiments, the first network element may be the second core network element in the above embodiments. In one example, taking the core network as EPC as an example, the second core network element is MME.

[0523] In some embodiments, the EPC may further include a first core network element. In one example, the first core network element is an S-GW.

[0524] In some embodiments, taking the access network as E-UTRAN as an example, a first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0525] In some embodiments, as shown in FIG4A , both the S-GW and the MME are deployed on the ground.

[0526] In one embodiment, the connection between the onboard eNB and the MME via the ground station is an S1-MME connection.

[0527] In one embodiment, the connection between the MME and the S-GW is an S11-U connection.

[0528] In some embodiments, the satellite link may be a feeder link.

[0529] In some embodiments, for a data transmission process initiated by a terminal (MO), the first network element executes steps S5301 to S5308.

[0530] In step S5301, uplink data is received.

[0531] The optional implementation of step S5301 can refer to the optional implementation of step S3105 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0532] In some embodiments, after step S5301, if no connection is established between the S-GW and the MME, a connection is established between the MME and the S-GW, and steps S5302 to S5303 are performed. Otherwise, step S5304 is performed.

[0533] In step S5302, a second message is sent.

[0534] The optional implementation of step S5302 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0535] In step S5303, the third message is received.

[0536] The optional implementation of step S5303 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0537] In step S5304, uplink data is sent.

[0538] The optional implementation of step S5304 can refer to the optional implementation of step S3108 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0539] In some embodiments, if the NAS release assistance information sent by the terminal indicates that no further downlink data transmission (i.e., downlink data transmission) is desired, then after step S5304, it means that all application layer data interaction has been completed via uplink data. In this case, steps S5305 to S5309 can be skipped. Otherwise, steps S5305 to S5309 are executed.

[0540] In step S5305, downlink data is received.

[0541] The optional implementation of step S5305 can refer to the optional implementation of step S3109 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0542] In some embodiments, after step S5305, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. In this case, step S5306 is executed.

[0543] In step S5306, it is detected that the feeder link is unavailable.

[0544] The optional implementation of step S5306 can refer to the optional implementation of step S3110 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0545] In step S5307, the downlink data is stored.

[0546] The optional implementation of step S5307 can refer to the optional implementation of step S3111 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0547] In step S5308, it is detected that the feeder link is available.

[0548] The optional implementation of step S5308 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0549] In step S5309, downlink data is sent.

[0550] The optional implementation of step S5309 can refer to the optional implementation of step S3113 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0551] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5301 to S5309. For example, the combination of steps S5301 and steps S5304 to S5309 can be implemented as an independent embodiment. For example, the combination of steps S5301 to S5305 and step S5309 can be implemented as an independent embodiment. For example, steps S5301 to S5309 can be implemented as an independent embodiment. It should be noted that one or more steps from steps S5301 to S5309 may constitute a possible independent embodiment, but are not limited to this.

[0552] In some embodiments, steps S5302 to S5303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0553] In some embodiments, steps S5306 to S5308 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0554] As shown in Figure 5D, Figure 5D is a schematic diagram of an implementation flow of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method, which is performed by a first network element. The above communication method includes steps S5401 to S5414.

[0555] In some embodiments, the first network element may be the second core network element in the above embodiments. In one example, taking the core network as EPC as an example, the second core network element is MME.

[0556] In some embodiments, the EPC may further include a first core network element. In one example, the first core network element is an S-GW.

[0557] In some embodiments, taking the access network as E-UTRAN as an example, a first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0558] In some embodiments, as shown in FIG4B , the S-GW is deployed on the ground, and the MME is deployed on a satellite. In this case, the MME may also be referred to as a satellite-borne MME.

[0559] In one embodiment, the connection between the onboard MME and the S-GW via the ground station is an S11-U connection.

[0560] In one embodiment, the connection between the eNB and the MME is an S1-MME connection.

[0561] In some embodiments, the satellite link may be a feeder link.

[0562] In some embodiments, for a data transmission process initiated by a terminal (MO), the first network element executes steps S5401 to S5414.

[0563] In step S5401, uplink data is received.

[0564] The optional implementation of step S5401 can refer to the optional implementation of step S3105 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0565] In step S5402, it is detected that the feeder link is unavailable.

[0566] The optional implementation of step S5402 can refer to the optional implementation of step S3203 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0567] In step S5403, the uplink data is stored.

[0568] The optional implementation of step S5403 can refer to the optional implementation of step S3204 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0569] In step S5404, it is detected that the feeder link is available.

[0570] The optional implementation of step S5404 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0571] In some embodiments, after step S5404, if a connection is not established between the S-GW and the MME, a connection is established between the MME and the S-GW, and steps S5405 to S5406 are executed.

[0572] In step S5405, the second message is sent.

[0573] The optional implementation of step S5405 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0574] In step S5406, a third message is received.

[0575] The optional implementation of step S5406 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0576] In step S5407, uplink data is sent.

[0577] The optional implementation of step S5407 can refer to the optional implementation of step S3208 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0578] In some embodiments, if the NAS release assistance information sent by the terminal indicates that no further downlink data transmission (i.e., downlink data transmission) is desired, then after step S5407, it means that all application layer data interaction has been completed via uplink data. In this case, steps S5406 to S5414 can be skipped. Otherwise, step S5406 is executed.

[0579] In step S5408, it is detected that the feeder link is unavailable.

[0580] The optional implementation of step S5408 can refer to the optional implementation of step S3110 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0581] In some embodiments, in step S5408, when the MME detects that the feeder link is about to become unavailable, the MME executes step S5409.

[0582] In step S5409, the second information is sent.

[0583] The optional implementation of step S5409 can refer to the optional implementation of step S3210 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0584] In step S5410, it is detected that the feeder link is available.

[0585] The optional implementation of step S5410 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0586] In step S5411, the second message is sent.

[0587] The optional implementation of step S5411 can refer to the optional implementation of step S5306 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0588] In step S5412, a third message is received.

[0589] The optional implementation of step S5412 can refer to the optional implementation of step S5307 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0590] In step S5413, downlink data is received.

[0591] The optional implementation of step S5413 can refer to the optional implementation of step S3215 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0592] In step S5414, downlink data is sent.

[0593] The optional implementation of step S5414 can refer to the optional implementation of step S3216 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0594] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5401 to S5414. For example, the combination of steps S5401 to S5404 and step S5407 can be implemented as an independent embodiment. For example, the combination of steps S5409 to S5410 and steps S5413 to S5414 can be implemented as an independent embodiment. For example, the combination of steps S5401 to S5407 can be implemented as an independent embodiment. For example, the combination of steps S5408 to S5414 can be implemented as an independent embodiment. For example, the combination of steps S5401 to S5404, steps S5407 to S5410, and steps S5413 to S5414 can be implemented as an independent embodiment. For example, the combination of steps S5401 to S5404 and steps S5407 to S5414 can be implemented as an independent embodiment. For example, the combination of step S5401, step S5407 to step S5410, and step S5413 to step S5414 can be implemented as an independent embodiment. For example, the combination of step S5401, step S5407 to step S5414 can be implemented as an independent embodiment. For example, the combination of step S5401 to step S5414 can be implemented as an independent embodiment. It should be noted that one or more steps from step S5401 to step S5414 may constitute a possible independent embodiment, but are not limited to this.

[0595] In some embodiments, steps S5405 to S5406 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0596] In some embodiments, steps S5411 to S5412 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0597] As shown in Figure 5E, Figure 5E is a schematic diagram of an implementation flow of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method performed by a first network element. The above communication method includes steps S5501 to S5510.

[0598] In some embodiments, the first network element may be the second core network element in the above embodiments. In one example, taking the core network as EPC as an example, the second core network element is MME.

[0599] In some embodiments, the EPC may further include a first core network element. In one example, the first core network element is an S-GW.

[0600] In some embodiments, as shown in FIG4B , the S-GW is deployed on the ground, and the MME is deployed on a satellite. In this case, the MME may also be referred to as a satellite-borne MME.

[0601] In one embodiment, the connection between the onboard MME and the S-GW via the ground station is an S11-U connection.

[0602] In one embodiment, the connection between the eNB and the MME is an S1-MME connection.

[0603] In some embodiments, the satellite link may be a feeder link.

[0604] In some embodiments, taking the access network as E-UTRAN as an example, a first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0605] In some embodiments, for a data transmission process received by a terminal (MT), the first network element executes steps S5501 to S5514.

[0606] In step S5501, the fourth message is received.

[0607] The optional implementation of step S5501 can refer to the optional implementation of step S3302 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0608] In some embodiments, after the S-GW notifies the MME that the downlink data has arrived, the connection between the satellite and the ground station is about to be disconnected and the feeder link is unavailable.

[0609] In step S5502, it is detected that the feeder link is unavailable.

[0610] The optional implementation of step S5502 can refer to the optional implementation of step S3110 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0611] In step S5503, the second information is sent.

[0612] The optional implementation of step S5503 can refer to the optional implementation of step S3304 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0613] In some embodiments, after step S5503, the connection between the satellite and the ground station is disconnected and the feeder link is unavailable. In this case, step S5504 is executed.

[0614] In step S5504, it is detected whether the feeder link is available.

[0615] The optional implementation of step S5504 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0616] In step S5505, the sixth message is sent.

[0617] The optional implementation of step S5505 can refer to the optional implementation of step S3307 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0618] In step S5506, the eighth message is received.

[0619] The optional implementation of step S5506 can refer to the optional implementation of step S3309 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0620] In step S5507, the second message is sent.

[0621] The optional implementation of step S5507 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0622] In step S5508, a third message is received.

[0623] The optional implementation of step S5508 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0624] In step S5509, downlink data is received.

[0625] The optional implementation of step S5509 can refer to the optional implementation of step S3109 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0626] In step S5510, downlink data is sent.

[0627] The optional implementation of step S5510 can refer to the optional implementation of step S3113 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0628] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5501 to S5510. For example, the combination of steps S5502 to S5504 can be implemented as an independent embodiment. For example, the combination of steps S5501 to S5506 and steps S5509 to S5510 can be implemented as an independent embodiment. For example, the combination of steps S5501 to S5510 can be implemented as an independent embodiment. It should be noted that one or more steps from steps S5501 to S5510 may constitute a possible independent embodiment, but are not limited to this.

[0629] In some embodiments, steps S5507 to S5508 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0630] As shown in Figure 5F, Figure 5F is a schematic diagram of an implementation flow of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method performed by a first network element. The communication method includes steps S5601 to S5611.

[0631] In some embodiments, the first network element may be the second core network element in the above embodiments. In one example, taking the core network as EPC as an example, the second core network element is MME.

[0632] In some embodiments, the EPC may further include a first core network element. In one example, the first core network element is an S-GW.

[0633] In some embodiments, taking the access network as E-UTRAN as an example, a first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0634] In some embodiments, as shown in FIG4A , both the S-GW and the MME are deployed on the ground.

[0635] In one embodiment, the connection between the eNB and the MME through the ground station is an S1-MME connection.

[0636] In one embodiment, the connection between the MME and the S-GW is an S11-U connection.

[0637] In some embodiments, the satellite link may be a feeder link.

[0638] In some embodiments, for a data transmission process received by a terminal (MT), the first network element executes steps S5601 to S5608.

[0639] In step S5601, the fourth message is received.

[0640] The optional implementation of step S5601 can refer to the optional implementation of step S3302 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0641] In step S5602, the fifth message is sent.

[0642] The optional implementation of step S5602 can refer to the optional implementation of step S3403 in Figure 3D and other related parts in the embodiment involved in Figure 3D, which will not be repeated here.

[0643] In step S5603, a second message is sent.

[0644] The optional implementation of step S5603 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0645] In step S5604, a third message is received.

[0646] The optional implementation of step S5604 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0647] In step S5605, downlink data is received.

[0648] The optional implementation of step S5605 can refer to the optional implementation of step S3109 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0649] In some embodiments, after step S5605, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. In this case, step S5606 is executed.

[0650] In step S5606, it is detected that the feeder link is unavailable.

[0651] The optional implementation of step S5606 can refer to the optional implementation of step S3110 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0652] In step S5607, the downlink data is stored.

[0653] The optional implementation of step S5607 can refer to the optional implementation of step S3111 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0654] In step S5608, it is detected that the feeder link is available.

[0655] The optional implementation of step S5608 can refer to the optional implementation of step S3112 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0656] In step S5609, the sixth message is sent.

[0657] The optional implementation of step S5609 can refer to the optional implementation of step S3306 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0658] In step S5610, the eighth message is received.

[0659] The optional implementation of step S5610 can refer to the optional implementation of step S3308 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0660] In step S5611, downlink data is sent.

[0661] The optional implementation of step S5611 can refer to the optional implementation of step S3113 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0662] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5601 to S5611. For example, the combination of steps S5606 to S5608 can be implemented as an independent embodiment. For example, the combination of steps S5601 to S5602 and steps S5605 to S5611 can be implemented as an independent embodiment. For example, the combination of steps S5601 to S5605 and steps S5609 to S5611 can be implemented as an independent embodiment. For example, the combination of steps S5601 to S5611 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S5601 to S5611 may form a possible independent embodiment, but are not limited to this.

[0663] In some embodiments, steps S5603 to S5604 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0664] As shown in Figure 6A, Figure 6A is a schematic diagram of an implementation process of a communication method performed by a first core network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method, which is performed by a first core network element. The above communication method includes steps S6101 to S6105.

[0665] In some embodiments, the core network is an EPC as an example. The EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW and the second core network element is an MME.

[0666] In some embodiments, taking the access network as E-UTRAN as an example, a first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0667] In some embodiments, as shown in FIG4B , the S-GW is deployed on the ground, and the MME is deployed on a satellite. In this case, the MME may also be referred to as a satellite-borne MME.

[0668] In one embodiment, the connection between the onboard MME and the S-GW via the ground station is an S11-U connection.

[0669] In one embodiment, the connection between the eNB and the MME is an S1-MME connection.

[0670] In some embodiments, the satellite link may be a feeder link.

[0671] In some embodiments, for a data transmission process initiated by a terminal (MO), the first network element executes steps S6101 to S6105.

[0672] In step S6101, second information is received.

[0673] The optional implementation of step S6101 can refer to the optional implementation of step S3210 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0674] In step S6102, the downlink data is stored.

[0675] The optional implementation of step S6102 can refer to the optional implementation of step S3211 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0676] In step S6103, a second message is received.

[0677] The optional implementation of step S6103 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0678] In step S6104, a third message is sent.

[0679] The optional implementation of step S3214 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0680] In step S6105, downlink data is sent.

[0681] The optional implementation of step S6105 can refer to the optional implementation of step S3215 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0682] The communication method involved in the embodiments of the present disclosure may include at least one of steps S6101 to S6105. For example, the combination of steps S6101 to S6102 and step S6105 may be implemented as an independent embodiment. For example, the combination of steps S6101 to S6105 may be implemented as an independent embodiment. It should be noted that one or more of steps S6101 to S6105 may constitute a possible independent embodiment, but is not limited to this.

[0683] In some embodiments, steps S6103 to S6104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0684] As shown in Figure 6B, Figure 6B is a schematic diagram of an implementation process of a communication method performed by a first core network element according to an embodiment of the present disclosure. The present embodiment of the present disclosure relates to a communication method, which is performed by a first core network element. The above communication method includes steps S6201 to S6207.

[0685] In some embodiments, the core network is an EPC as an example. The EPC may include a first core network element and a second core network element. In one example, the first core network element is an S-GW and the second core network element is an MME.

[0686] In some embodiments, as shown in FIG4B , the S-GW is deployed on the ground, and the MME is deployed on a satellite. In this case, the MME may also be referred to as a satellite-borne MME.

[0687] In one embodiment, the connection between the onboard MME and the S-GW via the ground station is an S11-U connection.

[0688] In one embodiment, the connection between the eNB and the MME is an S1-MME connection.

[0689] In some embodiments, the satellite link may be a feeder link.

[0690] In some embodiments, taking the access network as E-UTRAN as an example, a first access network element in the E-UTRAN is deployed on a satellite. In one example, the first access network element is a satellite-borne eNB.

[0691] In some embodiments, for a data transmission process received by a terminal (MT), the first network element executes steps S6201 to S6207.

[0692] In step S6201, downlink data is received.

[0693] The optional implementation of step S6201 can refer to the optional implementation of step S3301 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0694] In step S6202, the fourth message is sent.

[0695] The optional implementation of step S6202 can refer to the optional implementation of step S3302 in Figure 3C and other related parts in the embodiment involved in Figure 3C, which will not be repeated here.

[0696] In step S6203, the second information is received.

[0697] The optional implementation of step S6203 can refer to the optional implementation of step S3210 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0698] In step S6204, the downlink data is stored.

[0699] The optional implementation of step S6204 can refer to the optional implementation of step S3211 in Figure 3B and other related parts in the embodiment involved in Figure 3B, which will not be repeated here.

[0700] In step S6205, a second message is received.

[0701] The optional implementation of step S6205 can refer to the optional implementation of step S3106 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0702] In step S6206, a third message is sent.

[0703] The optional implementation of step S6206 can refer to the optional implementation of step S3107 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0704] In step S6207, downlink data is sent.

[0705] The optional implementation of step S6207 can refer to the optional implementation of step S3109 in Figure 3A and other related parts in the embodiment involved in Figure 3A, which will not be repeated here.

[0706] The communication method involved in the embodiments of the present disclosure may include at least one of steps S6201 to S6207. For example, the combination of steps S6201 to S6204 and step S6107 may be implemented as an independent embodiment. For example, the combination of steps S6201 to S6207 may be implemented as an independent embodiment. It should be noted that one or more of steps S6201 to S6207 may constitute a possible independent embodiment, but is not limited to this.

[0707] In some embodiments, steps S6205 to S6206 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0708] As shown in Figure 7A, Figure 7A is another flow diagram of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment relates to a communication method, which is performed by a first network element. The communication method of the present embodiment includes steps S7101 to S7102.

[0709] In step S7101, it is detected that the satellite link is unavailable.

[0710] For optional implementations of step S7101, please refer to steps S3102, S3110 and S3114 in Figure 3A, steps S3203, S3209 and S3217 in Figure 3B, steps S3303 and S3314 in Figure 3C, steps S3407 and S3415 in Figure 3D, and other related parts in the embodiments involved in Figures 3A, 3B, 3C and 3D, which will not be repeated here.

[0711] In step S7102, data is stored.

[0712] For optional implementations of step S7102, please refer to steps S3103, S3111 and S3115 in Figure 3A, steps S3204 and S3218 in Figure 3B, step S3315 in Figure 3C, steps S3408 and S3416 in Figure 3D, and other related parts in the embodiments involved in Figures 3A, 3B, 3C and 3D, which will not be repeated here.

[0713] In some embodiments, the above method may include the method described in the above embodiments on the communication system side and the first network element side, which will not be repeated here.

[0714] As shown in Figure 7B, Figure 7B is another flow diagram of a communication method performed by a first network element according to an embodiment of the present disclosure. The present embodiment relates to a communication method, which is performed by a first network element. The communication method of the present embodiment includes steps S7201 to S7202.

[0715] In step S7201, it is detected that the satellite link is unavailable.

[0716] For optional implementations of step S7201, please refer to steps S3102, S3110 and S3114 in Figure 3A, steps S3203, S3209 and S3217 in Figure 3B, steps S3303 and S3314 in Figure 3C, steps S3407 and S3415 in Figure 3D, and other related parts in the embodiments involved in Figures 3A, 3B, 3C and 3D, which will not be repeated here.

[0717] In step S7202, the first core network element is instructed to store data.

[0718] Optional implementations of step S7202 may refer to step S3210 in FIG. 3B , step S3304 in FIG. 3C , and other related parts in the embodiments involved in FIG. 3B and FIG. 3C , which will not be described in detail here.

[0719] In some embodiments, the above method may include the method described in the above embodiments on the communication system side and the first network element side, which will not be repeated here.

[0720] As shown in Figure 8, Figure 8 is another flow diagram of a communication method executed by a first core network element according to an embodiment of the present disclosure. The present embodiment relates to a communication method, which is executed by a first core network element. The communication method of the present embodiment includes step S801.

[0721] In step S801, second information is received.

[0722] Optional implementations of step S801 may refer to step S3211 in FIG. 3B , step S3305 in FIG. 3C , and other related parts in the embodiments involved in FIG. 3B and FIG. 3C , which will not be described in detail here.

[0723] In some embodiments, the above method may include the method described in the above embodiments on the communication system side and the first core network element side, which will not be repeated here.

[0724] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device) in any of the above methods.

[0725] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions, and in actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0726] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a CPU, a microprocessor, a graphics processing unit (GPU) (also understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0727] As shown in Figure 9A, Figure 9A is a schematic diagram illustrating the structure of a communication device according to an embodiment of the present disclosure. The structure of the communication device 91 may be as shown in Figure 9A. The communication device 91 includes a processing module 9101. In some embodiments, the processing module 9101 is configured to detect that a satellite link is unavailable; perform one of the following: store data; or instruct a first core network element to store data. The satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and a satellite. Optionally, the above-mentioned processing module 9102 is used to execute at least one of the other steps performed by the first network in any of the above methods (for example, step S3102, step S3103, step S3104, step S3110, step S3111, step S3112, step S3114, step S3115, step S3116, step S3203, step S3204, step S3205, step S3209, step S3212, step S3217, step S3218, step S3219, step S3303, step S3306, step S3314, step S3315, step S3316, step S3407, step S3408, step S3409, step S3414, step S3415, step S3416, but not limited to these), which will not be repeated here. In some embodiments, the communication device 91 further includes: a transceiver module 9102. In some embodiments, the transceiver module 9102 is used to send a second information, and the second information is used to instruct the first core network element to store the downlink data sent to the terminal at the first time, wherein the second information is determined according to the time when the feeder link between the satellite and the ground station is unavailable. Optionally, the above-mentioned transceiver module 9102 is used to execute the communication steps such as sending and / or receiving performed by the first network in any of the above methods (for example, step S3101, step S3105, step S3106, step S3107, step S3108, step S3109, step S3113, step S3117, step S3201, step S3202, step S3206, step S3207, step S3208, step S3210, step S3213, step S3214 3214, step S3216, step S3220, step S3302, step S3304, step S3307, step S3309, step S3310, step S3313, step S3317, step S3402, step S3403, step S3404, step S3405, step S3406, step S3410, step S3412, step S3413, step S3417, but not limited to these), no further details are given here.

[0728] As shown in Figure 9B, Figure 9B is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. The structure of the communication device 92 may be as shown in Figure 9B. The communication device 92 may include a transceiver module 9201. In some embodiments, the transceiver module 9201 is configured to receive second information, the second information being configured to instruct a first core network element to store downlink data sent to a terminal at a first time, wherein the second information is determined based on the time at which the feeder link between the satellite and the ground station is unavailable. Optionally, the transceiver module 9201 is configured to execute at least one of the communication steps of sending and / or receiving performed by the first core network element in any of the above methods (e.g., step S3106, step S3107, step S3108, step S3109, step S3206, step S3207, step S3208, step S3210, step S3213, step S3214, step S3215, step S3301, step S3302, step S3304, step S3310, step S3311, step S3312, step S3401, step S3402, step S3403, step S3404, step S3405, and step S3406, but not limited thereto), which are not further described herein. In some embodiments, the communication device 92 further includes: a processing module 9202. In some embodiments, the processing module 9202 is configured to store, at a first time, the downlink data sent to the terminal based on the second information. Optionally, the processing module 9202 is configured to execute at least one of the other steps (e.g., step S3211 and step S3305, but not limited thereto) performed by the first core network in any of the above methods, which are not further described herein.

[0729] In some embodiments, the transceiver module may include a transceiver module 9102 and / or a transceiver module 9201. The transceiver module 9102 and the transceiver module 9201 may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0730] As shown in Figure 10A, Figure 10A is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure. Network device 1010 can be a first network element, a first core network element, or a chip, chip system, or processor that supports the first network element to implement any of the above methods. Network device 1010 can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0731] As shown in Figure 10A, network device 1010 includes one or more processors 1011. Processor 1011 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data.

[0732] In some embodiments, the network device 1010 further includes one or more transceivers 1012. When the network device 1010 includes one or more transceivers 1012, the transceiver 1012 performs the communication steps of sending and / or receiving in the above method (e.g., step S3101, step S3105, step S3106, step S3107, step S3108, step S3109, step S3113, step S3117, step S3201, step S3202, step S3206, step S3207, step S3208, step S3210, step S3213, step S3214, step S3215, step S3216, step S3217). 5. At least one of step S3216, step S3220, step S3301, step S3302, step S3304, step S3307, step S3309, step S3310, step S3311, step S3312, step S3313, step S3317, step S3401, step S3402, step S3403, step S3404, step S3405, step S3406, step S3410, step S3412, step S3413, and step S3417, but not limited to these). Processor 1011 executes at least one of the other steps (for example, step S3102, step S3103, step S3104, step S3110, step S3111, step S3112, step S3114, step S3115, step S3116, step S3203, step S3204, step S3205, step S3209, step S3211, step S3212, step S3217, step S3218, step S3219, step S3303, step S3305, step S3306, step S3314, step S3315, step S3316, step S3407, step S3408, step S3409, step S3414, step S3415, step S3416, but not limited to these). In an optional embodiment, the transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0733] In some embodiments, network device 1010 also includes one or more memories 1013 for storing data. Optionally, all or part of memory 1013 may be located outside of network device 1010. In alternative embodiments, network device 1010 may include one or more interface circuits 1014. Interface circuits 1014 are optionally connected to memory 1013 and can be used to receive data from memory 1013 or other devices, or to send data to memory 1013 or other devices. For example, interface circuit 1014 can read data stored in memory 1013 and send the data to processor 1011.

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

[0735] As shown in Figure 10B, Figure 10B is a schematic diagram of a chip structure according to an embodiment of the present disclosure. If the network device 1010 can be a chip or a chip system, please refer to the schematic diagram of the chip structure 1020 shown in Figure 10B, but it is not limited thereto.

[0736] In some embodiments, chip 1020 may include one or more processors 1021 .

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

[0738] In some embodiments, the interface circuit 1022 performs the communication steps of sending and / or receiving in the above method (e.g., step S3101, step S3105, step S3106, step S3107, step S3108, step S3109, step S3113, step S3117, step S3201, step S3202, step S3206, step S3207, step S3208, step S3210, step S3213, step S3214, step S3215, step S3217). 6. At least one of step S3220, step S3301, step S3302, step S3304, step S3307, step S3309, step S3310, step S3311, step S3312, step S3313, step S3317, step S3401, step S3402, step S3403, step S3404, step S3405, step S3406, step S3410, step S3412, step S3413, and step S3417, but not limited thereto). The interface circuit 1022 performing the communication steps of sending and / or receiving in the above method, for example, means that the interface circuit 1022 performs data exchange between the processor 1021, chip 1020, memory 1023, or transceiver device. In some embodiments, the processor 9201 performs other steps (e.g., step S3101, step S3105, step S3106, step S3107, step S3108, step S3109, step S3113, step S3117, step S3201, step S3202, step S3206, step S3207, step S3208, step S3210, step S3213, step S3214, step S3215, step S3216, step S322 0, step S3301, step S3302, step S3304, step S3307, step S3309, step S3310, step S3311, step S3312, step S3313, step S3317, step S3401, step S3402, step S3403, step S3404, step S3405, step S3406, step S3410, step S3412, step S3413, step S3417, but not limited to these).

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

[0740] The embodiment of the present disclosure further provides a program product, which, when executed by the network device 1010, enables the network device 1010 to perform any of the above methods. Optionally, the program product is a computer program product.

[0741] The embodiments of the present disclosure also provide a computer program, which, when executed on a computer, enables the computer to execute any one of the above methods.

[0742] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. The embodiments disclosed herein are intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed in the embodiments disclosed herein. The specification and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

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

Claims

1. A communication method, performed by a first network element, the method comprising: Detecting that a satellite link is unavailable; Performing one of the following: Storing data; Instructing a first core network element to store data; Wherein, the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and the satellite.

2. The method according to claim 1, wherein The unavailability of the satellite link is determined according to first information, the first information comprising at least one of the following: Ephemeris information associated with the satellite; Time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

3. The method according to claim 1 or 2, wherein When the first network element is a first access network element, after detecting that the satellite link is unavailable, the storing data comprises at least one of the following: Storing uplink data sent by a terminal; Storing downlink data sent to the terminal.

4. The method according to claim 1 or 2, wherein When the first network element is a second core network element and the first network element is deployed on a satellite, after detecting that the satellite link is unavailable, the storing data comprises: Storing uplink data sent by a terminal.

5. The method according to claim 1 or 2, wherein When the first network element is a second core network element, after detecting that the satellite link is unavailable, the instructing the first core network element to store data comprises: Sending second information, the second information being used to instruct the first core network element to store downlink data sent to the terminal at a first time, wherein, the second information is determined according to the time when the feeder link is unavailable.

6. The method according to claim 5, wherein The second information is carried in a first message, the first message being used to release the connection between the first network element and the first core network element.

7. The method according to claim 6, wherein, The first message further carries third information, the third information being used to indicate that the reason for the connection release is the unavailability of the feeder link.

8. The method according to claim 1 or 2, wherein When the first network element is a second core network element and the first network element is deployed on the ground, after detecting that the satellite link is unavailable, the storing data comprises: Storing downlink data sent to the terminal.

9. The method according to any one of claims 1 to 8, wherein, After detecting that the satellite link is unavailable, the method further comprises: Detecting that the satellite link is available; Performing one of the following: Sending the stored data; Instructing the first core network element to send the stored data.

10. The method according to claim 9, wherein, The availability of the satellite link is determined according to first information, wherein, the first information comprises at least one of the following: Ephemeris information associated with the satellite; Time information determined based on the ephemeris information, the time information being used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

11. The method according to claim 9 or 10, wherein, When the first network element is a first access network element and the satellite link is the feeder link, after determining that the satellite link is available, the method further comprises: Sending the stored uplink data to a second core network element.

12. The method according to claim 9 or 10, wherein When the first network element is a first access network element and the satellite link is the service link, after determining that the satellite link is available, the method further comprises: Sending the stored downlink data to the terminal.

13. The method according to claim 9 or 10, wherein When the first network element is a second core network element and the first network element is deployed on the satellite, after determining that the satellite link is available, the method further includes: Sending the stored uplink data to the first core network element.

14. The method according to claim 9 or 10, wherein When the first network element is a second core network element and the first network element is deployed on the ground, after determining that the satellite link is available, the method further includes: Sending the stored downlink data to the first access network element.

15. The method according to claim 9 or 10, wherein, When the first network element is a second core network element, after determining that the satellite link is available, the instructing the first core network element to send the stored data includes: Sending a second message, where the second message is used to establish a connection between the first core network element and the second core network element, and the connection is used to receive the downlink data stored by the first core network element.

16. A communication method, performed by a first core network element, the method includes: Receiving second information, where the second information is used to indicate storing the downlink data sent to the terminal at a first time, and where the second information is determined according to the time when the feeder link between the satellite and the ground station is unavailable.

17. The method according to claim 16, wherein, The second information is carried in a first message, and the first message is used to release the connection between the second core network element and the first core network element.

18. The method according to claim 17, wherein The first message further carries third information, where the third information is used to indicate that the reason for the connection release is that the feeder link is unavailable.

19. The method according to claim 17, wherein, The method includes: Receiving a second message, where the second message is used to establish a connection between the second core network element and the first core network element; After the connection is established, sending the stored downlink data to the first network element.

20. The method according to any one of claims 16 to 19, wherein After receiving the second information, the method further includes: Receiving downlink data; Storing the downlink data within the first time.

21. A communication method, performed by a core network, the core network includes a first core network element and a second core network element; the method includes: The second core network element detects that the satellite link is unavailable; The second core network element performs one of the following: Storing data; Instructing the first core network element to store data; Where the satellite link is a feeder link between the satellite and the ground station or a service link between the terminal and the satellite.

22. The method according to claim 21, wherein, The satellite link being unavailable is determined according to first information, and the first information includes at least one of the following: Ephemeris information associated with the satellite; Time information determined based on the ephemeris information, where the time information is used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

23. The method according to claim 21 or 22, wherein, When the second core network element is deployed on the satellite, after the second core network element detects that the satellite link is unavailable, the second core network element storing data includes: The second core network element stores the uplink data sent by the terminal.

24. The method according to claim 21 or 22, wherein, After detecting that the satellite link is unavailable, the second core network element instructing the first core network element to store data includes: The second core network element sends second information, where the second information is used to instruct the first core network element to store downlink data sent to the terminal at a first time, and the second information is determined according to the time when the feeder link is unavailable.

25. The method according to claim 24, wherein, The second information is carried in a first message, and the first message is used to release the connection between the first network element and the first core network element.

26. The method according to claim 25, wherein The first message further carries third information, where the third information is used to indicate that the reason for the connection release is that the feeder link is unavailable.

27. The method according to claim 21 or 22, wherein When the second core network element is deployed on the ground, after the second core network element detects that the satellite link is unavailable, the data stored by the second core network element includes: The second core network element stores downlink data sent to the terminal.

28. The method according to any one of claims 21 to 27, wherein After the second core network element detects that the satellite link is unavailable, the method further includes: Detecting that the satellite link is available; Performing one of the following: Sending the stored data; Instructing the first core network element to send the stored data.

29. The method according to claim 28, wherein, The availability of the satellite link is determined according to first information, where the first information includes at least one of the following: Ephemeris information associated with the satellite; Time information determined based on the ephemeris information, where the time information is used to indicate the time when the satellite link is available and / or the time when the satellite link is unavailable.

30. The method according to claim 28 or 29, wherein, When the second core network element is deployed on the satellite, after the second core network element determines that the satellite link is available, the method further includes: The second core network element sends the stored uplink data to the first core network element.

31. The method according to claim 28 or 29, wherein, When the second core network element is deployed on the ground, after the second core network element determines that the satellite link is available, the method further includes: Sending the stored downlink data to a first access network element.

32. The method according to claim 28 or 29, wherein, The second core network element instructing the first core network element to send the stored data includes: The second core network element sends a second message, where the second message is used to establish a connection between the first core network element and the second core network element, and the connection is used to receive the downlink data stored by the first core network element.

33. A communication device, including: A processing module, configured to detect that the satellite link is unavailable; Performing one of the following: storing data; Instructing a first core network element to store data; where the satellite link is a feeder link between a satellite and a ground station or a service link between a terminal and the satellite.

34. A communication device, including: A transceiver module, configured to receive second information, where the second information is used to instruct to store downlink data sent to the terminal at a first time, and the second information is determined according to the time when the feeder link between the satellite and the ground station is unavailable.

35. A network device, including: One or more processors; One or more memories for storing instructions; Wherein, the processor is configured to call the instructions so that the network device executes the method according to any one of claims 1 to 15, 16 to 20.

36. A communication system, including: The first network element is configured to implement the communication method according to any one of claims 1 to 15; The first core network element is configured to implement the communication method according to any one of claims 16 to 20.

37. A storage medium, wherein, The storage medium stores instructions, wherein when the instructions are executed by a network device, the method according to any one of claims 1 to 15 and 16 to 20 can be executed.

Images