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

Abstract

The invention relates to a communication method, a communication device, network equipment, a communication system and a storage medium. The method comprises the following steps: detecting that a feeder line link between a satellite and a ground station is unavailable; and sending a first message, the first message being used for requesting the second network element to suspend a first connection, the first connection being a connection established between the first access network element and the first core network element for data transmission of the terminal. According to the invention, the storage and forwarding satellite operation of the communication system supporting satellite access is realized.

Description

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

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

[0002] The evolution of telecommunications network technology has seen the integration of non-terrestrial network (NTN) technologies and support for 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 connection can include intermittent connections between satellites and terminals, or between satellites and ground stations.

[0003]

[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 store and forward satellite operation 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 feeder link between a satellite and a ground station is unavailable; sending a first message, the first message being used to request a second network element to suspend a first connection, the first connection being a connection established between a first access network network element and a first core network network element for data transmission of a terminal.

[0007] According to the second aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a second network element. The method includes: receiving a first message, the first message is used to request to suspend a first connection, and the first connection is a connection established between a first access network network element and a first core network network element for data transmission of a terminal.

[0008] According to the third aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a first core network network element. The method includes: receiving a second message, the second information is used to indicate the release of a first connection, and the first connection is a connection established between the first access network network element and the first core network network element for data transmission of the terminal.

[0009] According to a fourth 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 feeder link between a satellite and a ground station is unavailable; the second core network network element sends a first message to a first access network element, wherein the first message is used to request the first access network element to suspend a first connection, wherein the first connection is a connection established between the first access network element and the first core network element for data transmission of a terminal.

[0010] According to the fifth aspect of an embodiment of the present disclosure, a communication device is proposed, including: a processing module for detecting that a feeder link between a satellite and a ground station is unavailable; a transceiver module for sending a first message, wherein the first message is used to request a second network element to suspend a first connection, and the first connection is a connection established between a first access network network element and a first core network network element for data transmission of a terminal.

[0011] According to the sixth aspect of an embodiment of the present disclosure, a communication device is proposed, including: a transceiver module for receiving a first message, the first message being used to request to suspend a first connection, the first connection being a connection established between a first access network element and a first core network element for data transmission of a terminal.

[0012] According to the seventh aspect of an embodiment of the present disclosure, a communication device is proposed, including: a transceiver module for receiving a second message, the second information being used to indicate the release of a first connection, the first connection being a connection established between a first access network element and a first core network element for data transmission of a terminal.

[0013] According to an eighth 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, second and third aspects.

[0014] According to the ninth aspect of an 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; a second network element, configured to implement the method as described in the second aspect; and a first core network network element, configured to implement the method as described in the third aspect.

[0015] According to the tenth 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 any method described in the first aspect, the second aspect, and the third aspect.

[0016] According to an eleventh aspect of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When executed by a network device, the instructions perform the method described in any one of the first, second, and third aspects.

[0017] The technical solution provided by the embodiments of the present disclosure implements store-and-forward satellite operations in a communication system supporting satellite access.

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

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

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

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

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

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

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

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

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

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

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

[0029] FIG7A is another schematic flow chart showing a communication method executed by a first network element side according to an embodiment of the present disclosure.

[0030] FIG7B is another schematic flow chart showing a communication method executed by a second network element side according to an embodiment of the present disclosure.

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

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

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

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

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

[0036] 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 feeder link between a satellite and a ground station is unavailable; sending a first message, the first message being used to request a second network element to suspend a first connection, the first connection being a connection established between a first access network network element and a first core network network element for data transmission of a terminal.

[0037] In the embodiment of the present disclosure, after detecting that the feeder link is unavailable, the first network element sends a first message to request the second network element to suspend the first connection established between the first access network network element and the first core network network element for data transmission of the terminal. In this way, in the event of an interruption of the satellite connection, data can be stored at the satellite and / or core network so that the stored data can be forwarded when the satellite connection is restored, thereby realizing storage and forwarding satellite operations and further launching delay-tolerant services.

[0038] In some possible implementations, the first message carries first information, where the first information is used to indicate that the feeder link is unavailable.

[0039] In some possible implementations, the method further includes: storing second information when the first connection is suspended; wherein the second information includes at least one of the following: data associated with the first connection, context of the terminal, and bearer context of the first connection.

[0040] In the embodiment of the present disclosure, the first network element stores the second information when the first connection is suspended, so that after the satellite connection is restored, the first connection can be restored in a timely manner, thereby forwarding the data stored in the satellite and / or core network when the first connection is suspended, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0041] In some possible implementations, the second information is also stored in the second network element.

[0042] In some possible implementations, when the first network element is a first access network element, the method further includes: when the first connection is suspended, maintaining the connection with the terminal.

[0043] In the embodiment of the present disclosure, when the first connection is suspended, the connection between the first access network element and the terminal is maintained, so that the terminal can still send uplink data to the first access network element, so that when the first connection is restored, the first access network element can forward the uplink data to the first core network element in a timely manner to continue the uplink data transmission, thereby realizing storage and forwarding satellite operations, and then launching delay-tolerant services.

[0044] In some possible implementations, after detecting that the feeder link between the satellite and the ground station is unavailable, the method further includes: receiving uplink data sent by the terminal; and storing the uplink data.

[0045] In the embodiment of the present disclosure, after detecting that the feeder link is unavailable, the first access network element can store the uplink data sent by the terminal. In this way, when the satellite connection is interrupted, the data can be stored at the satellite 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.

[0046] In some possible implementations, when the first network element is a second core network element, the method further includes: sending a second message, where the second message is used to instruct the first core network element to release the first connection.

[0047] In some possible implementations, the second message carries third information, and the third information is used to indicate the storage of downlink data sent to the terminal when the first connection is suspended. The third information is determined based on the satellite's ephemeris information and is used to indicate the storage duration of the downlink data.

[0048] In some possible implementations, the second message further carries fourth information, where the fourth information is used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable.

[0049] In some possible implementations, after sending the first message, the method further includes: detecting that the feeder link is available; and sending a third message, where the third message is used to request the second network element to restore the first connection.

[0050] In the embodiment of the present disclosure, after detecting that the feeder link is available, the first network element sends a third message to request the second network element to restore the first connection in order to forward the stored data. In this way, when the satellite connection is restored, the 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, the method further includes: after the first connection is restored, sending the stored uplink data to the first core network element.

[0052] In some possible implementations, when the first network element is a second core network element, the method further includes: sending a fourth message, the fourth message being used to instruct the first core network element to rebuild the first connection, the first connection being used by the first core network element to send stored downlink data to the terminal.

[0053] In the second aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a second network element. The method includes: receiving a first message, the first message is used to request to suspend a first connection, and the first connection is a connection established between a first access network network element and a first core network network element for data transmission of a terminal.

[0054] In some possible implementations, the first message carries first information, where the first information is used to indicate that the feeder link is unavailable.

[0055] In some possible implementations, the method further includes: when the first connection is suspended, storing second information, the second information including at least one of the following: data associated with the first connection, context of the terminal, and bearer context of the first connection.

[0056] In some possible implementations, the second information is also stored in the first network element.

[0057] In some possible implementations, when the second network element is a first access network element, the method further includes: maintaining the connection with the terminal when the first connection is suspended.

[0058] In a third 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 a second message, where the second information is used to indicate the release of a first connection, and the first connection is a connection established between the first access network network element and the first core network network element for data transmission of the terminal.

[0059] In some possible implementations, the second message carries third information, and the third information is used to indicate the storage of downlink data sent to the terminal when the first connection is suspended. The third information is determined based on the satellite's ephemeris information and is used to indicate the storage duration of the downlink data.

[0060] In some possible implementations, the second message further carries fourth information, where the fourth information is used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable.

[0061] In some possible implementations, the method includes: when the first connection is suspended, storing downlink data sent to the terminal.

[0062] In some possible implementations, the method further includes: receiving a fourth message, where the fourth message is used to request reestablishment of the first connection; and after the first connection is reestablished, sending the stored downlink data to the first access network element.

[0063] In a fourth 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 the feeder link between the satellite and the ground station is unavailable; the second core network network element sends a first message to the first access network network element, wherein the first message is used to request the first access network element to suspend a first connection, and the first connection is a connection established between the first access network network element and the first core network element for data transmission of the terminal.

[0064] In some possible implementations, the first message carries first information, where the first information is used to indicate that the feeder link is unavailable.

[0065] In some possible implementations, the method further includes: the second core network element storing second information when the first connection is suspended; wherein the second information includes at least one of the following: data associated with the first connection, the context of the terminal, and the bearer context of the first connection.

[0066] In some possible implementations, the second information is also stored in the first access network element.

[0067] In some possible implementations, the method further includes: the second core network element sending a second message to the first core network element, where the second message is used to instruct the first core network element to release the first connection.

[0068] In some possible implementations, the second message carries third information, and the third information is used to indicate the storage of downlink data sent to the terminal when the first connection is suspended. The third information is determined based on the satellite's ephemeris information and is used to indicate the storage duration of the downlink data.

[0069] In some possible implementations, the second message further carries fourth information, where the fourth information is used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable.

[0070] In some possible implementations, after the second core network network element sends the first message to the first access network network element, the method further includes: the second core network network element detects that the feeder link is available; the second core network network element sends a third message to the first access network network element, and the third message is used to request the second network element to restore the first connection.

[0071] In some possible implementations, the method also includes: the second core network element sends a fourth message to the first core network element, the fourth message is used to instruct the first core network element to rebuild the first connection, and the first connection is used by the first core network element to send stored downlink data to the terminal.

[0072] In some possible implementations, the method includes: when the first connection is suspended, the first core network element stores downlink data sent to the terminal.

[0073] In some possible implementations, the method further includes: after the first connection is reestablished, the first core network element sending the stored downlink data to the first access network element.

[0074] In a fifth 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.

[0075] In some possible implementations, the first message carries first information, where the first information is used to indicate that the feeder link is unavailable.

[0076] In some possible implementations, the processing module is further configured to store second information when the first connection is suspended; wherein the second information includes at least one of the following: data associated with the first connection, context of the terminal, and bearer context of the first connection.

[0077] In some possible implementations, the second information is also stored in the second network element.

[0078] In some possible implementations, when the first network element is a first access network element, the processing module is further configured to maintain the connection with the terminal when the first connection is suspended.

[0079] In some possible implementations, the transceiver module is further configured to receive uplink data sent by the terminal after the processing module detects that the feeder link between the satellite and the ground station is unavailable; the processing module is further configured to store the uplink data.

[0080] In some possible implementations, when the first network element is a second core network element, the transceiver module is further configured to send a second message, where the second message is configured to instruct the first core network element to release the first connection.

[0081] In some possible implementations, the second message carries third information, and the third information is used to indicate the storage of downlink data sent to the terminal when the first connection is suspended. The third information is determined based on the satellite's ephemeris information and is used to indicate the storage duration of the downlink data.

[0082] In some possible implementations, the second message further carries fourth information, where the fourth information is used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable.

[0083] In some possible implementations, the processing module is further configured to detect that the feeder link is available after the transceiver module sends the first message; the transceiver module is further configured to send a third message, where the third message is used to request the second network element to restore the first connection.

[0084] In some possible implementations, when the first network element is a first access network element, the transceiver module is further configured to send the stored uplink data to the first core network element after the first connection is restored.

[0085] In some possible implementations, when the first network element is the second core network element, the transceiver module is also used to send a fourth message, and the fourth message is used to instruct the first core network element to rebuild the first connection, and the first connection is used by the first core network element to send stored downlink data to the terminal.

[0086] In the sixth aspect, an embodiment of the present disclosure proposes a communication device, which is applied to a second network element. The device includes: a transceiver module, which is used to receive a first message, and the first message is used to request to suspend a first connection. The first connection is a connection established between the first access network network element and the first core network network element for data transmission of the terminal.

[0087] In some possible implementations, the first message carries first information, where the first information is used to indicate that the feeder link is unavailable.

[0088] In some possible implementations, the device further includes a processing module; the processing module is configured to store second information when the first connection is suspended, the second information including at least one of the following: data associated with the first connection, context of the terminal, and bearer context of the first connection.

[0089] In some possible implementations, the second information is also stored in the first network element.

[0090] In some possible implementations, when the second network element is a first access network element, the processing module is configured to maintain the connection with the terminal when the first connection is suspended.

[0091] In a seventh aspect, embodiments of the present disclosure provide a communication device, applied to a first core network element. The device includes: a transceiver module, configured to receive a second message, wherein the second message is configured to indicate the release of a first connection, where the first connection is a connection established between the first access network element and the first core network element for data transmission of a terminal.

[0092] In some possible implementations, the second message carries third information, and the third information is used to indicate the storage of downlink data sent to the terminal when the first connection is suspended. The third information is determined based on the satellite's ephemeris information and is used to indicate the storage duration of the downlink data.

[0093] In some possible implementations, the second message further carries fourth information, where the fourth information is used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable.

[0094] In some possible implementations, the device further includes a processing module; the processing module is configured to store downlink data sent to the terminal when the first connection is suspended.

[0095] In some possible implementations, the transceiver module is further configured to receive a fourth message, where the fourth message is used to request reestablishment of the first connection; and after the first connection is reestablished, send the stored downlink data to the first access network element.

[0096] In an eighth 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 aspect, the second aspect, and the third aspect and their possible implementations.

[0097] In the ninth 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 implementations; a first core network network element, configured to implement the method as described in the first aspect, the second aspect and the third aspect and any one of its possible implementations.

[0098] In a tenth aspect, an embodiment of the present disclosure provides a storage medium storing instructions that, when executed on a network device, cause the communication device to execute the method as described in any one of the first, second, and third aspects and their possible implementations.

[0099] In the eleventh aspect, an embodiment of the present disclosure proposes a computer program product. When the above-mentioned computer program product is executed by a communication device, the above-mentioned network device executes the method as described in any one of the first aspect, the second aspect and the third aspect and their possible implementations.

[0100] In a twelfth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a network device, enables the network device to execute the method as described in any one of the first aspect, the second aspect, and the third aspect and their possible implementations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] As shown in Figure 3A, Figure 3A is an exemplary interaction diagram illustrating 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 S3119.

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

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

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

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

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

[0164] In one embodiment, the connection between the ground station and the S-GW is an S1-U connection.

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

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

[0167] In some embodiments, the satellite link may comprise a feeder link.

[0168] In the embodiment of the present disclosure, the first network element is a first access network element, and the second network element is a second core network element.

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

[0170] In step S3101, the terminal sends a fifth message.

[0171] In some embodiments, the terminal is in an idle state (EPS connection management idle, ECM-IDLE).

[0172] In some embodiments, the MME receives the fifth message through the eNB.

[0173] In some embodiments, the fifth message is used for service request. In one example, the fifth message can be a service request message.

[0174] In some embodiments, the fifth message is a non-access stratum (NAS) message.

[0175] In some embodiments, the terminal sends the fifth message to the eNB, which then sends it to the MME.

[0176] In some embodiments, the eNB encapsulates the fifth message in an S1-AP message and sends it. In one example, the S1-AP message may be an initial UE message.

[0177] In some embodiments, the terminal encapsulates the fifth message into a radio resource control (RRC) message and sends it to the eNB. The eNB then encapsulates the fifth message into an S1-AP message and sends it to the MME.

[0178] In step S3102, the MME sends a sixth message.

[0179] In some embodiments, the eNB receives the sixth message.

[0180] In some embodiments, the sixth message is used to request the eNB to establish a first connection between the eNB and the S-GW for the terminal. The first connection is a connection established between the eNB and the S-GW for data transmission of the terminal.

[0181] In some embodiments, the sixth message is an S1-AP message. In one example, the seventh message may be an initial context setup request message.

[0182] In some embodiments, the sixth message may carry parameters such as the S-GW address and the S1 tunnel endpoint identifier (TEID) for uplink data. In one embodiment, the S-GW address, S1-TEID, and other parameters may be used to establish an S1-U bearer.

[0183] In step S3103, the eNB initiates a radio bearer establishment process.

[0184] In some embodiments, the eNB establishes a first connection for the terminal between itself and the S-GW, so that the terminal transmits data over the first connection.

[0185] In some embodiments, the terminal may send uplink data to the eNB through an RRC connection, and then the eNB may send the uplink data to the S-GW through the first connection.

[0186] In some embodiments, the eNB may send uplink data from the terminal to the S-GW according to parameters such as the S-GW address and S1-TEID.

[0187] In step S3104, the eNB sends a seventh message.

[0188] In some embodiments, the MME receives the seventh message.

[0189] In some embodiments, the seventh message is a response message to the sixth message. In one example, the seventh message may be an initial context setup complete message.

[0190] In some embodiments, the seventh message is a SI-AP message.

[0191] In some embodiments, the seventh message may carry parameters such as the eNB address and the S1-TEID of downlink data.

[0192] In some embodiments, after the first connection is established, the eNB sends a seventh message to the MME.

[0193] In step S3105 , the MME sends an eighth message.

[0194] In some embodiments, the S-GW receives the eighth message.

[0195] In some embodiments, the eighth message is used to request establishment of a first connection between the eNB and the S-GW for the terminal, such as an S1-U connection. In one example, the eighth message may be a modify bearer request message.

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

[0197] In some embodiments, the modify bearer request message may include parameters such as eNB address and S1-TEID of downlink data.

[0198] In some embodiments, after step S3105, the terminal may send uplink data to the S-GW via the first connection (e.g., the S1-U connection), in which case step S3106 is executed. Also, / or, the S-GW may send downlink data to the terminal via the first connection (e.g., the S1-U connection), in which case step S3107 is executed.

[0199] In step S3106, the terminal sends uplink data.

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

[0201] In some embodiments, the terminal sends uplink data to the S-GW through the first connection.

[0202] In some embodiments, the terminal sends uplink data to the eNB through an RRC connection, and the eNB then sends the uplink data to the S-GW through a first connection (such as an S1-U connection).

[0203] In step S3107, the S-GW sends downlink data.

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

[0205] In some embodiments, the S-GW sends downlink data to the terminal through the first connection.

[0206] In some embodiments, the S-GW sends downlink data to the eNB through a first connection (such as an S1-U connection), and the eNB then sends the downlink data to the terminal through an RRC connection.

[0207] In some embodiments, after step S3106 and / or step S3107, 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 S3108 is executed.

[0208] In step S3108, the eNB detects that the feeder link is unavailable.

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

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

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

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

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

[0214] 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 a feeder link is available and / or when the satellite link is unavailable. In one example, information A may indicate a period during which a feeder link is available or a time when the feeder link is available. In another example, information A may indicate a period during which a feeder link is unavailable or a time when the feeder link is unavailable.

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

[0216] In step S3109, the eNB sends a first message.

[0217] In some embodiments, the MME receives the first message.

[0218] In some embodiments, the eNB initiates the S1 connection suspension procedure.

[0219] In some embodiments, the first message is used to request the MME to suspend the first connection between the eNB and the S-GW. In one example, the first message may be an S1 connection suspend request message.

[0220] In some embodiments, the first message is an S1-AP message.

[0221] In some embodiments, the first message carries first information. In one embodiment, the first information is used to indicate that the reason for suspending the first connection is that the feeder link is unavailable. In one embodiment, the first information is used to indicate that the feeder link is unavailable.

[0222] In some embodiments, when the first connection is suspended, the eNB and the MME store second information. In one embodiment, the second information includes at least one of the following: data associated with the first connection, a terminal context, and a bearer context for the first connection. In one embodiment, the data associated with the first connection may be data transmitted via the first connection, data using the first connection, etc., which is not limited in the present embodiment.

[0223] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal.

[0224] In some embodiments, when the first connection is suspended, the eNB does not release the RRC connection between the eNB and the terminal.

[0225] In some embodiments, when the first connection is suspended, the eNB does not suspend the RRC connection with the terminal.

[0226] In some embodiments, after the first connection is suspended, the MME sends a response message to the eNB for the first message. In one example, the response message to the first message may be an S1 connection suspend response message.

[0227] In some embodiments, the response message to the first message is an S1-AP message.

[0228] In step S3110, the MME sends third information.

[0229] In some embodiments, the S-GW receives the third information.

[0230] In some embodiments, the third information is used to instruct to store downlink data sent to the terminal when the first connection is suspended.

[0231] In some embodiments, the third information is used to instruct to store downlink data sent to the terminal when the feeder link is unavailable.

[0232] In some embodiments, the third 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 third information may be downlink buffering duration time information.

[0233] In some embodiments, the third information is determined based on the time period during which the feeder link is unavailable. In one example, the eNB determines information A based on satellite ephemeris information or time information determined based on the satellite ephemeris information, and then determines the third information based on information A. The eNB then sends the third information to the MME, which in turn sends the third 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 period can be a time period or a moment.

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

[0235] In some embodiments, terms such as “the time when the feeder link is unavailable”, “the time when the first connection is suspended”, and “the first time” may be used interchangeably.

[0236] In some embodiments, the second message may further carry fourth information, and the fourth information may be used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable.

[0237] In some embodiments, after receiving the second message, the S-GW sends a response message to the second message to the MME. In one example, the response message to the second message may be a release access bearer response message.

[0238] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal, and the terminal can send uplink data to the eNB through the RRC connection. In this case, steps S3111 to S3112 can be performed.

[0239] In step S3111, the terminal sends uplink data.

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

[0241] In some embodiments, the terminal sends uplink data to the eNB through an RRC connection.

[0242] In step S3112, the eNB stores the uplink data.

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

[0244] In some embodiments, the eNB stores the uplink data after the first connection is suspended.

[0245] In some embodiments, the eNB stores the uplink data at the first time indicated by the third information.

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

[0247] In some embodiments, when the first connection is suspended, the S-GW receives downlink data, and at this time, steps S3113 to S3114 may be executed.

[0248] In step S3113, the S-GW receives downlink data.

[0249] In step S3114, the S-GW stores the downlink data.

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

[0251] In some embodiments, the S-GW stores the downlink data during the first suspended time period.

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

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

[0254] In some embodiments, after steps S3111 to S3112 and / or steps S3113 to S3114, step S3115 is performed.

[0255] In step S3115 , the eNB detects whether the feeder link is available.

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

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

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

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

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

[0261] In step S3116, the eNB sends a third message.

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

[0263] In some embodiments, the eNB initiates the S1 connection recovery procedure.

[0264] In some embodiments, the eNB initiates an S1 connection recovery procedure based on the stored second information to recover the first connection.

[0265] In some embodiments, the third message is used to request the MME to resume the first connection between the eNB and the S-GW. In one example, the first message may be an S1 connection resume request message.

[0266] In some embodiments, the third message is an S1-AP message.

[0267] In some embodiments, after the first connection is resumed, the MME sends a response message to the eNB for the third message. In one example, the response message to the first message may be an S1 connection resume response message.

[0268] In step S3117, the MME sends a fourth message.

[0269] In some embodiments, the S-GW receives the fourth message.

[0270] In some embodiments, the fourth message is used to request establishment of a first connection between the eNB and the S-GW, such as an S1-U connection. In one example, the fourth message may be a modify access bearer request message.

[0271] In some embodiments, the fourth message may include: an eNB address and a TEID of downlink data.

[0272] In some embodiments, after the first connection is established, the S-GW sends a response message of the fourth message to the MME. In one example, the response message of the fourth message may be a modify access bearer response message.

[0273] In some embodiments, after the first connection is established, the S-GW sends a modify access bearer response message to the MME.

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

[0275] In step S3118, the eNB sends uplink data.

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

[0277] In some embodiments, the eNB sends uplink data to the S-GW through the first connection.

[0278] In some embodiments, the eNB sends its own stored uplink data to the S-GW via a first connection (such as an S1-U connection) to achieve uplink data transmission.

[0279] In step S3119, the S-GW sends downlink data.

[0280] In some embodiments, the terminal receives downlink data through the eNB.

[0281] In some embodiments, the S-GW sends downlink data to the eNB through the first connection, and the eNB then sends the downlink data to the terminal.

[0282] In some embodiments, the S-GW sends the downlink data stored in itself to the eNB through a first connection (such as an S1-U connection), and the eNB sends the downlink data to the terminal to achieve downlink data transmission.

[0283] In some embodiments, if there is no further user plane data interaction, the eNB or MME triggers the S1 connection release procedure and the RRC connection release procedure. At this time, the terminal enters the idle state (ECM_IDLE).

[0284] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3119. For example, the combination of steps S3108 to S3110 can be implemented as an independent embodiment. For example, the combination of steps S3108 to S3118 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3106 and steps S3108 to S3118 can be implemented as an independent embodiment. For example, the combination of steps S3108 to S3110, steps S3113 to S3117, and step S3119 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3105, steps S3107 to S3110, steps S3113 to S3117, and step S3119 can be implemented as an independent embodiment. For example, the combination of steps S3108 to S3119 can be implemented as an independent embodiment. For example, the combination of step S3101 to step S3119 can be implemented as an independent embodiment. It should be noted that one or more steps in step S3101 to step S3119 may constitute a possible independent embodiment, but are not limited thereto.

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

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

[0287] In some embodiments, steps S3111 to S3112 and step S3118 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0289] In some embodiments, step S3106 and step S3107 can be exchanged in order or executed simultaneously, step S3111 to step S3112 and step S3113 to step S3114 can be exchanged in order or executed simultaneously, and step S3108 and step S3109 can be exchanged in order or executed simultaneously.

[0290] 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 S3219.

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

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

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

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

[0295] In one embodiment, the connection between the satellite-borne MME and the S-GWMME element via the ground station is an S11 connection.

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

[0297] In one embodiment, the connection between the satellite-borne eNB and the S-GW via the ground station is an S1-U connection.

[0298] In some embodiments, the satellite link may comprise a feeder link.

[0299] In the embodiment of the present disclosure, the first network element is a second core network element, and the second network element is a first access network element.

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

[0301] In step S3201, the terminal sends a fifth message.

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

[0303] In step S3202, the MME sends a sixth message.

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

[0305] In step S3203, the eNB initiates a radio bearer establishment process.

[0306] The optional implementation of step S3203 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.

[0307] In step S3204, the eNB sends a seventh message.

[0308] The optional implementation of step S3204 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.

[0309] In step S3205, the MME sends an eighth message.

[0310] The optional implementation of step S3205 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.

[0311] In some embodiments, after step S3205, the terminal may send uplink data to the S-GW via the first connection (e.g., the S1-U connection), in which case step S3206 is executed. And / or, the S-GW may send downlink data to the terminal via the first connection (e.g., the S1-U connection), in which case step S3207 is executed.

[0312] In step S3206, the terminal sends uplink data.

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

[0314] In step S3207, the S-GW sends downlink data.

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

[0316] In some embodiments, after step S3206 and / or step S3207, 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 S3208 is executed.

[0317] In step S3208, the MME detects that the feeder link is unavailable.

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

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

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

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

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

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

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

[0325] In step S3209, the MME sends a first message.

[0326] In some embodiments, the eNB receives the first message.

[0327] In some embodiments, the MME initiates the S1 connection suspension procedure.

[0328] In some embodiments, the first message is used to request the eNB to suspend the first connection between the eNB and the S-GW. In one example, the first message may be an S1 connection suspend request message.

[0329] In some embodiments, the first message is an S1-AP message.

[0330] In some embodiments, the first message carries first information. In one embodiment, the first information is used to indicate that the reason for suspending the first connection is that the feeder link is unavailable. In one embodiment, the first information is used to indicate that the feeder link is unavailable.

[0331] In some embodiments, when the first connection is suspended, the eNB and the MME store second information. In one embodiment, the second information includes at least one of the following: data associated with the first connection, a terminal context, and a bearer context for the first connection. In one embodiment, the data associated with the first connection may be data transmitted via the first connection, data using the first connection, etc., which is not limited in the present embodiment.

[0332] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal.

[0333] In some embodiments, when the first connection is suspended, the eNB does not release the RRC connection between the eNB and the terminal.

[0334] In some embodiments, when the first connection is suspended, the eNB does not suspend the RRC connection with the terminal.

[0335] In some embodiments, after the first connection is suspended, the eNB sends a response message to the MME for the first message. In one example, the response message to the first message may be an S1 connection suspend response message.

[0336] In some embodiments, the response message to the first message is an S1-AP message.

[0337] In step S3210, the MME sends third information.

[0338] In some embodiments, the S-GW receives the third information.

[0339] In some embodiments, the third information is used to instruct to store downlink data sent to the terminal when the first connection is suspended.

[0340] In some embodiments, the third information is used to instruct to store downlink data sent to the terminal when the feeder link is unavailable.

[0341] In some embodiments, the third 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 third information may be downlink buffering duration time information.

[0342] In some embodiments, the third 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 third information based on information B. The MME then sends the third 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.

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

[0344] In some embodiments, terms such as “the time when the feeder link is unavailable”, “the time when the first connection is suspended”, and “the first time” may be used interchangeably.

[0345] In some embodiments, the second message may further carry fourth information, and the fourth information may be used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable.

[0346] In some embodiments, after receiving the second message, the S-GW sends a response message to the second message to the MME. In one example, the response message to the second message may be a release access bearer response message.

[0347] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal, and the terminal can send uplink data to the eNB through the RRC connection. In this case, steps S3211 to S3212 can be performed.

[0348] In step S3211, the terminal sends uplink data.

[0349] The optional implementation of step S3211 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.

[0350] In step S3212, the eNB stores the uplink data.

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

[0352] In some embodiments, when the first connection is suspended, the S-GW receives downlink data, and at this time, steps S3213 to S3214 may be executed.

[0353] In step S3213, the S-GW receives downlink data.

[0354] In step S3214, the S-GW stores the downlink data.

[0355] The optional implementation of step S3214 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.

[0356] In some embodiments, after steps S3211 to S3212 and / or steps S3213 to S3214, step S3215 is performed.

[0357] In step S3215 , the MME detects that the feeder link is available.

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

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

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

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

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

[0363] In step S3216, the MME sends a third message.

[0364] In some embodiments, the eNB receives the third message.

[0365] In some embodiments, the MME initiates the S1 connection recovery procedure.

[0366] In some embodiments, the MME initiates an S1 connection recovery procedure based on the stored second information to recover the first connection.

[0367] In some embodiments, the third message is used to request the eNB to resume the first connection between the eNB and the S-GW. In one example, the first message may be an S1 connection resume request message.

[0368] In some embodiments, the third message is an S1-AP message.

[0369] In some embodiments, after the first connection is resumed, the eNB sends a response message to the third message to the MME. In one example, the response message to the first message may be an S1 connection resume response message.

[0370] In step S3217, the MME sends a fourth message.

[0371] The optional implementation of step S3217 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.

[0372] In step S3218, the eNB sends uplink data.

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

[0374] In step S3219, the S-GW sends downlink data.

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

[0376] In some embodiments, if there is no further user plane data interaction, the eNB or MME triggers the S1 connection release procedure and the RRC connection release procedure. At this time, the terminal enters the idle state (ECM_IDLE).

[0377] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3219. For example, the combination of steps S3208 to S3210 can be implemented as an independent embodiment. For example, the combination of steps S3208 to S3218 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3206 and steps S3208 to S3218 can be implemented as an independent embodiment. For example, the combination of steps S3208 to S3210, steps S3213 to S3217, and step S3219 can be implemented as an independent embodiment. For example, the combination of steps S3201 to S3205, steps S3207 to S3210, steps S3213 to S3217, and step S3219 can be implemented as an independent embodiment. For example, the combination of steps S3208 to S3219 can be implemented as an independent embodiment. For example, the combination of step S3201 to step S3219 can be implemented as an independent embodiment. It should be noted that one or more steps in step S3201 to step S3219 may constitute a possible independent embodiment, but are not limited thereto.

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

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

[0380] In some embodiments, steps S3211 to S3212 and step S3218 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0382] In some embodiments, step S3206 and step S3207 can be exchanged in order or executed simultaneously, step S3211 to step S3212 and step S3213 to step S3214 can be exchanged in order or executed simultaneously, and step S3208 and step S3209 can be exchanged in order or executed simultaneously.

[0383] 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 S3320.

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

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

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

[0387] 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-based MME.

[0388] In one embodiment, the connection between the satellite-borne MME and the S-GW via the ground station is an S11 connection.

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

[0390] In one embodiment, the connection between the satellite-borne eNB and the S-GW via the ground station is an S1-U connection.

[0391] In some embodiments, the satellite link may comprise a feeder link.

[0392] In the embodiment of the present disclosure, the first network element is a second core network element, and the second network element is a first access network element.

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

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

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

[0396] In step S3302, the S-GW sends a ninth message.

[0397] In some embodiments, the MME receives the ninth message.

[0398] In some embodiments, the ninth message is used to indicate the arrival of downlink data at the terminal. In one example, the ninth 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 EPS bearer ID (EBI).

[0399] 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 ninth message to the MME that has a control plane connection with the terminal to notify the MME of the arrival of the terminal's downlink data.

[0400] In some embodiments, if the downlink data is eligible for user plane EPS optimization and MT-early data transform (EDT) is applicable to the PDN connection, the S-GW may send the downlink data size to the MME for MT-EDT consideration.

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

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

[0403] The optional implementation of step S3303 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.

[0404] In step S3304, the MME sends third information.

[0405] In some embodiments, the S-GW receives the third information.

[0406] In some embodiments, the third information is used to instruct to store downlink data sent to the terminal when the first connection is suspended.

[0407] In some embodiments, the third information is used to instruct to store downlink data sent to the terminal when the feeder link is unavailable.

[0408] In some embodiments, the third 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 third information can be downlink buffering duration time information.

[0409] In some embodiments, the third 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 third information based on information B. The MME then sends the third 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.

[0410] In some embodiments, the third information may be carried in the tenth message. In some embodiments, the tenth message is an acknowledgment message of the ninth message. In one example, the tenth message may be an acknowledgment message (downlink data notification ack) of the downlink data notification message.

[0411] In some embodiments, terms such as “the time when the feeder link is unavailable”, “the time when the first connection is suspended”, and “the first time” may be used interchangeably.

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

[0413] The optional implementation of step S3305 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.

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

[0415] The optional implementation of step S3306 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.

[0416] In step S3307, the MME sends an eleventh message.

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

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

[0419] In some embodiments, when the terminal is registered with the MME and the MME detects that the feeder link is available, the MME may send an eleventh message to the terminal via the eNB. The MME may include the downlink data size in the eleventh message to help the eNB use MT-EDT.

[0420] In some embodiments, the eNB determines to use MT-EDT by adding an MT-EDT indication to the terminal in the eleventh message.

[0421] In step S3308, the terminal sends the twelfth message.

[0422] In some embodiments, the eNB receives the twelfth message.

[0423] In some embodiments, the twelfth message is used to establish a control plane connection.

[0424] In some embodiments, the twelfth message is carried in an RRC message and sent to the eNB. In one example, the RRC message may be an RRC connection resume request message.

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

[0426] In step S3309, the eNB sends the thirteenth message.

[0427] In some embodiments, the MME receives the thirteenth message.

[0428] In some embodiments, the thirteenth message is used to request the restoration of the terminal context. In one example, the thirteenth message may be a terminal context restoration request (UE context resume request) message.

[0429] In some embodiments, the eNB sends the thirteenth message to the MME via an S1-AP message.

[0430] In step S3310, the MME sends an eighth message.

[0431] The optional implementation of step S3310 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.

[0432] In step S3311, the MME sends the fourteenth message.

[0433] In some embodiments, the eNB receives a fourteenth message.

[0434] In some embodiments, the fourteenth message is a response message to the thirteenth message. In one example, the fourteenth message may be a UE context resume response message.

[0435] In some embodiments, the MME sends the fourteenth message to the eNB via an S1-AP message.

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

[0437] The optional implementation of step S3312 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.

[0438] In some embodiments, after step S3312, the connection between the satellite and the ground station is about to be disconnected and the feeder link is unavailable. In this case, step S3313 is executed.

[0439] In step S3313, the MME detects that the feeder link is unavailable.

[0440] The optional implementation of step S3313 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.

[0441] In step S3314, the MME sends third information.

[0442] The optional implementation of step S3314 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.

[0443] In step S3315, the MME sends a first message.

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

[0445] In step S3316, the S-GW stores the downlink data.

[0446] The optional implementation of step S3316 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.

[0447] In step S3317, the MME detects that the feeder link is available.

[0448] The optional implementation of step S3317 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.

[0449] In step S3318, the MME sends a third message.

[0450] The optional implementation of step S3318 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.

[0451] In step S3319, the MME sends a fourth message.

[0452] The optional implementation of step S3319 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.

[0453] In step S3320, the S-GW sends downlink data.

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

[0455] In some embodiments, if there is no further user plane data interaction, the eNB or MME triggers the S1 connection release procedure and the RRC connection release procedure. At this time, the terminal enters the idle state (ECM_IDLE).

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

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

[0458] In some embodiments, steps S3313 to S3319 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0460] In some embodiments, steps S3313 to S3320 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0461] In some embodiments, step S3315 and step S3316 may be executed in an interchanged order or simultaneously.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0478] In one embodiment, the connection between the ground station and the S-GW is an S1-U connection.

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

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

[0481] In some embodiments, the satellite link may comprise a feeder link.

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

[0483] In step S5101, the fifth message is forwarded.

[0484] The optional implementation of step S5101 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.

[0485] In step S5102, a radio bearer establishment process is initiated.

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

[0487] In step S5103, the seventh message is sent.

[0488] The optional implementation of step S5103 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.

[0489] In some embodiments, after the terminal sends uplink data to the S-GW and / or the S-GW sends downlink data to the terminal, the connection between the satellite and the ground station is disconnected or is about to be disconnected, and the feeder link is unavailable. At this time, step S5104 is executed.

[0490] In step S5104, it is detected that the feeder link is unavailable.

[0491] The optional implementation of step S5104 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.

[0492] In step S5105, a first message is sent.

[0493] The optional implementation of step S5105 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.

[0494] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal, and the terminal can send uplink data to the eNB through the RRC connection. In this case, steps S5106 to S5107 can be executed.

[0495] In step S5106, uplink data is received.

[0496] The optional implementation of step S5106 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.

[0497] In step S5107, the uplink data is stored.

[0498] The optional implementation of step S5107 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.

[0499] In some embodiments, after steps S5106 to S5107, step S5108 is performed.

[0500] In step S5108, it is detected that the feeder link is available.

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

[0502] In step S5109, the third message is sent.

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

[0504] In step S5110, uplink data is sent.

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

[0506] In some embodiments, if there is no further user plane data interaction, the eNB or MME triggers the S1 connection release procedure and the RRC connection release procedure. At this time, the terminal enters the idle state (ECM_IDLE).

[0507] 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 S5104 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 can be implemented as an independent embodiment. For example, the combination of steps S5101 to S5103 and steps S5106 to S5110 can be implemented as an independent embodiment. For example, the combination of steps S5101 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.

[0508] In some embodiments, steps S5101 to S5103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0510] In some embodiments, steps S5106 to S5110 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

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

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

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

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

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

[0517] In one embodiment, the connection between the ground station and the S-GW is an S1-U connection.

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

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

[0520] In some embodiments, the satellite link may comprise a feeder link.

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

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

[0523] In step S5201, the fifth message is forwarded.

[0524] The optional implementation of step S5201 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.

[0525] In step S5202, a radio bearer establishment process is initiated.

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

[0527] In step S5203, the seventh message is sent.

[0528] The optional implementation of step S5203 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.

[0529] In some embodiments, after step S5202, the terminal may send uplink data to the S-GW through the first connection (such as the S1-U connection).

[0530] In some embodiments, after the terminal sends uplink data to the S-GW, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. At this time, step S5204 is executed.

[0531] In step S5204, a first message is received.

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

[0533] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal, and the terminal can send uplink data to the eNB through the RRC connection. In this case, steps S5205 to S5206 can be executed.

[0534] In step S5205, uplink data is received.

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

[0536] In step S5206, the uplink data is stored.

[0537] The optional implementation of step S5206 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.

[0538] In some embodiments, after the MME detects that the feeder link is available, S5207 may be executed.

[0539] In step S5207, a third message is received.

[0540] The optional implementation of step S5207 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.

[0541] In step S5208, uplink data is sent.

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

[0543] In some embodiments, if there is no further user plane data interaction, the eNB or MME triggers the S1 connection release procedure and the RRC connection release procedure. At this time, the terminal enters the idle state (ECM_IDLE).

[0544] 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 step S5204 can be implemented as an independent embodiment. For example, the combination of steps S5205 to S5206 can be implemented as an independent embodiment. For example, the combination of steps S5205 to S5208 can be implemented as an independent embodiment. For example, the combination of steps S5204 to S5208 can be implemented as an independent embodiment. For example, the combination of steps S5201 to S5204 can be implemented as an independent embodiment. For example, the combination of steps S5201 to S5203 and steps S5205 to S5208 can be implemented as an independent embodiment. For example, the combination of steps S5201 to S5208 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S5201 to S5208 may constitute a possible independent embodiment, but are not limited to this.

[0545] In some embodiments, step S5204 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0546] In some embodiments, steps S5205 to S5208 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0547] In some embodiments, steps S5201 to S5203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0548] As shown in Figure 5C, Figure 5C 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 S5301 to S5307.

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

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

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

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

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

[0554] In one embodiment, the connection between the ground station and the S-GW is an S1-U connection.

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

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

[0557] In some embodiments, the satellite link may comprise a feeder link.

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

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

[0560] In step S5301, the eleventh message is forwarded.

[0561] The optional implementation of step S5301 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.

[0562] In step S5302, the twelfth message is received.

[0563] The optional implementation of step S5302 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.

[0564] In step S5303, the thirteenth message is sent.

[0565] The optional implementation of step S5303 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.

[0566] In step S5304, the fourteenth message is received.

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

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

[0569] In step S5305, a first message is received.

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

[0571] In some embodiments, after step S5304, the MME detects that the feeder link is available, and then executes step S5306.

[0572] In step S5306, a third message is received.

[0573] The optional implementation of step S5306 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.

[0574] In step S5307, the downlink data is forwarded.

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

[0576] In some embodiments, if there is no further user plane data interaction, the eNB or MME triggers the S1 connection release procedure and the RRC connection release procedure. At this time, the terminal enters the idle state (ECM_IDLE).

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

[0578] In some embodiments, step S5305 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0579] In some embodiments, step S5306 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0580] In some embodiments, steps S5301 to S5304 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0581] 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. This embodiment of the present disclosure relates to a communication method performed by a second network element. The above communication method includes steps S5401 to S5408.

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

[0583] In some embodiments, the core network further includes a first core network element. In one example, taking the core network as an EPC as an example, the first core network element is an S-GW.

[0584] In some embodiments, the second 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.

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

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

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

[0588] In one embodiment, the connection between the ground station and the S-GW is an S1-U connection.

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

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

[0591] In some embodiments, the satellite link may comprise a feeder link.

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

[0593] In step S5401, the fifth message is received.

[0594] The optional implementation of step S5401 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.

[0595] In step S5402, the sixth message is sent.

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

[0597] In step S5403, the seventh message is received.

[0598] The optional implementation of step S5403 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.

[0599] In step S5404, the eighth message is sent.

[0600] The optional implementation of step S5404 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.

[0601] In some embodiments, after step S5404, the terminal may send uplink data to the S-GW via the first connection (e.g., an S1-U connection). And / or, the S-GW may send downlink data to the terminal via the first connection (e.g., an S1-U connection). After the terminal sends uplink data to the S-GW and / or the S-GW sends downlink data to the terminal, 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 S5405 is executed.

[0602] In step S5405, a first message is received.

[0603] The optional implementation of step S5405 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.

[0604] In step S5406, the third information is sent.

[0605] The optional implementation of step S5406 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.

[0606] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal. The terminal can then send uplink data to the eNB via the RRC connection. And / or the S-GW can receive downlink data. The eNB then detects that the feeder link is available and executes step S5407.

[0607] In step S5407, a third message is received.

[0608] The optional implementation of step S5407 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.

[0609] In step S5408, the fourth message is sent.

[0610] The optional implementation of step S5408 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.

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

[0612] In some embodiments, steps S5401 to S5404 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0614] In some embodiments, steps S5407 to S5408 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0615] 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, which is performed by a first network element. The above communication method includes steps S5501 to S5510.

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

[0617] In some embodiments, the core network further includes a first core network element. In one example, taking the core network as an EPC as an example, the first core network element is an S-GW.

[0618] In some embodiments, the second 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.

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

[0620] In some embodiments, as shown in FIG4B , the S-GW is deployed on the ground, and the MME is deployed on the ground. In this case, the MME is called a spaceborne MME.

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

[0622] In one embodiment, the connection between the ground station and the S-GW is an S1-U connection.

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

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

[0625] In some embodiments, the satellite link may comprise a feeder link.

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

[0627] In step S5501, the fifth message is received.

[0628] The optional implementation of step S5501 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.

[0629] In step S5502, the sixth message is sent.

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

[0631] In step S5503, the seventh message is received.

[0632] The optional implementation of step S5503 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.

[0633] In step S5504, the eighth message is sent.

[0634] The optional implementation of step S5504 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.

[0635] In some embodiments, after step S5504, the terminal may send uplink data to the S-GW via the first connection (e.g., the S1-U connection). And / or, the S-GW may send downlink data to the terminal via the first connection (e.g., the S1-U connection). After the terminal sends uplink data to the S-GW and / or the S-GW sends downlink data to the terminal, 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 S5505 is executed.

[0636] In step S5505, it is detected that the feeder link is unavailable.

[0637] The optional implementation of step S5505 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.

[0638] In step S5506, the first message is sent.

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

[0640] In step S5507, the third information is sent.

[0641] The optional implementation of step S5507 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.

[0642] In some embodiments, while the first connection is suspended, the eNB maintains the RRC connection with the terminal. The terminal can then send uplink data to the eNB and / or the S-GW can receive downlink data via the RRC connection. After the terminal sends uplink data to the S-GW and / or the S-GW sends downlink data to the terminal, the satellite connects to the ground station and the feeder link becomes available. At this point, step S5508 is executed.

[0643] In step S5508, it is detected that the feeder link is available.

[0644] The optional implementation of step S5508 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.

[0645] In step S5509, the third message is sent.

[0646] The optional implementation of step S5509 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.

[0647] In step S5510, the fourth message is sent.

[0648] The optional implementation of step S5510 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.

[0649] 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 S5505 to S5507 can be implemented as an independent embodiment. For example, the combination of steps S5508 to S5510 can be implemented as an independent embodiment. For example, the combination of steps S5505 to S5510 can be implemented as an independent embodiment. For example, the combination of steps S5501 to S5507 can be implemented as an independent embodiment. For example, steps S5501 to S5510. It should be noted that one or more steps in steps S5501 to S5510 may constitute a possible independent embodiment, but are not limited to this.

[0650] In some embodiments, steps S5501 to S5504 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

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

[0653] 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, which is performed by a first network element. The above communication method includes steps S5601 to S5616.

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

[0655] In some embodiments, the core network further includes a first core network element. In one example, taking the core network as an EPC as an example, the first core network element is an S-GW.

[0656] In some embodiments, the second 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.

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

[0658] In some embodiments, as shown in FIG4B , the S-GW is deployed on the ground, and the MME is deployed on the ground. In this case, the MME is called a spaceborne MME.

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

[0660] In one embodiment, the connection between the ground station and the S-GW is an S1-U connection.

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

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

[0663] In some embodiments, the satellite link may comprise a feeder link.

[0664] In some embodiments, for a data transmission process initiated by a terminal (MT), the first network element performs steps S5601 to S5616.

[0665] In step S5601, the ninth message is received.

[0666] The optional implementation of step S5601 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.

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

[0668] In step S5602, it is detected that the feeder link is unavailable.

[0669] The optional implementation of step S5602 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.

[0670] In step S5603, the third information is sent.

[0671] The optional implementation of step S5603 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.

[0672] In step S5604, it is detected that the feeder link is available.

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

[0674] In step S5605, the eleventh message is sent.

[0675] The optional implementation of step S5605 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.

[0676] In step S5606, the thirteenth message is received.

[0677] The optional implementation of step S5606 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.

[0678] In step S5607, the eighth message is sent.

[0679] The optional implementation of step S5607 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.

[0680] In step S5608, the fourteenth message is sent.

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

[0682] In some embodiments, after step S5608, the S-GW sends downlink data. Subsequently, the connection between the satellite and the ground station is about to be disconnected, and the feeder link is unavailable. At this point, step S5609 is executed.

[0683] In step S5609, it is detected that the feeder link is unavailable.

[0684] The optional implementation of step S5609 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.

[0685] In step S5610, the third information is sent.

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

[0687] In step S5611, a first message is sent.

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

[0689] In step S5612, it is detected that the feeder link is available.

[0690] The optional implementation of step S5612 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.

[0691] In step S5613, a third message is sent.

[0692] The optional implementation of step S5613 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.

[0693] In step S5614, the fourth message is sent.

[0694] The optional implementation of step S5614 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.

[0695] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5601 to S5614. For example, the combination of steps S5602 to S5603 can be implemented as an independent embodiment. For example, the combination of steps S5601 to S5603 can be implemented as an independent embodiment. For example, the combination of steps S5604 to S5608 can be implemented as an independent embodiment. For example, the combination of steps S5609 to S5611 can be implemented as an independent embodiment. For example, the combination of steps S5612 to S5614 can be implemented as an independent embodiment. For example, the combination of steps S5609 to S5614 can be implemented as an independent embodiment. For example, the combination of steps S5604 to S5611 can be implemented as an independent embodiment. For example, the combination of steps S5604 to S5614 can be implemented as an independent embodiment. For example, the combination of steps S5602 to S5611 can be implemented as an independent embodiment. For example, the combination of steps S5602 to S5614 can be implemented as an independent embodiment. For example, the combination of steps S5601 to S5608 can be implemented as an independent embodiment. For example, the combination of steps S5601 to S5611 can be implemented as an independent embodiment. For example, the combination of steps S5601 to S5614 can be implemented as an independent embodiment. It should be noted that one or more of steps S5601 to S5614 may constitute an independent embodiment, but are not limited to this.

[0696] In some embodiments, step S5601 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0698] In some embodiments, steps S5611 to S5613 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0699] In some embodiments, steps S5614 to S5616 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0700] 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 communication method includes steps S6101 to S6109.

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

[0702] In some embodiments, the satellite link may comprise a feeder link.

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

[0704] In step S6101, the eighth message is received.

[0705] The optional implementation of step S6101 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.

[0706] In some embodiments, after step S6101, the terminal may send uplink data to the S-GW via the first connection (e.g., the S1-U connection), in which case step S6102 is performed. And / or, the S-GW may send downlink data to the terminal via the first connection (e.g., the S1-U connection), in which case step S6103 is performed.

[0707] In step S6102, uplink data is received.

[0708] The optional implementation of step S6102 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.

[0709] In step S6103, the S-GW sends downlink data.

[0710] The optional implementation of step S6103 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.

[0711] In some embodiments, after step S6102 and / or step S6103, the connection between the satellite and the ground station is disconnected or about to be disconnected, and the feeder link is unavailable. After the MME detects that the feeder link is unavailable, step S6104 is executed.

[0712] In step S6104, third information is received.

[0713] The optional implementation of step S6104 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.

[0714] In some embodiments, when the first connection is suspended, the eNB maintains the RRC connection with the terminal, and the terminal can send uplink data to the eNB through the RRC connection.

[0715] In some embodiments, when the first connection is suspended, the S-GW receives downlink data, and at this time, steps S36105 to S6106 can be executed.

[0716] In step S6105, downlink data is received.

[0717] In step S6106, the downlink data is stored.

[0718] The optional implementation of step S6106 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.

[0719] In some embodiments, after the terminal sends uplink data and / or the S-GW receives downlink data, step S6107 is performed.

[0720] In step S6107, the fourth message is received.

[0721] The optional implementation of step S6107 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.

[0722] In step S6108, uplink data is received.

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

[0724] In step S6109, downlink data is sent.

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

[0726] The communication method involved in the embodiments of the present disclosure may include at least one of steps S6101 to S6109. For example, the combination of step S6104 can be implemented as an independent embodiment. For example, the combination of step S6107 can be implemented as an independent embodiment. For example, the combination of steps S6105 to S6106 can be implemented as an independent embodiment. For example, the combination of steps S6104 to S6107 can be implemented as an independent embodiment. For example, the combination of steps S6101 to S6106 can be implemented as an independent embodiment. For example, the combination of steps S3101 to S3107 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S6101 to S6107 may constitute a possible independent embodiment, but are not limited to this.

[0727] In some embodiments, step S6107 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0728] In some embodiments, steps S6105 to S6107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0730] 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 S6209.

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

[0732] In some embodiments, the satellite link may comprise a feeder link.

[0733] In some embodiments, for a data transmission process initiated by a terminal (MT), the first core network element performs steps S6201 to S6209.

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

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

[0736] In step S6202, the ninth message is sent.

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

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

[0739] In step S6203, the third information is sent.

[0740] The optional implementation of step S6203 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.

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

[0742] The optional implementation of step S6204 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.

[0743] In some embodiments, after the MME detects that the feeder link is available, step S6205 is performed.

[0744] In step S6205, the eighth message is received.

[0745] The optional implementation of step S6205 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.

[0746] In step S6206, downlink data is sent.

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

[0748] In some embodiments, after step S6212, the connection between the satellite and the ground station is about to be disconnected, and the MME detects that the feeder link is unavailable. In this case, step S6213 is executed.

[0749] In step S6207, the third information is received.

[0750] The optional implementation of step S6207 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.

[0751] In step S6208, the downlink data is stored.

[0752] The optional implementation of step S6208 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.

[0753] In some embodiments, after the MME detects that the feeder link is available, step S6209 is performed.

[0754] In step S6209, the fourth message is received.

[0755] The optional implementation of step S6209 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.

[0756] In step S6210, uplink data is received.

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

[0758] In step S6211, downlink data is sent.

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

[0760] The communication method involved in the embodiments of the present disclosure may include at least one of steps S6201 to S6211. For example, the combination of steps S6203 to S6204 can be implemented as an independent embodiment. For example, the combination of steps S6207 to S6208 can be implemented as an independent embodiment. For example, step S6209 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6204 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6206 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6202 and steps S6205 to S6208 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6208 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6202 and steps S6205 to S6208 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6202 and steps S6205 to S6209 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6202 and steps S6205 to S6211 can be implemented as an independent embodiment. For example, the combination of steps S6201 to S6211 can be implemented as an independent embodiment. It should be noted that one or more steps from steps S6201 to S6211 may constitute an independent embodiment, but are not limited to this.

[0761] In some embodiments, steps S6203 to S6204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0762] In some embodiments, steps S6209 to S6211 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0764] In step S7101, it is detected that the feeder link is unavailable.

[0765] Optional implementations of step S7101 may be found in step S3108 of FIG. 3A , step S3208 of FIG. 3B , step S3303 and step S3313 in FIG. 3C , and other related parts of the embodiments involved in FIG. 3A , FIG. 3B and FIG. 3C , which will not be repeated here.

[0766] In step S7102, a first message is sent.

[0767] Optional implementations of step S7102 may be found in step S3109 of FIG. 3A , step S3209 of FIG. 3B , step S3315 of FIG. 3C , and other related parts of the embodiments involved in FIG. 3A , FIG. 3B and FIG. 3C , which will not be described in detail here.

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

[0769] As shown in Figure 7B, Figure 7B is another flow diagram of a communication method executed by a second network element according to an embodiment of the present disclosure. The present embodiment relates to a communication method, which is executed by a second network element. The communication method of the present embodiment includes step S7201.

[0770] In step S7201, a first message is received.

[0771] Optional implementations of step S7201 may refer to step S3109 in FIG. 3A , step S3209 in FIG. 3B , step S3315 in FIG. 3C , and other related parts in the embodiments involved in FIG. 3A , FIG. 3B and FIG. 3C , which will not be described in detail here.

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

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

[0774] In step S801, a second message is received.

[0775] Optional implementations of step S801 may refer to step S3110 in FIG. A , step S3210 in FIG. 3B , step S3314 in FIG. 3C , and other related parts in the embodiments involved in FIG. 3A , FIG. 3B , and FIG. 3C , which will not be repeated here.

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

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

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

[0779] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a CPU, a microprocessor, a graphics processing unit (GPU) (which can also be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, 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.

[0780] As shown in Figure 9A, Figure 9A is a structural diagram of a communication device according to an embodiment of the present disclosure. The structure of the above-mentioned communication device 91 can be as shown in Figure 9A. The communication device 91 includes: a processing module 9101. In some embodiments, the processing module 9101 is used to detect that the feeder link between the satellite and the ground station is unavailable. Optionally, the above-mentioned processing module 9101 is used to execute other steps performed by the first network in any of the above methods (for example, step S3101, step S3102, step S3104, step S3105, step S3109, step S3110, step S3111, step S3116, step S3117, step S3118, step S3119, step S3201, step S3202, step S3203, step S3204, step S3205, step S3206, step S3207, step S3208, step S3209, step S3210, step S3211, step S3212, step S3213, step S3214, step S3215, step S3216, step S3217, step S3218, step S3219, step S3220, step S3221 At least one of steps S3205, S3209, S3210, S3211, S3216, S3217, S3218, S3302, S3304, S3307, S3308, S3309, S3310, S3311, S3314, S3315, S3318, and S3319, but not limited thereto), 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 configured to send a first message, the first message being configured to request the second network element to suspend a first connection, the first connection being a connection established between the first access network element and the first core network element for data transmission of the terminal. Optionally, the above-mentioned transceiver module 9102 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first network in any of the above methods (for example, step S3103, step S3108, step S3112, step S3115, step S3108, step S3109, step S3113, step S3208, step S3212, step S3215, step S3303, step S3306, step S3313, step S3317, but not limited to these), which are not repeated here.

[0781] As shown in Figure 9B, Figure 9B is a structural diagram of a communication device shown according to an embodiment of the present disclosure. The structure of the above-mentioned communication device 92 can be as shown in Figure 9B. The communication device 92 may include: a transceiver module 9201. In some embodiments, the transceiver module 9201 is used to receive a first message, and the first message is used to request to suspend a first connection. The first connection is a connection established between the first access network network element and the first core network network element for data transmission of the terminal. Optionally, the transceiver module 9201 is used to execute the communication steps such as sending and / or receiving performed by the second network element in any of the above methods (for example, step S3101, step S3102, step S3104, step S3105, step S3109, step S3110, step S3111, step S3116, step S3117, step S3118, step S3119, step S3201, step S3202, step S3203, step S3204 , step S3205, step S3209, step S3210, step S3211, step S3216, step S3217, step S3218, step S3302, step S3304, step S3307, step S3308, step S3309, step S3310, step S3311, step S3314, step S3315, step S3318, step S3319, but not limited thereto), which will not be repeated here. In some embodiments, the communication device 92 further includes: a processing module 9202.

[0782] As shown in Figure 9C, Figure 9C 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 93 may be as shown in Figure 9C. The communication device 93 may include a transceiver module 9301. In some embodiments, the transceiver module 9301 is configured to receive a second message, the second message being used to instruct the release of a first connection, where the first connection is established between a first access network element and a first core network element for data transmission of a terminal. Optionally, the transceiver module 9301 is configured to execute at least one of the communication steps such as sending and / or receiving performed by the first core network element in any of the above methods (e.g., step S3105, step S3106, step S3107, step S3110, step S3113, step S3117, step S3118, step S3119, step S3207, step S3210, step S3213, step S3217, step S3218, step S3219, step S3301, step S3302, step S3304, step S3310, step S3312, step S3314, step S3319, and step S3320, but not limited thereto), which are not described in detail herein. In some embodiments, the processing module 9302 is configured to store downlink data when the first connection is suspended. Optionally, the above-mentioned processing module 9302 is used to execute at least one of the other steps (for example, step S3103, step S3114, step S3214, step S3305, step S3316, but not limited to these) performed by the first core network element in any of the above methods, which will not be repeated here.

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

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

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

[0786] 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 S3102, step S3104, step S3105, step S3106, step S3107, step S3109, step S3110, step S3111, step S3113, step S3116, step S3117, step S3118, step S3119, step S3201, step S3202, step S3203, step S3204, step S3205, step S3206, step S3207, step S3209, step S3110, step S3111, step S3113, step S3116, step S3117, step S3118, step S3119, step S3201, step S3202, step S3203, step S3204, step S3205, step S3206, step S3207, step S3208, step S3210, step S3211, step S3211 3205, step S3207, step S3209, step S3210, step S3211, step S3213, step S3216, step S3217, step S3218, step S3219, step S3301, step S3302, step S3304, step S3307, step S3308, step S3309, step S3310, step S3311, step S3312, step S3314, step S3315, step S3318, step S3319, step S3320, but not limited to). The processor 1011 executes at least one of the other steps (e.g., step S3103, step S3108, step S3112, step S3114, step S3115, step S3108, step S3109, step S3113, step S3208, step S3212, step S3214, step S3215, step S3303, step S3305, step S3306, step S3313, step S3316, step S3317, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

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

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

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

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

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

[0792] 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 S3102, step S3104, step S3105, step S3106, step S3107, step S3109, step S3110, step S3111, step S3113, step S3116, step S3117, step S3118, step S3119, step S3201, step S3202, step S3203, step S3204, step S3205, step S32 ...207, step S3208, step S3210, step S3211, step S3212, step S3213, step S3214, step S3215, step S3216, step S3217, step S3218, step S3219, step S3220 At least one of step S3207, step S3209, step S3210, step S3211, step S3213, step S3216, step S3217, step S3218, step S3219, step S3301, step S3302, step S3304, step S3307, step S3308, step S3309, step S3310, step S3311, step S3312, step S3314, step S3315, step S3318, step S3319, and step S3320, 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, the chip 1020, the memory 1023, or the transceiver device. In some embodiments, the processor 9201 performs at least one of the other steps (for example, step S3103, step S3103, step S3108, step S3112, step S3114, step S3115, step S3108, step S3109, step S3113, step S3208, step S3212, step S3214, step S3215, step S3303, step S3305, step S3306, step S3313, step S3316, step S3317, but not limited to these).

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

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

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

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

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

A communication method, performed by a first network element, comprising: Detecting that the feeder link between the satellite and the ground station is unavailable; A first message is sent, where the first message is used to request the second network element to suspend a first connection, where the first connection is a connection established between the first access network element and the first core network element for data transmission of the terminal. The method according to claim 1, wherein The first message carries first information, where the first information is used to indicate that the feeder link is unavailable. The method according to claim 1 or 2, wherein The method further includes: storing second information when the first connection is suspended; wherein the second information includes at least one of the following: data associated with the first connection, context of the terminal, and bearer context of the first connection. The method according to claim 3, wherein The second information is also stored in the second network element. The method according to any one of claims 1 to 4, wherein In a case where the first network element is the first access network element, the method further includes: when the first connection is suspended, maintaining the connection with the terminal. The method according to claim 5, wherein After detecting that the feeder link between the satellite and the ground station is unavailable, the method further includes: receiving uplink data sent by the terminal; and storing the uplink data. The method according to any one of claims 1 to 4, wherein In the case where the first network element is a second core network element, the method further includes: sending a second message, where the second message is used to instruct the first core network element to release the first connection. The method according to claim 7, wherein The second message carries third information, where the third information is used to indicate that downlink data sent to the terminal is stored when the first connection is suspended, and the third information is determined based on the ephemeris information of the satellite. The method according to claim 8, wherein The second message further carries fourth information, where the fourth information is used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable. The method according to any one of claims 1 to 9, wherein After sending the first message, the method further includes: detecting that the feeder link is available; and sending a third message, where the third message is used to request the second network element to restore the first connection. The method according to claim 10, wherein In a case where the first network element is the first access network element, the method further includes: after the first connection is restored, sending the stored uplink data to the first core network element. The method according to claim 10, wherein In the case where the first network element is a second core network element, the method further includes: sending a fourth message, wherein the fourth message is used to instruct the first core network element to rebuild the first connection, and the first connection is used by the first core network element to send stored downlink data to the terminal. A communication method, performed by a second network element, comprising: A first message is received, where the first message is used to request to suspend a first connection, where the first connection is a connection established between a first access network element and a first core network element for data transmission of a terminal. The method according to claim 13, wherein The first message carries first information, where the first information is used to indicate that the feeder link is unavailable. The method according to claim 13 or 14, wherein The method further includes: when the first connection is suspended, storing second information, where the second information includes at least one of the following: data associated with the first connection, a context of the terminal, and a bearer context of the first connection. The method according to claim 15, wherein The second information is also stored in the first network element. The method according to claim 15 or 16, wherein In a case where the second network element is a first access network element, the method further includes: when the first connection is suspended, maintaining the connection with the terminal. A communication method, performed by a first core network element, comprising: A second message is received, where the second message is used to instruct the release of a first connection, where the first connection is a connection established between a first access network element and a first core network element for data transmission of a terminal. The method according to claim 18, wherein The second message carries third information, where the third information is used to indicate storage of downlink data sent to the terminal when the first connection is suspended. The third information is determined based on the ephemeris information of the satellite and is used to indicate storage duration of the downlink data. The method according to claim 19, wherein The second message further carries fourth information, where the fourth information is used to indicate that the first connection is suspended because the feeder link is unavailable. The method according to any one of claims 18 to 20, wherein The method includes: when the first connection is suspended, storing downlink data sent to the terminal. The method according to claim 21, wherein The method further includes: receiving a fourth message, where the fourth message is used to request reestablishment of the first connection; and after the first connection is reestablished, sending the stored downlink data to the first access network element. A communication method is performed by a core network, the core network including a first core network element and a second core network element; the method comprising: The second core network element detects that a feeder link between the satellite and the ground station is unavailable; The second core network element sends a first message to the first access network element, where the first message is used to request the first access network element to suspend a first connection, where the first connection is a connection established between the first access network element and the first core network element for data transmission of the terminal. The method according to claim 23, wherein The first message carries first information, where the first information is used to indicate that the feeder link is unavailable. The method according to claim 23 or 24, wherein The method also includes: the second core network element storing second information when the first connection is suspended; wherein the second information includes at least one of the following: data associated with the first connection, the context of the terminal, and the bearer context of the first connection. The method according to claim 25, wherein The second information is also stored in the first access network element. The method according to any one of claims 23 to 26, wherein The method further includes: the second core network element sending a second message to the first core network element, where the second message is used to instruct the first core network element to release the first connection. The method according to claim 27, wherein The second message carries third information, and the third information is used to indicate that the downlink data sent to the terminal is stored when the first connection is suspended. The third information is determined based on the ephemeris information of the satellite and is used to indicate the storage duration of the downlink data. The method according to claim 28, wherein The second message further carries fourth information, where the fourth information is used to indicate that the reason why the first connection is suspended is that the feeder link is unavailable. The method according to any one of claims 23 to 29, wherein After the second core network element sends the first message to the first access network element, the method also includes: the second core network element detects that the feeder link is available; the second core network element sends a third message to the first access network element, and the third message is used to request the second network element to restore the first connection. The method according to claim 30, wherein The method also includes: the second core network element sending a fourth message to the first core network element, the fourth message is used to instruct the first core network element to rebuild the first connection, and the first connection is used by the first core network element to send stored downlink data to the terminal. The method according to any one of claims 23 to 30, wherein The method includes: when the first connection is suspended, the first core network element stores downlink data sent to the terminal. The method according to claim 31, wherein The method further includes: after the first connection is reestablished, the first core network element sending the stored downlink data to the first access network element. A communication device, comprising: a processing module, configured to detect that a satellite link is unavailable; Do one of the following: store data; Instructing the 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. A communication device, comprising: a processing module for detecting that a feeder link between the satellite and the ground station is unavailable; The transceiver module is used to send a first message, where the first message is used to request the second network element to suspend a first connection, where the first connection is a connection established between the first access network element and the first core network element for data transmission of the terminal. A communication device, comprising: The transceiver module is used to receive a first message, where the first message is used to request to suspend a first connection, where the first connection is a connection established between a first access network element and a first core network element for data transmission of a terminal. A communication device, comprising: The transceiver module is used to receive a second message, where the second message is used to indicate the release of a first connection, where the first connection is a connection established between a first access network element and a first core network element for data transmission of a terminal. A network device, comprising: one or more processors; One or more memories for storing instructions; wherein the processor is configured to call the instructions so as to cause the network device to perform the method according to any one of claims 1 to 12, 13 to 17, and 18 to 22. A communication system comprising: A first network element, configured to implement the method according to any one of claims 1 to 12; The second network element is configured to implement the method according to any one of claims 13 to 17; the first core network element is configured to implement the method according to any one of claims 18 to 22. A storage medium, wherein The storage medium stores instructions, wherein when the instructions are executed by the network device, the method according to any one of claims 1 to 12, 13 to 17, and 18 to 22 can be executed.

Images