Communication method, terminal, access network device, communication device, and storage medium

Abstract

The present disclosure relates to a communication method, a terminal, an access network device, a communication device, and a storage medium. The method comprises: receiving first information, the first information being used for indicating at least one of the following: whether a store-and-forward function is enabled, whether there is a feeder link between a satellite and a ground station, and whether a core network function is deployed on the satellite; and on the basis of the first information, determining a first operation. The present disclosure enables a terminal to operate on the basis of a change in at least one of the status of the store-and-forward function, the status of the feeder link, and the status of deployment of the core network function on the satellite indicated by a network.

Description

Communication method, terminal, access network device, communication device and storage medium Technical Field

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

[0002] The evolution of telecommunications network technology has seen the integration of non-terrestrial network (NTN) technologies and support for satellite access. This allows terminals to access the core network and conduct services via satellite access networks. However, due to issues such as insufficient satellite deployments and limited coverage, satellite access networks may not provide continuous satellite connectivity. This discontinuous satellite connection can include intermittent connections between satellites and terminals, or between satellites and ground stations.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure propose a communication method, a terminal, an access network device, a communication device, and a storage medium, so as to implement, for a communication system supporting satellite access, changes in the operation of the terminal according to at least one of the storage and forwarding functions indicated by the network, the feeder link conditions, and the deployment conditions of the core network functions on the satellite.

[0005] According to a first aspect of an embodiment of the present disclosure, an embodiment of the present disclosure proposes a communication method, which is executed by a terminal, and the method includes: receiving first information, the first information being used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; and determining a first operation based on the first information.

[0006] According to a second aspect of an embodiment of the present disclosure, an embodiment of the present disclosure proposes a communication method, which is executed by an access network device, and the access network device is deployed on a satellite. The method includes: sending first information, and the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; the first information is also used by the terminal to determine the first operation.

[0007] According to the third aspect of an embodiment of the present disclosure, an embodiment of the present disclosure proposes a terminal, including: a first transceiver module, used to receive first information, the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; a first processing module, used to determine a first operation based on the first information.

[0008] According to the fourth aspect of the embodiment of the present disclosure, the embodiment of the present disclosure proposes an access network device, including: a second transceiver module, used to send first information, the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; the first information is also used by the terminal to determine the first operation.

[0009] According to the fifth aspect of the embodiment of the present disclosure, the embodiment of the present disclosure proposes a communication device, including: one or more processors; wherein the above-mentioned communication device is used to execute the steps of the communication method described in any one of the first aspect, the second aspect and their optional implementation methods.

[0010] According to the sixth aspect of an embodiment of the present disclosure, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and an access network device; wherein the terminal is configured to execute the steps of the communication method as described in the first aspect and any one of its optional implementations, and the access network device is configured to execute the steps of the communication method as described in the second aspect and any one of its optional implementations.

[0011] According to the seventh aspect of the embodiment of the present disclosure, the embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0012] According to the eighth aspect of the embodiment of the present disclosure, the embodiment of the present disclosure proposes a program product. When the above program product is executed by a communication device, the above communication device executes the steps of the communication method as described in any one of the first aspect, the second aspect and their optional implementation methods.

[0013] According to the ninth aspect of the embodiment of the present disclosure, the embodiment of the present disclosure proposes a computer program, which, when running on a computer, enables the computer to execute the steps of the communication method as described in any one of the first aspect, the second aspect and their optional implementation methods.

[0014] According to a tenth aspect of the embodiments of the present disclosure, the embodiments of the present disclosure provide a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the steps of the communication method as described in any one of the first aspect, the second aspect, and their optional implementations.

[0015] The technical solution provided by the embodiments of the present disclosure is aimed at a communication system supporting satellite access, and can enable the terminal to operate according to changes in at least one of the storage and forwarding function conditions, the feeder link conditions, and the deployment conditions of the core network functions on the satellite.

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

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

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

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

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

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

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

[0023] FIG3 is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure.

[0024] FIG4A is a schematic diagram of an implementation flow of a communication method executed on a terminal side according to an embodiment of the present disclosure.

[0025] FIG4B is a schematic diagram of an implementation flow of a communication method executed on an access network device side according to an embodiment of the present disclosure.

[0026] FIG5A is a schematic diagram of an implementation flow of a communication method executed on a terminal side according to an embodiment of the present disclosure.

[0027] FIG5B is a schematic diagram of an implementation flow of a communication method executed on an access network device side according to an embodiment of the present disclosure.

[0028] FIG6A is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0029] FIG6B is a schematic structural diagram of an access network device according to an embodiment of the present disclosure.

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

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

[0032] Embodiments of the present disclosure provide a communication method, a terminal, an access network device, a communication device, and a storage medium.

[0033] In a first aspect, an embodiment of the present disclosure proposes a communication method, which is executed by a terminal, and the method includes: receiving first information, where the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; and determining a first operation based on the first information.

[0034] In an embodiment of the present disclosure, the terminal determines a first operation based on at least one of the storage and forwarding function conditions, the feeder link conditions, and the deployment of the core network function on the satellite indicated by the first information, thereby enabling the terminal to operate according to changes in at least one of the storage and forwarding function conditions, the feeder link conditions, and the deployment of the core network function on the satellite.

[0035] In some possible implementations, the first operation includes at least one of the following: sending uplink data in a radio resource control (RRC) idle state; transitioning from an RRC idle state to an RRC connected state and sending uplink data; remaining in an RRC idle state; prohibiting the sending of uplink data in an RRC connected state; prohibiting the transition from an RRC idle state to an RRC connected state; transitioning from an RRC idle state to an RRC connected state but prohibiting the sending of uplink data; not sending a first message in an RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data; and sending uplink data in an RRC connected state.

[0036] In some possible embodiments, based on the first information, a first operation is determined, including one of the following: when the first information indicates that the storage and forwarding function is turned on, determining to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off, determining to prohibit sending uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off, determining to remain in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off, determining to prohibit transitioning from the RRC idle state to the RRC connected state; when the first information indicates that the storage and forwarding function is turned off, determining to prohibit sending uplink data in the RRC connected state; when the first information indicates that the storage and forwarding function is turned off, determining to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data; when the first information indicates that the storage and forwarding function is turned off, determining not to send the first message in the RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data.

[0037] In some possible embodiments, based on the first information, a first operation is determined, including one of the following: when the first information indicates that the storage and forwarding function is turned on and there is a feeder link, determining to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and there is a feeder link, determining to switch from the RRC idle state to the RRC connected state and send uplink data; when the first information indicates that the storage and forwarding function is turned on and there is no feeder link, determining to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and there is no feeder link, determining to remain in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and there is no feeder link, determining to prohibit switching from the RRC idle state to the RRC connected state.

[0038] In some possible embodiments, based on the first information, a first operation is determined, including one of the following: when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, determining that uplink data is prohibited from being sent in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, determining that transitioning from the RRC idle state to the RRC connected state is prohibited; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, determining that uplink data is prohibited from being sent in the RRC connected state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determining that uplink data is sent in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determining to transition from the RRC idle state to the RRC connected state and send uplink data; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determining not to send the first message in the RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determining to send uplink data in the RRC connected state.

[0039] In some possible implementations, determining a first operation based on the first information includes one of the following: determining to send uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite; determining to switch from the RRC idle state to the RRC connected state and send uplink data when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite; determining to send uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; determining to remain in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; determining to prohibit switching from the RRC idle state to the RRC connected state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; determining to send uplink data in the RRC connected state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; and determining to switch from the RRC idle state to the RRC connected state but prohibit sending uplink data when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite.

[0040] In some possible implementations, based on the first information, determining a first operation includes one of the following: determining to send uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is deployed on the satellite; determining to switch from the RRC idle state to the RRC connected state and send uplink data when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is deployed on the satellite; determining to send uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is not deployed on the satellite; , when there is no feeder link and no core network function is deployed on the satellite, it is determined to remain in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, it is determined to prohibit the transition from the RRC idle state to the RRC connected state; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, it is determined to send uplink data in the RRC connected state; when the first information indicates that the storage and forwarding function is turned off, there is no feeder link, and the core network function is deployed on the satellite, it is determined to transition from the RRC idle state to the RRC connected state but prohibit the sending of uplink data.

[0041] In some possible implementations, before receiving the first information, the method further includes: sending second information, where the second information is used to indicate whether the terminal supports a store and forward function.

[0042] In the embodiment of the present disclosure, the terminal may also report to the access network device whether it supports the store and forward function, so as to achieve capability interaction with the network.

[0043] In the second aspect, an embodiment of the present disclosure proposes a communication method, which is executed by an access network device, and the access network device is deployed on a satellite. The method includes: sending first information, and the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; the first information is also used by the terminal to determine the first operation.

[0044] In some possible implementations, the first operation includes at least one of the following: sending uplink data in the RRC idle state; transitioning from the RRC idle state to the RRC connected state and sending uplink data; remaining in the RRC idle state; prohibiting the sending of uplink data in the RRC connected state; prohibiting the transition from the RRC idle state to the RRC connected state; transitioning from the RRC idle state to the RRC connected state but prohibiting the sending of uplink data; not sending the first message in the RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data; sending uplink data in the RRC connected state.

[0045] In some possible embodiments, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on; prohibiting the sending of uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned off; remaining in the RRC idle state when the first information indicates that the storage and forwarding function is turned off; prohibiting the transition from the RRC idle state to the RRC connected state when the first information indicates that the storage and forwarding function is turned off; prohibiting the sending of uplink data in the RRC connected state when the first information indicates that the storage and forwarding function is turned off; transitioning from the RRC idle state to the RRC connected state but prohibiting the sending of uplink data when the first information indicates that the storage and forwarding function is turned off; not sending the first message in the RRC connected state when the first information indicates that the storage and forwarding function is turned off, the first message is used to request uplink resources, and the uplink resources are used to send uplink data.

[0046] In some possible embodiments, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and there is a feeder link; converting from the RRC idle state to the RRC connected state and sending uplink data when the first information indicates that the storage and forwarding function is turned on and there is a feeder link; sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link; remaining in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link; prohibiting the conversion from the RRC idle state to the RRC connected state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link; prohibiting the sending of uplink data in the RRC connected state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link.

[0047] In some possible embodiments, the first operation includes at least one of the following: when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, prohibiting the sending of uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, prohibiting the transition from the RRC idle state to the RRC connected state; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, determining to prohibit the sending of uplink data in the RRC connected state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, sending uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, transitioning from the RRC idle state to the RRC connected state and sending uplink data; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, not sending the first message in the RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, sending uplink data in the RRC connected state.

[0048] In some possible implementations, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite; transitioning from the RRC idle state to the RRC connected state and sending uplink data when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite; sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; remaining in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; prohibiting transitioning from the RRC idle state to the RRC connected state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; prohibiting sending uplink data in the RRC connected state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; transitioning from the RRC idle state to the RRC connected state but prohibiting sending uplink data when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite.

[0049] In some possible implementations, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the store and forward function is turned on, there is a feeder link and the core network function is deployed on the satellite; converting from the RRC idle state to the RRC connected state and sending uplink data when the first information indicates that the store and forward function is turned on, there is a feeder link and the core network function is deployed on the satellite; determining to send uplink data in the RRC idle state when the first information indicates that the store and forward function is turned on, there is no feeder link and the core network function is not deployed on the satellite; and determining to send uplink data in the RRC idle state when the first information indicates that the store and forward function is turned on and there is no feeder link and the core network function is not deployed on the satellite. In the case of a feeder link and no core network function is deployed on the satellite, the RRC idle state is maintained; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, the transition from the RRC idle state to the RRC connected state is prohibited; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, the sending of uplink data in the RRC connected state is prohibited; when the first information indicates that the storage and forwarding function is turned off, there is no feeder link, and the core network function is deployed on the satellite, the RRC idle state is transitioned to the RRC connected state but the sending of uplink data is prohibited.

[0050] In some possible implementations, the first operation includes at least one of the following: receiving second information, where the second information is used to indicate whether the terminal supports a store and forward function, and the second information is used to determine the first information.

[0051] In the third aspect, an embodiment of the present disclosure proposes a terminal, including: a first transceiver module, used to receive first information, the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; a first processing module, used to determine a first operation based on the first information.

[0052] In some possible implementations, the first operation includes at least one of the following: sending uplink data in a radio resource control (RRC) idle state; transitioning from an RRC idle state to an RRC connected state and sending uplink data; remaining in an RRC idle state; prohibiting the sending of uplink data in an RRC connected state; prohibiting the transition from an RRC idle state to an RRC connected state; transitioning from an RRC idle state to an RRC connected state but prohibiting the sending of uplink data; not sending a first message in an RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data; and sending uplink data in an RRC connected state.

[0053] In some possible implementations, the first processing module is further used to perform one of the following: when the first information indicates that the storage and forwarding function is turned on, determine to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off, determine to prohibit sending uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off, determine to remain in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off, determine to prohibit transitioning from the RRC idle state to the RRC connected state; when the first information indicates that the storage and forwarding function is turned off, determine to prohibit sending uplink data in the RRC connected state; when the first information indicates that the storage and forwarding function is turned off, determine to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data; when the first information indicates that the storage and forwarding function is turned off, determine not to send the first message in the RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data.

[0054] In some possible embodiments, the first processing module is further used to perform one of the following: when the first information indicates that the storage and forwarding function is turned on and there is a feeder link, determine to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and there is a feeder link, determine to switch from the RRC idle state to the RRC connected state and send uplink data; when the first information indicates that the storage and forwarding function is turned on and there is no feeder link, determine to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and there is no feeder link, determine to remain in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and there is no feeder link, determine to prohibit switching from the RRC idle state to the RRC connected state.

[0055] In some possible implementations, the first processing module is further used to perform one of the following: when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, determine that uplink data is prohibited from being sent in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, determine that transitioning from the RRC idle state to the RRC connected state is prohibited; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, determine that uplink data is prohibited from being sent in the RRC connected state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determine that uplink data is sent in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determine to transition from the RRC idle state to the RRC connected state and send uplink data; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determine not to send the first message in the RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, determine to send uplink data in the RRC connected state.

[0056] In some possible implementations, the first processing module is further used to perform one of the following: when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite, determine to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite, determine to switch from the RRC idle state to the RRC connected state and send uplink data; when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite, determine to send uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite, determine to remain in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite, determine to prohibit switching from the RRC idle state to the RRC connected state; when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite, determine to send uplink data in the RRC connected state; when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite, determine to switch from the RRC idle state to the RRC connected state but prohibit sending uplink data when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite.

[0057] In some possible implementations, the first processing module is further used to perform one of the following: determining to send uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is deployed on the satellite; determining to switch from the RRC idle state to the RRC connected state and send uplink data when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is deployed on the satellite; determining to send uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is deployed on the satellite; When there is a feeder link and no core network function is deployed on the satellite, it is determined to remain in the RRC idle state; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, it is determined to prohibit the transition from the RRC idle state to the RRC connected state; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, it is determined to send uplink data in the RRC connected state; when the first information indicates that the storage and forwarding function is turned off, there is no feeder link, and the core network function is deployed on the satellite, it is determined to transition from the RRC idle state to the RRC connected state but prohibit the sending of uplink data.

[0058] In some possible implementations, the first transceiver module is further configured to send second information before receiving the first information, where the second information is used to indicate whether the terminal supports a store and forward function.

[0059] In the fourth aspect, an embodiment of the present disclosure proposes an access network device, including: a second transceiver module, used to send first information, the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; the first information is also used by the terminal to determine the first operation.

[0060] In some possible implementations, the first operation includes at least one of the following: sending uplink data in the RRC idle state; transitioning from the RRC idle state to the RRC connected state and sending uplink data; remaining in the RRC idle state; prohibiting the sending of uplink data in the RRC connected state; prohibiting the transition from the RRC idle state to the RRC connected state; transitioning from the RRC idle state to the RRC connected state but prohibiting the sending of uplink data; not sending the first message in the RRC connected state, the first message being used to request uplink resources, and the uplink resources being used to send uplink data; sending uplink data in the RRC connected state.

[0061] In some possible embodiments, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on; prohibiting the sending of uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned off; remaining in the RRC idle state when the first information indicates that the storage and forwarding function is turned off; prohibiting the transition from the RRC idle state to the RRC connected state when the first information indicates that the storage and forwarding function is turned off; prohibiting the sending of uplink data in the RRC connected state when the first information indicates that the storage and forwarding function is turned off; transitioning from the RRC idle state to the RRC connected state but prohibiting the sending of uplink data when the first information indicates that the storage and forwarding function is turned off; not sending the first message in the RRC connected state when the first information indicates that the storage and forwarding function is turned off, the first message is used to request uplink resources, and the uplink resources are used to send uplink data.

[0062] In some possible embodiments, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and there is a feeder link; converting from the RRC idle state to the RRC connected state and sending uplink data when the first information indicates that the storage and forwarding function is turned on and there is a feeder link; sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link; remaining in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link; prohibiting the conversion from the RRC idle state to the RRC connected state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link; prohibiting the sending of uplink data in the RRC connected state when the first information indicates that the storage and forwarding function is turned on and there is no feeder link.

[0063] In some possible embodiments, the first operation includes at least one of the following: when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, prohibiting the sending of uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, prohibiting the transition from the RRC idle state to the RRC connected state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, sending uplink data in the RRC idle state; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, transitioning from the RRC idle state to the RRC connected state and sending uplink data; when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, not sending the first message in the RRC connected state, the first message is used to request uplink resources, and the uplink resources are used to send uplink data; when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, sending uplink data in the RRC connected state.

[0064] In some possible implementations, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite; transitioning from the RRC idle state to the RRC connected state and sending uplink data when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite; sending uplink data in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; remaining in the RRC idle state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; prohibiting transitioning from the RRC idle state to the RRC connected state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; prohibiting sending uplink data in the RRC connected state when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite; transitioning from the RRC idle state to the RRC connected state but prohibiting sending uplink data when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite.

[0065] In some possible implementations, the first operation includes at least one of the following: sending uplink data in the RRC idle state when the first information indicates that the store and forward function is turned on, there is a feeder link and the core network function is deployed on the satellite; converting from the RRC idle state to the RRC connected state and sending uplink data when the first information indicates that the store and forward function is turned on, there is a feeder link and the core network function is deployed on the satellite; determining to send uplink data in the RRC idle state when the first information indicates that the store and forward function is turned on, there is no feeder link and the core network function is not deployed on the satellite; and determining to send uplink data in the RRC idle state when the first information indicates that the store and forward function is turned on and there is no feeder link and the core network function is not deployed on the satellite. In the case of a feeder link and no core network function is deployed on the satellite, the RRC idle state is maintained; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, the transition from the RRC idle state to the RRC connected state is prohibited; when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, the sending of uplink data in the RRC connected state is prohibited; when the first information indicates that the storage and forwarding function is turned off, there is no feeder link, and the core network function is deployed on the satellite, the RRC idle state is transitioned to the RRC connected state but the sending of uplink data is prohibited.

[0066] In some possible implementations, the first operation includes at least one of the following: receiving second information, where the second information is used to indicate whether the terminal supports a store and forward function, and the second information is used to determine the first information.

[0067] In a fifth aspect, an embodiment of the present disclosure proposes a communication device, comprising: one or more processors; wherein the above-mentioned communication device is used to execute the steps of the communication method described in any one of the first aspect, the second aspect and their optional implementation methods.

[0068] In the sixth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and an access network device; wherein the terminal is configured to execute the steps of the communication method as described in the first aspect and any one of its optional implementations, and the access network device is configured to execute the steps of the communication method as described in the second aspect and any one of its optional implementations.

[0069] In a seventh aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0070] In an eighth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the steps of the communication method as described in any one of the first aspect, the second aspect and their optional implementation methods.

[0071] In a ninth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the steps of the communication method as described in any one of the first aspect, the second aspect, and their optional implementations.

[0072] In a tenth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the steps of the communication method as described in any one of the first aspect, the second aspect, and their optional implementations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0091] In some embodiments, the terms “terminal,” “terminal device,” “user equipment (UE),” “user terminal,” “mobile station (MS),” “mobile terminal (MT),” “subscriber station,” “mobile unit,” “subscriber unit,” “wireless unit,” “remote unit,” “mobile device,” “wireless device,” “wireless communication device,” “remote device,” “mobile subscriber station,” “access terminal,” “mobile terminal,” “wireless terminal,” “remote terminal,” “handset,” “user agent,” “mobile client,” “client,” and the like may be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0129] For a regenerative architecture for satellite access, where at least base station functionality is deployed onboard the satellite, latency-tolerant services can be delivered even with discontinuous satellite connectivity. This requires the satellite to support store-and-forward (S&F) functionality, allowing data to be stored onboard in the event of a satellite connection interruption and forwarded when the connection is restored. This requires implementing terminal operation based on changes in at least one of the following: network-directed S&F functionality, feeder link availability, and the deployment of core network functionality onboard the satellite.

[0130] In order to solve the above problems, the embodiments of the present disclosure provide a communication method, a terminal, an access network device, a communication device and a storage medium, so as to realize the terminal's operation according to at least one of the storage and forwarding functions indicated by the network, the feeder link conditions and the deployment conditions of the core network functions on the satellite in a communication system supporting satellite access.

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

[0132] In the embodiments of the present disclosure, an E-UTRAN access network is used as an example for description. The access network equipment in the E-UTRAN is deployed on a satellite. In one example, the access network equipment is a satellite-borne eNB.

[0133] In some embodiments, the core network is taken as EPC as an example for description.

[0134] In some embodiments, some or all of the core network functions in the EPC can be deployed on the satellite.

[0135] In some embodiments, no core network functions in the EPC may be deployed on the satellite.

[0136] In some embodiments, the terminal may be in an RRC idle state, an RRC inactive state, or an RRC connected state. In some embodiments, the RRC idle state or the RRC inactive state may be described as an RRC non-connected state. In some embodiments, the term "RRC idle state" may be replaced with the term "RRC non-connected state."

[0137] In the embodiment of the present disclosure, the “RRC idle state” is taken as an example of the “RRC non-connected state” to illustrate the communication method provided by the embodiment of the present disclosure.

[0138] In step S310, the terminal sends second information.

[0139] In some embodiments, the access network device receives the second information.

[0140] In some embodiments, the second information indicates whether the terminal supports the store-and-forward function. In some embodiments, the access network device may determine the terminal's capability information for the store-and-forward function based on the second information. In some embodiments, the access network device may determine whether to authorize the terminal to use the store-and-forward function based on the second information. In some embodiments, the access network device may determine, based on the second information, the resources required to allocate to the terminal for use of the store-and-forward function. In some embodiments, the access network device may determine, based on the second information, whether to send the first information to the terminal.

[0141] In some embodiments, the second information may be carried in RRC signaling. In some embodiments, the second information may be carried in terminal capability information, such as UE capability information. In some embodiments, the second information may be carried in terminal assistance information, such as UE assistance information.

[0142] In step S320, the access network device sends first information.

[0143] In some embodiments, the terminal receives first information.

[0144] In some embodiments, the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; and based on the first information, a first operation is determined.

[0145] In some embodiments, whether the storage and forwarding function is enabled can be understood as: whether the access network device enables the storage and forwarding function, or whether the serving cell enables the storage and forwarding function.

[0146] In some embodiments, whether the store and forward function is enabled can also be understood as: whether the access network device supports the store and forward function, or whether the serving cell supports the store and forward function. In some embodiments, the access network device or serving cell supporting the store and forward function can be understood as the access network device or serving cell having the ability to provide the store and forward function.

[0147] In some embodiments, the access network device or serving cell enabling the store and forward function can be understood as: the access network device or serving cell supports the store and forward function and enables the store and forward function. In some embodiments, the access network or serving cell enabling the store and forward function can be understood as: the access network or serving cell supports the store and forward function and authorizes the terminal to use the store and forward function.

[0148] In some embodiments, the access network device or serving cell supporting the store and forward function can be understood as: the access network device or serving cell has resources to perform the store and forward function.

[0149] In some embodiments, authorizing a terminal to use the storage and forwarding function can be understood as: the access network device allocates resources required for the storage and forwarding function to the terminal, such as storage space, uplink and downlink resources for forwarding data, etc.

[0150] In some embodiments, disabling the store and forward function of an access network device or a serving cell can be understood as: the access network device or the serving cell supports the store and forward function but has disabled the store and forward function. In some embodiments, disabling the store and forward function of an access network device or a serving cell can also be understood as: the access network device or the serving cell does not support the store and forward function.

[0151] In some embodiments, the access network device or serving cell not supporting the store and forward function can be understood as: the access network device or serving cell does not have resources to perform the store and forward function.

[0152] In some embodiments, the access network device or serving cell not supporting the store and forward function can be understood as: the access network device or serving cell does not authorize the terminal to use the store and forward function.

[0153] In some embodiments, disabling the storage and forwarding function of the access network device or serving cell can be understood as: the access network device or serving cell supports the storage and forwarding function, but does not authorize the terminal to use the storage and forwarding function.

[0154] In some embodiments, whether there is a feeder link between the satellite and the ground station can be understood as: whether there is a feeder link, whether the feeder link is available, whether there is a connection between the satellite and the ground station, whether the feeder link is disconnected, etc.

[0155] In some embodiments, whether there is a feeder link between the satellite and the ground station can also be understood as: whether there is a feeder link at the current moment, or whether there is a feeder link at a future moment.

[0156] In some embodiments, if a feeder link exists at the current moment, the feeder link has been interrupted, and the connection between the satellite and the ground station has been disconnected.

[0157] In some embodiments, if there is a feeder link at a future time, the feeder link is about to be interrupted, and the connection between the satellite and the ground station is about to be disconnected.

[0158] In some embodiments, the access network device can detect whether a feeder link exists based on the third information. In one embodiment, the third information can be pre-configured or sent to the access network device by operation administration and maintenance (OAM).

[0159] In some embodiments, the third information may include at least one of satellite-associated ephemeris information and time information determined based on the satellite's ephemeris information. The time information determined based on the ephemeris information may be used to indicate the time when the feeder link exists and / or the time when the feeder link does not exist. In one example, the third information may indicate a period when the feeder link exists or a moment when the feeder link does not exist. In another example, the third information may indicate a period when the feeder link does not exist or a moment when the feeder link does not exist.

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

[0161] In some embodiments, whether core network functions are deployed on a satellite can be understood as: no core network functions are deployed on the satellite, some core network functions are deployed on the satellite, or all core network functions are deployed on the satellite. In one example, deploying some core network functions on a satellite can be understood as: some MME and / or AMF functions are deployed on the satellite, or all MME and / or AMF functions are deployed on the satellite.

[0162] In some embodiments, the first information may be carried in at least one of RRC signaling, media access control-control element (MAC-CE) signaling, downlink control information (DCI), and system messages. In some embodiments, the system message may include a master information block (MIB), a system information block (SIB), and the like.

[0163] In step S330, the terminal determines a first operation according to the first information.

[0164] In some embodiments, the first operation includes at least one of the following: sending uplink data in the RRC idle state, transitioning from the RRC idle state to the RRC connected state and sending uplink data, remaining in the RRC idle state, prohibiting the sending of uplink data in the RRC connected state, prohibiting the transition from the RRC idle state to the RRC connected state, transitioning from the RRC idle state to the RRC connected state but prohibiting the sending of uplink data, sending uplink data in the RRC connected state, and not sending a first message for requesting uplink resources in the RRC connected state. The uplink resources are used by the terminal to send uplink data.

[0165] In some embodiments, the terminal may send uplink data in the RRC idle state in at least one of the following ways: control plane optimization (CIoT EPS / 5GS optimization) of cellular internet of things (CIoT) in evolved packet system (EPS) or 5G system (5GS), user plane optimization (CIoT EPS / 5GS optimization) of CIoT in EPS / 5GS, mobile originating-early data transmission for control plane CIoT EPS / 5GS optimization, MO-EDT for user plane CIoT EPS / 5GS optimization, preconfigured uplink resource (PUR) for control plane optimization of CIoT in EPS / 5GS, and PUR for user plane CIoT EPS optimization. Of course, the terminal may also send uplink data in other ways in the RRC idle state. The above is only an example and is not specifically limited in the embodiments of the present disclosure.

[0166] In some embodiments, transitioning from the RRC idle state to the RRC connected state and sending uplink data can be understood as: in the RRC idle state, an RRC connection establishment process can be initiated to transition from the RRC idle state to the RRC connected state, and then uplink data can be sent in the RRC connected state. In one example, in the RRC idle state, an RRC setup message, an RRC resume message, etc. can be sent to initiate the RRC connection establishment process. In some embodiments, uplink resources can be requested in the RRC connected state, and uplink data can be sent on the uplink resources. In one example, in the RRC connected state, a first message can be sent to initiate a process such as a service request (SR) or random access, thereby requesting the obtained uplink resources.

[0167] In some embodiments, remaining in the RRC idle state may be understood as: no attempt should be made to enter the RRC connected state in the RRC idle state, or no RRC connection establishment process should be initiated in the RRC idle state, etc.

[0168] In some embodiments, prohibiting the sending of uplink data in the RRC connected state can be understood as: not attempting to enter the RRC connected state in the RRC idle state, or attempting to enter the RRC connected state in the RRC idle state but not sending uplink data, etc.

[0169] In some embodiments, prohibiting transition from the RRC idle state to the RRC connected state may be understood as: no attempt should be made to enter the RRC connected state in the RRC idle state.

[0170] In some embodiments, transitioning from the RRC idle state to the RRC connected state but prohibiting sending uplink data can be understood as: attempting to transition to the RRC connected state in the RRC idle state but not sending uplink data, or, transitioning from the RRC idle state to the RRC connected state but not sending uplink data.

[0171] In some embodiments, sending uplink data in the RRC connected state can be understood as: switching from the RRC idle state to the RRC connected state and sending uplink data, or, sending a first message in the RRC connected state and sending uplink data on the uplink resources requested by the first message, or, sending uplink data through an uplink channel according to the scheduling of the access network device.

[0172] In some embodiments, not sending the first message in the RRC connected state can be understood as: the first message should not be sent in the RRC connected state, or uplink resources should not be requested in the RRC connected state.

[0173] In some embodiments, the terminal may determine different first operations for different contents indicated by the first information.

[0174] In some embodiments, the first information indicates whether the store and forward function is enabled, and the terminal determines the first operation based on the first information.

[0175] In some embodiments, when the first information indicates that the store and forward function is turned on, the terminal may determine to send uplink data in the RRC idle state. In this case, the first operation is to send uplink data in the RRC idle state.

[0176] In some embodiments, when the first information indicates that the store and forward function is turned off, the terminal may determine to prohibit sending uplink data in the RRC idle state. In this case, the first operation is to send uplink data in the RRC idle state.

[0177] In some embodiments, when the first information indicates that the storage and forwarding function is turned off, the terminal may determine to remain in the RRC idle state. In this case, the first operation is to remain in the RRC idle state.

[0178] In some embodiments, when the first information indicates that the store and forward function is turned off, the terminal may determine to prohibit the transition from the RRC idle state to the RRC connected state. In this case, the first operation is to prohibit the transition from the RRC idle state to the RRC connected state.

[0179] In some embodiments, when the first information indicates that the store and forward function is turned off, the terminal may determine to prohibit sending uplink data in the RRC connection state. In this case, the first operation is to prohibit sending uplink data in the RRC connection state.

[0180] In some embodiments, when the first information indicates that the storage and forwarding function is turned off, the terminal can determine to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data. At this time, the first operation is to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data.

[0181] In some embodiments, when the first information indicates that the storage and forwarding function is turned off, the terminal may determine not to send the first message in the RRC connection state. At this time, the first operation is not to send the first message in the RRC connection state.

[0182] In some embodiments, the first information indicates whether the store and forward function is enabled and whether a feeder link exists, and the terminal determines the first operation according to the first information.

[0183] In some embodiments, when the first information indicates that the store and forward function is turned on and there is a feeder link, the terminal may determine to send uplink data in the RRC idle state. At this time, the first operation is to send uplink data in the RRC idle state.

[0184] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and there is a feeder link, the terminal can determine to transition from the RRC idle state to the RRC connected state and send uplink data. At this time, the first operation is to transition from the RRC idle state to the RRC connected state and send uplink data.

[0185] In some embodiments, when the first information indicates that the store and forward function is turned on and there is no feeder link, the terminal may determine to send uplink data in the RRC idle state. At this time, the first operation is to send uplink data in the RRC idle state.

[0186] In some embodiments, when the first information indicates that the store and forward function is enabled and there is no feeder link, the terminal may determine to remain in the RRC idle state. In this case, the first operation is to remain in the RRC idle state.

[0187] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and there is no feeder link, the terminal can determine to prohibit the transition from the RRC idle state to the RRC connected state. At this time, the first operation is to prohibit the transition from the RRC idle state to the RRC connected state.

[0188] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, the terminal can determine to prohibit sending uplink data in the RRC idle state. At this time, the first operation is to prohibit sending uplink data in the RRC idle state.

[0189] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, the terminal can determine to prohibit the transition from the RRC idle state to the RRC connected state. At this time, the first operation is to prohibit the transition from the RRC idle state to the RRC connected state.

[0190] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, the terminal may determine to prohibit sending uplink data in the RRC connection state. At this time, the first operation is to prohibit sending uplink data in the RRC connection state.

[0191] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, the terminal may determine to send uplink data in the RRC idle state. At this time, the first operation is to send uplink data in the RRC idle state.

[0192] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, the terminal can determine to transition from the RRC idle state to the RRC connected state and send uplink data. At this time, the first operation is to transition from the RRC idle state to the RRC connected state and send uplink data.

[0193] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and there is no feeder link, the terminal can determine not to send the first message in the RRC connection state. At this time, the first operation is not to send the first message in the RRC connection state.

[0194] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and there is a feeder link, the terminal may determine to send uplink data in the RRC connection state. In this case, the first operation is to send uplink data in the RRC connection state.

[0195] In some embodiments, the first information indicates whether the storage and forwarding function is enabled and whether a core network function is deployed on the satellite, and the terminal determines the first operation based on the first information.

[0196] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite, the terminal can determine to send uplink data in the RRC idle state. At this time, the first operation is to send uplink data in the RRC idle state.

[0197] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and the core network function is deployed on the satellite, the terminal can determine to transition from the RRC idle state to the RRC connected state and send uplink data. At this time, the first operation is to transition from the RRC idle state to the RRC connected state and send uplink data.

[0198] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and no core network function is deployed on the satellite, the terminal can determine to send uplink data in the RRC idle state. At this time, the first operation is to send uplink data in the RRC idle state.

[0199] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and no core network function is deployed on the satellite, the terminal can determine to remain in the RRC idle state. At this time, the first operation is to remain in the RRC idle state.

[0200] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite, the terminal can determine to prohibit the transition from the RRC idle state to the RRC connected state. At this time, the first operation is to prohibit the transition from the RRC idle state to the RRC connected state.

[0201] In some embodiments, when the first information indicates that the storage and forwarding function is turned on and the core network function is not deployed on the satellite, the terminal can determine to send uplink data in the RRC connection state. At this time, the first operation is to send uplink data in the RRC connection state.

[0202] In some embodiments, when the first information indicates that the storage and forwarding function is turned off and the core network function is deployed on the satellite, the terminal can determine to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data. At this time, the first operation is to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data.

[0203] In some embodiments, the first information indicates whether the storage and forwarding function is enabled, whether a feeder link exists, and whether a core network function is deployed on the satellite, and the terminal determines the first operation based on the first information.

[0204] In some embodiments, when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is deployed on the satellite, the terminal can determine to send uplink data in the RRC idle state. At this time, the first operation is to send uplink data in the RRC idle state.

[0205] In some embodiments, when the first information indicates that the storage and forwarding function is turned on, there is a feeder link and the core network function is deployed on the satellite, the terminal can determine to transition from the RRC idle state to the RRC connected state and send uplink data. At this time, the first operation is to transition from the RRC idle state to the RRC connected state and send uplink data.

[0206] In some embodiments, when the first information indicates that the storage and forwarding function is turned on, there is no feeder link and no core network function is deployed on the satellite, the terminal can determine to send uplink data in the RRC idle state. At this time, the first operation is to send uplink data in the RRC idle state.

[0207] In some embodiments, when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, the terminal can determine to remain in the RRC idle state. At this time, the first operation is to remain in the RRC idle state.

[0208] In some embodiments, when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, the terminal can determine that the transition from the RRC idle state to the RRC connected state is prohibited. At this time, the first operation is to prohibit the transition from the RRC idle state to the RRC connected state.

[0209] In some embodiments, when the first information indicates that the storage and forwarding function is turned on, there is no feeder link, and no core network function is deployed on the satellite, the terminal can determine to send uplink data in the RRC connection state. At this time, the first operation is to send uplink data in the RRC connection state.

[0210] In some embodiments, when the first information indicates that the storage and forwarding function is turned off, there is no feeder link and the core network function is deployed on the satellite, the terminal can determine to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data. At this time, the first operation is to transition from the RRC idle state to the RRC connected state but prohibit sending uplink data.

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

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

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

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

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

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

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

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

[0219] In some embodiments, terms such as “should,” “allow,” “expect,” “may,” “could,” and “attempt” may be used interchangeably.

[0220] In some embodiments, terms such as "should not", "prohibited", "not expected", "may not", "cannot" and the like can be used interchangeably.

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

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

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

[0224] As shown in Figure 4A, Figure 4A is a schematic diagram of an implementation flow of a communication method executed by a terminal side according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which is executed by a terminal. The above communication method includes steps S4101 to S4103.

[0225] In step S4101, the second information is sent.

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

[0227] In some embodiments, the terminal sends the second information to the access network device, but is not limited thereto, and the second information may also be sent to other entities.

[0228] In step S4102, first information is received.

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

[0230] In some embodiments, the terminal receives the first information sent by the access network device, but is not limited thereto, and may also receive the first information sent by other entities.

[0231] In step S4103, a first operation is determined according to the first information.

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

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

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

[0235] As shown in Figure 4B, Figure 4B is a schematic diagram of an implementation flow of a communication method performed by an access network device according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which is performed by an access network device. The above communication method includes steps S4201 to S4202.

[0236] In step S4201, second information is received.

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

[0238] In some embodiments, the access network device receives the second information sent by the terminal, but is not limited thereto and may also receive the second information sent by other entities.

[0239] In step S4202, the first information is sent.

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

[0241] In some embodiments, the access network device sends the first information to the terminal, but is not limited thereto, and the first information may also be sent to other entities.

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

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

[0244] As shown in Figure 5A, Figure 5A is a schematic diagram of an implementation flow of a communication method executed by a terminal side according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which is executed by a terminal. The above communication method includes steps S5101 to S5102.

[0245] In step S5101, first information is received.

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

[0247] In some embodiments, the terminal receives the first information sent by the access network device, but is not limited thereto, and may also receive the first information sent by other entities.

[0248] In step S5102, a first operation is determined according to the first information.

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

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

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

[0252] In step S5201, the first information is sent.

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

[0254] In some embodiments, the access network device sends the first information to the terminal, but is not limited thereto, and the first information may also be sent to other entities.

[0255] In some embodiments, the present disclosure provides a communication method. The method may include the following:

[0256] In some embodiments, the network (e.g., eNB or gNB) provides the following information:

[0257] The store and forward function is enabled;

[0258] The store and forward function is turned off;

[0259] Core network functions deployed on satellites;

[0260] There is a feeder link connection;

[0261] No feeder link connection;

[0262] Whether the UE is allowed to use the store and forward function;

[0263] Among them, the core network functions deployed on the satellite include: no core network functions deployed, partial core network functions (such as MME, AMF or partial MME / AMF functions) and all core network functions.

[0264] In some embodiments, the network indicates that the store and forward function is enabled, and the RRC idle UE can send uplink data in the following ways:

[0265] Control Plane CIoT EPS optimization;

[0266] User Plane CIoT EPS / 5GS optimizations;

[0267] MO-EDT for Control Plane CIoT EPS optimization;

[0268] MO-EDT for User Plane CIoT EPS optimization;

[0269] PUR for Control Plane CIoT EPS optimization;

[0270] PUR for User Plane CIoT EPS optimization.

[0271] In some embodiments, the network indicates that the storage and forwarding function is turned on, and the satellite is deployed with some or all core network functions and / or a feeder link connection. In addition to sending data in the above manner, the RRC idle UE can also send data after switching from the RRC idle state to the RRC connected state, that is, sending data through the PUSCH according to the scheduling of the eNB.

[0272] In some embodiments, the network indicates that the store and forward function is turned on, and the satellite is not deployed with core network functions and / or has no feeder link connection. In addition to sending data in the above manner, the RRC idle UE should not attempt to switch to the RRC connected state, or should not send data after switching to the RRC connected state.

[0273] In some embodiments, if the network indicates that the store and forward function is turned off, or the network indicates that the storage function is turned off and there is no feeder link connection, the RRC idle UE should not send uplink data using the above method, nor should it switch to the RRC connected state.

[0274] In some embodiments, the network indicates that the store and forward function is turned off, or the network indicates that the storage function is turned off and there is no feeder link connection, the RRC idle UE may attempt to transition to the RRC connected state, but should not send data.

[0275] In some embodiments, the network indicates that the storage function is turned off, or the network indicates that the storage function is turned off and there is no feeder link connection, and the satellite is deployed with some or all core network functions, the RRC idle UE can transition to the RRC connected state, but should not send data.

[0276] In some embodiments, the network indicates that the storage function is closed and indicates that there is a feederlink connection. The RRC idle UE can send data using any data sending method, such as the data sending method described above.

[0277] In some embodiments, if the network indicates that the storage function is turned off, or if the network indicates that the storage function is turned off and there is no feeder link connection, the RRC connected UE should not request an uplink scheduling grant, such as sending an SR message, for random access.

[0278] In some embodiments, the network indicates that the storage function is turned off and indicates that there is a feederlink connection. The RRC connected UE can obtain uplink scheduling authorization and send uplink data.

[0279] In some embodiments, the UE reports to the network whether the store and forward function is supported.

[0280] In some embodiments, the above method may include the method described in the above embodiments on the communication system side, terminal side and access network device side, which will not be repeated here.

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

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

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

[0284] As shown in Figure 6A, Figure 6A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. The structure of the terminal 61 can be as shown in Figure 6A. Terminal 61 includes: a first transceiver module 6101. In some embodiments, the first transceiver module 6101 is used to receive first information, and the first information is used to indicate at least one of the following: whether the store and forward function is enabled, whether there is a feeder link between the satellite and the ground station, and whether the core network function is deployed on the satellite. Optionally, the first transceiver module 6101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods (for example, step S310 and step S320, but not limited thereto), which are not further described here. In some embodiments, terminal 61 also includes a first processing module 6102. In some embodiments, the first processing module 6102 is used to determine a first operation based on the first information. Optionally, the first processing module 6102 is used to perform at least one of the other steps (for example, step 330, but not limited thereto) performed by the terminal in any of the above methods, which are not further described here.

[0285] As shown in Figure 6B, Figure 6B is a structural diagram of an access network device according to an embodiment of the present disclosure. The structure of the above-mentioned access network device 62 can be as shown in Figure 6B. The access network device 62 may include: a second transceiver module 6201. In some embodiments, the second transceiver module 6201 is used to send first information, and the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether the core network function is deployed on the satellite; the first information is also used for the terminal to determine the first operation. Optionally, the second transceiver module 6201 is used to perform at least one of the communication steps such as sending and / or receiving (for example, step S310, step S320, but not limited to this) performed by the access network device in any of the above methods, which will not be repeated here.

[0286] In some embodiments, the transceiver module may include a transceiver module 6102 and / or a transceiver module 6201. The transceiver module 6102 and the transceiver module 6201 may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0287] As shown in Figure 7A, Figure 7A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. Communication device 71 can be a terminal, an access network device, a chip, a chip system, or a processor that supports the terminal to implement any of the above methods, or a chip, a chip system, or a processor that supports the access network device to implement any of the above methods. Communication device 71 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0288] As shown in FIG7A , the communication device 71 includes one or more processors 711. Processor 711 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, while the central processing unit can be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute programs, and process program data.

[0289] In some embodiments, the communication device 71 further includes one or more transceivers 712. When the communication device 71 includes one or more transceivers 712, the transceiver 712 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S310, step S320, but not limited thereto). The processor 711 performs at least one of the other steps (for example, step 330, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc. may be interchangeable, terms such as transmitter, transmitting unit, transmitter, transmitting circuit, etc. may be interchangeable, and terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be interchangeable.

[0290] In some embodiments, the communication device 71 also includes one or more memories 713 for storing data. Alternatively, all or part of the memories 713 may be located outside the communication device 71. In alternative embodiments, the communication device 71 may include one or more interface circuits 714. Optionally, the interface circuits 714 are connected to the memories 713 and may be used to receive data from the memories 713 or other devices, or to send data to the memories 713 or other devices. For example, the interface circuits 714 may read data stored in the memories 713 and send the data to the processor 711.

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

[0292] As shown in Figure 7B, Figure 7B is a schematic diagram of a chip structure according to an embodiment of the present disclosure. If the communication device 71 can be a chip or a chip system, please refer to the schematic diagram of the chip structure 720 shown in Figure 7B, but it is not limited thereto.

[0293] In some embodiments, chip 720 may include one or more processors 721 .

[0294] In some embodiments, chip 720 may further include one or more interface circuits 722. Alternatively, terms such as interface circuit, interface, and transceiver pin may be used interchangeably. In some embodiments, chip 720 may further include one or more memories 723 for storing data. Alternatively, all or part of memories 723 may be located external to chip 720. Optionally, interface circuit 722 is connected to memory 723 and may be configured to receive data from memory 723 or other devices, or to send data to memory 723 or other devices. For example, interface circuit 722 may read data stored in memory 723 and send the data to processor 721.

[0295] In some embodiments, the interface circuit 722 performs at least one of the communication steps (e.g., step S310 and step S320, but not limited thereto) in the above method. The interface circuit 722 performing the communication steps (e.g., step S310 and step S320, but not limited thereto) in the above method, for example, means that the interface circuit 722 performs data exchange between the processor 721, chip 720, memory 723, or transceiver device. In some embodiments, the processor 721 performs at least one of the other steps (e.g., step 330, but not limited thereto).

[0296] The embodiment of the present disclosure further proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 71, the communication device 71 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

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

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

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

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

Claims

1. A communication method, performed by a terminal, comprising: receiving first information, where the first information is used to indicate at least one of the following: whether a store and forward function is enabled, whether a feeder link exists between the satellite and the ground station, and whether a core network function is deployed on the satellite; A first operation is determined according to the first information.

2. The method according to claim 1, wherein The first operation includes at least one of the following: Sending uplink data in the radio resource control RRC idle state; Transition from RRC idle state to RRC connected state and send uplink data; Remain in RRC idle state; Prohibit sending uplink data in RRC connected state; The transition from RRC idle state to RRC connected state is prohibited; Transition from RRC idle state to RRC connected state but prohibiting uplink data transmission; Not sending a first message in the RRC connected state, where the first message is used to request uplink resources, and the uplink resources are used to send uplink data; Send uplink data in RRC connected state.

3. The method according to claim 1 or 2, wherein: The determining of the first operation according to the first information includes one of the following: When the first information indicates that the store and forward function is enabled, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is disabled, determining to prohibit sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is disabled, determining to maintain the RRC idle state; When the first information indicates that the store and forward function is disabled, determining to prohibit transitioning from the RRC idle state to the RRC connected state; When the first information indicates that the store and forward function is disabled, determining to prohibit sending uplink data in the RRC connected state; When the first information indicates that the store and forward function is disabled, determining to transition from the RRC idle state to the RRC connected state but prohibiting uplink data transmission; When the first information indicates that the storage and forwarding function is turned off, it is determined not to send a first message in the RRC connection state, where the first message is used to request uplink resources, and the uplink resources are used to send uplink data.

4. The method according to claim 1 or 2, wherein: The determining of the first operation according to the first information includes one of the following: When the first information indicates that the store and forward function is enabled and the feeder link exists, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled and the feeder link exists, determining to switch from the RRC idle state to the RRC connected state and sending uplink data; When the first information indicates that the store and forward function is enabled and the feeder link does not exist, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled and the feeder link does not exist, determining to maintain the RRC idle state; When the first information indicates that the store and forward function is enabled and the feeder link does not exist, it is determined that transition from the RRC idle state to the RRC connected state is prohibited.

5. The method according to claim 1 or 2, wherein: The determining of the first operation according to the first information includes one of the following: When the first information indicates that the store and forward function is turned off and the feeder link does not exist, determining to prohibit sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is disabled and the feeder link does not exist, determining to prohibit transitioning from the RRC idle state to the RRC connected state; When the first information indicates that the store and forward function is turned off and the feeder link does not exist, determining to prohibit sending uplink data in the RRC connected state; When the first information indicates that the store and forward function is turned off and the feeder link exists, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is turned off and the feeder link exists, determining to transition from the RRC idle state to the RRC connected state and sending uplink data; When the first information indicates that the store and forward function is disabled and the feeder link does not exist, determining not to send a first message in the RRC connected state, where the first message is used to request uplink resources, and the uplink resources are used to send uplink data; When the first information indicates that the store and forward function is turned off and the feeder link exists, it is determined to send uplink data in the RRC connected state.

6. The method according to claim 1 or 2, wherein: The determining of the first operation according to the first information includes one of the following: When the first information indicates that the store and forward function is enabled and a core network function is deployed on the satellite, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled and a core network function is deployed on the satellite, determining to transition from the RRC idle state to the RRC connected state and sending uplink data; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, determining to maintain the RRC idle state; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, determining that transitioning from the RRC idle state to the RRC connected state is prohibited; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, determining to send uplink data in an RRC connected state; When the first information indicates that the storage and forwarding function is turned off and the core network function is deployed on the satellite, it is determined to switch from the RRC idle state to the RRC connected state but prohibit sending uplink data.

7. The method according to claim 1 or 2, wherein: The determining of the first operation according to the first information includes one of the following: When the first information indicates that the store and forward function is enabled, the feeder link exists, and a core network function is deployed on the satellite, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled, the feeder link exists, and a core network function is deployed on the satellite, determining to transition from the RRC idle state to the RRC connected state and sending uplink data; When the first information indicates that the store and forward function is enabled, the feeder link does not exist, and no core network function is deployed on the satellite, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled, the feeder link does not exist, and no core network function is deployed on the satellite, determining to maintain the RRC idle state; When the first information indicates that the store and forward function is enabled, the feeder link does not exist, and no core network function is deployed on the satellite, determining that transitioning from the RRC idle state to the RRC connected state is prohibited; When the first information indicates that the store and forward function is enabled, the feeder link does not exist, and no core network function is deployed on the satellite, determining to send uplink data in the RRC connected state; When the first information indicates that the storage and forwarding function is turned off, the feeder link does not exist, and the core network function is deployed on the satellite, it is determined to switch from the RRC idle state to the RRC connected state but prohibit sending uplink data.

8. The method according to any one of claims 1 to 7, wherein: Before receiving the first information, the method further includes: Second information is sent, where the second information is used to indicate whether the terminal supports a store and forward function.

9. A communication method, performed by an access network device, comprising: Sending first information, wherein the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; the first information is also used by the terminal to determine the first operation.

10. The method according to claim 9, wherein: The first operation includes at least one of the following: Sending uplink data in the radio resource control RRC idle state; Transition from RRC idle state to RRC connected state and send uplink data; Remain in RRC idle state; Prohibit sending uplink data in RRC connected state; The transition from RRC idle state to RRC connected state is prohibited; Transition from RRC idle state to RRC connected state but prohibiting uplink data transmission; Not sending a first message in the RRC connected state, where the first message is used to request uplink resources, and the uplink resources are used to send uplink data; Send uplink data in RRC connected state.

11. The method according to claim 9 or 10, wherein: The first operation includes at least one of the following: When the first information indicates that the store and forward function is enabled, sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is disabled, prohibiting uplink data from being sent in the RRC idle state; When the first information indicates that the store and forward function is disabled, maintaining the RRC idle state; When the first information indicates that the store and forward function is disabled, prohibiting transition from the RRC idle state to the RRC connected state; When the first information indicates that the store and forward function is disabled, prohibiting uplink data from being sent in the RRC connected state; When the first information indicates that the store and forward function is disabled, the RRC idle state is switched to the RRC connected state but uplink data transmission is prohibited; In a case where the first information indicates that the store and forward function is turned off, the first message is not sent in the RRC connected state, the first message is used to request uplink resources, and the uplink resources are used to send uplink data.

12. The method according to claim 9 or 10, wherein: The first operation includes at least one of the following: When the first information indicates that the store and forward function is enabled and the feeder link exists, sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled and the feeder link exists, switching from the RRC idle state to the RRC connected state and sending uplink data; When the first information indicates that the store and forward function is enabled and the feeder link does not exist, sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled and the feeder link does not exist, maintaining the RRC idle state; If the first information indicates that the store and forward function is enabled and the feeder link does not exist, prohibiting transition from the RRC idle state to the RRC connected state; When the first information indicates that the store and forward function is enabled and the feeder link does not exist, sending uplink data in the RRC connected state is prohibited.

13. The method according to claim 9 or 10, wherein: The first operation includes at least one of the following: When the first information indicates that the store and forward function is turned off and the feeder link does not exist, prohibiting the sending of uplink data in the RRC idle state; If the first information indicates that the store and forward function is disabled and the feeder link does not exist, prohibiting transition from the RRC idle state to the RRC connected state; When the first information indicates that the store and forward function is turned off and the feeder link does not exist, determining to prohibit sending uplink data in the RRC connected state; When the first information indicates that the store and forward function is turned off and the feeder link exists, sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is disabled and the feeder link exists, switching from the RRC idle state to the RRC connected state and sending uplink data; When the first information indicates that the store and forward function is disabled and the feeder link does not exist, the first message is not sent in the RRC connected state, where the first message is used to request uplink resources, and the uplink resources are used to send uplink data; When the first information indicates that the storage and forwarding function is turned off and the feeder link exists, uplink data is sent in the RRC connected state.

14. The method according to claim 9 or 10, wherein: The first operation includes at least one of the following: When the first information indicates that the store and forward function is enabled and a core network function is deployed on the satellite, uplink data is sent in the RRC idle state; When the first information indicates that the store and forward function is enabled and a core network function is deployed on the satellite, the RRC idle state is switched to the RRC connected state and uplink data is sent; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, maintaining the RRC idle state; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, prohibiting transition from the RRC idle state to the RRC connected state; When the first information indicates that the store and forward function is enabled and no core network function is deployed on the satellite, transmitting uplink data in the RRC connected state is prohibited; When the first information indicates that the storage and forwarding function is turned off and the core network function is deployed on the satellite, the RRC idle state is converted to the RRC connected state but the sending of uplink data is prohibited.

15. The method according to claim 9 or 10, wherein: The first operation includes at least one of the following: When the first information indicates that the store and forward function is enabled, the feeder link exists, and a core network function is deployed on the satellite, sending uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled, the feeder link exists, and a core network function is deployed on the satellite, the RRC idle state is switched to the RRC connected state and uplink data is sent; When the first information indicates that the store and forward function is enabled, the feeder link does not exist, and no core network function is deployed on the satellite, determining to send uplink data in the RRC idle state; When the first information indicates that the store and forward function is enabled, the feeder link does not exist, and no core network function is deployed on the satellite, maintaining the RRC idle state; If the first information indicates that the store and forward function is enabled, the feeder link does not exist, and no core network function is deployed on the satellite, prohibiting transition from the RRC idle state to the RRC connected state; In the case where the first information indicates that the storage and forwarding function is enabled, the feeder link does not exist, and the core network function is not deployed on the satellite In this case, it is prohibited to send uplink data in the RRC connected state; When the first information indicates that the storage and forwarding function is turned off, the feeder link does not exist, and the core network function is deployed on the satellite, the RRC idle state is converted to the RRC connected state but the sending of uplink data is prohibited.

16. The method according to claim 9 or 10, wherein: The first operation includes at least one of the following: Second information is received, where the second information is used to indicate whether the terminal supports a store and forward function, and the second information is used to determine the first information.

17. A terminal comprising: A first transceiver module is configured to receive first information, where the first information is configured to indicate at least one of the following: whether a store and forward function is enabled, whether a feeder link exists between the satellite and the ground station, and whether a core network function is deployed on the satellite; The first processing module is configured to determine a first operation according to the first information.

18. An access network device, comprising: The second transceiver module is used to send first information, where the first information is used to indicate at least one of the following: whether the storage and forwarding function is turned on, whether there is a feeder link between the satellite and the ground station, and whether a core network function is deployed on the satellite; the first information is also used by the terminal to determine the first operation.

19. A communication device comprising: one or more processors; one or more memories for storing instructions; The processor is configured to call the instruction so that the access network device executes the method according to any one of claims 1 to 16.

20. A communication system comprising: A terminal configured to implement the communication method according to any one of claims 1 to 8; Access network equipment, configured to implement the communication method according to any one of claims 9 to 16.

21. A computer-readable storage medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the steps of the communication method according to any one of claims 1 to 16 are implemented.

22. A computer program product comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the steps of the communication method according to any one of claims 1 to 16.

Images