Communication method and device based on NTN, communication equipment, communication system and storage medium

CN119586174APending Publication Date: 2025-03-07BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380010024.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-07-07
Publication Date
2025-03-07

AI Technical Summary

Technical Problem

In the NTN scenario, in the storage and forwarding mode of the satellite access network, the terminal device cannot effectively authorize the use of the storage and forwarding function, resulting in the interruption of service communication when the feeder link cannot provide continuous connection.

Method used

By implementing the authorization mechanism of storage and forwarding functions on the terminal and network side, the terminal receives authorization messages to enable the storage and forwarding functions, and through the management of storage and forwarding time information, it ensures that data can be interrupted when the link between satellite and ground stations is interrupted Store and forward data.

Benefits of technology

In the NTN scenario, the service communication between the terminal and the network is not interrupted, ensuring the storage and forwarding capabilities of data when the link is interrupted, and adapting to a satellite communication environment with discontinuous coverage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119586174A_ABST
    Figure CN119586174A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an NTN-based communication method and device, communication equipment, a communication system and a storage medium. The method comprises the steps that a first message from a first network function is received, the first message is used for indicating and authorizing a terminal to use a storage and forwarding function, and the storage and forwarding function is used for transmitting data of the terminal in a storage and forwarding mode in NTN access. According to the technical scheme provided by the embodiment of the invention, the service communication between the terminal side and the network side is realized under the condition that the feeder link cannot provide continuous connection in the NTN scene.
Need to check novelty before this filing date? Find Prior Art

Description

NTN-based communication method and device, communication equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication method and apparatus, a communication device, a communication system, and a storage medium based on a non-terrestrial network (NTN). Background Art

[0002] In the field of communications technology, satellite communications can complement cellular communications. With the development of communications technology, the integration of satellite and cellular communications will gradually deepen. For example, in a 5G communications network, a UE can access the 5G core network via a satellite access network. This is a type of NTN network. When the satellite access network supports store-and-forward mode, authorization is required for the terminal's service to use the access network's store-and-forward feature.

[0003] Summary of the Invention

[0004] In the NTN scenario, in order to adapt to the satellite access network working in the store and forward mode, the authorized terminal needs to be able to use the store and forward function.

[0005] The embodiments of the present disclosure provide a communication method and apparatus based on NTN, a communication device, a communication system, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method based on an NTN is provided. The method is performed by a terminal. The method includes receiving a first message from a first network function, wherein the first message is used to instruct the terminal to authorize use of a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner during NTN access.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method based on an NTN is provided. The method is performed by a first network function. The method includes: sending a first message to a terminal, wherein the first message is used to indicate authorization for the terminal to use a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner during NTN access.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method based on an NTN is provided. The method is performed by a second network function. The method includes: receiving a second message from a terminal, wherein the second message includes a request for store-and-forward time information from the second network function; and sending a third message to the terminal, wherein the third message includes the store-and-forward time information.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a communication method based on an NTN is provided. The method includes: sending a first message to a terminal, wherein the first message is used to instruct the terminal to authorize the terminal to use a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner during NTN access.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a communication device based on an NTN is provided. The device is disposed in a terminal. The device includes a receiving module. The receiving module is configured to receive a first message from a first network function. The first message is used to authorize the terminal to use a store-and-forward function. The store-and-forward function is used to transmit terminal data in a store-and-forward manner during NTN access.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a communication device based on an NTN is provided. The device is provided in a first network function. The device includes a sending module. The sending module is configured to send a first message to a terminal. The first message is used to indicate authorization for the terminal to use a store-and-forward function. The store-and-forward function is used to transmit terminal data in a store-and-forward manner during NTN access.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a communication device based on an NTN is provided. The device is executed by a second network function. The device includes a receiving module and a sending module. The receiving module is configured to receive a second message from a terminal. The second message includes a request for store-and-forward time information from the second network function. The sending module is configured to send a third message to the terminal. The third message includes the store-and-forward time information.

[0013] According to an eighth aspect of the embodiments of the present disclosure, a communication device is provided. The communication device includes at least one processor. The processor is configured to invoke instructions to execute the communication method described in the first, second, third, or fourth aspects.

[0014] According to a ninth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a first network function and a third network function. The third network function is configured to send a terminal's subscription information to the first network function. The first network function is configured to receive the subscription information from the third network function and, based on the subscription information and / or operator policy, determine whether to authorize the terminal to use a store-and-forward function.

[0015] According to a tenth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a terminal, an access network device, and a core network device. The terminal is configured to implement the communication method described in the first aspect. The core network device is configured to implement the communication methods described in the second, third, and fourth aspects.

[0016] According to an eleventh aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed by a processor, the instructions perform the communication method described in the first, second, third, or fourth aspects.

[0017] According to a twelfth aspect of the embodiments of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a processor, they perform the communication method described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0018] Through the embodiments of the present disclosure, the network side can authorize the terminal to use the store and forward function, thereby realizing service communication between the terminal side and the network side when the feeder link cannot provide continuous connection in the NTN scenario.

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

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0021] FIG1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0022] FIG2 is a schematic diagram of a communication scenario provided according to an embodiment of the present disclosure.

[0023] FIG3 is a schematic diagram of a storage and forwarding working scenario provided according to an embodiment of the present disclosure.

[0024] FIG4A is an exemplary interaction diagram of an NTN-based communication method provided according to an embodiment of the present disclosure.

[0025] FIG4B is an exemplary interaction diagram of an NTN-based communication method provided according to an embodiment of the present disclosure.

[0026] FIG4C is an exemplary interaction diagram of an NTN-based communication method provided according to an embodiment of the present disclosure.

[0027] FIG5A is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0028] FIG5B is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0029] FIG6A is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0030] FIG6B is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0031] FIG7A is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0032] FIG7B is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0033] FIG8 is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0034] FIG9 is an exemplary flowchart of an NTN-based communication method according to an embodiment of the present disclosure.

[0035] FIG10 is an exemplary interaction diagram of an NTN-based communication method provided according to an embodiment of the present disclosure.

[0036] FIG11A is an exemplary interaction diagram of an NTN-based communication method provided according to an embodiment of the present disclosure.

[0037] FIG11B is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure.

[0038] FIG12A is an exemplary interaction diagram of an NTN-based communication method provided according to an embodiment of the present disclosure.

[0039] FIG12B is an exemplary interaction diagram of an NTN-based communication method provided according to an embodiment of the present disclosure.

[0040] FIG13 is an exemplary structural diagram of an NTN-based communication device provided according to an embodiment of the present disclosure.

[0041] FIG14 is an exemplary structural diagram of an NTN-based communication device provided according to an embodiment of the present disclosure.

[0042] FIG15 is an exemplary structural diagram of an NTN-based communication device provided according to an embodiment of the present disclosure.

[0043] FIG16 is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0044] The embodiments of the present disclosure provide a communication method and apparatus based on NTN, a communication device, a communication system, and a storage medium.

[0045] In a first aspect, embodiments of the present disclosure provide a communication method based on an NTN. The method is performed by a terminal. The method includes receiving a first message from a first network function, wherein the first message is used to instruct the terminal to authorize use of a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner during NTN access.

[0046] According to an embodiment of the present disclosure, when a terminal uses NTN access, the first network function authorizes the terminal to use the store-and-forward function through a first message, thereby enabling the terminal's store-and-forward function. This allows for communication with the terminal and maintains service uninterrupted even when feeder links in the NTN scenario cannot provide a continuous connection.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the first message may include storage and forwarding time information.

[0048] According to an embodiment of the present disclosure, the first message may include store-and-forward time information. In this way, the terminal may obtain the store-and-forward time information through the first message, thereby learning the characteristics of the store-and-forward function.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the operation of receiving the first message from the first network function may include: receiving the first message sent by the first network function and forwarded by the access network device.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the operation of receiving a first message sent by a first network function and forwarded by an access network device may include: receiving storage and forwarding time information sent by the access network device.

[0051] According to an embodiment of the present disclosure, if the access network device stores store-and-forward time information, the access network device can send the store-and-forward time information to the terminal at the same time as forwarding the first message. In this way, if the first message indicates authorization for the terminal to use the store-and-forward function, the access network device provides the store-and-forward time information to the terminal.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the first message may include a token and address information of the second network function. The token is used to authorize the terminal to obtain the storage and forwarding time information from the second network function.

[0053] According to an embodiment of the present disclosure, the first network function may instruct the terminal to use the store-and-forward function through a first message, and the terminal may obtain the store-and-forward time information from the corresponding second network function according to the token.

[0054] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: sending a second message to the second network function, wherein the second message is used to request storage and forwarding time information from the second network function; and receiving a third message from the second network function, wherein the third message includes storage and forwarding time information.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the second message may include a token.

[0056] According to an embodiment of the present disclosure, the terminal can obtain the storage and forwarding time information from the second network function, which enables the storage and forwarding time information to be uniformly managed by the second network function.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the store-and-forward time information may include at least one of the following: a data storage start time and a data storage duration. The data storage start time is determined based on the start time of an interruption in the feeder link between the satellite and the ground station. The data storage duration is determined based on the duration between the start time of the feeder link interruption and the time when the feeder link is restored.

[0058] According to the embodiment of the present disclosure, the terminal can obtain the storage and forwarding time information including the data storage start time and the data storage duration. In this way, the terminal can perform data transmission based on this information to cooperate with the satellite access network to realize the storage and forwarding function.

[0059] In a second aspect, embodiments of the present disclosure provide a communication method based on an NTN. The method is performed by a first network function. The method includes: sending a first message to a terminal, wherein the first message is used to instruct the terminal to authorize the terminal to use a store-and-forward function, wherein the store-and-forward function is used to transmit terminal data in a store-and-forward manner during NTN access.

[0060] In combination with some embodiments of the second aspect, in some embodiments, the first message may include storage and forwarding time information.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: receiving storage and forwarding time information from an access network device.

[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the first message may include a token and address information of the second network function. The token is used to authorize the terminal to obtain the storage and forwarding time information from the second network function.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, the store-and-forward time information may include at least one of the following: a data storage start time and a data storage duration. The data storage start time is determined by the start time of a feeder link interruption between the satellite and the ground station. The data storage duration is determined based on the duration between the start of the feeder link interruption and the time the feeder link is restored.

[0064] In combination with some embodiments of the second aspect, in some embodiments, before the operation of sending the first message to the terminal, the above method may also include: receiving contract information of the terminal from the third network function; based on the contract information and / or operator policy, determining whether the terminal is authorized to use the storage and forwarding function.

[0065] According to an embodiment of the present disclosure, the first network function may determine, based on subscription information and / or operator policy, whether to authorize the terminal to use the store-and-forward function. Thus, if the terminal user has subscribed to the store-and-forward function and complies with the operator policy, the first network function may authorize the terminal to use the store-and-forward function.

[0066] In a third aspect, embodiments of the present disclosure provide an NTN-based communication method. The method is performed by a second network function. The method includes: receiving a second message from a terminal, wherein the second message includes a request for store-and-forward time information from the second network function; and sending a third message to the terminal, wherein the third message includes the store-and-forward time information.

[0067] In conjunction with some embodiments of the third aspect, in some embodiments, the second information may include a token, which is used to authorize the terminal to obtain the store-and-forward time information from the second network function.

[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the store-and-forward time information may include at least one of the following: a data storage start time and a data storage duration. The data storage start time is determined based on the start time of a feeder link interruption between the satellite and the ground station. The data storage duration is determined based on the duration between the start of the feeder link interruption and the time the feeder link is restored.

[0069] In a fourth aspect, embodiments of the present disclosure provide an NTN-based communication method. The method includes: sending a first message to a terminal, wherein the first message is used to instruct the terminal to authorize use of a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner during NTN access.

[0070] In combination with some embodiments of the fourth aspect, in some embodiments, the above method further includes: receiving storage and forwarding time information from an access network device.

[0071] In combination with some embodiments of the fourth aspect, in some embodiments, the above method also includes: receiving a second message from the terminal, wherein the second message includes information for requesting storage and forwarding time; and sending a third message to the terminal, wherein the third message includes storage and forwarding time information.

[0072] In a fifth aspect, embodiments of the present disclosure provide an NTN-based communication device. The device is provided in a terminal. The device includes a receiving module. The receiving module is configured to receive a first message from a first network function, wherein the first message is used to instruct the terminal to authorize the terminal to use a store-and-forward function, wherein the store-and-forward function is used to transmit terminal data in a store-and-forward manner during NTN access.

[0073] In combination with some embodiments of the fifth aspect, in some embodiments, the first message may include storage and forwarding time information.

[0074] In combination with some embodiments of the fifth aspect, in some embodiments, the receiving module can be configured to: receive a first message sent by the first network function and forwarded by the access network device.

[0075] In combination with some embodiments of the fifth aspect, in some embodiments, the receiving module can be configured to: receive storage and forwarding time information sent by the access network device.

[0076] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first message may include a token and address information of the second network function. The token is used to authorize the terminal to obtain the storage and forwarding time information from the second network function.

[0077] In conjunction with some embodiments of the fifth aspect, in some embodiments, the apparatus may further include a sending module. The sending module is configured to: send a second message to the second network function, the second message being used to request the second network function for storage and forwarding time information; and receive a third message from the second network function, wherein the third message includes the storage and forwarding time information.

[0078] In combination with some embodiments of the fifth aspect, in some embodiments, the second message may include a token.

[0079] In conjunction with some embodiments of the fifth aspect, in some embodiments, the store-and-forward time information may include at least one of the following: a data storage start time and a data storage duration. The data storage start time is determined based on the start time of an interruption in the feeder link between the satellite and the ground station. The data storage duration is determined based on the duration between the start time of the feeder link interruption and the time when the feeder link is restored.

[0080] In a sixth aspect, embodiments of the present disclosure provide an NTN-based communication device. The device is configured in a first network function. The device includes a sending module. The sending module is configured to send a first message to a terminal, wherein the first message is used to authorize the terminal to use a store-and-forward function, wherein the store-and-forward function is used to transmit terminal data in a store-and-forward manner during NTN access.

[0081] In combination with some embodiments of the sixth aspect, in some embodiments, the first message may include storage and forwarding time information.

[0082] In conjunction with some embodiments of the sixth aspect, in some embodiments, the apparatus may further include a receiving module. The receiving module may be configured to receive storage and forwarding time information from an access network device.

[0083] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first message may include a token and address information of the second network function. The token is used to authorize the terminal to obtain the storage and forwarding time information from the second network function.

[0084] In conjunction with some embodiments of the sixth aspect, in some embodiments, the store-and-forward time information may include at least one of the following: a data storage start time and a data storage duration. The data storage start time is determined based on the start time of a feeder link interruption between the satellite and the ground station. The data storage duration is determined based on the duration between the start of the feeder link interruption and the time the feeder link is restored.

[0085] In conjunction with some embodiments of the sixth aspect, in some embodiments, the receiving module may be configured to receive subscription information of a terminal from a third network function. The apparatus may further include a processing module. The processing module is configured to determine, based on the subscription information and / or operator policy, whether the terminal is authorized to use the store-and-forward function.

[0086] In a seventh aspect, embodiments of the present disclosure provide an NTN-based communication device. The device is configured in a second network function. The device includes a receiving module and a sending module. The receiving module is configured to receive a second message from a terminal, wherein the second message includes a request for store-and-forward time information from the second network function. The sending module is configured to send a third message to the terminal, wherein the third message includes the store-and-forward time information.

[0087] In conjunction with some embodiments of the seventh aspect, in some embodiments, the second information may include a token, and the token is used to authorize the terminal to obtain the storage and forwarding time information from the second network function.

[0088] In conjunction with some embodiments of the seventh aspect, in some embodiments, the store-and-forward time information may include at least one of the following: a data storage start time and a data storage duration. The data storage start time is determined based on the start time of a feeder link interruption between the satellite and the ground station. The data storage duration is determined based on the duration between the start of the feeder link interruption and the time the feeder link is restored.

[0089] In an eighth aspect, an embodiment of the present disclosure provides a communication device. The communication device includes at least one processor. The processor is configured to invoke instructions to execute the communication method as described in any one of the first aspect, the second aspect, the third aspect, the fourth aspect, and the embodiments thereof.

[0090] In a ninth aspect, embodiments of the present disclosure provide a communications system. The communications system includes a first network function and a third network function. The third network function is configured to send a terminal's subscription information to the first network function. The first network function is configured to receive the subscription information from the third network function and, based on the subscription information and / or operator policy, determine whether to authorize the terminal to use a store-and-forward function.

[0091] In conjunction with some embodiments of the ninth aspect, in some embodiments, the communication system further includes a second network function configured to provide store-and-forward time information.

[0092] In a tenth aspect, embodiments of the present disclosure provide a communication system. The communication system includes a terminal, an access network device, and a core network device. The terminal is configured to perform the communication method described in any one of the first aspect and its embodiments. The access network device is configured to perform the communication method described in any one of the second, third, and fourth aspects and their embodiments.

[0093] In an eleventh aspect, an embodiment of the present disclosure provides a storage medium storing instructions that, when executed by a processor, perform the communication method as described in any one of the first, second, third, and fourth aspects and their embodiments.

[0094] In a twelfth aspect, a computer program or computer program product is provided. The computer program or computer program product includes code. When executed by a processor, the instructions perform the communication method as described in any one of the first aspect, the second aspect, the third aspect, the fourth aspect, and the embodiments thereof.

[0095] It is understood that the aforementioned NTN-based communication devices, communication equipment, communication systems, storage media, computer programs, and computer program products are all used to implement the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can be referenced to the beneficial effects of the corresponding methods and will not be repeated here.

[0096] The present disclosure provides a communication method and apparatus, communication device, communication system, and storage medium based on NTN. In some embodiments, the terms "communication method" and "information processing method" and "information transmission method" are interchangeable; the terms "communication apparatus" and "information processing apparatus" and "information transmission apparatus" are interchangeable; and the terms "communication system" and "information processing system" are interchangeable.

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

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

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

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

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

[0102] In some embodiments, the terms "at least one", "one or more", etc. can be used interchangeably.

[0103] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in 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 same applies when there are more branches such as A, B, and C.

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

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

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

[0107] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", and "if..." can be used interchangeably.

[0108] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

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

[0110] In some embodiments, "network" can be interpreted as devices included in the network (for example, access network equipment, core network equipment, data network equipment, etc.).

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

[0112] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

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

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

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

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

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

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

[0119] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things (IoT) device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

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

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

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

[0123] In some embodiments, the core network device 103 may be a single device including a first network element 1031, a second network element 1032, a third network element 1033, etc., or may be a plurality of devices or a device group including part or all of the first network element 1031, the second network element 1032, and the third network element 1033. Network devices may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0124] In some embodiments, the first network element 1031 is, for example, an access management function (AMF).

[0125] In some embodiments, the first network element 1031 may be used to perform user access and mobility management, and its name is not limited thereto.

[0126] In some embodiments, the second network element 1032 is, for example, a server.

[0127] In some embodiments, the second network element 1032 may be configured to store and provide storage and forwarding time information, and its name is not limited thereto.

[0128] In some embodiments, the second network element 1032 may be independent of the core network device 103 . That is, the core network device 103 may not include the second network element 1032 .

[0129] In some embodiments, the second network element 1032 may be a part of the core network device 103. That is, the core network device 103 may include the second network element 1032.

[0130] In some embodiments, the third network element 1033 is, for example, a unified data management (UDM) function.

[0131] In some embodiments, the third network element 1033 can be used for user subscription data management, and its name is not limited thereto.

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

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

[0134] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. 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.

[0135] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), 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, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0136] In the field of communications technology, satellite communications can complement cellular communications. With the development of communications technology, the integration of satellite and cellular communications will gradually deepen. For example, in a 5G communication network, a UE can access the 5G core network via a satellite access network. This is a type of NTN network.

[0137] Figure 2 is a schematic diagram of a communication scenario according to an embodiment of the present disclosure. As shown in Figure 2, a satellite in a satellite access network supports gNB functionality and establishes communication connections with a UE and a ground station via a service link and a feeder link, respectively.

[0138] For example, for non-geostationary orbit (NGSO) satellites, the number of deployed satellites is limited, and the coverage area of ​​satellites is also limited, making it difficult for satellite access networks to provide continuous coverage. This discontinuous coverage can lead to interruptions in the service link between the satellite and the UE, and the feeder link between the satellite and the ground receiving station.

[0139] In some embodiments, for the service link, mobility enhancement, power saving technology and the like are proposed for the case of discontinuous coverage.

[0140] In some embodiments, for the feeder link, in response to the situation where the link is interrupted, it is proposed that the satellite access network supports storage and forwarding features to achieve business communications in the event of a feeder link interruption. Figure 3 is a schematic diagram of a storage and forwarding working scenario provided according to an embodiment of the present disclosure. As shown in Figure 3, when the satellite is at position 1, the satellite can communicate with the UE through the service link (for example, exchange data) and store data from the UE; when the satellite moves to position 2, the satellite can communicate with the ground network through the feeder link (for example, exchange data) and send the stored data to the ground network. Of course, data from the ground network can also be delivered to the UE through the reverse operation process.

[0141] In some embodiments, the satellite access network supports storage and forwarding features, which are particularly suitable for delay-tolerant / non-real-time IoT services carried out by terminals.

[0142] In some embodiments, for the above scenario, the store-and-forward feature is described using store-and-forward time information. When the satellite access network supports store-and-forward mode, in order to ensure that UE service communications are not affected when the feeder link is interrupted, the UE also needs to know the start and duration of data storage to cooperate with the satellite access network's data storage and forwarding function, thereby enabling the delivery of non-real-time services in the event of feeder link interruptions.

[0143] FIG4A is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to an NTN-based communication method, which is applied to a communication system 100. As shown in FIG4A , the method includes steps S4110 to S4150.

[0144] In step S4110 , the access network device 102 sends storage and forwarding time information to the first network element 1031 .

[0145] In some embodiments, the access network device 102 may send store and forward information.

[0146] In some embodiments, the first network element 1031 may receive storage and forwarding time information.

[0147] In some embodiments, the store and forward time information may be used to characterize store and forward characteristics.

[0148] In some embodiments, the store-and-forward time information may be generated based on operational information of satellites in the NTN.

[0149] In some embodiments, the name of the storage and forwarding time information is not limited, and may be, for example, storage and forwarding information, storage and forwarding parameters, storage and forwarding indication information, etc.

[0150] In some embodiments, the storage and forwarding time information may include at least one of the following: data storage start time, and data storage duration.

[0151] In some embodiments, the data storage start time is used to indicate the start time of data storage. In other words, starting from the data storage start time, the data sent by the terminal 101 to the access network device 101 is stored in the access network device 101.

[0152] In some embodiments, the data storage start time may be the time when the access network device 102 starts storing the data of the terminal 101. In some embodiments, the data storage start time may be the time when the access network device 102 starts storing the data of the terminal 101 when the feeder link is unavailable. In one example, the data storage start time may be the moment when the access network device 102 starts storing the data of the terminal 101 when the feeder link is unavailable.

[0153] In some embodiments, the data storage start time may be determined based on the disconnection time of the feeder link between the satellite and the ground station. In this case, the disconnection time of the feeder link between the satellite and the ground station may be the start time of data storage. It is understood that the data storage start time may also be earlier or later than the disconnection time of the feeder link between the satellite and the ground station.

[0154] In some embodiments, the data storage duration may be determined based on the duration of the feeder link between the satellite and the ground station from the time of disconnection to the time of restoration.

[0155] In some embodiments, the data storage duration may be the duration that the access network device 102 stores the data of the terminal 101. In some embodiments, the data storage duration may be the duration that the access network device 102 stores the data of the terminal 101 when the feeder link is unavailable.

[0156] In some embodiments, the storage and forwarding time information may be fixed. In one example, when the deployment of the access network device 102 remains unchanged, the storage and forwarding time information may remain unchanged.

[0157] In some embodiments, the storage and forwarding function with the above-mentioned data storage and forwarding time information can be implemented as follows: data storage starts at the data storage start time, and the data is saved within the time indicated by the data storage duration. At the end of or after the time duration, the access network device 102 can send the stored data to the ground station or even the core network device 103.

[0158] In some embodiments, the data sent by the terminal 101 to the access network device 102 when the data storage start time is about to arrive may be stored in the access network device 102 until the data storage duration ends.

[0159] In some embodiments, the data sent by the terminal 101 to the access network device 102 before the data storage start time may not be stored and forwarded.

[0160] In some embodiments, the data sent by the terminal 101 to the access network device 102 within the data storage period may be stored in the access network device 102 until the data storage period ends.

[0161] In some embodiments, the access network device 102 may send N2 signaling to the first network element 1031. The N2 signaling may include store-and-forward time information. In one example, the N2 signaling may be required for connection configuration between the gNB and a 5G core network function (e.g., AMF). In one example, the N2 signaling may be independent of the UE. In one example, the N2 signaling may be used to exchange configuration data between the access network device 102 and the first network element 1031.

[0162] In some embodiments, the first network element 1031 may receive N2 signaling, which may include storage and forwarding time information.

[0163] In some embodiments, the access network device 102 may send a next generation application protocol (NGAP) message to the first network element 1031. The NGAP message may include store-and-forward time information. In one example, the NGAP message is a message sent by the gNB to the AMF during the UE registration procedure.

[0164] In some embodiments, the first network element 1031 may receive an NGAP message. The NGAP message may include store-and-forward time information.

[0165] In some embodiments, the storage and forwarding time information may be determined by the access network device 102 .

[0166] In some embodiments, the storage and forwarding time information may be obtained by the access network device 102 from an external server.

[0167] In some embodiments, the storage and forwarding time information may be obtained by the access network device 102 from an operation, administration and maintenance server (OAM server).

[0168] It is understood that step S4110 is optional. In some embodiments, the storage and forwarding time information may be pre-configured in the first network element 1031. In some embodiments, the storage and forwarding time information may be pre-configured in other network elements in the core network device 103, and the first network element 1031 may receive the storage and forwarding time information from the other network elements in the core network device 103.

[0169] In step S4120 , the terminal 101 sends a registration request message to the first network element 1031 .

[0170] In some embodiments, terminal 101 may send a registration request message.

[0171] In some embodiments, the first network element 1031 may receive a registration request message.

[0172] In some embodiments, the terminal 101 may send a registration request message to the access network device 102 , and the access network device 102 may then send the registration request message to the first network element 1031 .

[0173] In some embodiments, the registration request message may be used by the terminal 101 to initiate a registration process.

[0174] In some embodiments, the registration request message may include at least one of the following: an access type, a radio access technology (RAT) type.

[0175] In some embodiments, the access type may be used to indicate the type of network that the terminal 101 accesses.

[0176] In some embodiments, the access type may be a third generation partnership project (3GPP) access.

[0177] In some embodiments, the access type may be non-3GPP access.

[0178] In some embodiments, the RAT type may be accessed by a low earth orbit satellite-new radio (LEO-NR) or accessed by a ground base station. Of course, the RAT type may also be other types, which is not specifically limited in the embodiments of the present disclosure.

[0179] In some embodiments, step S4110 may be executed before step S4120, after step S4120, or simultaneously with step S4120, and this is not specifically limited in the embodiments of the present disclosure.

[0180] In step S4130 , the third network element 1033 sends the signing information to the first network element 1031 .

[0181] In some embodiments, the third network element 1033 may send the contract information.

[0182] In some embodiments, the first network element 1031 may receive subscription information.

[0183] In some embodiments, the contract information may include the contract data of the terminal 101 .

[0184] In some embodiments, the subscription information may include subscription data of the user of terminal 101 .

[0185] In some embodiments, the subscription data may include information indicating whether the terminal 101 supports the store-and-forward function. In one example, the subscription data may be used to indicate that the terminal 101 supports the store-and-forward function. In another example, the subscription data may be used to indicate that the terminal 101 does not support the store-and-forward function.

[0186] In some embodiments, the subscription data may include information indicating whether the terminal 101 has subscribed to the store-and-forward function. For example, the subscription data may indicate that the terminal 101 has purchased the store-and-forward function from the operator and that the operator allows the terminal 101 to implement the store-and-forward function.

[0187] In some embodiments, the third network element 1033 may send the subscription information to the first network element 1031 through a Nudm_SDM_Get service operation (Nudm_SDM_Get service operation).

[0188] In step S4140 , the first network element 1031 determines whether the terminal 101 is authorized to use the store and forward function.

[0189] In some embodiments, the store and forward function is used to transmit the data of the terminal in a store and forward manner in NTN access.

[0190] In some embodiments, the store and forward function can be used to transmit terminal data in a store and forward manner when the feeder link connection between the satellite and the ground station in NTN access is discontinuous.

[0191] In some embodiments, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function based on subscription information and / or operator policy.

[0192] In some embodiments, the first network element 1031 may determine not to authorize the terminal 101 to use the store and forward function based on subscription information and / or operator policy.

[0193] In some embodiments, the first network element 1031 may determine, based on the contract information, not to authorize the terminal 101 to use the store-and-forward function. In some embodiments, if the contract information indicates that the terminal 101 does not support the store-and-forward function, the first network element 1031 may determine, based on the contract information, not to authorize the terminal 101 to use the store-and-forward function.

[0194] In some embodiments, the first network element 1031 may determine, based on the contract information, to authorize the terminal 101 to use the store and forward function. In some embodiments, if the contract information indicates that the terminal 101 supports the store and forward function, the first network element 1031 may determine, based on the contract information, to authorize the terminal 101 to use the store and forward function.

[0195] In some embodiments, the first network element 1031 may determine not to authorize the terminal 101 to use the store and forward function based on operator policy.

[0196] In some embodiments, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function based on operator policy.

[0197] In some embodiments, when the subscription information indicates that the terminal 101 supports the store-and-forward function, based on the operator's policy, the first network element 1031 may determine to authorize the terminal 101 to use the store-and-forward function.

[0198] In some embodiments, when the subscription information indicates that the terminal 101 supports the store-and-forward function, based on the operator's policy, the first network element 1031 may determine not to authorize the terminal 101 to use the store-and-forward function.

[0199] In some embodiments, when the subscription information indicates that the terminal 101 does not support the store and forward function, based on the operator's policy, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function.

[0200] In some embodiments, when the subscription information indicates that the terminal 101 does not support the store and forward function, based on the operator's policy, the first network element 1031 may determine not to authorize the terminal 101 to use the store and forward function.

[0201] In step S4150 , the first network element 1031 sends a first message to the terminal 101 .

[0202] In some embodiments, the first network element 1031 may send a first message.

[0203] In some embodiments, terminal 101 may receive a first message.

[0204] In some embodiments, the first message may be used to indicate to the terminal 101 that the terminal 101 is authorized to use the store and forward function.

[0205] In some embodiments, the name of the first message is not limited, and may be, for example, a notification message, an indication message, etc.

[0206] In some embodiments, the first message may include enabling information, which may be used to enable a store-and-forward function of the terminal 101 .

[0207] In some embodiments, the first message may include store-and-forward time information.

[0208] In some embodiments, the storage and forwarding time information may include at least one of the following: data storage start time, and data storage duration.

[0209] In some embodiments, the first network element 1031 may send the first message to the terminal 101 in the following manner: the first network element 1031 may send the first message to the access network device 102, and the access network device 102 may transparently transmit the first message to the terminal 101. In other words, the access network device 102 may transparently transmit the first message from the first network element 1031 to the terminal 101.

[0210] In some embodiments, the first network element 1031 may send the first message to the terminal 101 in the following manner: the first network element 1031 may send the first message to the access network device 102, and the access network device 102 may forward the first message to the terminal 101. In other words, the access network device 102 may forward the first message from the first network element 1031 to the terminal 101.

[0211] In some embodiments, the first message may include enabling information.

[0212] In some embodiments, the first message may include store-and-forward time information.

[0213] In some embodiments, access network device 102 may send storage and forwarding time information to terminal 101 when forwarding the first message to terminal 101. In one example, the storage and forwarding time information may be carried in the first message. In another example, the storage and forwarding time information may be carried in another message or signaling different from the first message.

[0214] In some embodiments, the first message may be a non-access stratum (NAS) message.

[0215] In some embodiments, the first message may be a registration accept message sent by the first network element 1031 .

[0216] In some embodiments, the first message may be a message in a user configuration update procedure.

[0217] In some embodiments, after the access network device 102 accesses the storage and forwarding time information, the first message may be an air interface message.

[0218] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S4110 to S4150. For example, step S4150 may be implemented as an independent embodiment. For example, step S4150 may be implemented as an independent embodiment. For example, the combination of steps S4140 and S4150 may be implemented as an independent embodiment. For example, the combination of steps S4130 and S4140 may be implemented as an independent embodiment. For example, the combination of steps S4130, S4140, and S4150 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S4110 to S4150 are not limited to these.

[0219] In some embodiments, steps S4110, S4120, S4130, and S4140 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0220] In some embodiments, steps S4110, S4120, S4130, and S4150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0221] FIG4B is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to an NTN-based communication method, which is applied to a communication system 100. As shown in FIG4B , the method includes steps S4210 to S4260.

[0222] In step S4210 , the terminal 101 sends a registration request message to the first network element 1031 .

[0223] In some embodiments, the optional implementation of step S4210 can refer to the optional implementation of step S4120 in Figure 4A and other related parts in the embodiment involved in Figure 4A.

[0224] In some embodiments, terminal 101 may send a registration request message.

[0225] In some embodiments, the first network element 1031 may receive a registration request message.

[0226] In some embodiments, the terminal 101 may send a registration request message to the access network device 102 , and the access network device 102 may then send the registration request message to the first network element 1031 .

[0227] In some embodiments, the registration request message may be used by the terminal 101 to initiate a registration process.

[0228] In some embodiments, the registration request message may include at least one of the following: an access type, a radio access technology (RAT) type.

[0229] In some embodiments, the access type may be used to indicate the type of network that the terminal 101 accesses.

[0230] In some embodiments, the access type may be 3GPP access.

[0231] In some embodiments, the access type may be non-3GPP access.

[0232] In some embodiments, the RAT type may be accessed by a low earth orbit satellite-new radio (LEO-NR) or accessed by a ground base station. Of course, the RAT type may also be other types, which is not specifically limited in the embodiments of the present disclosure.

[0233] In step S4220, the third network element 1033 sends the signing information to the first network element 1031.

[0234] In some embodiments, the optional implementation of step S4220 can refer to the optional implementation of step S4130 in Figure 4A and other related parts of the embodiment involved in Figure 4A, which will not be repeated here.

[0235] In some embodiments, the third network element 1033 may send the contract information.

[0236] In some embodiments, the first network element 1031 may receive subscription information.

[0237] In some embodiments, the contract information may include contract data of the terminal 101 .

[0238] In some embodiments, the subscription data may include information indicating whether the terminal 101 supports the store-and-forward function. In one example, the subscription data may be used to indicate that the terminal 101 supports the store-and-forward function. In another example, the subscription data may be used to indicate that the terminal 101 does not support the store-and-forward function.

[0239] In some embodiments, the subscription data may include information indicating whether the terminal 101 has subscribed to the store-and-forward function. For example, the subscription data may indicate that the terminal 101 has purchased the store-and-forward function from the operator and that the operator allows the terminal 101 to implement the store-and-forward function.

[0240] In some embodiments, the third network element 1033 may send the subscription information to the first network element 1031 through a Nudm_SDM_Get service operation (Nudm_SDM_Get service operation).

[0241] In step S4230 , the first network element 1031 determines to authorize the terminal 101 to use the store and forward function.

[0242] In some embodiments, the optional implementation of step S4230 can refer to the optional implementation of step S4140 in Figure 4A and other related parts of the embodiment involved in Figure 4A, which will not be repeated here.

[0243] In some embodiments, the store and forward function is used to transmit the data of the terminal in a store and forward manner in NTN access.

[0244] In some embodiments, the store and forward function can be used to transmit terminal data in a store and forward manner when the feeder link connection between the satellite and the ground station in NTN access is discontinuous.

[0245] In some embodiments, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function based on subscription information and / or operator policy.

[0246] In some embodiments, the first network element 1031 may determine not to authorize the terminal 101 to use the store and forward function based on subscription information and / or operator policy.

[0247] In some embodiments, the first network element 1031 may determine, based on the contract information, not to authorize the terminal 101 to use the store-and-forward function. In some embodiments, if the contract information indicates that the terminal 101 does not support the store-and-forward function, the first network element 1031 may determine, based on the contract information, not to authorize the terminal 101 to use the store-and-forward function.

[0248] In some embodiments, the first network element 1031 may determine, based on the contract information, to authorize the terminal 101 to use the store and forward function. In some embodiments, if the contract information indicates that the terminal 101 supports the store and forward function, the first network element 1031 may determine, based on the contract information, to authorize the terminal 101 to use the store and forward function.

[0249] In some embodiments, the first network element 1031 may determine not to authorize the terminal 101 to use the store and forward function based on operator policy.

[0250] In some embodiments, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function based on operator policy.

[0251] In some embodiments, when the subscription information indicates that the terminal 101 supports the store-and-forward function, based on the operator's policy, the first network element 1031 may determine to authorize the terminal 101 to use the store-and-forward function.

[0252] In some embodiments, when the subscription information indicates that the terminal 101 supports the store-and-forward function, based on the operator's policy, the first network element 1031 may determine not to authorize the terminal 101 to use the store-and-forward function.

[0253] In some embodiments, when the subscription information indicates that the terminal 101 does not support the store and forward function, based on the operator's policy, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function.

[0254] In some embodiments, when the subscription information indicates that the terminal 101 does not support the store and forward function, based on the operator's policy, the first network element 1031 may determine not to authorize the terminal 101 to use the store and forward function.

[0255] In step S4240 , the first network element 1031 sends a first message to the terminal 101 .

[0256] In some embodiments, the first network element 1031 may send a first message.

[0257] In some embodiments, terminal 101 may receive a first message.

[0258] In some embodiments, the first message may be used to indicate to the terminal 101 that the terminal 101 is authorized to use the store and forward function.

[0259] In some embodiments, the name of the first message is not limited, and may be, for example, a notification message, an indication message, etc.

[0260] In some embodiments, the first message may be a non-access stratum (NAS) message.

[0261] In some embodiments, the first message may be a registration accept message sent by the first network element 1031 .

[0262] In some embodiments, the first message may be a message in a user configuration update procedure.

[0263] In some embodiments, the first message may include a token and address information of the second network element 1032 .

[0264] In some embodiments, the token may be used to obtain storage and forwarding time information from the second network element 1032 .

[0265] In some embodiments, the token may be used to authorize the terminal 101 to obtain the storage and forwarding time information from the second network element 1032 .

[0266] In some embodiments, the token may be associated with the store-and-forward time information in the second network element 1032 .

[0267] In some embodiments, a token may be associated with a terminal 101. In one example, one terminal 101 may correspond to a specific token.

[0268] In some embodiments, a token may be associated with the first network element 1031. In one example, one first network element 1031 may correspond to a specific token.

[0269] In some embodiments, the address information may be used for communication between the terminal 101 and the second network element 1032 .

[0270] In some embodiments, the address information may be used to indicate an Internet protocol (IP) address of the second network element 1032 .

[0271] In some embodiments, the first network element 1031 may send the first message to the terminal 101 in the following manner: the first network element 1031 may send the first message to the access network device 102 , and the access network device 102 may transparently transmit the first message to the terminal 101 .

[0272] In some embodiments, the first network element 1031 may send the first message to the terminal 101 in the following manner: the first network element 1031 may send the first message to the access network device 102 , and the access network device 102 may forward the first message to the terminal 101 .

[0273] In some embodiments, the first message may be a registration accept message sent by the first network element 1031 .

[0274] In step S4250 , the terminal 101 sends a second message to the second network element 1032 .

[0275] In some embodiments, terminal 101 may send a second message.

[0276] In some embodiments, the second network element 1032 may receive the second message.

[0277] In some embodiments, the name of the second message is not limited, and may be, for example, a request message, a query message, etc.

[0278] In some embodiments, the second message may be used to request the second network element 1032 to store and forward time information.

[0279] In some embodiments, the terminal 101 may send a second message to the second network element 1032 based on the address information in the first message.

[0280] In some embodiments, the second message may include a token.

[0281] In some embodiments, the second network element 1032 may be a server located outside the core network device 103 (ie, an external server).

[0282] In some embodiments, the second network element 1032 may be a server located in the core network device 103 .

[0283] In step S4260 , the second network element 1032 sends a third message to the terminal 101 .

[0284] In some embodiments, the second network element 1032 may send a third message.

[0285] In some embodiments, terminal 101 may receive a third message.

[0286] In some embodiments, the name of the third message is not limited, and may be, for example, a response message, a confirmation message, etc.

[0287] In some embodiments, the third message may be a response message to the second message.

[0288] In some embodiments, the third message may be used to indicate the storage and forwarding time information to the terminal 101 .

[0289] In some embodiments, the third message may include store-and-forward time information.

[0290] In some embodiments, the store-and-forward time information may be used to characterize the store-and-forward function. In other words, the store-and-forward time information may include parameters that characterize the store-and-forward function.

[0291] In some embodiments, the name of the storage and forwarding time information is not limited, and may be, for example, storage and forwarding parameters, storage and forwarding indication information, etc.

[0292] In some embodiments, the storage and forwarding time information may include at least one of the following: data storage start time, and data storage duration.

[0293] In some embodiments, the data storage start time is used to indicate the start time of data storage. In other words, starting from the data storage start time, the data sent by the terminal 101 to the access network device 101 is stored in the access network device 101.

[0294] In some embodiments, the data storage start time may be the time when the access network device 102 starts storing the data of the terminal 101. In some embodiments, the data storage start time may be the time when the access network device 102 starts storing the data of the terminal 101 when the feeder link is unavailable. In one example, the data storage start time may be the moment when the access network device 102 starts storing the data of the terminal 101 when the feeder link is unavailable.

[0295] In some embodiments, the data storage start time may be determined based on the disconnection time of the feeder link between the satellite and the ground station. In this case, the disconnection time of the feeder link between the satellite and the ground station may be the start time of data storage. It is understood that the start time of data storage may also be earlier or later than the disconnection time of the feeder link between the satellite and the ground station.

[0296] In some embodiments, the data storage duration may be the duration that the access network device 102 stores the data of the terminal 101. In some embodiments, the data storage duration may be the duration that the access network device 102 stores the data of the terminal 101 when the feeder link is unavailable.

[0297] In some embodiments, the storage and forwarding time information may be fixed. In one example, when the deployment of the access network device 102 remains unchanged, the storage and forwarding time information may remain unchanged.

[0298] In some embodiments, the storage and forwarding function with the above-mentioned data storage and forwarding time information can be implemented as follows: data storage starts at the data storage start time, and the data is saved within the time indicated by the data storage duration. At the end of or after the time duration, the access network device 102 can send the stored data to the ground station or even the core network device 103.

[0299] In some embodiments, the data sent by the terminal 101 to the access network device 102 when the data storage start time is about to arrive may be stored in the access network device 102 until the data storage duration ends.

[0300] In some embodiments, the data sent by the terminal 101 to the access network device 102 before the data storage start time may not be stored and forwarded.

[0301] In some embodiments, the data sent by the terminal 101 to the access network device 102 within the data storage period may be stored in the access network device 102 until the data storage period ends.

[0302] In some embodiments, the second network element 1032 sending the third message to the terminal 101 can be achieved in the following manner: the second network element 1032 can obtain the storage and forwarding time information related to the token based on the token in the second message; the second network element 1032 can carry the obtained storage and forwarding time information in the third message and send it to the terminal 101.

[0303] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S4210 to S4260. For example, step S4230 may be implemented as an independent embodiment. For example, step S4240 may be implemented as an independent embodiment. For example, the combination of steps S4230 and S4240 may be implemented as an independent embodiment. For example, the combination of steps S4220 and S4230 may be implemented as an independent embodiment. For example, the combination of steps S4220, S4230, and S4240 may be implemented as an independent embodiment. For example, the combination of steps S4240, S4250, and S4260 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S4210 to S4260 are not limited to these.

[0304] In some embodiments, steps S4210, S4220, S4230, S4250, and S4260 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0305] In some embodiments, steps S4110, S4120, and S4130 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0306] FIG4C is an exemplary interaction diagram of the NTN-based communication method provided according to an embodiment of the present disclosure. As shown in FIG4C , the method includes steps S4310 to S4350.

[0307] In step S4310 , the access network device 102 sends storage and forwarding time information to the core network device 103 .

[0308] The optional implementation of step S4310 can refer to the optional implementation of step S4110 in Figure 4A, as well as other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0309] In step S4320 , the terminal 101 sends a registration request message to the core network device 103 .

[0310] The optional implementation of step S4310 can refer to the optional implementation of step S4120 in Figure 4A, step S4210 in Figure 4B, and other related parts in the embodiments involved in Figures 4A and 4B, which will not be repeated here.

[0311] In step S4330 , the core network device 103 sends a first message to the terminal 101 .

[0312] The optional implementation of step S4330 can refer to the optional implementation of step S4150 in Figure 4A, step S4240 in Figure 4B, and other related parts in the embodiments involved in Figures 4A and 4B, which will not be repeated here.

[0313] In step S4340 , the terminal 101 sends a second message to the core network device 103 .

[0314] The optional implementation of step S4340 can refer to the optional implementation of step S4250 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0315] In step S4350, the core network device 103 sends a third message to the terminal.

[0316] The optional implementation of step S4350 can refer to the optional implementation of step S4260 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0317] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S4310 to S4350. For example, step S4310 may be implemented as an independent embodiment. For example, a combination of steps S4330 may be implemented as an independent embodiment. For example, a combination of steps S4340 and S4350 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more of steps S4310 to S4350 are not limited to this.

[0318] In some embodiments, steps S4320, S4330, S4340, and S4350 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0319] In some embodiments, steps S4310, S4320, S4340, and S4350 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0320] In some embodiments, steps S4310, S4320, and S4330 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0322] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

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

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

[0325] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

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

[0327] FIG5A is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to an NTN-based communication method, which is applied to a terminal 101. As shown in FIG5A , the method includes steps S5110 to S5120.

[0328] In step S5110, a registration request message is sent.

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

[0330] In some embodiments, the terminal 101 may send a registration request message to the first network element 1031 , but is not limited thereto and may also send a registration request message to other entities.

[0331] In some embodiments, the registration request message may be a message received by the first network element 1031 from the terminal 101 .

[0332] In step S5120, the first message is obtained.

[0333] The optional implementation of step S5120 can refer to the optional implementation of step S4150 in Figure 4A and other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0334] In some embodiments, the terminal 101 may receive a first message from the first network element 1031 , but is not limited thereto and may also receive a first message from other entities.

[0335] In some embodiments, the first message may be a message sent by the first network element 1031 to the terminal 101 .

[0336] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S5110 to S5120. For example, step S5120 may be implemented as an independent embodiment. For example, the combination of steps S5110 and S5120 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S4210 to S4260 are not limited to this.

[0337] In some embodiments, step S5110 is optional and may be omitted or replaced in different embodiments.

[0338] FIG5B is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. The present disclosure relates to an NTN-based communication method, which is applied to a terminal 101. As shown in FIG5B , the method includes steps S5210 to S5240.

[0339] In step S5210, a registration request message is sent.

[0340] The optional implementation of step S5210 can refer to the optional implementation of step S4210 in Figure 4B and other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0341] In some embodiments, the terminal 101 may send a registration request message to the first network element 1031 , but is not limited thereto and may also send a registration request message to other entities.

[0342] In some embodiments, the registration request message may be a message received by the first network element 1031 from the terminal 101 .

[0343] In step S5220, the first message is obtained.

[0344] The optional implementation of step S5220 can refer to the optional implementation of step S4240 in Figure 4B and other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0345] In some embodiments, the terminal 101 may receive a first message from the first network element 1031 , but is not limited thereto and may also receive a first message from other entities.

[0346] In some embodiments, the first message may be a message sent by the first network element 1031 to the terminal 101 .

[0347] In step S5230, a second message is sent.

[0348] The optional implementation of step S5230 can refer to the optional implementation of step S4250 in Figure 4B and other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0349] In some embodiments, the terminal 101 may send the second message to the second network element 1032 , but is not limited thereto and may also send the second message to other entities.

[0350] In some embodiments, the second message may be a message received by the second network element 1032 from the terminal 101 .

[0351] In step S5240, the third message is obtained.

[0352] The optional implementation of step S5240 can refer to the optional implementation of step S4260 in Figure 4B and other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0353] In some embodiments, the terminal 101 may receive a third message from the second network element 1032 , but is not limited thereto and may also receive a third message from other entities.

[0354] In some embodiments, the third message may be a message sent by the second network element 1032 to the terminal 101 .

[0355] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S5210 to S5240. For example, step S5220 may be implemented as an independent embodiment. For example, the combination of steps S5210 and S5220 may be implemented as an independent embodiment. For example, the combination of steps S5230 and S5240 may be implemented as an independent embodiment. For example, the combination of steps S5220, S5230, and S5240 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S5210 to S5240 are not limited to these.

[0356] In some embodiments, step S5210 is optional and may be omitted or replaced in different embodiments.

[0357] In some embodiments, steps S5210, S5230, and S5240 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0358] Figure 6A is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to an NTN-based communication method, which is applied to access network device 102. As shown in Figure 6A, the method includes steps S6110 and S6130.

[0359] In step S6110, store and forward time information is sent.

[0360] The optional implementation of step S6110 can refer to the optional implementation of step S4110 in Figure 4A, as well as other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0361] In some embodiments, the access network device 102 may send the storage and forwarding time information to the first network element 1031 , but is not limited thereto and may also send the storage and forwarding time information to other entities.

[0362] In some embodiments, the first network element 1031 may obtain storage and forwarding time information from the access network device 102 .

[0363] In step S6120, a registration request message is transmitted.

[0364] The optional implementation of step S6120 can refer to the optional implementation of step S4120 in Figure 4A, as well as other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0365] In some embodiments, the access network device 102 may transmit the registration request message from the terminal 101 to the first network element 1031 .

[0366] In some embodiments, the access network device 102 may receive a registration request message from the terminal 101 and send the registration request message to the first network element 1031 .

[0367] In step S6130, the first message is delivered.

[0368] The optional implementation of step S6120 can refer to the optional implementation of step S4150 in Figure 4A, as well as other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0369] In some embodiments, the access network device 102 may deliver the first message from the first network element 1031 to the terminal 101 .

[0370] In some embodiments, the access network device 102 may transmit the first message in a transparent manner.

[0371] In some embodiments, the access network device 102 may transmit the first message in a forwarding manner.

[0372] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S6110 to S6130. For example, step S6110 may be implemented as an independent embodiment. For example, step S6130 may be implemented as an independent embodiment. For example, the combination of steps S6110 and S6130 may be implemented as an independent embodiment. For example, the combination of steps S6110 and S6120 may be implemented as an independent embodiment. For example, the combination of steps S6110, S6120, and S6130 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S6110 to S6130 are not limited to these.

[0373] In some embodiments, steps S6120 and S6130 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0374] In some embodiments, steps S6110 and S6120 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0375] FIG6B is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. The present disclosure relates to an NTN-based communication method, which is applied to access network device 102. As shown in FIG6B , the method includes steps S6210 and S6240.

[0376] In step S6210, a registration request message is transmitted.

[0377] The optional implementation of step S6210 can refer to the optional implementation of step S4210 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0378] In some embodiments, the access network device 102 may transmit the registration request message from the terminal 101 to the first network element 1031 .

[0379] In some embodiments, the access network device 102 may receive a registration request message from the terminal 101 and send the registration request message to the first network element 1031 .

[0380] In step S6220, the first message is delivered.

[0381] The optional implementation of step S6220 can refer to the optional implementation of step S4240 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0382] In some embodiments, the access network device 102 may deliver the first message from the first network element 1031 to the terminal 101 .

[0383] In some embodiments, the access network device 102 may transmit the first message in a transparent manner.

[0384] In some embodiments, the access network device 102 may transmit the first message in a forwarding manner.

[0385] In step S6230, the second message is delivered.

[0386] The optional implementation of step S6230 can refer to the optional implementation of step S4250 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0387] In step S6240, the third message is delivered.

[0388] The optional implementation of step S6240 can refer to the optional implementation of step S4260 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0389] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S6210 to S6240. For example, step S6220 may be implemented as an independent embodiment. For example, a combination of steps S6240 may be implemented as an independent embodiment. For example, a combination of steps S6230 and S6240 may be implemented as an independent embodiment. For example, a combination of steps S6220, S6230, and S6240 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more of steps S6210 to S6240 are not limited to this.

[0390] In some embodiments, steps S6210, S6230, and S6240 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0391] In some embodiments, steps S6210 and S6220 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0392] FIG7A is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to an NTN-based communication method, which is applied to the first network element 1031. As shown in FIG7A , the method includes steps S7110 to S7150.

[0393] In step S7110, store and forward time information is obtained.

[0394] The optional implementation of step S7110 can refer to the optional implementation of step S4110 in Figure 4A, step S6110 in Figure 6A, and other related parts in the embodiments involved in Figures 4A and 6A, which will not be repeated here.

[0395] In some embodiments, the first network element 1031 may receive storage and forwarding time information from the access network device 102, but is not limited thereto and may also receive storage and forwarding time information from other entities.

[0396] In some embodiments, the first network element 1031 may obtain storage and forwarding time information specified by the protocol.

[0397] In some embodiments, the first network element 1031 may obtain the storage and forwarding time information from an upper layer.

[0398] In some embodiments, the first network element 1031 may perform processing to obtain storage and forwarding time information.

[0399] In some embodiments, the first network element 1031 may be pre-configured with storage and forwarding time information.

[0400] In step S7120, a registration request message is obtained.

[0401] The optional implementation of step S7120 can refer to the optional implementation of step S4120 in Figure 4A, step S5110 in Figure 5A, and other related parts in the embodiments involved in Figures 4A and 5A, which will not be repeated here.

[0402] In some embodiments, the first network element 1031 may receive a registration request message from the terminal 101 , but is not limited thereto. The first network element 1031 may also receive a registration request message from the access network device 102 or other entities.

[0403] In step S7130, the contract information is obtained.

[0404] The optional implementation of step S7130 can refer to the optional implementation of step S4130 in Figure 4A, as well as other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0405] In some embodiments, the first network element 1031 may receive contract information from the third network element 1033 , but is not limited thereto and may also receive contract information from other entities.

[0406] In step S7140, the store and forward function is determined.

[0407] The optional implementation of step S7140 can refer to the optional implementation of step S4140 in Figure 4A, as well as other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0408] In some embodiments, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function based on subscription information and / or operator policy.

[0409] In step S7150, a first message is sent.

[0410] The optional implementation of step S7150 can refer to the optional implementation of step S4150 in Figure 4A, as well as other related parts in the embodiment involved in Figure 4A, which will not be repeated here.

[0411] In some embodiments, the first network element 1031 may send the first message to the terminal 101 , but is not limited thereto, and may also send the first message to the access network device 102 or other entities.

[0412] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S7110 to S7150. For example, step S7150 may be implemented as an independent embodiment. For example, step S7150 may be implemented as an independent embodiment. For example, the combination of steps S7140 and S7150 may be implemented as an independent embodiment. For example, the combination of steps S7130 and S7140 may be implemented as an independent embodiment. For example, the combination of steps S7130, S7140, and S7150 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S7110 to S7150 are not limited to these.

[0413] In some embodiments, steps S7110, S7120, S7130, and S7140 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0414] In some embodiments, steps S7110, S7120, S7130, and S7150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0415] FIG7B is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to an NTN-based communication method, which is applied to the first network element 1031. As shown in FIG7B , the method includes steps S7210 to S7240.

[0416] In step S7210, a registration request message is obtained.

[0417] The optional implementation of step S7210 can refer to the optional implementation of step S4210 in Figure 4B, step S5210 in Figure 5B, and other related parts in the embodiments involved in Figures 4B and 5B, which will not be repeated here.

[0418] In some embodiments, the first network element 1031 may receive a registration request message from the terminal 101 , but is not limited thereto. The first network element 1031 may also receive a registration request message from the access network device 102 or other entities.

[0419] In step S7220, the contract information is obtained.

[0420] The optional implementation of step S7220 can refer to the optional implementation of step S4220 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0421] In some embodiments, the first network element 1031 may receive contract information from the third network element 1033 , but is not limited thereto and may also receive contract information from other entities.

[0422] In step S7230, it is determined that the store and forward function is authorized.

[0423] The optional implementation of step S7230 can refer to the optional implementation of step S4230 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0424] In some embodiments, the first network element 1031 may determine to authorize the terminal 101 to use the store and forward function based on subscription information and / or operator policy.

[0425] In step S7240, the first message is sent.

[0426] The optional implementation of step S7240 can refer to the optional implementation of step S4240 in Figure 4B, as well as other related parts in the embodiment involved in Figure 4B, which will not be repeated here.

[0427] In some embodiments, the first network element 1031 may send the first message to the terminal 101 , but is not limited thereto, and may also send the first message to the access network device 102 or other entities.

[0428] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S7210 to S7240. For example, step S7230 may be implemented as an independent embodiment. For example, step S7240 may be implemented as an independent embodiment. For example, the combination of steps S7230 and S7240 may be implemented as an independent embodiment. For example, the combination of steps S7220 and S7230 may be implemented as an independent embodiment. For example, the combination of steps S7220, S7230, and S7240 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S7210 to S7240 are not limited to these.

[0429] In some embodiments, steps S7210, S7220, and S7230 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0430] In some embodiments, steps S7210 and S7240 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0431] Figure 8 is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to an NTN-based communication method, which is applied to the second network element 1032. As shown in Figure 8, the method includes steps S810 and S820.

[0432] In step S810, a second message is obtained.

[0433] The optional implementation of step S810 can refer to the optional implementation of step S4250 in Figure 4B, step S530 in Figure 5B, and other related parts in the embodiments involved in Figures 4B and 5B, which will not be repeated here.

[0434] In some embodiments, the second network element 1032 may receive a second message from the terminal 101 .

[0435] In some embodiments, the second message may be a message sent by the terminal 101 to the second network element 1032 .

[0436] In step S820, a third message is sent.

[0437] The optional implementation of step S820 can refer to the optional implementation of step S4260 in Figure 4B, step S540 in Figure 5B, and other related parts in the embodiments involved in Figures 4B and 5B, which will not be repeated here.

[0438] In some embodiments, the second network element 1031 may send the third message to the terminal 101, but is not limited thereto and may also send the first message to other entities.

[0439] The NTN-based communication method involved in the embodiments of the present disclosure may include at least one of steps S810 to S820. For example, step S820 may be implemented as an independent embodiment. For example, a combination of steps S810 and S820 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more of steps S7210 to S7240 are not limited to this.

[0440] In some embodiments, step S810 is optional and may be omitted or replaced in different embodiments.

[0441] Figure 9 is an exemplary flow chart of an NTN-based communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to an NTN-based communication method, which is applied to the third network element 1033. As shown in Figure 9, the method includes step S910.

[0442] In step S910, the contract signing information is sent.

[0443] The optional implementation methods of step S910 can be found in step S4130 of Figure 4A, step S4220 of Figure 4B, step S7130 of Figure 7A, step S7220 of Figure 7B, and other related parts in the embodiments involved in Figures 4A, 4B, 7A, and 7B, which will not be repeated here.

[0444] In some embodiments, the third network element 1033 may send the contract information to the first network element 1031 .

[0445] In some embodiments, the third network element 1033 may send the subscription information to the first network element 1031 through the Nudm_SDM_Get service operation.

[0446] Figure 10 is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to an NTN-based communication method, which is applied to a core network device 103. As shown in Figure 10, the method includes step S1010.

[0447] In step S1010 , the first network element 1031 obtains subscription information from the third network element 1033 .

[0448] The optional implementation methods of step S1010 can be found in step S4130 of Figure 4A, step S4220 of Figure 4B, step S7130 of Figure 7A, step S7220 of Figure 7B, and the optional methods of step S910 of Figure 9, as well as other related parts in the embodiments involved in Figures 4A, 4B, 7A, 7B, and 9, which will not be repeated here.

[0449] In some embodiments, the third network element 1033 may send the contract information to the first network element 1031 .

[0450] In step S1020 , the first network element 1031 determines whether the terminal is authorized to use the store and forward function.

[0451] The optional implementation of step S1020 can be found in step S4140 of Figure 4A, step S4230 of Figure 4B, step S7140 of Figure 7A, step S7230 of Figure 7B, and other related parts in the embodiments involved in Figures 4A, 4B, 7A, and 7B, which will not be repeated here.

[0452] The NTN-based communication method according to the embodiments of the present disclosure may include at least one of steps S1010 to S1020. For example, step S1010 may be implemented as an independent embodiment. For example, step S1020 may be implemented as an independent embodiment. For example, a combination of steps S1010 and S1020 may be implemented as an independent embodiment.

[0453] In some embodiments, step S1010 is optional and may be omitted or replaced in different embodiments.

[0454] In some embodiments, step S1020 is optional and may be omitted or replaced in different embodiments.

[0455] FIG11A is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure. The present disclosure relates to an NTN-based communication method. As shown in FIG11A , the method includes step S10110.

[0456] In step S11110 , the first network element 1031 sends a first message to the terminal 101 .

[0457] For optional implementation methods of step S11110, please refer to step S4150 of Figure 4A, step S4240 of Figure 4B, step S5120 of Figure 5A, step S5220 of Figure 5B, step S7150 of Figure 7A, step S7240 of Figure 7B, and other related parts in the embodiments involved in Figures 4A, 4B, 5A, 5B, 7A, and 7B, which will not be repeated here.

[0458] FIG11B is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure. The present disclosure relates to an NTN-based communication method. As shown in FIG11B , the method includes steps S11210 and S11220.

[0459] In step S11210 , the terminal 101 sends a second message to the second network element 1032 .

[0460] The optional implementation methods of step S11210 can refer to the optional methods of step S4250 in Figure 4B, step S5230 in Figure 5B, step S810 in Figure 8, and other related parts in the embodiments involved in Figures 4B, 5B, and 8, which will not be repeated here.

[0461] In step S11220 , the second network element 1032 sends a third message to the terminal 101 .

[0462] The optional implementation methods of step S11220 can refer to the optional methods of step S4260 in Figure 4B, step S5240 in Figure 5B, step S820 in Figure 8, and other related parts in the embodiments involved in Figures 4B, 5B, and 8, which will not be repeated here.

[0463] FIG12A is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure. The present disclosure relates to an NTN-based communication method. As shown in FIG12A , the method includes steps S12110 to S12150.

[0464] In step S12110, the store-and-forward time information includes information indicating the start and duration of data storage. If the feeder link becomes unavailable, the gNB begins data storage for UE data exchanged using satellite access. The data storage duration reflects the length of time data needs to be stored due to the feeder link unavailability.

[0465] Considering that satellite network deployment does not change frequently, the storage and forwarding time information is relatively fixed. Therefore, after the satellite network is deployed, such storage and forwarding time information can be pre-configured in the 5GC (e.g., AMF), or received from the RAN through the N2 procedure (using UE-independent N2 signaling to exchange configuration data) as described in 4.2.7 of TS 23.502, or received from the RAN through the NGAP message during the UE registration procedure as described in 4.2.2.2.2 of TS 23.502.

[0466] In step S12120, if the UE wants to access the 5GC using satellite access, the UE initiates a registration request to the AMF. The registration request message contains the access type and the RAT type. The RAT type indicates the access network used by the UE, for example, LEO-NR.

[0467] In step S12130, after receiving the registration request, the AMF can obtain the UE's subscription data (i.e., subscription information) from the UDM through the Nudm_SDM_Get service operation. The UE's subscription data includes information indicating whether the UE has subscribed to support the store and forward feature.

[0468] In step S12140, based on the UE's subscription information and / or operator policy, the AMF authorizes the UE using satellite access to enable the store and forward feature.

[0469] In step S12150, the AMF sends a Registration Accept message to the UE, indicating that the UE is authorized to use the store-and-forward feature. In some embodiments, the Registration Accept message may include store-and-forward time information. In some embodiments, if the RAN receives the Registration Accept message (step 12150a), the RAN may send the store-and-forward time information along with the Registration Accept message to the UE (step S12150b).

[0470] FIG12B is an exemplary interaction diagram of an NTN-based communication method according to an embodiment of the present disclosure. The present disclosure relates to an NTN-based communication method. As shown in FIG12B , the method includes steps S12210 to S12260.

[0471] In step S12210, if the UE wants to access the 5GC using satellite access, the UE initiates a registration request to the AMF. The registration request message contains the access type and the RAT type. The RAT type indicates the access network used by the UE, for example, LEO-NR.

[0472] In step S12220, after receiving the registration request, the AMF can obtain the UE's subscription data (i.e., subscription information) from the UDM through the Nudm_SDM_Get service operation. The UE's subscription data includes information indicating whether the UE has subscribed to support the store and forward feature.

[0473] In step S12230, based on the UE's subscription information and / or operator policy, the AMF authorizes the UE using satellite access to enable the store-and-forward feature. The AMF provides the UE with an authorization token and the server's IP address. The server's IP address indicates the server with which the UE can communicate to obtain store-and-forward time information.

[0474] In step S12240, the AMF sends a Registration Accept message to the UE, indicating that the UE is authorized to use the store and forward feature. The Registration Accept message also includes a token and the IP address of the server.

[0475] In step S12250, if the UE is authorized to use the store and forward feature, the UE sends a request message to the server using the token and the server's IP address.

[0476] In step S12260, the server returns data storage and forwarding time information to the UE. The storage and forwarding time information includes information indicating the start and duration of data storage. If the feeder link becomes unavailable, the gNB starts data storage for UE data exchanged using satellite access. The data storage duration reflects the length of time data needs to be stored due to the feeder link unavailability.

[0477] In some embodiments, the RAN provides the store-and-forward time information to the AMF. For example, the RAN sends the store-and-forward time information to the AMF via the N2 procedure (using UE-independent N2 signaling to exchange configuration data) as described in 4.2.7 of TS 23.502. For another example, the RAN sends the store-and-forward time information to the AMF via an NGAP message during the UE registration procedure as described in 4.2.2.2.2 of TS 23.502.

[0478] In some embodiments, the store-and-forward time information is determined by the RAN or obtained by the RAN from an external server (eg, OAM).

[0479] In some embodiments, the UE is authorized (eg, based on the UE's subscription information and / or operator policy) to use the data store and forward feature.

[0480] In some embodiments, the RAN or 5GC network function (e.g., AMF or SMF) provides storage and forwarding time information to the UE.

[0481] In some embodiments, the storage and forwarding time information includes at least one of the following information elements: the start of data storage and the data storage duration.

[0482] In some embodiments, indication information may also be provided to the UE to indicate that the UE is authorized to use the store and forward feature.

[0483] In some embodiments, if the storage and forwarding time information is provided by 5GC, the storage and forwarding time information can be sent to the UE using NAS messages (e.g., messages of registration acceptance, user configuration update process, etc.).

[0484] In some embodiments, if the store-and-forward time information is provided by the RAN, the store-and-forward time information may be sent to the UE upon receiving a NAS message (eg, a Registration Accept message).

[0485] In some embodiments, the UE may obtain the store-and-forward time information from an external server via a token.

[0486] In some embodiments, the token is assigned to the UE by the 5GC if the UE is authorized to use the store and forward feature.

[0487] In the embodiments shown in Figures 12A and 12B, exemplarily, the UE is the terminal 101, the RAN is the access network device 102, the AMF is the first network element 1031, the server is the second network element 1032, and the UDM is the third network element 1033.

[0488] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

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

[0490] It should be understood that the division of the various units or modules in the above devices 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 devices, 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.

[0491] In the embodiments of the present disclosure, a 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 a 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 to implement 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.

[0492] FIG13 is an exemplary structural diagram of an NTN-based communication device according to an embodiment of the present disclosure. As shown in FIG13 , the NTN-based communication device 1300 may include at least one of a sending module 1310 and a receiving module 1320 .

[0493] In some embodiments, the above-mentioned sending module 1310 can be used to execute at least one of the sending-related steps performed by the terminal 101 in any of the above methods (for example, step S4120, step S4210, step S4250, step S5110, step S5210, step S5230, step S7150, step S810, step S11210, step S12120, step S12210, step S12250, but not limited to this).

[0494] In some embodiments, the above-mentioned receiving module 1030 can be used to execute at least one of the reception-related steps performed by the terminal 101 in any of the above methods (for example, step S4150, step S4240, step S4260, step S5120, step S5220, step S5240, step S5410, step S7150, step S820, step S11110, step S11220, step S12150, step S12240, step S12260, but not limited to these).

[0495] FIG14 is an exemplary structural diagram of an NTN-based communication device according to an embodiment of the present disclosure. As shown in FIG14 , the NTN-based communication device 1400 may include at least one of a sending module 1410 , a receiving module 1420 , and a processing module 1430 .

[0496] In some embodiments, the above-mentioned sending module 1410 can be used to execute at least one of the sending-related steps (for example, step S4150, step S4240, step S5120, step S5220, step S5410, step S7150, step S7240, step S11110, step S12150, but not limited to) performed by the first network element 1031 in any of the above methods.

[0497] In some embodiments, the above-mentioned receiving module 1420 can be used to execute at least one of the receiving-related steps performed by the first network element 1031 in any of the above methods (for example, step S4110, step S4120, step S4130, step S4210, step S4220, step S5110, step S5210, step S610, step S7110, step S7120, step S7130, step S7210, step S7220, step S910, step S1010, step S12110, step S12120, step S12130, step S12210, step S12220, but not limited to these).

[0498] In some embodiments, the above-mentioned processing module 1430 can be used to execute at least one of the determination-related steps (for example, step S4140, step S4230, step S7140, step S7230, step S12140, step S12230, but not limited to these) performed by the first network element 1031 in any of the above methods.

[0499] FIG15 is an exemplary structural diagram of an NTN-based communication device according to an embodiment of the present disclosure. As shown in FIG15 , the NTN-based communication device 1500 may include at least one of a sending module 1510 and a receiving module 1520 .

[0500] In some embodiments, the above-mentioned sending module 1510 can be used to execute at least one of the sending-related steps (for example, step S4260, step S5240, step S820, step S11220, step S12260, but not limited to these) performed by the second network element 1032 in any of the above methods.

[0501] In some embodiments, the above-mentioned receiving module 1520 can be used to execute at least one of the reception-related steps of the second network element 1032 in any of the above methods (for example, step S4250, step S5230, step S810, step S11210, step S12250, but not limited to these).

[0502] Figure 16 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 1600 can be a network device (e.g., an access network device or a core network device), a terminal (e.g., a user device), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above communication methods. Communication device 1600 can be used to implement the communication method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0503] As shown in Figure 16, the communication device 1600 includes one or more processors 1601. The processor 1601 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. The processor 1601 is used to call instructions to enable the communication device 1600 to execute any of the above communication methods.

[0504] In some embodiments, the communication device 1600 further includes one or more memories 1602 for storing instructions. Alternatively, all or part of the memories 1602 may be located outside the communication device 1600.

[0505] In some embodiments, the communication device 1600 further includes one or more transceivers 1603. When the communication device 1600 includes one or more transceivers 1603, the communication steps such as sending and receiving in the above method are performed by the transceiver 1603, and the other steps are performed by the processor 1601.

[0506] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0507] Optionally, the communication device 1600 further includes one or more interface circuits 1604, which are connected to the memory 1602. The interface circuits 1604 may be configured to receive signals from the memory 1602 or other devices, and may be configured to send signals to the memory 1602 or other devices. For example, the interface circuits 1604 may read instructions stored in the memory 1602 and send the instructions to the processor 1601.

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

[0509] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 1600, the communication device 1600 executes any of the above communication methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

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

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

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

[0513] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A communication method based on a non-terrestrial network NTN, performed by a terminal, and comprising: A first message is received from a first network function, wherein the first message is used to indicate that the terminal is authorized to use a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner in NTN access.

2. The method according to claim 1, wherein: The first message includes store-and-forward time information.

3. The method according to claim 1, wherein: The receiving a first message from a first network function comprises: Receive the first message sent by the first network function and forwarded by the access network device.

4. The method according to claim 3, wherein: Receiving the first message sent by the first network function and forwarded by the access network device includes: Receive storage and forwarding time information sent by the access network device.

5. The method according to claim 1, wherein: The first message includes a token and address information of a second network function, wherein the token is used to authorize the terminal to obtain storage and forwarding time information from the second network function.

6. The method according to claim 5, wherein: The method further comprises: Sending a second message to the second network function, wherein the second message is used to request the second network function for the storage and forwarding time information; A third message is received from a second network function, wherein the third message includes the store-and-forward time information.

7. The method according to claim 6, wherein: The second message includes the token.

8. The method according to any one of claims 2, 4 to 7, wherein: The storage and forwarding time information includes at least one of the following: data storage start time, data storage duration; Among them, the data storage start time is determined based on the start time of the interruption of the feeder link between the satellite and the ground station, and the data storage duration is determined based on the duration between the start time of the interruption of the feeder link and the time when the feeder link is restored.

9. A communication method based on a non-terrestrial network NTN, performed by a first network function, comprising: A first message is sent to a terminal, wherein the first message is used to indicate that the terminal is authorized to use a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner in NTN access.

10. The method according to claim 9, wherein: The first message includes store-and-forward time information.

11. The method according to claim 9 or 10, wherein: The method further comprises: The storage and forwarding time information is received from the access network device.

12. The method according to claim 9, wherein: The first message includes a token and address information of a second network function, wherein the token is used to authorize the terminal to obtain storage and forwarding time information from the second network function.

13. The method according to any one of claims 10 to 12, wherein: The storage and forwarding time information includes at least one of the following: data storage start time, data storage duration; Among them, the data storage start time is determined based on the start time of the feeder link interruption between the satellite and the ground station, and the data storage duration is determined based on the duration between the start time of the interruption of the feeder link and the time when the feeder link is restored.

14. The method according to any one of claims 9 to 13, wherein: Before sending the first message to the terminal, the method further includes: receiving subscription information of the terminal from a third network function; Based on the subscription information and / or operator policy, determine whether to authorize the terminal to use the store-and-forward function.

15. A communication method based on a non-terrestrial network (NTN), performed by a second network function, and comprising: receiving a second message from the terminal, wherein the second message includes information for requesting storage and forwarding time information from the second network function; A third message is sent to the terminal, wherein the third message includes the storage and forwarding time information.

16. The method according to claim 15, wherein: The second information includes a token, and the token is used to authorize the terminal to obtain the storage and forwarding time information from the second network function.

17. The method according to claim 15 or 16, wherein: The storage and forwarding time information includes at least one of the following: data storage start time, data storage duration; Among them, the data storage start time is determined based on the start time of the interruption of the feeder link between the satellite and the ground station, and the data storage duration is determined based on the duration between the start time of the interruption of the feeder link and the time when the feeder link is restored.

18. A communication method based on a non-terrestrial network (NTN), comprising: A first message is sent to a terminal, wherein the first message is used to indicate that the terminal is authorized to use a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner in NTN access.

19. The method according to claim 18, wherein: The method further comprises: Receives store and forward time information from access network equipment.

20. The method according to claim 18, wherein: The method further comprises: receiving a second message from the terminal, wherein the second message includes information for requesting storage and forwarding time; A third message is sent to the terminal, wherein the third message includes the storage and forwarding time information.

21. A communication device based on a non-terrestrial network (NTN), arranged in a terminal, and comprising: The receiving module is configured to receive a first message from a first network function, wherein the first message is used to indicate that the terminal is authorized to use a store-and-forward function, wherein the store-and-forward function is used to transmit data of the terminal in a store-and-forward manner in NTN access.

22. A communication device based on a non-terrestrial network NTN, arranged in a first network function, and comprising: The sending module is configured to send a first message to the terminal, wherein the first message is used to indicate that the terminal is authorized to use a store and forward function, wherein the store and forward function is used to transmit data of the terminal in a store and forward manner in NTN access.

23. A communication device based on a non-terrestrial network NTN, arranged in a second network function, and comprising: A receiving module configured to receive a second message from the terminal, wherein the second message includes information for requesting storage and forwarding time information from the second network function; The sending module is configured to send a third message to the terminal, wherein the third message includes the storage and forwarding time information.

24. A communication device comprising: at least one processor; The processor is used to call instructions to execute the communication method according to any one of claims 1 to 20.

25. A communication system comprising a first network function and a third network function; in, The third network function is configured to: send the subscription information of the terminal to the first network function; The first network function is configured to: receive the subscription information from the third network function; and determine, based on the subscription information and / or operator policy, whether to authorize the terminal to use a store-and-forward function.

26. The communication system of claim 25, further comprising a second network function; in, The second network function is configured to provide store and forward time information.

27. A communication system, comprising a terminal, an access network device, and a core network device, wherein: The terminal is configured to implement the communication method according to any one of claims 1 to 8, and the core network device is configured to implement the communication method according to any one of claims 18 to 20.

28. A storage medium, wherein: The storage medium stores instructions, wherein the instructions, when executed by a processor, perform the communication method according to any one of claims 1 to 20.