Communication method, communication device, communication system, apparatus, and storage medium

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, an apparatus, and a storage medium. The method comprises: determining that a service link between a terminal and an access network device of a non-terrestrial network is available; and sending a first message to the access network device, the first message comprising a first parameter requested by the terminal and related to storage and forwarding of uplink data, such hat the access network device determines a second parameter on the basis of the first message, wherein the second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data. In embodiments of the present disclosure, a terminal requests an access network device for a parameter related to storage and forwarding of uplink data, so that the access network device determines whether to accept the request of the terminal and determines a parameter, for the terminal, related to storage and forwarding of the uplink data.

Description

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

[0001] The present disclosure relates to the field of communication technologies, and in particular to communication methods, communication equipment, communication systems, devices, and storage media. Background Art

[0002] In related technologies, terminals can communicate with terrestrial networks via satellite-based access network equipment. In some cases, both the service link and the feeder link may be unavailable for a period of time, requiring the satellite to perform store-and-forward operations for uplink data. Therefore, further research is needed into parameters related to store-and-forward data.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a communication method, a communication device, a communication system, an apparatus, and a storage medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a communication method, which is executed by a terminal, and the method includes:

[0006] Determining that a service link with an access network device of a non-terrestrial network is available, sending a first message to the access network device, so that the access network device determines a second parameter according to the first message;

[0007] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal; the first parameter includes one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0008] The QoS information includes the requested QoS or QoS priority;

[0009] The second parameter is used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

[0010] In the above embodiment, the terminal sends a first message to the access network device, so that the access network device determines the second parameter based on the first message; in this way, the access network device can determine whether to store and forward the uplink data sent by the terminal based on the second parameter, so that the access network device can provide services for some delay-insensitive data transmission services when the link is unavailable, avoiding the unavailability of data transmission services due to the disconnection of the service link or feeder link.

[0011] In a second aspect, an embodiment of the present disclosure provides a communication method, which is performed by an access network device of a non-terrestrial network, and the method includes:

[0012] The receiving terminal sends a first message, and determines a second parameter of the access network device according to the first message;

[0013] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal, the first parameter including at least one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0014] The QoS information includes the requested QoS or QoS priority;

[0015] The second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority for stored and forwarded data.

[0016] In the above embodiment, the access network device receives the first message sent by the terminal and determines the second parameter based on the first message, where the second parameter is a parameter for the access network device to determine whether to store and forward the uplink data; in this way, the access network device can determine whether to store and forward the uplink data based on the second parameter, and can provide services for some delay-insensitive data transmission services when the link is unavailable, thereby avoiding the unavailability of data transmission services due to the disconnection of the service link or feeder link.

[0017] In a third aspect, an embodiment of the present disclosure provides a communication method, which is performed by a first network element. The method includes:

[0018] receiving a fifth message sent by an access network device of a non-terrestrial network;

[0019] The fifth message is the fourth message or the S1-AP initial terminal message;

[0020] The fourth message is used to request a third parameter related to storage and forwarding;

[0021] The S1-AP initial terminal message includes uplink data;

[0022] The third parameter includes at least one of the second information and the third information;

[0023] The second information includes at least one of the following:

[0024] a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority;

[0025] The third information includes at least one of the following:

[0026] Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

[0027] In the above embodiment, a method is provided for receiving a fifth message sent by an access network device of a non-terrestrial network, wherein the fifth message is the fourth message or the S1-AP initial terminal message; in this way, the first network element can send a third parameter to the access network device or receive uplink data, so that the access network device determines whether to store and forward the uplink data sent by the terminal according to the third parameter, or enables the access network device to provide services for some delay-insensitive data transmission services when the link is unavailable, thereby avoiding the unavailability of data transmission services due to the disconnection of the service link or feeder link.

[0028] In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

[0029] A processing module, configured to determine whether a service link between the access network device and the non-terrestrial network is available;

[0030] a sending module, configured to send a first message to the access network device, so that the access network device determines a second parameter according to the first message;

[0031] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal; the first parameter includes one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0032] The QoS information includes the requested QoS or QoS priority;

[0033] The second parameter is used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

[0034] In a fifth aspect, an embodiment of the present disclosure provides an access network device for a non-terrestrial network, including:

[0035] A receiving module, configured to receive a first message sent by a terminal;

[0036] a processing module, configured to determine a second parameter of the access network device according to the first message;

[0037] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal, the first parameter including at least one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0038] The QoS information includes the requested QoS or QoS priority;

[0039] The second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority for stored and forwarded data.

[0040] In a sixth aspect, an embodiment of the present disclosure provides a first network element, including:

[0041] a receiving module, configured to receive a fifth message sent by an access network device of a non-terrestrial network;

[0042] The fifth message is the fourth message or the S1-AP initial terminal message;

[0043] The fourth message is used to request a third parameter related to storage and forwarding;

[0044] The S1-AP initial terminal message includes uplink data;

[0045] The third parameter includes at least one of the second information and the third information;

[0046] The second information includes at least one of the following:

[0047] a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority;

[0048] The third information includes at least one of the following:

[0049] Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

[0050] In a seventh aspect, an embodiment of the present disclosure provides a terminal, including:

[0051] one or more processors;

[0052] The terminal is used to execute the communication method described in any one of the first aspects of the embodiments of this disclosure.

[0053] In an eighth aspect, an embodiment of the present disclosure provides an access network device for a non-terrestrial network, including:

[0054] one or more processors;

[0055] The access network device of the non-terrestrial network is used to execute the communication method described in any one of the second aspects of the embodiments of the present disclosure.

[0056] In a ninth aspect, an embodiment of the present disclosure provides a first network element, including:

[0057] one or more processors;

[0058] The first network element is used to execute the communication method described in any one of the third aspects of the embodiments of the present disclosure.

[0059] In the tenth aspect, an embodiment of the present disclosure proposes a communication system, comprising: a terminal, an access network device of a non-terrestrial network, and a first network element; wherein the terminal is configured to implement the communication method of any one of the first aspect of the embodiment of the present disclosure; the access network device of the non-terrestrial network is configured to implement the communication method of any one of the second aspect of the embodiment of the present disclosure; and the first network element is configured to implement the communication method of any one of the third aspect of the embodiment of the present disclosure.

[0060] In an eleventh aspect, an embodiment of the present disclosure proposes a storage medium, which, when an instruction is executed on a communication device, enables the communication device to execute any one of the communication methods of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0062] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0063] FIG1B is an exemplary schematic diagram showing a satellite in a normal or default operating mode according to an embodiment of the present disclosure;

[0064] FIG1C is an exemplary schematic diagram illustrating a satellite in a store-and-forward operation mode according to an embodiment of the present disclosure;

[0065] FIG1D is an exemplary schematic diagram showing mobile-initiated data transmission according to an embodiment of the present disclosure;

[0066] FIG2A is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure;

[0067] FIG2B is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure;

[0068] FIG2C is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure;

[0069] FIG2D is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure;

[0070] FIG3 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0071] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0072] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0073] FIG6A is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;

[0074] FIG6B is a schematic diagram of the structure of an access network device of a non-terrestrial network proposed in an embodiment of the present disclosure;

[0075] FIG6C is a schematic structural diagram of a first network element proposed in an embodiment of the present disclosure;

[0076] FIG7A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0077] FIG7B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0078] The embodiments of the present disclosure provide a communication method, a communication device, a communication system, an apparatus, and a storage medium.

[0079] In a first aspect, an embodiment of the present disclosure provides a communication method, which is executed by a terminal, and the method includes:

[0080] Determining that a service link with an access network device of a non-terrestrial network is available, sending a first message to the access network device, so that the access network device determines a second parameter according to the first message;

[0081] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal; the first parameter includes one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0082] The QoS information includes the requested QoS or QoS priority;

[0083] The second parameter is used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

[0084] In the above embodiment, the terminal sends a first message to the access network device, so that the access network device determines the second parameter based on the first message; in this way, the access network device can determine whether to store and forward the uplink data sent by the terminal based on the second parameter, so that the access network device can provide services for some delay-insensitive data transmission services when the link is unavailable, avoiding the unavailability of data transmission services due to the disconnection of the service link or feeder link.

[0085] In a second aspect, an embodiment of the present disclosure provides a communication method, which is performed by an access network device of a non-terrestrial network. The method includes:

[0086] The receiving terminal sends a first message, and determines a second parameter of the access network device according to the first message;

[0087] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal, the first parameter including at least one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0088] The QoS information includes the requested QoS or QoS priority;

[0089] The second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority for stored and forwarded data.

[0090] In the above embodiment, the access network device receives the first message sent by the terminal and determines the second parameter based on the first message, where the second parameter is a parameter for the access network device to determine whether to store and forward the uplink data; in this way, the access network device can determine whether to store and forward the uplink data based on the second parameter, and can provide services for some delay-insensitive data transmission services when the link is unavailable, thereby avoiding the unavailability of data transmission services due to the disconnection of the service link or feeder link.

[0091] In a third aspect, an embodiment of the present disclosure provides a communication method, which is performed by a first network element. The method includes:

[0092] receiving a fifth message sent by an access network device of a non-terrestrial network;

[0093] The fifth message is the fourth message or the S1-AP initial terminal message;

[0094] The fourth message is used to request a third parameter related to storage and forwarding;

[0095] The S1-AP initial terminal message includes uplink data;

[0096] The third parameter includes at least one of the second information and the third information;

[0097] The second information includes at least one of the following:

[0098] a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority;

[0099] The third information includes at least one of the following:

[0100] Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

[0101] In the above embodiment, a method is provided for receiving a fifth message sent by an access network device of a non-terrestrial network, wherein the fifth message is the fourth message or the S1-AP initial terminal message; in this way, the first network element can send a third parameter to the access network device or receive uplink data, so that the access network device determines whether to store and forward the uplink data sent by the terminal according to the third parameter, or enables the access network device to provide services for some delay-insensitive data transmission services when the link is unavailable, thereby avoiding the unavailability of data transmission services due to the disconnection of the service link or feeder link.

[0102] In conjunction with some embodiments of the third aspect, in some embodiments, the third parameter includes at least one of the second information and the third information;

[0103] The second information includes at least one of the following:

[0104] a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority;

[0105] The third information includes at least one of the following:

[0106] Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

[0107] In the above-described embodiment, the contents included in the second information and the third information are provided.

[0108] In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

[0109] A processing module, configured to determine whether a service link between the access network device and the non-terrestrial network is available;

[0110] a sending module, configured to send a first message to the access network device, so that the access network device determines a second parameter according to the first message;

[0111] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal; the first parameter includes one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0112] The QoS information includes the requested QoS or QoS priority;

[0113] The second parameter is used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

[0114] In a fifth aspect, an embodiment of the present disclosure provides an access network device for a non-terrestrial network, including:

[0115] A receiving module, configured to receive a first message sent by a terminal;

[0116] a processing module, configured to determine a second parameter of the access network device according to the first message;

[0117] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal, the first parameter including at least one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0118] The QoS information includes the requested QoS or QoS priority;

[0119] The second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority for stored and forwarded data.

[0120] In a sixth aspect, an embodiment of the present disclosure provides a first network element, including:

[0121] a receiving module, configured to receive a fifth message sent by an access network device of a non-terrestrial network;

[0122] The fifth message is the fourth message or the S1-AP initial terminal message;

[0123] The fourth message is used to request a third parameter related to storage and forwarding;

[0124] The S1-AP initial terminal message includes uplink data;

[0125] The third parameter includes at least one of the second information and the third information;

[0126] The second information includes at least one of the following:

[0127] a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority;

[0128] The third information includes at least one of the following:

[0129] Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

[0130] It is understandable that the above-mentioned communication method, terminal, access network device, first network element, device, communication system, storage medium, program product, computer program, chip or chip system are all used to perform the method 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 method and will not be repeated here.

[0131] The embodiments of the present disclosure provide a communication method, a communication device, a communication system, an apparatus, and a storage medium. In some embodiments, the terms communication method, signal transmission method, wireless frame transmission method, etc. are interchangeable, and the terms information processing system, communication system, etc. are interchangeable.

[0132] 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. In the absence of 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 implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

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

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

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

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

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

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

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

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

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

[0142] In some embodiments, terms such as "greater than", "less 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.

[0143] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "device", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0144] In some embodiments, “access network device (AN device)”, “radio access network device (radio

[0145] The terms access network device (RAN device),” “base station (BS)”, “radio base station”, “fixed station”, “node”, “access point”, “transmission point (TP)”, “reception point (RP)”, “transmission / reception point (TRP)”, “panel”, “antenna panel”, “antenna array”, “cell”, “macro cell”, “small cell”, “femto cell”, “pico cell”, “sector”, “cell group”, “carrier”, “component carrier”, and “bandwidth part (BWP)” are used interchangeably.

[0146] In some embodiments, the device may refer to a device on the ground, such as an access network device and / or a core network device on the ground; it may also refer to a device on a satellite, such as an access network device and / or a core network device on a satellite; the embodiments of the present disclosure do not limit whether the device is a device on the ground or a device on a satellite, nor do they limit whether the device refers to an access network device or a core network device.

[0147] In some embodiments, the terms "terminal", "terminal device", "user equipment (terminal)", "terminal (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, etc. can be used interchangeably.

[0148] In some embodiments, the device may refer to a device on the ground, such as an access network device and / or a core network device on the ground; it may also refer to a device on a satellite, such as an access network device and / or a core network device on a satellite; the embodiments of the present disclosure do not limit whether the device is a device on the ground or a device on a satellite, nor do they limit whether the device refers to an access network device or a core network device.

[0149] 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, it can also be called 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, language such as "uplink" and "downlink" can also be replaced by language 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 side links.

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

[0151] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0152] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

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

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

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

[0156] In some embodiments, "predetermined" and "preset" can be interpreted as pre-specified in a protocol, etc., or can be interpreted as a pre-set action performed by a device, etc.

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

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

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

[0160] FIG1A is an exemplary schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a terminal 101 , an access network device 102 of a non-terrestrial network, and a first network element 103 .

[0161] In some embodiments, the terminal includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, 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 a wireless terminal device in a smart home, but is not limited thereto. It is 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. It is known to those skilled in the art that with the evolution of 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. The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0162] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5th generation mobile communication system-Advanced (5G-Advanced), 6th generation mobile communication system (6G), 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 IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 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, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be employed.

[0163] In some embodiments, 3GPP Rel 16, Rel 17, and Rel 18 have studied the integration of satellite components into EPS and 5GS. In 3GPP Rel 19, satellite store and forward (S&F) operations have been studied as part of the study. The satellite store and forward operations are designed for scenarios where gNB / eNB are embedded on the satellite. According to 3GPP 23.700-29 [1], the S&F operations in 5G systems with satellite access are intended to provide a certain degree of delay-tolerant communication services to terminals under satellite coverage with intermittent / temporary satellite connectivity (for example, when the satellite is not connected to the terrestrial network via a feeder link or ISL).

[0164] Figure 1B is an exemplary diagram illustrating a satellite in normal or default operating mode according to an embodiment of the present disclosure. As shown in Figure 1B , in the satellite's "normal or default operating" mode, signaling and data exchange between a terminal accessed via the satellite and a remote terrestrial network requires the simultaneous activation of both the service link and the feeder link. 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.

[0165] Figure 1C is an exemplary schematic diagram of a satellite storage and forwarding operation mode according to an embodiment of the present disclosure. As shown in Figure 1C, compared to the currently assumed "normal or default operation" of a 5G system with satellite access, in the storage and forwarding operation mode, the end-to-end exchange of signaling or data traffic is treated as a combination of two steps that are not concurrent in time (such as step A and step B in Figure 1C). In step A, signaling / data exchange is performed between the terminal and the satellite without the satellite being connected to the ground network at the same time (i.e., the satellite is able to operate a service link without an active feeder link connection). In step B, a connection between the satellite and the ground network 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.

[0166] In the scenario shown in Figure 1C above, due to the circular motion of the satellite, the access network equipment (e.g., gNB) on the satellite is very likely to operate with an active feeder link connection in one period, and then periodically operate with an inactive feeder link connection in the next period. For terminals connected to the access network equipment via a service link, when the feeder link is available, the access network equipment performs normal or default satellite operations. If the satellite movement causes the terminal to be unaware of the feeder link unavailability, the access network equipment, if it supports store-and-forward operation, continues to receive information from the terminal and initiates store-and-forward operation. If it supports store-and-forward operation, the access network equipment discards messages from the terminal.

[0167] FIG1D is an exemplary schematic diagram of mobile-initiated data transmission according to an embodiment of the present disclosure. As shown in FIG1D , the process includes the following steps:

[0168] Step 0: The terminal is in EPS Connection Management (ECM) idle state.

[0169] In step 1, the terminal sends an integrity-protected Non-Access Stratum Packet Data Unit (NAS PDU) to the eNodeB. The Non-Access Stratum Protocol Data Unit includes a Radio Resource Control Connection Setup Request or a Radio Resource Control Early Data Request, which may also be referred to as an RRC Connection Setup Request or an RRC Early Data Request. The Non-Access Stratum Protocol Data Unit also carries an Enhanced Packet System (EPS) bearer identifier and encrypted uplink data. The Non-Access Stratum Protocol Data Unit also includes NAS release assistance information, which is used to indicate whether no further uplink or downlink data transmission is expected, or whether only a single downlink data transmission is expected after the uplink data transmission (for example, confirmation or response to uplink data).

[0170] Step 1b, in the case of NB-IoT, if the eNodeB has not previously retrieved the EPS negotiated QoS profile, it can retrieve the profile from the Mobility Management Entity (MME). The Mobility Management Entity Code (MME Code) in the S-TMSI of the RRC Connection Request message is used to identify the Mobility Management Entity. In the case of network sharing, the Mobility Management Entity Code must be unique within the overlapping area of ​​the operator's Mobility Management Entity pool. Before triggering step 2 and throughout the RRC connection process, the eNodeB can prioritize requests from different terminals. The eNodeB can retrieve other parameters (for example, the wireless capabilities of the terminal).

[0171] In step 2, the eNodeB forwards the non-access stratum protocol data unit (NAPU) sent in step 1 to the mobility management entity (MME) via an S1-AP Initial Terminal message. If an RRC Early Data Request (RDR) was received in step 1, the eNodeB includes an "EDT Session" indication in the S1-AP Initial Terminal message. To assist with positioning services, the eNodeB indicates the terminal's coverage level to the MME. If a "Non-Access Stratum Release Assistance Information" message is received from the terminal, the traffic profile is overridden, and the MME does not send the traffic profile to the eNodeB.

[0172] In step 3, if a service gap timer is running in the mobility management (MM) context of the terminal stored in the mobility management entity, and the mobility management entity is not waiting for an MT paging response from the terminal, the mobility management entity rejects the request by discarding the NASData PDU and sending a service rejection message with an appropriate cause to the terminal. The mobility management entity may also provide the terminal with a mobility management backoff timer set to the remaining value of the service gap timer, and then execute step 15.

[0173] The MME checks the integrity of incoming NAS PDUs and decrypts the data contained therein. If necessary, the MME performs (and the terminal responds to) any EMM or ESM procedures, such as those related to security.

[0174] Step 4a: If the S11-U connection is not established, the mobility management entity sends a modify bearer request message to the serving gateway (S-GW) for each public data network connection. The modify bearer request message includes: the mobility management entity address, the tunnel endpoint identifier of the mobility management entity downlink traffic, the delayed downlink packet notification request, the radio access type (Radio Access Type, RAT), the LTE-M radio access type flag reported to the public data network gateway (Public Data Network GW, P-GW), and the origination (Mobile Original, MO) abnormal data counter. The serving gateway can now send downlink data to the terminal.

[0175] In step 4b, if the S11-U connection is established, the terminal accesses via the NB-IoT wireless access type, and the RRC establishment cause is set to "MO abnormal data", the mobility management entity shall notify the serving gateway.

[0176] Step 5: The serving gateway sends a bearer modification request to the public data network gateway (Public Data Network GW, P-GW).

[0177] Step 6: The public data network gateway sends a bearer modification response to the serving gateway.

[0178] In step 7, if a modify bearer request message was sent in step 4, the serving network shall return a modify bearer response to the mobility management entity. The modify bearer response includes the address of the serving gateway and the tunnel endpoint identifier (TEID) of the uplink traffic as a response to the modify bearer request message. The address of the serving gateway and the tunnel endpoint identifier of the serving gateway in the S11-U user plane are used by the mobility management entity to forward uplink data to the serving gateway.

[0179] Step 8: The mobility management entity sends uplink data to the public data network gateway via the serving gateway.

[0180] In step 9, if no downlink data is expected based on the non-access layer release assistance information from the terminal in step 1, it means that all application layer data exchanges have been completed and uplink data transmission has been completed; if the mobility management entity is unaware of the suspended MT traffic and no S1-U bearer is established, skip step 10 and proceed to step 11.

[0181] Otherwise, the downlink data may arrive at the public data network gateway, which sends the downlink data to the mobility management entity through the serving gateway. If no downlink data is received, steps 10-12 are skipped, and after no activity is detected in step 13, the eNodeB may trigger step 14. When the RRC connection is active, the terminal can still send uplink data and receive downlink data via non-access stratum protocol data units, which are carried by S1AP uplink or downlink messages. At any time when the terminal does not establish a user plane bearer, it can provide uplink data to the non-access stratum release assistance information. In this case, if necessary, the eNodeB can indicate the coverage level of the terminal to the mobility management entity to assist in positioning.

[0182] Step 10: If downlink data is received in step 9, the mobility management entity encrypts and performs integrity protection on the downlink data.

[0183] Step 11: If step 10 is performed, the downlink data is encapsulated in a non-access stratum protocol data unit (NASPDU) and sent to the eNodeB via an S1-AP downlink NASP message. If the configuration in the mobility management entity indicates that the eNodeB supports acknowledgment of downlink NASP PDUs, and acknowledgment of downlink NASP PDUs is enabled in the terminal's subscription information, the mobility management entity instructs the eNodeB to request acknowledgment in the S1-AP downlink NASP message. If step 10 is not performed, or if a NASP service accept message is not sent, the mobility management entity sends a connection establishment indication to the eNodeB, indicating that the establishment of the logical S1 connection associated with the terminal has been completed.

[0184] If a NAS Release Assistance message with uplink data is received and indicates that downlink data is expected, then, unless the mobility management entity is aware of additional pending MT traffic and unless an S1-U bearer is established, the mobility management entity immediately sends an S1 Terminal Context Release Command upon receipt of an S1-AP message containing downlink data encapsulated in a non-access stratum protocol data unit (NAS PDU), indicating that the eNodeB should release the RRC connection immediately after successfully sending data to the terminal. Alternatively, if an "EDT session" is received; if the indication is received in step 2, the mobility management entity may include an end indication indicating that no further data is expected in the S1-AP message, including downlink data encapsulated in NAS PDUs. If the mobility management entity includes an end indication indicating that no further data is expected, and if the eNodeB does not continue to establish an RRC connection, the eNodeB skips step 12a and initiates step 12b.

[0185] If the received NAS information indicates that no downlink data is expected, this means that all application layer data exchanges have completed the UL data transfer. In this case, unless the MME is aware of the additional pending MT traffic and unless an S1-U bearer is established:

[0186] The mobility management entity sends an S1AP terminal context release command:

[0187] immediately after an S1AP DL NAS transfer (NAS Service Accept), in which case steps 12b and 14 are skipped, or

[0188] Following the S1AP connection establishment indication, steps 12a, 12b, 13 and 14 are skipped in this case.

[0189] Optionally, if the mobility management entity receives an "EDT session" indication from the eNodeB in step 2, the mobility management entity shall include an end indication with no further data in the S1AP DL NAS TRANSPORT (NAS service accept) or S1AP CONNECTION ESTABLISHMENT indication. If the eNodeB does not proceed with the RRC connection establishment, the eNodeB skips step 12a and initiates the stop step 12b.

[0190] If the terminal is accessed through an NB-IoT unit, or through a WB-E-UTRAN unit and is capable of using CE mode B, in order to determine the retransmission strategy of the non-access stratum protocol data unit, the mobility management entity should take into account the transmission delay of the non-access stratum protocol data unit and CE mode B, the restrictive parameters stored in the mobility management context of the mobility management entity, and the CE mode (if applicable), that is, set a sufficiently long NAS timer based on the worst transmission delay.

[0191] In step 12a, the eNodeB sends an RRC downlink data message containing downlink data encapsulated in a non-access stratum protocol data unit (NASPDU). If an S1 Terminal Context Release command is sent after the S1-AP message with the NASPDU is sent in step 11, then after the eNodeB completes the downlink data transmission of the NASPDU to the terminal and confirms the MME in step 13, step 15 is completed immediately, and the eNodeB does not need to proceed to step 14. If header compression is applied to the PDN, the terminal performs header decompression to reconstruct the IP header.

[0192] In step 12b, if there is no further data in the S1AP message received from the mobility management entity, the eNodeB may send an RRC EarlyDataComplete message containing any NAS payload (non-access stratum protocol data unit or non-access stratum service accept message) received from step 11. In this example, step 14 is skipped.

[0193] In step 13, if the mobility management entity requests, the eNodeB sends a NASDelivery indication to the mobility management entity.

[0194] In step 14, if no non-access stratum protocol data unit is received for a period of time, the eNodeB will release S1 starting from step 15.

[0195] In step 15, the eNodeB or MME triggers the S1 release procedure. Alternatively, if the mobility management entity sent the "S1 Terminal Context Release Command" in step 11, the S1 release procedure is triggered starting from step 5, or starting from the "Connection Suspension Procedure." The next time the terminal enters the ECM connected state, the terminal and the mobility management entity store the Robust Header Compression (ROHC) configuration and context information for uplink or downlink data transmission.

[0196] FIG2A is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a communication method for use in a communication system 100, the method comprising:

[0197] In step S2100 , the terminal decides to transmit uplink data through an access network device of a non-terrestrial network.

[0198] In some embodiments, the terminal determines to send uplink data to an access network device of the non-terrestrial network according to the first information.

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

[0200] The first unavailable period of the service link;

[0201] duration of the first unavailability period;

[0202] a second retention period for store-and-forward data;

[0203] A second storage quota for store-and-forward data;

[0204] First forwarding priority for store-and-forward data;

[0205] Store and forward strategy.

[0206] Optionally, in the embodiment of the present disclosure, the non-terrestrial access network device may be a base station device on a satellite, such as a 4G base station eNodeB.

[0207] The embodiment of the present disclosure is divided into two schemes, steps S2101a and S2101b, according to different situations of whether an RRC connection has been established between the terminal and the access network device; wherein, step S2101a corresponds to the situation where an RRC connection has not been established between the terminal and the access network device, and step S2101b corresponds to the situation where an RRC connection has been established between the terminal and the access network device.

[0208] Step S2101a: The terminal sends an RRC connection request or an RRC connection recovery request to the access network device.

[0209] In some embodiments, a service link exists between the terminal and an access network device of a non-terrestrial network, and the terminal can obtain relevant information of the service link, including but not limited to: the first unavailable period of the service link and the duration of the first unavailable period.

[0210] In some embodiments, the terminal determines that the service link between the terminal and the access network device of the non-terrestrial network is available through at least one of a first unavailable period of the service link, a duration of the first unavailable period, and ephemeris of the satellite.

[0211] In some embodiments, when a service link is available, the terminal sends a first message to the access network device. The first message may be an RRC connection request or an RRC connection recovery request. The first message includes a first parameter requested by the terminal related to storage and forwarding of uplink data, so that the access network device determines a second parameter based on the first message. The second parameter is a parameter used to determine whether to store and forward the uplink data.

[0212] In some embodiments, the first parameter includes at least one of a data size of the uplink data, QoS information, and a first forwarding priority of storage and forwarding.

[0213] In some embodiments, the QoS information includes a requested QoS or a QoS priority;

[0214] In some embodiments, the second parameter includes at least one of a first retention period for stored and forwarded data, a first storage quota, and a second forwarding priority.

[0215] Step S2101b: The terminal sends an RRC early data request to the access network device.

[0216] In some embodiments, an RRC connection has been established between the terminal and the access network device, and the first message may be an RRC early data request.

[0217] In some embodiments, when the first message is an RRC early data request, the terminal sends a second non-access layer protocol data unit to the access network device.

[0218] In some embodiments, the second non-access stratum protocol data unit includes the first message and uplink data.

[0219] The embodiment of the present disclosure provides two solutions, step S2102a and step S2102b, according to different situations of whether the access network device stores the third parameter; wherein, step S2102a corresponds to the situation where the access network device does not store the third parameter, and step S2102b corresponds to the situation where the access network device stores the third parameter.

[0220] Step S2102a: The access network device sends a fourth message to the first network element.

[0221] In some embodiments, after receiving the RRC connection request or the RRC connection recovery request or the RRC early data request, the access network device sends a fourth message to the first network element, where the fourth message is used to request the third parameter.

[0222] Optionally, the first network element may be a Mobility Management Entity (MME).

[0223] In some embodiments, after sending the fourth message to the first network element, the access network device receives the third parameter sent by the first network element.

[0224] In some embodiments, the third parameter includes at least one of the second information and the third information.

[0225] In some embodiments, the second information includes a second unavailable period of the service link between the terminal and the access network device, the duration of the second unavailable period, a third unavailable period of the feeder link between the access network device and the first network element, the duration of the third unavailable period, a first retention period of stored and forwarded data, a first storage quota, and at least one of a second forwarding priority.

[0226] In some embodiments, the third information includes at least one of subscription information of the terminal, EPS negotiated QoS configuration information, and wireless capabilities.

[0227] In some embodiments, the access network device determines the second parameter based on at least one of the first parameter and the third parameter.

[0228] Step S2102b: The access network device determines whether to accept the request from the terminal.

[0229] In some embodiments, if the access network device stores the third parameter locally, the access network device directly obtains the third parameter locally.

[0230] In some embodiments, the access network device determines whether to accept the first message sent by the terminal according to at least one of the first parameter, the second parameter, and the third parameter.

[0231] The embodiment of the present disclosure provides two solutions, step S2103a and step S2103b, according to different situations of whether the access network device agrees to accept the first message; wherein, step S2103a corresponds to the situation where the access network device refuses to accept the first message, and step S2103b corresponds to the situation where the access network device accepts the RRC connection request or the RRC connection recovery request.

[0232] Step S2103a: The access network device sends an RRC connection rejection message to the terminal.

[0233] In some embodiments, if the access network device rejects the RRC connection request, RRC connection recovery request, or RRC early data request sent by the terminal, an RRC connection rejection message is sent to the terminal.

[0234] In some embodiments, the RRC connection rejection message further includes the reason why the access network device rejects the first message.

[0235] In some embodiments, the reasons why the access network device rejects the RRC connection request or RRC connection recovery request or RRC early data request include but are not limited to: the uplink data requested by the terminal is greater than the storage quota of the remaining storage and forwarding data of the terminal, the access network device cannot meet the QoS or QoS level required by the terminal, the retention period of the storage and forwarding data is greater than the time before the unavailability period (i.e., the remaining time is insufficient), and the access network device is congested.

[0236] Step S2103b: The access network device sends an RRC connection establishment message or an RRC connection recovery message to the terminal.

[0237] In some embodiments, if the first message is an RRC connection establishment request or an RRC connection recovery request, and the access network device accepts the first message sent by the terminal, the access network device sends an RRC connection establishment message or an RRC connection recovery message to the terminal in response to the RRC connection establishment request or RRC connection recovery request sent by the terminal.

[0238] It should be noted that if the first message is an RRC early data request and the access network device receives the first message sent by the terminal, step S2103b and step S2104 are skipped.

[0239] Step S2104: The terminal sends an RRC connection completion message to the access network device.

[0240] In some embodiments, after receiving the RRC connection establishment message or the RRC connection recovery message sent by the access network device, the terminal sends an RRC connection completion message to the access network device.

[0241] In some embodiments, the RRC connection complete message further includes a first non-access stratum protocol data unit, the first non-access stratum protocol data unit including uplink data.

[0242] Step S2105: The access network device stores and forwards uplink data.

[0243] In some embodiments, the access network device performs a store and forward operation on the uplink data according to the determined second parameter.

[0244] In some embodiments, the access network device may obtain the availability status of the feeder link between itself and the first network element.

[0245] In some embodiments, if the feeder link is unavailable, the access network device stores the uplink data and updates the remaining storage quota of the terminal for storing and forwarding data based on the size of the uplink data.

[0246] In some embodiments, if the feeder link is available, step S2105 is skipped and the uplink data is sent directly to the first network element.

[0247] It should be noted that the initial storage quota of the terminal for storing and forwarding data is the first storage quota in the second parameter.

[0248] Step S2106: The access network device sends an S1-AP initial terminal message to the first network element.

[0249] In some embodiments, if the feeder link between the access network device and the first network element is available, the access network device sends an S1-AP initial termination message to the first network element, where the S1-AP initial termination message includes uplink data.

[0250] In some embodiments, if the first message is an RRC early data request, the S1-AP initial terminal message further includes an "EDT session", where the EDT session is used to indicate the coverage level of the terminal.

[0251] Step S2107: performing uplink data transmission via a non-access stratum protocol data unit.

[0252] For optional implementations of step S2107, reference may be made to the optional implementations of steps 3 to 10 in FIG1D and other related parts of the embodiment involved in FIG1D , which will not be described in detail here.

[0253] Step S2108: The first network element sends downlink data to the access network device.

[0254] In some embodiments, the first network element encapsulates the received downlink data into a third non-access stratum protocol data unit, and sends the third non-access stratum protocol data unit to the access network device through the S1-AP downlink.

[0255] Step S2109: The access network device stores and forwards the downlink data.

[0256] In some embodiments, the service link between the access network device and the terminal is unavailable, and the access network device stores the downlink data.

[0257] In some embodiments, if the service link is available, step S2109 is skipped and downlink data is sent directly to the terminal.

[0258] It should be noted that the access network device updates the terminal's remaining storage and forwarding data quota based on the size of the downlink data. It should be understood that in the disclosed embodiments, the terminal's storage and forwarding data quota is updated in real time. When uplink data or downlink data is stored, the terminal's remaining storage and forwarding data quota decreases accordingly; conversely, when the access network device sends uplink data or downlink data, the terminal's remaining storage and forwarding data quota increases accordingly.

[0259] The embodiment of the present disclosure provides two solutions, step S2110a and step S2110b, according to different situations of whether the received third non-access layer protocol data unit includes downlink data; wherein, step S2110a corresponds to the situation where the third non-access layer protocol data unit includes downlink data, and step S2110b corresponds to the situation where the third non-access layer protocol data unit does not include downlink data.

[0260] Step S2110a: The access network device sends an RRC downlink message to the terminal.

[0261] In some embodiments, a service link between the access network device and the terminal is available, and the access network device sends an RRC downlink data message to the terminal.

[0262] In some embodiments, the RRC downlink data message includes a fourth non-access stratum protocol data unit, and the fourth non-access stratum protocol data unit includes downlink data.

[0263] Step S2110b: The access network device sends an RRC early data completion message to the terminal.

[0264] In some embodiments, the service link between the access network device and the terminal is available, and the access network device sends an RRC early data completion message to the terminal.

[0265] In some embodiments, the RRC early data complete message is used to indicate that the third non-access stratum protocol data unit received by the access network device does not include downlink data.

[0266] Step S2111: performing uplink data transmission via a non-access stratum protocol data unit.

[0267] For optional implementations of step S2111, reference may be made to the optional implementations of step 13 and step 14 in FIG1D , and other related parts of the embodiment involved in FIG1D , which will not be described in detail here.

[0268] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0269] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2111. Any one or more steps of the embodiment of the present disclosure may be implemented separately, or the order may be arbitrarily changed and implemented in free combination without contradiction.

[0270] FIG2B is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2B , the embodiment of the present disclosure relates to a communication method for use in a communication system 100, the method comprising:

[0271] In step S2200 , the terminal decides to transmit uplink data through an access network device of a non-terrestrial network.

[0272] For optional implementations of step S2200, reference may be made to the optional implementations of step 2100 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0273] In some embodiments, the first network element may also be a device of a non-terrestrial network. When the first network element is an MME network element, it can be understood as MME onboard.

[0274] The embodiment of the present disclosure is divided into two schemes, steps S2201a and S2201b, according to different situations of whether an RRC connection has been established between the terminal and the access network device; wherein, step S2201a corresponds to the situation where an RRC connection has not been established between the terminal and the access network device, and step S2201b corresponds to the situation where an RRC connection has been established between the terminal and the access network device.

[0275] Step S2201a: The terminal sends an RRC connection request or an RRC connection recovery request to the access network device.

[0276] For optional implementations of step S2201a, reference may be made to the optional implementations of step 2101a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0277] Step S2201b: The terminal sends an RRC early data request to the access network device.

[0278] For optional implementations of step S2201b, reference may be made to the optional implementations of step 2101b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0279] The embodiment of the present disclosure provides two solutions, step S2202a and step S2202b, according to different situations of whether the access network device stores the third parameter; wherein, step S2202a corresponds to the situation where the access network device does not store the third parameter, and step S2202b corresponds to the situation where the access network device stores the third parameter.

[0280] Step S2202a: The access network device sends a fourth message to the first network element.

[0281] For optional implementations of step S2202a, reference may be made to the optional implementations of step 2102a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0282] Step S2202b: The access network device determines whether to accept the request from the terminal.

[0283] For optional implementations of step S2202b, reference may be made to the optional implementations of step 2102b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0284] The embodiment of the present disclosure provides two solutions, step S2203a and step S2203b, according to different situations of whether the access network device agrees to accept the first message; wherein, step S2203a corresponds to the situation where the access network device refuses to accept the first message, and step S2203b corresponds to the situation where the access network device accepts the RRC connection request or the RRC connection recovery request.

[0285] Step S2203a: The access network device sends an RRC connection rejection message to the terminal.

[0286] For optional implementations of step S2203a, reference may be made to the optional implementations of step 2103a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0287] Step S2203b: The access network device sends an RRC connection establishment message or an RRC connection recovery message to the terminal.

[0288] For optional implementations of step S2203b, please refer to the optional implementations of step 2203b in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0289] Step S2204: The terminal sends an RRC connection completion message to the access network device.

[0290] For optional implementations of step S2204, reference may be made to the optional implementations of step 2104 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0291] Step S2205: The access network device sends an S1-AP initial terminal message to the first network element.

[0292] For optional implementations of step S2205, reference may be made to the optional implementations of step 2106 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0293] In some embodiments, the S1-AP initial terminal message further includes a second parameter, the second parameter including at least one of a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

[0294] Step S2206: The first network element stores and forwards uplink data.

[0295] In some embodiments, the first network element saves the second parameter into the context of the terminal.

[0296] In some embodiments, the first gateway determines whether to store and forward the uplink data based on the second parameter.

[0297] In some embodiments, the first network element determines the status of the feeder link based on at least one of the ephemeris of the satellite, a fourth unavailable period of the feeder link between the first network element and the access network device, and a duration of the fourth unavailable period.

[0298] In some embodiments, if the feeder link is unavailable, the uplink data is stored, and when the feeder link is available, the uplink data is sent to the serving gateway of the ground network.

[0299] In some embodiments, if the feeder link is available, step S2206 is skipped and the uplink data is sent directly to the serving gateway of the ground network.

[0300] Step S2207: Perform uplink data transmission via a non-access stratum protocol data unit.

[0301] For optional implementations of step S2207, reference may be made to the optional implementations of steps 3 to 10 in FIG. 1D and other related parts of the embodiment involved in FIG. 1D , which will not be described in detail here.

[0302] Step S2208: The first network element stores and forwards downlink data.

[0303] In some embodiments, the first network element receives a third non-access stratum protocol data unit sent by a serving gateway S-GW, where the third non-access stratum protocol data unit includes downlink data.

[0304] In some embodiments, the first network element obtains the status of the service link between the first network element and the terminal.

[0305] In some embodiments, if the service link is unavailable, the third non-access layer protocol data unit is stored, and when the service link is available, the third non-access layer protocol data unit is sent to the access network device.

[0306] In some embodiments, if the service link is available, step S2208 is skipped and the third non-access layer protocol data unit is directly sent to the access network device.

[0307] Step S2209: The first network element sends downlink data to the access network device.

[0308] For optional implementations of step S2209, reference may be made to the optional implementations of step 2108 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0309] The embodiment of the present disclosure provides two solutions, step S2210a and step S2210b, according to different situations of whether the received third non-access layer protocol data unit includes downlink data; wherein, step S2210a corresponds to the situation where the third non-access layer protocol data unit includes downlink data, and step S2210b corresponds to the situation where the third non-access layer protocol data unit does not include downlink data.

[0310] Step S2210a: The access network device sends an RRC downlink message to the terminal.

[0311] For optional implementations of step S2210a, reference may be made to the optional implementations of step 2110a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0312] Step S2210b: The access network device sends an RRC early data completion message to the terminal.

[0313] For optional implementations of step S2210b, reference may be made to the optional implementations of step 2110b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0314] Step S2211: Uplink data transmission is performed through a non-access stratum protocol data unit.

[0315] Optional implementations of step S2211 can refer to the optional implementations of steps 1b to 11 in FIG. 1D , and other related parts of the embodiment involved in FIG. 1D , which will not be described in detail here.

[0316] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2201 to S2211. Any one or more steps of the embodiment of the present disclosure may be implemented separately, or the order may be arbitrarily changed and freely combined without contradiction. Figure 2C shows an interactive diagram of the communication method according to the embodiment of the present disclosure. As shown in Figure 2C, the embodiment of the present disclosure relates to a communication method for use in a communication system 100, the method comprising:

[0317] In step S2300 , the terminal decides to transmit uplink data through an access network device of a non-terrestrial network.

[0318] For optional implementations of step S2300, reference may be made to the optional implementations of step 2100 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0319] The embodiment of the present disclosure is divided into two schemes, steps S2301a and S2301b, according to different situations of whether an RRC connection has been established between the terminal and the access network device; wherein, step S2201a corresponds to the situation where an RRC connection has not been established between the terminal and the access network device, and step S2201b corresponds to the situation where an RRC connection has been established between the terminal and the access network device.

[0320] Step S2301a: The terminal sends an RRC connection request or an RRC connection recovery request to the access network device.

[0321] For optional implementations of step S2301a, reference may be made to the optional implementations of step 2101a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0322] Step S2301b: The terminal sends an RRC early data request to the access network device.

[0323] For optional implementations of step S2301b, reference may be made to the optional implementations of step 2101b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0324] The embodiment of the present disclosure provides two solutions, step S2302a and step S2302b, according to different situations of whether the access network device stores the third parameter; wherein, step S2302a corresponds to the situation where the access network device does not store the third parameter, and step S2302b corresponds to the situation where the access network device stores the third parameter.

[0325] Step S2302a: The access network device sends a fourth message to the first network element.

[0326] For optional implementations of step S2302a, reference may be made to the optional implementations of step 2102a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0327] Step S2302b: The access network device determines whether to accept the request from the terminal.

[0328] For optional implementations of step S2302b, reference may be made to the optional implementations of step 2102b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0329] The embodiment of the present disclosure provides two solutions, step S2303a and step S2303b, according to different situations of whether the access network device agrees to accept the first message; wherein, step S2303a corresponds to the situation where the access network device refuses to accept the first message, and step S2303b corresponds to the situation where the access network device accepts the RRC connection request or the RRC connection recovery request.

[0330] Step S2303a: The access network device sends an RRC connection rejection message to the terminal.

[0331] For optional implementations of step S2303a, reference may be made to the optional implementations of step 2103a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0332] Step S2303b: The access network device sends an RRC connection establishment message or an RRC connection recovery message to the terminal.

[0333] For optional implementations of step S2303b, reference may be made to the optional implementations of step 2203b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0334] Step S2304: The terminal sends an RRC connection completion message to the access network device.

[0335] For optional implementations of step S2304, reference may be made to the optional implementations of step 2104 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0336] In some embodiments, the RRC connection complete message further includes a first parameter.

[0337] Step S2305: The access network device stores and forwards uplink data.

[0338] For optional implementations of step S2305, reference may be made to the optional implementations of step 2105 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0339] Step S2306: The access network device sends an S1-AP initial terminal message to the first network element.

[0340] For optional implementations of step S2306, reference may be made to the optional implementations of step 2106 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0341] In some embodiments, the S1-AP initial terminal message further includes a first parameter.

[0342] Step S2307: The first network element determines whether to accept the S1-AP initial terminal message.

[0343] In some embodiments, the first network element determines whether to accept or reject the S1-AP initial terminal message based on the first parameter and a locally stored fourth parameter.

[0344] In some embodiments, the fourth parameter is at least one of a third retention period, a third storage quota, and a third forwarding priority of the stored and forwarded data of the terminal.

[0345] Step S2308: The first network element sends a third message to the terminal.

[0346] In some embodiments, the first network element sends a third message to the terminal through the access network device, where the third message is used to instruct the first network element to accept or reject the S1-AP initial terminal message.

[0347] Optionally, if the third message is used to instruct the first network element to reject the S1-AP initial termination message sent by the access network device, the third message further includes a reason for rejecting the S1-AP initial termination message.

[0348] Step S2309: Perform uplink data transmission via a non-access layer protocol data unit.

[0349] Optional implementations of step S2309 can refer to the optional implementations of steps 3 to 10 in FIG. 1D , and other related parts of the embodiment involved in FIG. 1D , which will not be described in detail here.

[0350] Step S2310: The first network element sends downlink data to the access network device.

[0351] In some embodiments, the first network element receives a third non-access stratum protocol data unit sent by a serving gateway S-GW.

[0352] In some embodiments, the third non-access stratum protocol data unit includes downlink data.

[0353] In some embodiments, the first network element determines the status of the feeder link based on at least one of the ephemeris of the satellite, a fourth unavailable period of the feeder link between the first network element and the access network device, and a duration of the fourth unavailable period;

[0354] In some embodiments, if the feeder link is available, the third non-access stratum protocol data unit is sent to the access network device.

[0355] Step S2311: The access network device stores and forwards downlink data.

[0356] In some embodiments, the access network device receives a third non-access stratum protocol data unit.

[0357] In some embodiments, the access network device determines the status of the service link, where the status of the service link includes available or unavailable.

[0358] In some embodiments, the access network device performs a store and forward operation on the third non-access layer protocol data unit according to the status of the service link.

[0359] The embodiment of the present disclosure provides two solutions, step S2312a and step S2312b, according to different situations of whether the received third non-access layer protocol data unit includes downlink data; wherein, step S2312a corresponds to the situation where the third non-access layer protocol data unit includes downlink data, and step S2312b corresponds to the situation where the third non-access layer protocol data unit does not include downlink data.

[0360] Step S2312a: The access network device sends an RRC downlink message to the terminal.

[0361] For optional implementations of step S2312a, reference may be made to the optional implementations of step 2110a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0362] Step S2312b: The access network device sends an RRC early data completion message to the terminal.

[0363] For optional implementations of step S2312b, reference may be made to the optional implementations of step 2110b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0364] Step S2313: Perform uplink data transmission via a non-access layer protocol data unit.

[0365] For optional implementations of step S2313, reference may be made to the optional implementations of steps 13 to 14 in FIG. 1D and other related parts of the embodiment involved in FIG. 1D , which will not be described in detail here.

[0366] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2301 to S2313. Any one or more steps of the embodiment of the present disclosure may be implemented separately, or the order may be arbitrarily changed and implemented in free combination without contradiction.

[0367] FIG2D is a schematic diagram of an interaction of a communication method according to an embodiment of the present disclosure. As shown in FIG2D , an embodiment of the present disclosure relates to a communication method for use in a communication system 100, the method comprising:

[0368] In step S2400 , the terminal decides to transmit uplink data through an access network device of a non-terrestrial network.

[0369] For optional implementations of step S2400, reference may be made to the optional implementations of step 2100 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0370] In some embodiments, the first network element may also be a device in a non-terrestrial network. When the first network element is an MME network element, this can be understood as MME onboarding. The disclosed embodiments are divided into two schemes, steps S2401a and S2401b, depending on whether an RRC connection has been established between the terminal and the access network device. Step S2401a corresponds to a situation where no RRC connection has been established between the terminal and the access network device, and step S2401b corresponds to a situation where an RRC connection has been established between the terminal and the access network device.

[0371] Step S2401a: The terminal sends an RRC connection request or an RRC connection recovery request to the access network device.

[0372] For optional implementations of step S2401a, reference may be made to the optional implementations of step 2101a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0373] Step S2401b: The terminal sends an RRC early data request to the access network device.

[0374] For optional implementations of step S2401b, reference may be made to the optional implementations of step 2101b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0375] The embodiment of the present disclosure provides two solutions, step S2402a and step S2402b, according to different situations of whether the access network device stores the third parameter; wherein, step S2402a corresponds to the situation where the access network device does not store the third parameter, and step S2402b corresponds to the situation where the access network device stores the third parameter.

[0376] Step S2402a: The access network device sends a fourth message to the first network element.

[0377] For optional implementations of step S2402a, reference may be made to the optional implementations of step 2102a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0378] Step S2402b: The access network device determines whether to accept the request from the terminal.

[0379] For optional implementations of step S2402b, reference may be made to the optional implementations of step 2102b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0380] The embodiment of the present disclosure provides two solutions, step S2403a and step S2403b, according to different situations of whether the access network device agrees to accept the first message; wherein, step S2403a corresponds to the situation where the access network device refuses to accept the first message, and step S2403b corresponds to the situation where the access network device accepts the RRC connection request or the RRC connection recovery request.

[0381] Step S2403a: The access network device sends an RRC connection rejection message to the terminal.

[0382] For optional implementations of step S2403a, reference may be made to the optional implementations of step 2103a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0383] Step S2403b: The access network device sends an RRC connection establishment message or an RRC connection recovery message to the terminal.

[0384] For optional implementations of step S2403b, reference may be made to the optional implementations of step 2203b in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0385] Step S2404: The terminal sends an RRC connection completion message to the access network device.

[0386] For optional implementations of step S2404, reference may be made to the optional implementations of step 2104 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0387] In some embodiments, the RRC connection complete message further includes a first parameter.

[0388] Step S2405: The access network device sends an S1-AP initial terminal message to the first network element.

[0389] For optional implementations of step S2405, reference may be made to the optional implementations of step 2106 in FIG2A and other related parts of the embodiment involved in FIG2A, which will not be described in detail here.

[0390] In some embodiments, the S1-AP initial terminal message further includes a first parameter.

[0391] Step S2406: The first network element determines whether to accept the S1-AP initial terminal message.

[0392] In some embodiments, the first network element determines whether to accept or reject the S1-AP initial terminal message based on the first parameter and a locally stored fourth parameter.

[0393] In some embodiments, the fourth parameter is at least one of a third retention period, a third storage quota, and a third forwarding priority of the stored and forwarded data of the terminal.

[0394] Step S2407: The first network element stores and forwards uplink data.

[0395] In some embodiments, the first network element determines the status of the feeder link based on at least one of the ephemeris of the satellite, a fourth unavailable period of the feeder link between the first network element and the access network device, and a duration of the fourth unavailable period.

[0396] In some embodiments, if the feeder link is unavailable, the uplink data is stored, and when the feeder link is available, the uplink data is sent to the serving gateway of the ground network.

[0397] In some embodiments, if a feeder link is available, uplink data is sent directly to a serving gateway of the terrestrial network.

[0398] Step S2408: The first network element sends a third message to the terminal.

[0399] In some embodiments, the first network element sends a third message to the terminal through the access network device, where the third message is used to instruct the first network element to accept or reject the S1-AP initial terminal message.

[0400] Optionally, if the third message is used to instruct the first network element to reject the S1-AP initial termination message sent by the access network device, the third message further includes a reason for rejecting the S1-AP initial termination message.

[0401] Step S2409: performing uplink data transmission via a non-access stratum protocol data unit.

[0402] Optional implementations of step S2409 can be found in the optional implementations of steps 3 to 10 in FIG. 1D , and other related parts of the embodiment involved in FIG. 1D , which will not be described in detail here.

[0403] Step S2410: The first network element stores and forwards downlink data.

[0404] In some embodiments, the first network element receives a third non-access stratum protocol data unit sent by a serving gateway S-GW, where the third non-access stratum protocol data unit includes downlink data.

[0405] In some embodiments, the first network element determines a status of a service link between the first network element and the terminal.

[0406] In some embodiments, if the service link is unavailable, the third non-access layer protocol data unit is stored, and when the service link is available, the third non-access layer protocol data unit is sent to the access network device.

[0407] In some embodiments, if the service link is available, a third non-access layer protocol data unit is sent to the access network device.

[0408] Step S2411: The first network element sends downlink data to the access network device.

[0409] For optional implementations of step S2411, reference may be made to the optional implementations of step 2108 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0410] The embodiment of the present disclosure provides two solutions, step S2412a and step S2412b, according to different situations of whether the received third non-access layer protocol data unit includes downlink data; wherein, step S2412a corresponds to the situation where the third non-access layer protocol data unit includes downlink data, and step S2412b corresponds to the situation where the third non-access layer protocol data unit does not include downlink data.

[0411] Step S2412a: The access network device sends an RRC downlink message to the terminal.

[0412] For optional implementations of step S2412a, reference may be made to the optional implementations of step 2110a in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0413] Step S2412b: The access network device sends an RRC early data completion message to the terminal.

[0414] For optional implementations of step S2412b, reference may be made to the optional implementations of step 2110b in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0415] Step S2413: Uplink data transmission is performed through a non-access layer protocol data unit.

[0416] For optional implementations of step S2413, reference may be made to the optional implementations of steps 13 to 14 in FIG. 1D and other related parts of the embodiment involved in FIG. 1D , which will not be described in detail here.

[0417] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2401 to S2413. Any one or more steps of the embodiment of the present disclosure may be implemented separately, or the order may be arbitrarily changed and implemented in free combination without contradiction.

[0418] FIG3 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3 , the embodiment of the present disclosure involves a terminal 101, and the method includes:

[0419] In step S3101, the terminal decides to transmit uplink data through an access network device of a non-terrestrial network.

[0420] For optional implementations of step S3101, please refer to the optional implementations of step 2100 in Figure 2A, step S2200 in Figure 2B, step S2300 in Figure 2C, step S2400 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0421] The embodiment of the present disclosure is divided into two schemes, steps S3102a and S3102b, according to different situations of whether an RRC connection has been established between the terminal and the access network device; wherein, step S3102a corresponds to the situation where an RRC connection has not been established between the terminal and the access network device, and step S3102b corresponds to the situation where an RRC connection has been established between the terminal and the access network device.

[0422] Step S3102a: The terminal sends an RRC connection request or an RRC connection recovery request to the access network device.

[0423] The optional implementation of step S3102a can be found in the optional implementation of step S2101a in Figure 2A, step S2201a in Figure 2B, step S2301a in Figure 2C, step S2401a in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0424] In some embodiments, the terminal sends a first message to the access network device.

[0425] In some embodiments, the first message includes an RRC connection request or an RRC connection resumption request.

[0426] Step S3102b: The terminal sends an RRC early data request to the access network device.

[0427] The optional implementation of step S3102b can be found in the optional implementation of step S2101b in Figure 2A, step S2201b in Figure 2B, step S2301b in Figure 2C, step S2401b in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0428] In some embodiments, the terminal sends a first message to the access network device.

[0429] In some embodiments, the first message is an RRC Early Data Request.

[0430] The embodiment of the present disclosure provides two solutions, step S3103a and step S3103b, according to different situations of whether the access network device agrees to accept the first message; wherein, step S3103a corresponds to the situation where the access network device refuses to accept the first message, and step S3103b corresponds to the situation where the access network device accepts the RRC connection request or the RRC connection recovery request.

[0431] Step S3103a: Receive an RRC connection rejection message sent by the access network device.

[0432] For optional implementations of step S3103a, please refer to the optional implementations of step 2103a in Figure 2A, step S2203a in Figure 2B, step S2303a in Figure 2C, and step S2403a in Figure 2D, as well as other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0433] Step S3103b: Receive an RRC connection establishment message or an RRC connection recovery message sent by the access network device.

[0434] For the optional implementation of step S3103b, please refer to the optional implementation of step 2103b in Figure 2A, step S2203b in Figure 2B, step S2303b in Figure 2C, step S2403b in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0435] Step S3104: Send an RRC connection completion message to the access network device.

[0436] For optional implementations of step S3104, please refer to the optional implementations of step 2104 in Figure 2A, step S2204 in Figure 2B, step S2304 in Figure 2C, step S2404 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0437] Step S3105a: Receive the RRC downlink message sent by the access network device.

[0438] For the optional implementation of step S3105a, please refer to the optional implementation of step 2110a in Figure 2A, step S2210a in Figure 2B, step S2312a in Figure 2C, step S2412a in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0439] Step S3105b: Receive the RRC early data completion message sent by the access network device.

[0440] The optional implementation of step S3105b can be found in the optional implementation of step 2110b of Figure 2A, step S2210b of Figure 2B, step S2312b of Figure 2C, step S2412b of Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0441] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3105b. Any one or more steps of the embodiment of the present disclosure may be implemented separately, or the order may be arbitrarily changed and implemented in free combination without contradiction.

[0442] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure relates to an access network device of a non-terrestrial network, and the method includes:

[0443] Step S4101a: receiving an RRC connection request or an RRC connection recovery request sent by the terminal.

[0444] For optional implementations of step S4101a, please refer to the optional implementations of step 2101a in Figure 2A, step S2201a in Figure 2B, step S2301a in Figure 2C, and step S2401a in Figure 2D, as well as other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0445] Step S4101b: receiving an RRC early data request sent by the terminal.

[0446] For the optional implementation of step S4101b, please refer to the optional implementation of step 2101b in Figure 2A, step S2201b in Figure 2B, step S2301b in Figure 2C, step S2401b in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0447] Step S4102a: Send a fourth message to the first network element.

[0448] For optional implementations of step S4102a, please refer to the optional implementations of step 2102a in Figure 2A, step S2202a in Figure 2B, step S2302a in Figure 2C, and step S2402a in Figure 2D, as well as other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0449] Step S4102b, determining whether to accept the request from the terminal.

[0450] For optional implementations of step S4102b, please refer to the optional implementations of step 2102b in Figure 2A, step S2202b in Figure 2B, step S2302b in Figure 2C, and step S2402b in Figure 2D, as well as other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0451] Step S4103a: Send an RRC connection rejection message to the terminal.

[0452] For optional implementations of step S4103a, please refer to the optional implementations of step 2103a in Figure 2A, step S2203a in Figure 2B, step S2303a in Figure 2C, and step S2403a in Figure 2D, as well as other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0453] Step S4103b: Send an RRC connection establishment message or an RRC connection recovery message to the terminal.

[0454] For the optional implementation of step S4103b, please refer to the optional implementation of step 2103b in Figure 2A, step S2203b in Figure 2B, step S2303b in Figure 2C, step S2403b in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0455] Step S4104: receiving an RRC connection completion message sent by the terminal.

[0456] For optional implementations of step S4104, please refer to the optional implementations of step 2104 in Figure 2A, step S2204 in Figure 2B, step S2304 in Figure 2C, step S2404 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0457] Step S4105: store and forward uplink data.

[0458] For optional implementations of step S4105, reference may be made to step 2105 in FIG. 2A , the optional implementations of step S2305 in FIG. 2C , and other related parts in the embodiments involved in FIG. 2A and FIG. 2C , which will not be described in detail here.

[0459] Step S4106: Send a SA-AP initial terminal message to the first network element.

[0460] For the optional implementation of step S4106, please refer to the optional implementation of step 2106 in Figure 2A, step S2205 in Figure 2B, step S2306 in Figure 2C, step S2405 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0461] Step S4107: performing uplink data transmission via a non-access stratum protocol data unit.

[0462] For optional implementations of step S4107, please refer to the optional implementations of step 2107 in Figure 2A, step S2207 in Figure 2B, step S2309 in Figure 2C, step S2409 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0463] Step S4108: Receive downlink data sent by the first network element.

[0464] For optional implementations of step S4108, please refer to the optional implementations of step 2108 in Figure 2A, step S2209 in Figure 2B, step S2310 in Figure 2C, step S2411 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0465] Step S4109: store and forward downlink data.

[0466] Optional implementations of step S4109 can be found in step 2109 of FIG. 2A , optional implementations of step S2311 of FIG. 2C , and other related parts of the embodiments involved in FIG. 2A and FIG. 2C , which will not be described in detail here.

[0467] The embodiment of the present disclosure provides two solutions, step S4110a and step S4110b, according to different situations of whether the received third non-access layer protocol data unit includes downlink data; wherein, step S4110a corresponds to the situation where the third non-access layer protocol data unit includes downlink data, and step S4110b corresponds to the situation where the third non-access layer protocol data unit does not include downlink data.

[0468] Step S4110a: Send an RRC downlink message to the terminal.

[0469] For optional implementations of step S4110a, please refer to the optional implementations of step 2110a in Figure 2A, step S2210a in Figure 2B, step S2312a in Figure 2C, and step S2412a in Figure 2D, as well as other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0470] Step S4110b: Send an RRC early data request to the terminal.

[0471] For the optional implementation of step S4110b, please refer to the optional implementation of step 2110b in Figure 2A, step S2210b in Figure 2B, step S2312b in Figure 2C, step S2412b in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0472] Step S4111: Uplink data transmission is performed through a non-access layer protocol data unit.

[0473] The optional implementation of step S4111 can refer to the optional implementation of step 2111 in Figure 2A, step S2211 in Figure 2B, step S2313 in Figure 2C, step S2413 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0474] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4101a to S4111. Any one or more steps of the embodiment of the present disclosure may be implemented separately, or the order may be arbitrarily changed and implemented in free combination without contradiction.

[0475] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure involves a first network element 103, and the method includes:

[0476] Step S5101: Receive a fourth message sent by an access network device.

[0477] For optional implementations of step S5101, please refer to the optional implementations of step 2102a in Figure 2A, step S2202a in Figure 2B, step S2302a in Figure 2C, and step S2402a in Figure 2D, as well as other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0478] Step S5102: Receive an S1-AP initial terminal message sent by the access network device.

[0479] For optional implementations of step S5102, please refer to the optional implementations of step 2106 in Figure 2A, step S2205 in Figure 2B, step S2306 in Figure 2C, step S2405 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0480] Step S5103: Determine whether to accept the S1-AP initial terminal message.

[0481] Optional implementations of step S5103 can be found in the optional implementations of step S2307 in FIG. 2C , step S2406 in FIG. 2D , and other related parts in the embodiments involved in FIG. 2C and FIG. 2D , which will not be described in detail here.

[0482] Step S5104: store and forward uplink data.

[0483] For optional implementations of step S5104, reference may be made to the optional implementations of step S2206 in FIG. 2B , step S2407 in FIG. 2D , and other related parts in the embodiments involved in FIG. 2B and FIG. 2D , which will not be described in detail here.

[0484] Step S5105: Send a third message to the terminal through the access network device.

[0485] The optional implementation of step S5105 can refer to the optional implementation of step S2308 in Figure 2C, step S2408 in Figure 2D, and other related parts in the embodiments involved in Figures 2C and 2D, which will not be repeated here.

[0486] Step S5106: Perform uplink data transmission via a non-access stratum protocol data unit.

[0487] The optional implementation of step S5106 can be found in the optional implementation of step 2107 in Figure 2A, step S2207 in Figure 2B, step S2309 in Figure 2C, step S2409 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0488] Step S5107: store and forward downlink data.

[0489] The optional implementation of step S5107 can refer to the optional implementation of step S2208 in Figure 2B, step S2410 in Figure 2D, and other related parts in the embodiments involved in Figures 2B and 2D, which will not be repeated here.

[0490] Step S5108: Send downlink data to the access network device.

[0491] The optional implementation of step S5108 can be found in the optional implementation of step 2108 in Figure 2A, step S2209 in Figure 2B, step S2310 in Figure 2C, step S2411 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0492] Step S5109: performing uplink data transmission via a non-access stratum protocol data unit.

[0493] The optional implementation of step S5109 can be found in the optional implementation of step 2111 in Figure 2A, step S2211 in Figure 2B, step S2313 in Figure 2C, step S2413 in Figure 2D, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, and 2D, which will not be repeated here.

[0494] The communication method involved in the embodiment of the present disclosure may include at least one of steps S5101 to S5109. Any one or more steps of the embodiment of the present disclosure may be implemented separately, or the order may be arbitrarily changed and implemented in free combination without contradiction.

[0495] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided that includes units or modules for implementing each step performed by a first network element in any of the above methods.

[0496] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. 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. 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), which realizes the functions of some or all of the above units or modules 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, it 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 the form of software called by the processor, and the rest by hardware circuits.

[0497] 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 central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and 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.

[0498] FIG6A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG6A , the terminal may include: a processing module 6101 and a sending module 6102 .

[0499] In some embodiments, the processing module is configured to determine that a service link with an access network device of a non-terrestrial network is available.

[0500] In some embodiments, the sending module is configured to send a first message to the access network device, so that the access network device determines a second parameter according to the first message;

[0501] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal; the first parameter includes one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0502] The QoS information includes the requested QoS or QoS priority;

[0503] The second parameter is used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

[0504] Optionally, the above-mentioned receiving module is used to execute the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, such as step S3101, which will not be repeated here.

[0505] FIG6B is a schematic diagram of the structure of an access network device of a non-terrestrial network proposed in an embodiment of the present disclosure. As shown in FIG6B , the access network device of the non-terrestrial network may include: a receiving module 6201 and a processing module 6202 .

[0506] In some embodiments, the receiving module is used to receive a first message sent by the terminal.

[0507] In some embodiments, the processing module is configured to determine a second parameter of the access network device according to the first message;

[0508] The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal, the first parameter including at least one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding;

[0509] The QoS information includes the requested QoS or QoS priority;

[0510] The second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority for stored and forwarded data.

[0511] Optionally, the above-mentioned receiving module is used to execute the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, such as step S4101, which will not be repeated here.

[0512] FIG6C is a schematic diagram of the structure of a first network element proposed in an embodiment of the present disclosure. As shown in FIG6C , the first network element may include: a receiving module 6301 .

[0513] In some embodiments, the receiving module is configured to receive a fifth message sent by an access network device of a non-terrestrial network;

[0514] The fifth message is the fourth message or the S1-AP initial terminal message;

[0515] The fourth message is used to request a third parameter related to storage and forwarding;

[0516] The S1-AP initial terminal message includes uplink data; the third parameter includes at least one of the second information and the third information;

[0517] The second information includes at least one of the following:

[0518] a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority;

[0519] The third information includes at least one of the following:

[0520] Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

[0521] Optionally, the above-mentioned receiving module is used to execute the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, such as step S5101, which will not be repeated here.

[0522] Figure 7A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a device (e.g., an access network device, a core network device, etc.), or an IoT device, or a chip, chip system, or processor that supports the device to implement any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0523] As shown in Figure 7A, the communication device 8100 includes one or more processors 8101. The processor 8101 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 the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0524] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2101, but not limited thereto), and the processor 8101 performs at least one of the other steps (e.g., step S2102, 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.

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

[0526] The communication device 8100 described in the above embodiments may be a device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 7A . 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 device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0527] 7B is a schematic diagram of the structure of the chip 8200 proposed in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG7B , but the present disclosure is not limited thereto.

[0528] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

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

[0530] In some embodiments, the interface circuit 8202 performs at least one of the communication steps (e.g., step S2101, but not limited thereto) in the above method, such as sending and / or receiving. The interface circuit 8202 performing the communication steps (e.g., sending and / or receiving) in the above method, for example, means that the interface circuit 8202 performs data exchange between the processor 8201, chip 8200, memory 8203, or a transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps (e.g., step S2102, but not limited thereto).

[0531] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute 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 temporary storage medium.

[0532] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0533] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, characterized in that: Executed by a terminal, the method includes: Determining that a service link with an access network device of a non-terrestrial network is available, sending a first message to the access network device, so that the access network device determines a second parameter according to the first message; The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal; the first parameter includes one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding; The QoS information includes the requested QoS or QoS priority; The second parameter is used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

2. The method according to claim 1, characterized in that The determining that the service link between the access network device and the non-terrestrial network is available also includes: Determining, according to the first information, to transmit the uplink data to the access network device; The first information includes at least one of the following: a first unavailable period of the service link; duration of the first unavailable period; a second retention period for store-and-forward data; A second storage quota for store-and-forward data; a first forwarding priority of the stored and forwarded data; Store and forward strategy.

3. The method according to claim 1 or 2, characterized in that Determining that a service link between the terminal and the access network device of the non-terrestrial network is available is performed by at least one of the following: a first unavailable period of the service link; duration of the first unavailable period; Satellite's ephemeris.

4. The method according to any one of claims 1 to 3, characterized in that The sending of the first message to the access network device further includes: receiving a second message sent by the access network device; The first message is an RRC connection request, the second message is used to indicate acceptance of the first message, and the second message is an RRC connection establishment message; or The first message is an RRC connection recovery request, the second message is used to indicate acceptance of the first message, and the second message is an RRC connection recovery message; or, The first message is an RRC connection request, an RRC connection recovery request, or an RRC early data request, and the second message is used to indicate the rejection of the first message. The second message is an RRC connection rejection message, and the RRC connection rejection message includes the reason for rejecting the first message.

5. The method according to claim 4, characterized in that The second message is used to indicate acceptance of the first message; The receiving of the second message sent by the access network device further includes: An RRC connection completion message is sent to the access network device, where the RRC connection completion message includes a first non-access layer protocol data unit, and the first non-access layer protocol data unit includes the uplink data.

6. The method according to claim 5, characterized in that The RRC connection completion message also includes the first parameter.

7. The method according to any one of claims 1 to 3, characterized in that The first message is an RRC early data request; The sending a first message to the access network device includes: Sending a second non-access layer protocol data unit to the access network device; The second non-access layer protocol data unit includes the first message and the uplink data.

8. The method according to claim 5 or 6, characterized in that The sending of the RRC connection completion message to the access network device further includes: receiving a third message sent by the access network device, where the third message is used to instruct the first network element to accept or reject the S1-AP initial terminal message; The S1-AP initial terminal message is determined and sent by the access network device according to the RRC connection completion message or the RRC early data request sent by the terminal, and the S1-AP initial terminal message includes the uplink data.

9. The method according to claim 8, characterized in that The third message is used to instruct the first network element to reject the S1-AP initial termination message sent by the access network device, and the third message includes a reason for rejecting the S1-AP initial termination message.

10. The method according to claim 5 or 6, characterized in that The sending of the RRC connection completion message to the access network device further includes: Receiving an RRC downlink data message or an RRC early data complete message sent by the access network device; The RRC downlink data message includes a fourth non-access stratum protocol data unit, and the fourth non-access stratum protocol data unit includes downlink data; The RRC early data complete message is used to indicate that the third non-access layer protocol data unit received by the access network device does not include downlink data.

11. A communication method, characterized in that: The method is performed by an access network device of a non-terrestrial network, and includes: The receiving terminal sends a first message, and determines a second parameter of the access network device according to the first message; The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal, the first parameter including at least one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding; The QoS information includes the requested QoS or QoS priority; The second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority for stored and forwarded data.

12. The method according to claim 11, characterized in that The determining the second parameter according to the first message includes: Acquire, according to the first message, a third parameter related to storage and forwarding; The second parameter is determined according to at least one of the first parameter and the third parameter.

13. The method according to claim 12, characterized in that The acquiring of a third parameter related to storage and forwarding includes: Acquire the third parameter locally; or, Send a fourth message to the first network element, where the fourth message is used to request the third parameter, and receive the third parameter sent by the first network element.

14. The method according to claim 12 or 13, characterized in that The third parameter includes at least one of the second information and the third information; The second information includes at least one of the following: a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a third unavailable period of the feeder link between the access network device and the first network element, a duration of the third unavailable period, a first retention period for stored and forwarded data, a first storage quota, and a second forwarding priority; The third information includes at least one of the following: Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

15. The method according to any one of claims 10 to 14, characterized in that: The first message is an RRC connection request or an RRC connection recovery request; The receiving terminal sends a first message, and then further includes: determining, based on at least one of the first parameter, the second parameter, and the third parameter, whether to accept or reject the first message; Sending a second message to the terminal, where the second message is used to indicate acceptance or rejection of the first message; The first message is an RRC connection request, the second message is used to indicate acceptance of the first message, and the second message is an RRC connection establishment message; or The first message is an RRC connection recovery request, the second message is used to indicate acceptance of the first message, and the second message is an RRC connection recovery message; or, The first message is an RRC connection request, an RRC connection recovery request, or an RRC early data request, and the second message is used to indicate the rejection of the first message. The second message is an RRC connection rejection message, and the RRC connection rejection message includes the reason for rejecting the first message.

16. The method according to claim 15, characterized in that The sending of a second message to the terminal, where the second message is used to indicate receipt of the first message, further includes: An RRC connection completion message sent by the terminal is received, where the RRC connection completion message includes a first non-access stratum protocol data unit, and the first non-access stratum protocol data unit includes the uplink data.

17. The method according to claim 16, characterized in that The RRC connection completion message also includes the first parameter.

18. The method according to any one of claims 10 to 15, characterized in that: The first message is an RRC early data request; The receiving terminal sending a first message includes: receiving a second non-access layer protocol data unit sent by the terminal; The second non-access layer protocol data unit includes the first message and the uplink data.

19. The method according to any one of claims 10 to 18, characterized in that: The determining of the second parameter further comprises: Perform a store and forward operation on the uplink data according to the second parameter.

20. The method according to claim 19, characterized in that The performing a store and forward operation on the uplink data includes: The feeder link between the access network device and the first network element is unavailable, storing the uplink data, updating the storage quota of the remaining stored and forwarded data of the terminal according to the first storage quota, and sending an S1-AP initial terminal message including the uplink data to the first network element when the feeder link is available; The feeder link is available, and an S1-AP initial terminal message including the uplink data is sent to the first network element.

21. The method according to claim 20, characterized in that The S1-AP initial terminal message also includes the second parameter.

22. The method according to claim 20, characterized in that The step of sending an S1-AP initial terminal message including the uplink data to the first network element further includes: Receive a third message sent by the first network element, and send the third message to the terminal, where the third message is used to instruct the first network element to accept or reject the S1-AP initial terminal message.

23. The method according to claim 22, characterized in that The third message is used to instruct the first network element to reject the S1-AP initial termination message sent by the access network device. The third message also includes a reason for rejecting the S1-AP initial termination message.

24. The method according to any one of claims 20 to 23, characterized in that: The step of sending an S1-AP initial terminal message including the uplink data to the first network element further includes: A third non-access stratum protocol data unit sent by the first network element is received, where the third non-access stratum protocol data unit includes downlink data.

25. The method according to claim 24, characterized in that The receiving of the third non-access layer protocol data unit sent by the first network element further includes: The service link between the access network device and the terminal is unavailable, storing the downlink data and updating the storage quota of the remaining stored and forwarded data according to the first retention period, the storage quota of the remaining stored and forwarded data, and the second forwarding priority; The service link is available, sending an RRC downlink data message or an RRC early data complete message to the terminal; The RRC downlink data message includes a fourth non-access stratum protocol data unit, and the fourth non-access stratum protocol data unit includes the downlink data; The RRC early data complete message is used to indicate that the third non-access layer protocol data unit received by the access network device does not include downlink data.

26. A communication method, characterized in that: Executed by a first network element, the method includes: receiving a fifth message sent by an access network device of a non-terrestrial network; The fifth message is the fourth message or the S1-AP initial terminal message; The fourth message is used to request a third parameter related to storage and forwarding; The S1-AP initial terminal message includes uplink data; The third parameter includes at least one of the second information and the third information; The second information includes at least one of the following: a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority; The third information includes at least one of the following: Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

27. The method according to claim 26, characterized in that The fifth message is the fourth message; The step of receiving the fifth message sent by the access network device of the non-terrestrial network further includes: Determining the third parameter, and sending the third parameter to the access network device; Receive an S1-AP initial terminal message sent by the access network device.

28. The method according to claim 27, characterized in that The determining of the third parameter includes: Get the third parameter of local storage; or, Send a request to other network elements storing the third parameter, so that the other network elements send the third parameter to the first network element.

29. The method according to claim 26, wherein The fifth message is an S1-AP initial terminal message; Before receiving the fifth message sent by the access network device of the non-terrestrial network, the method further includes: Receive a fourth message sent by the access network device.

30. The method according to any one of claims 26 to 29, characterized in that: The S1-AP initial terminal message further includes a second parameter, which includes at least one of a first retention period, a first storage quota, and a second forwarding priority of stored and forwarded data.

31. The method according to claim 30, wherein The fifth message is an S1-AP initial terminal message; The step of receiving the fifth message sent by the access network device of the non-terrestrial network further includes: The second parameter is saved in the context of the terminal.

32. The method according to any one of claims 26 to 29, wherein: The S1-AP initial terminal message further includes a first parameter, which includes at least one of a data size of the uplink data, QoS information, and a first forwarding priority of storage and forwarding, and the QoS information includes a requested QoS or a QoS priority.

33. The method according to claim 32, characterized in that The step of receiving the fifth message sent by the access network device of the non-terrestrial network further includes: determining, based on the first parameter and a locally stored fourth parameter, whether to accept or reject the S1-AP initial terminal message; sending a third message to the terminal through the access network device, where the third message is used to instruct the first network element to accept or reject the S1-AP initial terminal message; The fourth parameter is at least one of a third retention period, a third storage quota, and a third forwarding priority of the data stored and forwarded by the terminal.

34. The method according to claim 33, wherein The third message is used to instruct the first network element to reject the S1-AP initial termination message sent by the access network device. The third message also includes a reason for rejecting the S1-AP initial termination message.

35. The method according to claim 28, wherein The step of receiving the fifth message sent by the access network device of the non-terrestrial network further includes: When a link between the first network element and the serving gateway is unavailable, the uplink data is stored, and when the link is available, the uplink data is sent to the serving gateway; The link between the first network element and the serving gateway is available, and the uplink data is sent to the serving gateway.

36. The method according to claim 35, characterized in that The sending of the uplink data to the serving gateway further includes: Receiving downlink data sent by the serving gateway; A third non-access stratum protocol data unit is sent to the access network device, where the third non-access stratum protocol data unit includes the downlink data.

37. The method according to claim 36, wherein The sending of the third non-access layer protocol data unit to the access network device further includes: determining a state of the feeder link based on at least one of a satellite ephemeris, a fourth unavailable period of the feeder link between the first network element and the access network device, and a duration of the fourth unavailable period; When the feeder link is unavailable, storing the third non-access layer protocol data unit, and sending the third non-access layer protocol data unit to the access network device when the feeder link is available; The feeder link is available, and the third non-access layer protocol data unit is sent to the access network device.

38. A terminal, characterized in that: include: A processing module, configured to determine whether a service link between the access network device and the non-terrestrial network is available; a sending module, configured to send a first message to the access network device, so that the access network device determines a second parameter according to the first message; The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal; the first parameter includes one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding; The QoS information includes the requested QoS or QoS priority; The second parameter is used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority of the stored and forwarded data.

39. An access network device for a non-terrestrial network, characterized in that: include: A receiving module, configured to receive a first message sent by a terminal; a processing module, configured to determine a second parameter of the access network device according to the first message; The first message includes a first parameter related to storage and forwarding of uplink data requested by the terminal, the first parameter including at least one of the following: data size of the uplink data, QoS information, and a first forwarding priority for storage and forwarding; The QoS information includes the requested QoS or QoS priority; The second parameter is a parameter used by the access network device to determine whether to store and forward the uplink data, and the second parameter includes at least one of the following: a first retention period, a first storage quota, and a second forwarding priority for stored and forwarded data.

40. A first network element, characterized in that: include: a receiving module, configured to receive a fifth message sent by an access network device of a non-terrestrial network; The fifth message is the fourth message or the S1-AP initial terminal message; The fourth message is used to request a third parameter related to storage and forwarding; The S1-AP initial terminal message includes uplink data; The third parameter includes at least one of the second information and the third information; The second information includes at least one of the following: a second unavailable period of the service link between the terminal and the access network device, a duration of the second unavailable period, a first data retention period for storage and forwarding, a first storage quota, and a second forwarding priority; The third information includes at least one of the following: Subscription information of the terminal, QoS configuration information negotiated by EPS, and wireless capabilities.

41. A terminal, characterized in that: include: one or more processors; The processor is configured to execute the communication method according to any one of claims 1 to 10.

42. An access network device for a non-terrestrial network, characterized in that: include: one or more processors; The processor is configured to execute the communication method according to any one of claims 11 to 25.

43. A first network element, characterized in that: include: one or more processors; The processor is configured to execute the communication method according to any one of claims 26 to 37.

44. A communication system, characterized in that include: A terminal, configured to implement the communication method according to any one of claims 1 to 10; Access network equipment of a non-terrestrial network, configured to implement the communication method according to any one of claims 11 to 25; The first network element is used to implement the communication method according to any one of claims 26 to 37.

45. A storage medium storing instructions, characterized in that: When the instructions are executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1 to 10, 11 to 25, and 26 to 37.

Images