Method and apparatus for wireless communication

Abstract

A method and apparatus of wireless communication are provided. The method includes determining, by a first device, first information, the first information being associated with transmission of second information, the second information including signaling and / or data stored and / or forwarded through a satellite.

Description

Wireless communication method and device Technical Field

[0001] The present application relates to the field of communication technology, and more particularly, to a method and device for wireless communication. Background Art

[0002] In the store-and-forward mode of a satellite, the connection between the satellite and the terminal device, known as the service link, and the connection between the satellite and the ground station, known as the feeder link, cannot be available simultaneously. Therefore, both uplink signaling and / or data and downlink signaling and / or data must be stored on the satellite for a period of time in store-and-forward mode. However, the storage space on the satellite is limited, and transmission resources may also be limited.

[0003] Summary of the Invention

[0004] The present application provides a method and device for wireless communication. The following introduces various aspects of the present application.

[0005] In a first aspect, a wireless communication method is provided, comprising: a first device determining first information, wherein the first information is associated with the transmission of second information, and the second information includes signaling and / or data stored and / or forwarded via a satellite.

[0006] In a second aspect, a wireless communication method is provided, comprising: a second device sending first information to a first device, wherein the first information is associated with the transmission of second information, and the second information includes signaling and / or data stored and / or forwarded via a satellite.

[0007] According to a third aspect, a communication device is provided, which is a first device, and includes: a determination unit for determining first information, wherein the first information is associated with the transmission of second information, and the second information includes signaling and / or data stored and / or forwarded via a satellite.

[0008] In a fourth aspect, a communication device is provided, which is a second device, and the device includes: a first sending unit, used to send first information to the first device, the first information is associated with the transmission of second information, and the second information includes signaling and / or data stored and / or forwarded via a satellite.

[0009] In a fifth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the device executes part or all of the steps in the method of the first aspect or the second aspect.

[0010] In a sixth aspect, a communication device is provided, comprising a processor for calling a program from a memory so that the device executes part or all of the steps in the method of the first aspect or the second aspect.

[0011] In a seventh aspect, a chip is provided, comprising a processor for calling a program from a memory so that the chip executes part or all of the steps in the method of the first aspect or the second aspect.

[0012] In an eighth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a communication device to execute part or all of the steps in the method of the first aspect or the second aspect.

[0013] In a ninth aspect, a computer program product is provided, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device to perform some or all of the steps of the methods of the various aspects described above. In some implementations, the computer program product may be a software installation package.

[0014] In a tenth aspect, a computer program is provided, which enables a communication device to execute part or all of the steps in the method of the first aspect or the second aspect.

[0015] The embodiments of the present application introduce first information to determine the transmission of signaling and / or data (i.e., second information) stored and / or forwarded through the satellite, or manage the transmission process of the second information, thereby helping to improve system performance, such as improving the storage space utilization of the satellite. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1A is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0017] FIG1B is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0018] FIG1C is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0019] FIG2 is a schematic diagram of the communication process when the satellite operates in the normal mode.

[0020] FIG3 is a schematic diagram of the communication process when the satellite operates in the store-and-forward mode.

[0021] FIG4 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0022] FIG5 is a schematic diagram of a process for configuring first information by a functional entity on a satellite according to an embodiment of the present application.

[0023] FIG6 is a flow chart of configuring the first information based on the signing message in an embodiment of the present application.

[0024] FIG7 is a schematic diagram of a process for configuring first information of a ground-deployed network element in an embodiment of the present application.

[0025] FIG8 is a flow chart of data storage and / or forwarding and flow control under CIoT UP optimization according to an embodiment of the present application.

[0026] FIG9 is a flow chart of data storage and / or forwarding and flow control under CIoT CP optimization according to an embodiment of the present application.

[0027] FIG10 is a flow chart of data storage and / or forwarding and flow control under another CIoT CP optimization according to an embodiment of the present application.

[0028] FIG11 is a schematic structural diagram of a communication device according to an embodiment of the present application.

[0029] FIG12 is a schematic structural diagram of another communication device according to an embodiment of the present application.

[0030] FIG13 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0031] The technical solutions in this application will be described below with reference to the accompanying drawings. For ease of understanding, the following first introduces a schematic diagram of the communication system architecture of an embodiment of this application with reference to Figure 1. Figure 1A is a schematic diagram of a communication system architecture provided in an embodiment of this application. The network architecture may include terminal devices, access network (AN) network elements, and core network network elements.

[0032] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0033] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless core network element, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a dispatching entity that provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0034] An access network element can be an access network device. This device is used by terminals to wirelessly access the network architecture and is primarily responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. An access network device can also be referred to as a radio access network (RAN) device. For example, an access network device can be a base station. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the access network device.

[0035] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0036] In some deployments, the access network device in the embodiments of the present application may refer to a CU or a DU, or the access network device may include a CU and a DU. The gNB may also include an AAU.

[0037] The types of core network elements may include user plane function (UPF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF), data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management function (UDM), network exposure function (NEF), network repository function (NRF), and network slice-specific authentication and authorization function (NSSAAF). Among them, the UPF network element is mainly responsible for the transmission of user data, and the other network elements can be called control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control, etc., to ensure the reliable and stable transmission of user data.

[0038] The UPF network element can be used to forward and receive data from the terminal. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward it to the data network. Among them, the transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element may include: the user plane connection between the UPF network element and the access network device, and the establishment of a channel between the access network device and the terminal. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.

[0039] The AMF network element can be used to manage the terminal's access to the core network, such as terminal location update, network registration, access control, terminal mobility management, terminal attachment and detachment, etc. The AMF network element can also provide control plane storage resources for the session while providing services for the terminal's session, to store the session identifier, the SMF network element identifier associated with the session identifier, etc.

[0040] The SMF network element can be used to select a user plane network element for the terminal, redirect the user plane network element for the terminal, allocate an Internet Protocol (IP) address to the terminal, establish a bearer (also called a session) between the terminal and the UPF network element, modify and release the session, and control QoS.

[0041] The PCF network element is used to provide policies to the AMF network element and the SMF network element, such as QoS policy and slice selection policy.

[0042] The AF network element is used to interact with the 3GPP core network elements to support application-affected data routing, access network exposure functions, and interact with the PCF network elements for policy control.

[0043] A DN can provide data services to users on networks such as the Internet Protocol Multimedia Service (IMS) and the Internet. A DN can contain multiple application servers (ASs) that provide different application services, such as carrier services, Internet access, or third-party services. The ASs can implement the AF functionality.

[0044] NSSF is used for network slice selection and supports the following functions: selecting a set of network slice implementation schemes to serve terminal devices; determining the allowed network slice selection assistance information (NSSAI) and, when necessary, determining the mapping to the contracted single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI and, when necessary, determining the mapping to the contracted S-NSSAI; determining the set of AMFs that may be used to query terminal devices, or determining a list of candidate AMFs based on the configuration.

[0045] AUSF is used to receive the request from AMF to authenticate the terminal, request the key from UDM, and then forward the issued key to AMF for authentication processing.

[0046] UDM includes functions such as the generation and storage of user contract data, management of authentication data, and supports interaction with external third-party servers.

[0047] NEF is used for capability exposure. That is, based on NEF, network capabilities can be exported to external networks. External, untrusted applications can access core network data through NEF to ensure network security. NEF can also provide external application QoS capability exposure, event subscription, and AF request distribution.

[0048] The NRF is used to register, manage, and monitor the status of core network elements, enabling automated management of these elements. Upon startup, a core network element must register with the NRF before it can provide services. Registration information may include the core network element's type, address, and service list.

[0049] In addition, some networks (such as 5G networks) have added a network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various core network elements and network management systems, and big data statistics, analysis, or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control terminal device access based on the data analysis results.

[0050] In some communication systems (such as 5G systems), core network elements may also be referred to as network functions (NFs).

[0051] Each network element in FIG1A can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function implemented on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figure is only an example of the network elements included in the entire network architecture. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0052] Those skilled in the art will appreciate that the network architecture shown in FIG1A does not limit the network architecture. In a specific implementation, the network architecture may include more or fewer network elements than shown, or may combine certain network elements. It should be understood that in FIG1A , the AN or RAN is represented by (R)AN.

[0053] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which network devices and terminal devices are located.

[0054] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of the present application, the network device may also be a base station set up in a location such as land or water.

[0055] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0056] For example, FIG1B is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG1B , a terminal device 1101 and a satellite 1102 are included, and wireless communication can be performed between the terminal device 1101 and the satellite 1102. The network formed between the terminal device 1101 and the satellite 1102 can also be referred to as an NTN. In the architecture of the communication system shown in FIG1B , the satellite 1102 can have the function of a base station, and the terminal device 1101 and the satellite 1102 can communicate directly. In the system architecture, the satellite 1102 can be referred to as a network device. In some embodiments of the present application, a plurality of network devices 1102 may be included in the communication system, and each network device 1102 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0057] For example, FIG1C is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG1C , it includes a terminal device 1201, a satellite 1202, and a base station 1203. Wireless communication can be performed between the terminal device 1201 and the satellite 1202, and communication can be performed between the satellite 1202 and the base station 1203. The network formed between the terminal device 1201, the satellite 1202, and the base station 1203 can also be referred to as an NTN. In the architecture of the communication system shown in FIG1C , the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be transferred through the satellite 1202. In this system architecture, the base station 1203 can be referred to as a network device. In some embodiments of the present application, a plurality of network devices 1203 may be included in the communication system, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0058] It should be noted that Figures 1A-1C are only examples of the system to which this application is applicable. Of course, the method shown in the embodiment of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc., and the embodiment of this application does not make specific limitations on this.

[0059] In some embodiments of the present application, the wireless communication system shown in Figures 1A-1C may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but the embodiments of the present application are not limited to this.

[0060] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1A as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0061] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0062] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0063] The “configuration” in the embodiment of the present application may include configuration through at least one of system messages, radio resource control (RRC) signaling and media access control element (MAC CE).

[0064] In some embodiments of the present application, "predefined" or "preset" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device or a network device). This application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

[0065] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0066] For ease of understanding, some relevant technical knowledge involved in the embodiments of this application is first introduced. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.

[0067] Non-terrestrial network (NTN)

[0068] The Third Generation Partnership Project (3GPP) is currently researching NTN technology. NTN typically uses satellite communications to provide communication services to terrestrial users. Compared to terrestrial cellular networks, satellite communications offer many unique advantages.

[0069] First, satellite communications are not restricted by user geography. For example, conventional terrestrial communication networks cannot cover areas where network equipment cannot be deployed, such as oceans, mountains, and deserts. Similarly, terrestrial communication networks do not cover certain sparsely populated areas. However, because satellite communications can cover a large ground area and orbit the Earth, theoretically, every corner of the Earth can be covered by a satellite communication network.

[0070] Secondly, satellite communications have significant social value. They can provide low-cost coverage to remote, mountainous areas and impoverished countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies. From this perspective, satellite communications help narrow the digital divide with developed regions and promote their development.

[0071] Again, satellite communication has the advantage of long distance, and the increase in communication distance does not significantly increase the cost of communication.

[0072] Finally, satellite communications are highly stable and not affected by natural disasters.

[0073] Communication satellites are classified according to their orbital altitude into low Earth orbit (LEO), medium Earth orbit (MEO), geostationary Earth orbit (GEO), and high elliptical orbit (HEO). Currently, research focuses on LEO and GEO satellites.

[0074] LEO satellites typically operate at altitudes between 500 and 1500 km. Accordingly, their orbital period is approximately 1.5 to 2 hours. For LEO satellites, the signal propagation delay for single-hop communication between users is typically less than 20 milliseconds. The maximum satellite visibility time for LEO satellites is approximately 20 minutes. LEO satellites offer advantages such as short signal propagation distances, low link loss, and low transmit power requirements for user devices.

[0075] GEO satellites orbit at an altitude of 35,786 km. They orbit the Earth every 24 hours. For GEO satellites, the signal propagation delay for single-hop communication between users is typically about 250 milliseconds.

[0076] To ensure satellite coverage and increase the capacity of the entire satellite communication system, satellites typically use multiple beams to cover the ground. Therefore, a single satellite can form dozens or even hundreds of beams to cover the ground. A single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0077] Currently, the NTN system includes the NR-NTN system and the Internet of Things (IoT)-NTN system.

[0078] Satellite network architecture

[0079] Currently, 3GPP is considering two types of satellites: transparent payload satellites and store-and-forward (S&F) satellites. The following describes the network architecture of a store-and-forward satellite, using Figures 2 and 3.

[0080] In some scenarios, the store-and-forward model refers to the situation where the service link (service link) used by satellites to serve users and the feeder link (feeder link) between the satellite and the ground gateway in the NTN network are not available at the same time. Therefore, the satellite needs to store the transmitted data when one link is connected and forward it when the other link is connected. This can reduce the cost of ground gateway deployment and increase deployment flexibility, that is, the ground gateway does not need to be deployed in areas close to users. This store-and-forward model is suitable for services that are not sensitive to latency requirements, or in other words, this store-and-forward model is suitable for services that do not have strict latency requirements.

[0081] For ease of understanding, the following describes the communication process of the satellite operating in normal mode and store-and-forward mode in conjunction with FIG2 and FIG3 , respectively.

[0082] As shown in Figure 2, when the satellite operates in normal mode, when the terminal device exchanges signaling or data with the ground receiving station through the satellite, the service link and the feeder link are required to be available at the same time, so the end-to-end connection between the terminal device and the ground receiving station through the satellite is continuous.

[0083] As shown in FIG3 , the satellite operates in a store-and-forward mode, the service link and the feeder link cannot be available at the same time, and the signaling / data interaction between the terminal device and the ground receiving station via the satellite may include steps 1 and 2.

[0084] In step 1, signaling and data are exchanged between the terminal device and the satellite via a service link. At this point, there is no feeder link between the satellite and the ground receiving station, and the satellite stores the data to be transmitted. As the satellite moves away from the terminal device, the service link is disconnected.

[0085] In step 2, when the satellite flies over the ground receiving station, the satellite establishes a connection with the ground receiving station. In this way, the satellite and the ground receiving station can communicate through the feeder link. At this time, the satellite can send the stored data to be transmitted to the ground receiving station through the feeder link.

[0086] It should be noted that the above description, in conjunction with steps 1 and 2, describes the process of transmitting the data to be transmitted from the terminal device to the ground receiving station via satellite. Correspondingly, the process of transmitting the data to be transmitted from the ground receiving station to the terminal device via satellite is similar and will not be repeated for the sake of brevity.

[0087] 5GS optimization for Cellular IoT (CIoT)

[0088] Cellular IoT, also known as machine-type communication (MTC) in earlier 3GPP releases, is currently supported only on Evolved Universal Terrestrial Radio Access (E-UTRA) for control plane optimization and user plane optimization. These CIoT 5GS optimizations are not supported on non-3GPP radio access technology (RAT) types.

[0089] When a network is configured to support CIoT, CIoT functionality is provided by both the visited and home networks. Cellular IoT functionality applies to both non-roaming and roaming scenarios, and the availability of certain features depends on the existence of appropriate roaming agreements between operators.

[0090] Some CIoT functions are controlled by subscription data, while other CIoT functions are controlled by instructions sent by the UE to the network.

[0091] Unless explicitly stated, the functions added to the 3GPP standard protocols to support CIoT are generally applicable and are not limited to any specific scenario, use case or UE type.

[0092] A UE includes a 5G preferred network behavior in the registration request message to indicate the behaviors that the UE can support and the network behaviors that the UE prefers to use. 5G mobility management, that is, the 5GMM capability field includes the following 5G Preferred Network Behavior:

[0093] Support for control plane CIoT 5GS optimisation

[0094] Support for user plane CIoT 5GS optimisation

[0095] ●Whether N3 data transmission is supported;

[0096] ●Whether header compression for control plane cellular IoT 5GS optimization is supported.

[0097] The following 5G Preferred Network Behaviours can be included in the Other fields:

[0098] ●Preference for control-plane cellular IoT 5GS optimization or user-plane cellular IoT 5GS optimization.

[0099] If the UE indicates support for N3 data transmission, the UE supports data transmission not limited to CIoT 5GS optimization. If the UE indicates support for user plane CIoT 5GS optimization, then it should also indicate support for N3 data transmission.

[0100] The AMF may indicate the network behavior preferred by the network among the network behaviors supported by 5G, such as one or more of the following:

[0101] ●Whether control plane CIoT 5GS optimization is supported.

[0102] ●Whether user-side CIoT 5GS optimization is supported.

[0103] ●Whether N3 data transmission is supported.

[0104] ●Whether to support header compression optimized by control plane CIoT 5GS.

[0105] It should be noted that the indication may be for each registration area.

[0106] If the AMF indicates support for user plane CIoT 5GS optimization, it shall also indicate support for N3 data transmission. If the UE and AMF indicate support for user plane CIoT 5GS optimization, the AMF indicates to the RAN that user plane CIoT 5GS optimization for the UE is supported.

[0107] For narrowband Internet of Things (NB-IoT) UEs that only support control plane CIoT 5GS optimization, the AMF shall include support for control plane CIoT 5GS optimization in the registration accept message. UEs supporting NB-IoT shall always indicate support for control plane CIoT 5GS optimization. UEs supporting WB (wide band)-E-UTRA shall always indicate support for N3 data transmission.

[0108] The 5G Preferred Network Behaviour indication from the UE can be used to influence policy decisions, resulting in the rerouting of Registration Requests from one AMF to another.

[0109] The following introduces the CIoT 5GS optimization of the control plane and the CIoT 5GS optimization of the user plane respectively.

[0110] Control Plane CIoT 5GS Optimization

[0111] The control plane CIoT 5GS is optimized for exchanging user data between the UE and SMF via non-access stratum (NAS) messages in the uplink and downlink directions without establishing a user plane connection for the protocol data unit (PDU) session. The UE and AMF perform integrity protection and encryption on user data through the NAS PDU integrity protection and encryption functions. For Internet protocol (IP) and Ethernet data, the UE and SMF can negotiate and perform header compression.

[0112] In the context of control plane CIoT 5GS optimization, established or activated user plane resources / connections refer to wireless user plane resources / connections, namely data radio bearers and N3 tunnels.

[0113] UE and AMF negotiate to support and use control plane CIoT 5GS optimization. When the control plane CIoT 5GS optimization function is used and the PDU session type is unstructured, SMF selects NEF or UPF based on the UE subscription message.

[0114] If the UE and the network have negotiated support and use of control plane CIoT 5GS optimization, then during the PDU session establishment process, the AMF indicates to the SMF that control plane CIoT 5GS optimization can be used for data transmission. The AMF can also determine whether a new PDU session should only use control plane CIoT 5GS optimization (i.e., a user plane connection will never be established for a new PDU session) based on the preferred and supported network behavior, subscription data, other established PDU sessions and local policies. If the PDU session should only use control plane CIoT 5GS optimization, the AMF provides the SMF with a control plane only indicator during the PDU session establishment. For example, the SMF can provide the UE with a control plane only indication in a session management request. The UE and SMF that receive this indication should always apply control plane CIoT 5GS optimization for this PDU session.

[0115] The following rules apply when the control plane only indicator is used during PDU session establishment:

[0116] If N3 data forwarding is not successfully negotiated, all PDU sessions should carry the control plane only indicator.

[0117] If N3 data forwarding is not successfully negotiated, then

[0118] - For a new PDU session pointing to a DNN / S-NSSAI, the subscription message for SMF selection contains the invoke NEF indication, i.e. for a PDU session anchored at NEF, the AMF must always carry the control plane only indicator;

[0119] - For a new PDU session pointing to a DNN / S-NSSAI, the subscription message used for SMF selection does not contain the invoke NEF indication (i.e. for a PDU session not anchored at the UPF), and interworking with the evolved packet system (EPS) based on the subscription message is supported:

[0120] For the first PDU session, the AMF determines whether to include the control plane only indicator based on local policy.

[0121] If the AMF included the control plane only indicator in the previous PDU session anchored to the UPF for interworking with EPS, the AMF shall also include the control plane only indicator in the new PDU session;

[0122] If the AMF did not include the control plane only indicator in the previous PDU session anchored to the UPF for interworking with EPS, the AMF shall also not include the control plane only indicator in the new PDU session;

[0123] - For a new PDU Session pointing to a DNN / S-NSSAI where the subscription message for SMF selection does not contain the invoke NEF indication and interoperability with EPS is not supported based on the subscription message, the AMF determines individually for each PDU Session whether the control plane only indicator is included.

[0124] If, in addition to the control plane CIoT 5GS optimization, the UE and the AMF successfully negotiate N3 data transport, the UE or SMF may request the establishment of N3 data transport for one or more PDU sessions for which the control plane only indicator is not received. In the connection management (CM)-connected state (i.e., CM-CONNECTED), the UE and the network use N3 delivery for PDU sessions with established user plane resources and use NAS for data transport for PDU sessions without established user plane resources.

[0125] If the AMF determines that the Control Plane Only Indicator associated with a PDU Session is no longer applicable, for example due to changes in preferred and supported network behaviour, subscription data and local policy, the AMF shall request the SMF to release the PDU Session.

[0126] When the RAT type is E-UTRA, early data transmission can be initiated by the UE for mobile-initiated control plane CIoT 5GS optimization.

[0127] User-side CIoT 5GS optimization

[0128] The user plane CIoT 5GS optimization supports the transmission of user plane data from CM-IDLE without initiating a service request process to establish an access stratum (AS) context in NG-RAN and UE.

[0129] The RRC connection can be suspended using the connection suspend procedure if the following conditions are met:

[0130] -UE and AMF negotiate user plane CIoT 5GS optimization through NAS;

[0131] -The UE has indicated support for user plane CIoT 5GS optimization in the UE radio capabilities;

[0132] -AMF has indicated to RAN that it supports CIoT 5GS optimization of the user plane for the UE;

[0133] - The UE has established at least one PDU Session with an active UP connection, i.e. an AS context is established in the NG-RAN and the UE.

[0134] When the UE is in CM-IDLE with suspend, based on a trigger from the NAS layer, the UE shall attempt to resume the connection in the CM-IDLE with suspend procedure. If the connection recovery and suspend procedures in CM-IDLE fail, the UE shall initiate the NAS procedure with suspend. In order to maintain support for user plane CIoT 5GS optimization to achieve UE mobility between different NG-RAN nodes, the AS context shall be transferred between NG-RAN nodes.

[0135] For MT data or signaling when the UE is in the suspended CM-IDLE state, the network triggered service request procedure can be applied to establish a connection.

[0136] By using the connection suspension procedure: the UE stores the AS information when transitioning to CM-IDLE; the NG-RAN stores the AS information, the next generation access protocol (NGAP) UE association and the PDU session context of the UE; the AMF stores the NGAP UE association and other information required to resume the UE later, interacts with the SMF to deactivate the user plane resources of the UE PDU session and enter CM-IDLE.

[0137] The NG-RAN may decide to delete the stored UE context and NGAP association based on implementation. In this case, the RAN shall initiate the AN release procedure and the NG-RAN shall not initiate any RRC procedure to inform the UE: UE context release.

[0138] By using the connection resumption and suspension procedures in CM-IDLE: the UE resumes its connection to the network from CM-IDLE using the AS information stored during the connection suspension procedure; the NG-RAN notifies the AMF that the connection with the UE has been resumed; the AMF enters CM-CONNECTED and interacts with the SMF to activate user plane resources for the UE's PDU session; the UE can initiate early data transmission during connection resumption to achieve mobile-initiated user plane CIoT 5GS optimization.

[0139] If the AMF establishes an NGAP UE association with a new NG-RAN node that is different from the stored NGAP UE association, e.g. the UE initiates a service request or registration procedure from a different NG-RAN node, the AMF initiates a UE N2 Release Command to the old NG-RAN node.

[0140] When the UE is in the suspended CM-IDLE state, the NG-RAN maintains the N3 tunnel endpoint information. During the connection suspension procedure, the UPF is instructed to delete the AN's DL N3 tunnel information, while the UPF retains the UL N3 tunnel information (i.e., the UPF receives and forwards UL data). If the UE sends (mobile originated, MO) data through the resumption procedure, the NG-RAN can send the MO data to the UPF addressed by the N3 tunnel endpoint information. In the event that the serving NG-RAN node changes due to UE mobility, if the NG-RAN determines that it cannot connect to the UPF addressed by the N3 tunnel endpoint information, the NG-RAN performs a path switching procedure before sending the MO data received from the UE.

[0141] When the RAT type is E-UTRA, early data transmission can be initiated by the UE for mobile-initiated user plane CIoT 5GS optimization.

[0142] Rate control of user data

[0143] The rate of user data sent to and from a UE (e.g., a UE optimized for CIoT 5GS) can be controlled in two different ways: serving public land mobile network (PLMN) rate control and small data rate control.

[0144] Serving PLMN rate control is intended to allow the serving PLMN to protect its signalling radio bearers in the AMF and NG-RAN from the load generated by NAS packets. Small data rate control is intended to allow the home PLMN (HPLMN) operator to offer customer services such as "maximum Y messages per day".

[0145] The SMF in the serving PLMN may send small data rate control parameters for emergency PDU sessions.

[0146] The Serving PLMN rate control value may be configured in the (V-)SMF. At PDU Session Establishment and PDU Session Modification, the (V-)SMF may inform the UE and UPF / NEF of any PDU Session-granular local Serving PLMN rate control that the Serving PLMN intends to perform for NAS packets. The (V-)SMF shall indicate the Serving PLMN rate control command to the UPF only if the PDU Session uses N4 and is set to Control Plane Only. The (V-)SMF shall indicate the Serving PLMN rate control command to the NEF only if the PDU Session uses NEF.

[0147] The serving PLMN rate control is configured by the operator and is expressed as "X NAS packets / 6 minutes", where X is an integer and must not be less than 10. The uplink and downlink NAS packets have the following limits:

[0148] - The UE shall limit the rate at which it generates uplink NAS data PDUs to comply with the serving PLMN policy. In the UE, indicated rate control applies only to the PDU Session in which it is received, so the UE shall limit the rate of its uplink NAS data PDUs to comply with the indicated rate of the PDU Session. The indicated rate is valid until the PDU Session is released.

[0149] - The UPF / NEF shall limit the rate at which it generates downlink data PDUs. In the UPF / NEF, the indicated rate control applies only to the PDU session receiving that rate, so the UPF / NEF shall limit the rate of its downlink data PDUs to comply with the rate indicated for that PDU session.

[0150] - The (V-)SMF may enforce these limits per PDU Session by dropping or delaying packets that exceed these limits. The Serving PLMN rate does not include SMS using NAS transport PDUs. The (V-)SMF initiates Serving PLMN rate control upon receipt of the first NAS data PDU.

[0151] The (H-)SMF may determine whether to apply small data rate control based on, for example, operator policy, subscription, DNN, S-NSSAI, RAT type, etc. The (H-)SMF may send small data uplink rate control commands to the UE using the protocol configuration option (PCO) information element. The (H-)SMF informs the UPF or NEF of any small data rate control that should be performed. The small data rate control applies to data packets sent on this PDU session over a data radio bearer or a signaling radio bearer (NAS data packets).

[0152] The rate control information for uplink and downlink is separate and takes the form of an integer "number of packets per time unit" and an integer "number of additional exception report packets allowed per time unit" once the rate control limit is reached.

[0153] The UE shall comply with this uplink rate control command. If the UE exceeds the uplink "number of packets per time unit", the UE may still send uplink exception reports if allowed and the "number of additional allowed exception reports per time unit" has not been exceeded. The UE shall consider this rate control command valid until it receives a new rate control command from the (H-)SMF.

[0154] When a PDU Session is first established, the (H-)SMF may provide the configured small data rate control parameters to the UE and UPF or NEF. When a PDU Session is released, the small data rate control state (including the number of packets still allowed in a given time unit, the number of additional exception reports still allowed in a given time unit, and the end time of the current small data rate control validity period) may be stored in the AMF so that it can be retrieved for subsequent re-establishment of a new PDU Session.

[0155] When a new PDU session is subsequently established, the (H-)SMF may receive the previously stored small data rate control state. If the validity period of the previously stored small data rate control state has not expired, the (H-)SMF may provide the UE and UPF / NEF with parameters including the previously stored small data rate control state in addition to the configured small data rate control parameters, and use the previously stored small rate control state as the parameters for the initial application. If the parameters for the initial application are provided, the UE and UPF or NEF first apply the initial application parameters. When the validity period of the initially applied small data rate control expires, the configured small data rate control parameters provided by the SMF shall be used.

[0156] For UPF and NEF, the small data rate control is based on the "maximum allowed rate" in each direction. If the (H-)SMF provides the "number of additional exception report packets allowed per time unit", then the "maximum allowed rate" is equal to the "number of packets per time unit" plus the "number of additional exception report packets allowed per time unit", otherwise the "maximum allowed rate" is equal to the "number of packets per time unit".

[0157] UPF or NEF can enforce the uplink rate by dropping or delaying packets that exceed the "maximum allowed rate". UPF or NEF should enforce the downlink rate by dropping or delaying packets that exceed the downlink portion of the "maximum allowed rate".

[0158] As mentioned earlier, the connection between the satellite and the terminal device in store-and-forward mode, namely the service link, and the connection between the satellite and the ground station, namely the feeder link, cannot be available at the same time. Therefore, for uplink services, when the service link is available, the uplink data will be sent and stored on the satellite. When the feeder link is available, the stored data will be sent to the ground station. For downlink services, when the feeder link is available, the downlink data is sent from the ground station to the satellite and stored in the satellite. When the service link is available, the downlink data is sent to the terminal device. Therefore, in store-and-forward mode, the satellite only supports non-real-time services with delay tolerance, such as CIoT and SMS.

[0159] As can be seen, both uplink signaling and / or data and downlink signaling and / or data need to be stored on the satellite for a period of time in the store-and-forward mode. However, the storage space on the satellite is limited, and the transmission resources may also be limited.

[0160] When multiple terminal devices or multiple services need to be stored and / or forwarded on a satellite, if the storage space on the satellite is full, the storage and / or forwarding of subsequent services may not be performed.

[0161] In addition, in some scenarios, data may be stored on the satellite and not forwarded, occupying the storage space on the satellite. For example, a large number of terminal devices and a large number of business data flows need to be stored and / or forwarded through a certain satellite. Then, for some low-priority terminal devices and low-priority business flows, their data will be stored on the satellite. For another example, if the terminal device has left the coverage area of ​​the satellite or is turned off, then even if the service link is available, the satellite cannot establish an RRC connection with the terminal device, resulting in the downlink data still not being sent to the terminal device, and thus being stored in the satellite for a long time. The above data occupying the satellite's storage space for a long time may cause the satellite to be unable to perform storage and / or forwarding operations normally.

[0162] In addition, when transmission resources, especially air interface resources, are limited, if multiple terminal devices or multiple services need to be stored and / or forwarded, then how to handle the storage and / or forwarding requirements of multiple terminal devices or multiple services is a problem that needs to be solved.

[0163] In order to solve one or more of the above problems, an embodiment of the present application provides a method for wireless communication, which manages the transmission process of signaling and / or data (i.e., second information) stored and / or forwarded via satellite by introducing first information, thereby helping to improve system performance.

[0164] The following is an introduction to the wireless communication method provided in an embodiment of the present application in conjunction with Figure 4. The method shown in Figure 4 involves a first device, or the method shown in Figure 4 may involve a first device and a second device. The first device may be a terminal device, or the first device may be a network element or server deployed on the ground. The second device may be a device deployed on a satellite. It should be noted that the method provided in an embodiment of the present application is not only applicable to 5G scenarios, but also to other communication systems such as 4G. For example, the network elements in the 5G scenario mentioned below can be replaced with network elements with the same or similar functions in other communication systems such as 4G.

[0165] 4 , in step S410 , the first device determines first information.

[0166] The above-mentioned first information can be associated with the transmission of the second information, such as the first information can be used to manage the transmission process of the second information. In other words, the above-mentioned first information can be used to determine the transmission of the second information. The second information may include signaling and / or data stored and / or forwarded by satellite. For example, the second information may include signaling and / or data of one or more terminal devices that need to be stored and / or forwarded by satellite. For another example, the second information may include signaling and / or data of one or more business flows that need to be stored and / or forwarded by satellite. For another example, the second information may include signaling and / or data of one or more network elements or servers deployed on the ground that need to be stored and / or forwarded by satellite.

[0167] In some embodiments, the second information may be one or more of the following: a radio resource control (RRC) message; downlink signaling and / or data; uplink signaling and / or data; a non-access stratum (NAS) signaling message, or a NAS data packet carried in an RRC early data request or RRC connection establishment message; and downlink NAS transmission information. For example, the RRC message mentioned here may be used to initiate an RRC state transition.

[0168] The wireless communication method provided in the embodiments of the present application can be applied, for example, to the aforementioned scenarios supporting 5GS optimization of cellular Internet of Things, such as control plane CIoT 5GS optimization and / or user plane CIoT 5GS optimization.

[0169] When there is uplink data to be sent, the terminal device in the CM-IDLE suspended state can send an RRC signaling message to the access network device on the satellite, wherein the RRC message can be used to initiate an RRC state transition, for example. In this case, the second information may include an RRC message and uplink signaling and / or data. If there is further downlink data to be transmitted, such as the AS release assistance information (RAI) indicating that only a single downlink data transmission is performed after the uplink transmission, then the second information may include downlink signaling and / or data. This method can be applied to scenarios that support user-plane CIoT 5GS optimization.

[0170] If the terminal device is in CM-CONNECTED, a NAS signaling message may be sent carrying the encrypted PDU session ID (or EPS bearer ID) and the encrypted uplink data. In this case, the second information may include the NAS message and uplink signaling and / or data. This method may be applied to scenarios supporting control plane CIoT 5GS optimization.

[0171] If the terminal device is in the IDLE state, the terminal device may first establish an RRC connection or send an RRC early data request (RRC early data request), where the RRC early data request may carry a NAS data packet. In this case, the second information may include the NAS data packet carried in the RRC early data request or RRC connection establishment message.

[0172] As mentioned above, the storage space on the satellite is limited. Therefore, in some embodiments, the first information may include a storage limit (or storage threshold), which can be used to indicate the maximum amount of signaling and / or data that the satellite can store. By setting a storage limit, it is possible to avoid situations where the satellite's storage space is full and storage and / or forwarding cannot be performed. For example, it can prevent data from a terminal device or a service from being stored unlimitedly on the satellite, thereby squeezing out storage resources available for other terminal devices or other services and impacting other services.

[0173] In some embodiments, the first information may include a storage time, which may be used to indicate the maximum time the satellite stores signaling and / or data. For example, the storage time may include a storage duration, such as 30 minutes. In another example, the storage time may include a storage start time point and an end time point, or the storage time may include an end time point.

[0174] In some embodiments, the storage time corresponding to the signaling stored and / or forwarded via the satellite and the data stored and / or forwarded via the satellite may be the same, or the storage time may be set separately for the signaling stored and / or forwarded via the satellite and the data stored and / or forwarded via the satellite.

[0175] In some embodiments, when the storage time expires, the satellite can delete the stored data or signaling, thereby preventing signaling and / or data that has exceeded the storage time from occupying satellite storage space for a long time. To improve the reliability of data storage and / or forwarding, when the storage time expires, or when the storage time is about to expire (such as the first time before the storage time expires), the satellite can attempt to establish a connection with the recipient of the signaling and / or data, or attempt to forward the signaling and / or data to the recipient. If the connection establishment fails or the forwarding fails, the satellite can delete the signaling and / or data.

[0176] By setting the storage time, it is possible to avoid long-term storage of some low-priority terminal devices, service signaling and / or data, as well as signaling messages and user data of terminal devices that have left the satellite coverage, turned off the satellite communication function, or are in shutdown flight mode on the satellite, thereby ensuring the utilization of storage space on the satellite.

[0177] In some embodiments, the first information may include a priority, which may be used to determine the order in which the satellite stores and / or forwards multiple second information; and / or, the priority may be used to determine the first information, such as the storage limit, storage time, and traffic limit of the first device or the service associated with the first device.

[0178] For example, the priority can be in numerical form, such that a smaller value indicates a higher priority, or a larger value indicates a higher priority. For another example, the priority can reuse existing parameters or be determined based on some existing parameters. As an example, the priority can reuse the QoS parameter allocation and retention priority (ARP). For another example, the priority can be determined based on the service type associated with the second information. As an example, meteorological and geographical test data can have a higher priority than some multimedia services.

[0179] Managing the transmission of the second information based on priority helps avoid congestion caused by simultaneously processing signaling and / or data from multiple terminal devices or multiple services, while also ensuring that the transmission of the second information of important services or terminal devices is completed first.

[0180] As mentioned above, in the store-and-forward mode, transmission resources may be limited. Therefore, the first information may include flow control parameters, such as a flow limit (or flow threshold), to control the flow of service data flows carried on the satellite, thereby helping to reduce the probability of congestion.

[0181] In some embodiments, the traffic limit may include a total traffic limit (or may be referred to as a total traffic threshold). For example, the total traffic limit may be used to indicate the maximum value of the sum of the number of signaling and data transmitted by the satellite per unit time. As an example, the total traffic limit may include a maximum of 10 Mbits of data transmitted per minute, or a maximum of 10 data packets transmitted within 10 minutes. As another example, the total traffic limit may be used to indicate the maximum amount of data allowed to be stored on the satellite. As an example, the total traffic limit may be used to indicate the total limit of signaling and data that can be stored on the satellite by the first device and / or a service associated with the first device. As another example, the total traffic limit may also include a data limit and a signaling limit. The data limit and the signaling limit may be indicated by the maximum value of the bytes transmitted per unit time, such as a maximum data volume of 100 Mbits / minute, or by the maximum number of data packets allowed to be transmitted, such as 10 data packets.

[0182] In some embodiments, the traffic quota may also include a control plane signaling quota (or a control plane signaling threshold). For example, the control plane signaling quota indicates the maximum amount of control plane signaling that can be transmitted by the satellite per unit time, such as the maximum signaling and / or data volume or the number of signaling and / or data packets. In another example, the control plane signaling quota indicates the maximum amount of control plane signaling that can be transmitted, such as the maximum signaling and / or data volume or the number of signaling and / or data packets.

[0183] In some embodiments, the traffic quota may include a user plane data quota (or user plane data threshold). For example, the user plane data quota indicates the maximum amount of user plane data that can be transmitted by the satellite per unit time, such as the maximum data volume or number of data packets. In another example, the user plane data quota may indicate the maximum amount of user plane data allowed to be transmitted, such as the maximum data volume or number of data packets.

[0184] As an example, serving PLMN rate control can be used as a control plane signaling limit (which can be used only in the control plane-only mode mentioned above, i.e., CP ONLY mode); and / or, access point name (APN) rate control can be used as a total traffic limit to enhance CIoT EPS optimization.

[0185] As another example, serving PLMN rate control can be used as a control plane signaling limit (only for CP ONLY mode); and / or, small data rate control can be used as an overall traffic limit to enhance CIoT 5GS optimization.

[0186] In some embodiments, the flow control parameters in the first information, such as flow limits, may include limits in a single direction or total limits in both directions. For example, the flow limit may include one or more of the following: total uplink flow limit, total downlink flow limit, uplink control plane signaling limit, downlink control plane signaling limit, uplink user plane data limit, and downlink user plane data limit. For another example, the total flow limit mentioned above may refer to the total limit of uplink flow and downlink flow; the control plane signaling limit may be the sum of the uplink control plane signaling limit and the downlink control plane signaling limit; and the user plane data limit may be the sum of the uplink user plane data limit and the downlink user plane data limit.

[0187] Setting traffic limits for different data transmission methods, such as control plane signaling limits and user plane data limits, helps avoid congestion in different data transmission channels, thereby further improving system performance. Furthermore, users can flexibly choose the appropriate data transmission method based on the control plane signaling limits and user plane signaling limits, namely, transmitting data through the control plane or the user plane.

[0188] It should be noted that the above-mentioned signaling or data limits are mainly for signaling and data that need to be stored and / or forwarded through satellites. The signaling interaction between terminal devices and functional entities on satellites, and between ground-deployed network elements and functional entities on satellites are not within the limit.

[0189] In some embodiments, a first device may receive first indication information sent by a second device. The first indication information may be used to indicate whether the satellite is in store-and-forward mode. As an example, if the first indication information indicates that the satellite is in store-and-forward mode, the first device may determine the transmission of the second information based on the first information, or manage the transmission of the second information based on the first information. If the first indication information indicates that the satellite is not in store-and-forward mode, the first device may not manage the transmission of the second information based on the first information. To save signaling overhead, the first indication information may be used to indicate that the satellite is in store-and-forward mode. In other words, when the satellite is not in store-and-forward mode, the first indication information may not be sent.

[0190] In some embodiments, the first information may also include one or more of the following: the above-mentioned first indication information; the validity period of part or all of the information in the first information; the device identification of the device associated with the first information; the device address of the device associated with the first information; and descriptive information of the business flow associated with the first information.

[0191] Because the satellite's storage space, satellite load status, service link availability, and feeder link availability may vary, the first information may include the validity period of some or all of the information in the first information to dynamically adjust the first information, thereby helping to improve the utilization of the satellite's storage space. For example, when the service link is available, the satellite may forward downlink signaling and / or data to a terminal device; when the feeder link is available, the satellite may forward uplink signaling and / or data to a network element or server deployed on the ground. After the data stored in the satellite is forwarded, the remaining storage space in the satellite may increase. Therefore, the first information may include the validity period of some or all of the information in the first information. Furthermore, because the service link availability and feeder link availability are associated with the satellite's ephemeris information, the validity period of some or all of the information in the first information can be determined based on the satellite's ephemeris information.

[0192] The first information associated with different devices may be different, so the first information may include the device identifier of the associated device.

[0193] In some embodiments, the configuration granularity of the first information may include one or more of the following: device granularity; service type granularity; user granularity; protocol data unit (PDU) session granularity; quality of service (QoS) flow granularity; and service flow granularity. Among them, the configuration granularity of the first information is device granularity, that is, the first information can be configured separately for different devices; the configuration granularity of the first information is service type granularity, that is, the first information can be configured separately for different service types; the configuration granularity of the first information is user granularity, that is, the first information can be configured separately for different users; the configuration granularity of the first information is PDU session granularity, that is, the first information can be configured separately for different PDU sessions; the configuration granularity of the first information is QoS flow granularity, that is, the first information can be configured separately for different QoS flows; the configuration granularity of the first information is service flow granularity, that is, the first information can be configured separately for different service flows.

[0194] If the first information includes multiple types of information, the configuration granularities of the multiple types of information in the first information may be the same or different.

[0195] For example, the priority configuration granularity can be device-level. For example, priorities can be assigned to different terminal devices. A functional entity on the satellite can determine the order in which storage requests from multiple devices are processed based on the device priorities, and / or can determine the order in which signaling and / or data from multiple devices are forwarded based on the device priorities.

[0196] For another example, the configuration granularity of the priority can be the service type granularity or the service flow granularity. In this case, the satellite can determine the order of processing the storage and / or forwarding of the service flow based on the priority of the service type and / or the service flow priority.

[0197] For example, priority granularity can include device priority, service type priority, and service flow priority. Device priority, service type priority, and service flow priority can have different priorities. For example, when a satellite processes the storage and / or forwarding of multiple service flows from multiple devices, it can prioritize the storage and / or forwarding order based on the device priority. For multiple service flows from the same device, the storage and / or forwarding order for the device's multiple service flows can be further determined based on the service type and / or service flow priority. As an example, the second information includes service flows M and N for device A, and service flows X and Y for device B. If the priority of device A is higher than that of device B, then the priority of service flows M and N is higher than the priority of service flows X and Y. Furthermore, if the priority of service flow M is higher than that of service flow N, and the priority of service flow X is higher than that of service flow Y, then the satellite's storage and forwarding processing order is service flow M, service flow N, service flow X, and service flow Y.

[0198] It should be understood that the priorities of the above-mentioned device priority, service type priority, and service flow priority are given for illustrative purposes only and are not limited in this application. For example, the priority of the service type may also be higher than the device priority. Still taking the example of the second information including service flow M and service flow N of device A, and service flow X and service flow Y of device B, if the service type priority of service flow M and service flow Y is the highest, then the storage and / or forwarding order of service flow M and service flow Y can be determined based on the priority of device A and the priority of device B. If the priority of device B is higher than the priority of device A, then the priority of service flow Y is higher than the priority of service flow M.

[0199] In some embodiments, parameters of different granularities in the first information may be used simultaneously or individually.

[0200] The various parameters in the first information can be configured or updated through various processes. For example, the basic parameters of the terminal device included in the first information can be configured through the registration process and the terminal device configuration update process. For another example, the first information of the PDU session granularity (packet data network (PDN) connection (PDN connection) granularity), QoS flow granularity, and service flow granularity can be configured through the PDU session establishment, modification process or service request process. For another example, the first information of the terminal device granularity can be configured in the registration process and the attach process, while the first information of the service granularity can be configured in the PDU session establishment, modification process, service request process, attach process, etc.

[0201] In some embodiments, one or more parameters in the first information may be preconfigured or predefined. For example, the priority may be preconfigured or predefined. As an example, services such as weather and natural disasters may be preconfigured or predefined with a higher priority.

[0202] In some embodiments, one or more parameters in the first information may be determined based on the satellite's storage space usage. For example, when the satellite has a large amount of remaining storage space, the values ​​of parameters such as storage space, storage time, and data traffic limit in the first information may be larger; when the satellite has a small amount of remaining storage space, the values ​​of parameters such as storage space, storage time, and data traffic limit in the first information may be smaller.

[0203] In some embodiments, one or more parameters in the first information can be determined based on the satellite's load status. The satellite's load status may include, for example, the number of terminal devices accessing the satellite, the number of terminal devices served by the satellite, and the number of service flows carried by the satellite. For example, when a large number of terminal devices access the satellite and / or a large number of service flows are carried by the satellite, the flow control parameter values ​​in the first information may be smaller; when a small number of terminal devices access the satellite and / or a small number of service flows are carried by the satellite, the flow control parameter values ​​in the first information may be larger. In this way, the utilization of the satellite's storage space can be improved while avoiding congestion.

[0204] In some embodiments, one or more parameters in the first information can be determined based on the available time of the satellite's service link and / or the available time of the satellite's feeder link. For example, if the first device is a terminal device, then one or more parameters in the first information can be determined based on the available time of the satellite's service link; if the first device is a network element or server deployed on the ground, then one or more parameters in the first information can be determined based on the available time of the satellite's feeder link. For another example, the value of the storage time is determined based on the available time of the satellite's service link and / or the available time of the satellite's feeder link. For another example, when the available time of the satellite's service link is large, and / or the available time of the satellite's feeder link is large, it can be considered that the storage space on the satellite can be cleared. In this case, the value of the flow control parameter associated with the first device can be large.

[0205] In some embodiments, one or more parameters in the first information may be determined based on the subscription message. The subscription message may include, for example, one or more of the following: the priority of the contracted terminal device (such as the priority of the NB-IoT terminal device), the storage limit of the contracted terminal device, the storage time of the contracted terminal device, the priority of the contracted service (such as the association of the contracted service priority with the ARP of the 5GS), the storage limit of the contracted service, and the storage time of the contracted service.

[0206] In some embodiments, the subscription message can be stored on the satellite or in a device deployed on the ground. Usually, the subscription messages of all users are very large. Storing them in network elements deployed on the ground for other devices to access and obtain can save a lot of storage space for user data and signaling messages, thereby helping to improve the space utilization of the satellite. For example, the subscription message can be stored in the UDM / unified data repository (UDR) function or the home subscriber server (HSS). Among them, the UDM / UDR or HSS can be deployed on the satellite or on the ground.

[0207] Based on the different storage locations of the contract message, or based on the different deployment locations of the device storing the contract message, the method for determining one or more parameters in the first information based on the contract message is different. For example, when the contract message is stored on a satellite, the satellite can determine the first information based on the contract message, or the satellite sends the contract message to the first device, and the first device determines the first information based on the contract message. Optionally, the satellite can send the determined first information to the first device. For another example, when the contract message is stored in a device deployed on the ground, such as the first device, the first device can determine the first information based on the contract message, or the contract message can be sent to the satellite, and the satellite determines the first information based on the contract message. Optionally, the first device can send the first information to the satellite. Further, the satellite can forward the first information to other devices deployed on the ground. As an example, when the first device is a network element or server deployed on the ground, the first device can send the determined first information to the satellite, and further, the satellite can forward the first information to the terminal device.

[0208] Before the first device or satellite receives the subscription message, a query request message for the subscription message may be sent. The query request message may include one or more of the following: device identification information; QoS flow identification information; PDU session ID; and service flow description information. The device identification information, QoS flow identification information, and PDU session ID may be used to identify the device, associated QoS flow, or associated PDU session associated with the target subscription message being queried. The service flow description information may be used to identify a certain service data flow. The service flow description information may, for example, include an IP five-tuple (i.e., source / destination address, source / destination identifier, and protocol identifier).

[0209] In some embodiments, one or more parameters in the first information may be determined based on a request message from the first device, such as a request message from a terminal device. In other words, the first device may send a request message. The request message from the first device may be used to request the first information desired by the first device.

[0210] The first information may include one or more of the parameters or messages mentioned above, and the request message of the first device may be used to request the expected values ​​of the one or more parameters or messages mentioned above. Therefore, in some embodiments, the request message may include one or more of the following: a requested priority; a requested storage limit; a requested storage time; a requested total traffic limit; a requested control plane signaling limit; and a requested user plane data limit.

[0211] In some embodiments, in order to distinguish request messages from different devices, the request message may further include a device identifier of the first device.

[0212] In some embodiments, the first device may receive a response message to the request message sent by another device, such as the second device. The response message may include the first information. Therefore, to facilitate receiving the first information, the request message may include the address information of the first device.

[0213] The timing of sending the request message of the first device may include multiple. For example, after the first device learns that the satellite is in the store and forward mode, it may send the request message of the first device to the satellite to request the satellite to allocate the first information to it. For another example, when the quota in the first information associated with the first device is exhausted or is about to be exhausted, the first device may send the above request message. For another example, when the storage time in the first information associated with the first device is about to expire, the first device may send the above request message. For another example, when the validity period of one or more parameters in the first information associated with the first device expires or is about to expire, the first device may send the above request message. For another example, when the first information associated with the first device cannot meet the business needs of the first device, such as when the data that the first device needs to send exceeds the traffic quota associated with the first device, the first device may send the above request message.

[0214] In some embodiments, the request message of the first device can be carried in one or more of the following: a registration request message (registration request) in the registration process, a PDU session establishment acceptance message (PDU session establishment accept) in the PDU session establishment process, a PDU session modification request (PDU session modification request) in the PDU session modification process, a service request (service request) in the service request process, an attachment request message (attach request) in the attach process, a TAU request message (TAU request) in the tracking area update (TAU) process, and a PDN connection request message (PDN connectivity request) in the PDN connection request process of the terminal device; it can also be a process for a new UE to request the satellite to allocate the first information.

[0215] The first information can be determined based on one or more of the above-mentioned determinations, that is, the first information can be determined based on one or more of the following: pre-configuration information; contract message; storage space usage of the satellite; load status of the satellite; request message of the first device; available time of the satellite's service link; and available time of the satellite's feeder link; wherein the request message of the first device is used to request the first information desired by the first device.

[0216] It should be noted that the aforementioned determination of the first information by the first device may include the first device determining the first information based on one or more of the aforementioned information, or may include the first device receiving the first information sent by the second device, or in other words, the second device sending the first information to the first device. In some embodiments, when the first device determines the first information based on the one or more of the aforementioned information, the first device may receive satellite-related information sent by the satellite, such as the satellite's storage space usage, load status, and other information, to assist the first device in determining the first information.

[0217] In some embodiments, the first information may be updated. Since one or more information associated with the first information, such as the satellite's storage space usage, the satellite's load status, the satellite's service link availability, and the satellite's feeder link availability, may change, timely updating of the first information helps improve the utilization of the satellite's storage space and improve system performance.

[0218] For example, the first information may be updated based on one or more of the following: the expiration of the validity period of some or all of the information in the first information; an update request message from the first device; the establishment of a connection between the first device and the satellite; and the amount of signaling and / or data in the second information exceeds the limit indicated by the first information. As an example, when the first device establishes a connection with the satellite for the first time, the first information configured by the satellite may be received. When the first device establishes a connection with the satellite again, the first information may be updated, or the first device may receive an update to the first information. As another example, when there is remaining storage space in the satellite or when the storage space in the satellite is relatively sufficient, if the amount of signaling and / or data in the second information exceeds the limit indicated by the first information, the first information may be updated, or the first device may receive an update to the first information.

[0219] In some embodiments, before the first device sends signaling and / or data to the second device, the first device may determine whether the signaling and / or data to be sent exceeds the limit indicated by the first information based on one or more parameters of the first information.

[0220] In some embodiments, if the signaling and / or data in the second information exceeds the limit indicated in the first information (e.g., the amount of signaling and / or data in the second information exceeds the limit indicated in the first information), the first device performs one or more of the following: suspending the generation or delaying the sending of the second information; and sending an update request message for the first information. Delaying the sending of the second information may, for example, include waiting for the next unit of time (at which time the traffic limit is updated) before sending the second information. Delaying the sending of the second information may also include waiting for the first information to be updated before sending the second information.

[0221] In some embodiments, upon receiving signaling and / or data sent by the first device, the second device may first determine whether the amount of signaling and / or data exceeds the limit indicated in the first information. This can prevent untrusted terminal devices or untrusted ground stations from excessively sending signaling messages and user data, thereby excessively occupying storage resources on the satellite and causing other (e.g., trusted) terminal devices and other services to be unable to perform storage and / or forwarding normally.

[0222] In some embodiments, if the signaling and / or data in the second message exceeds the limit indicated in the first message (e.g., the amount of signaling and / or data in the second message exceeds the limit indicated in the first message), the second device may discard or delete part or all of the second message. For example, the second device may discard or delete the information in the second message that exceeds the limit. Optionally, in this case, the second device may notify the first device of the information that was not successfully sent. For another example, the second device may discard or delete all of the second message to facilitate implementation.

[0223] In some embodiments, if there is remaining storage space in the satellite, or if the satellite has sufficient storage space, and if the signaling and / or data in the second information exceeds the limit indicated in the first information (the amount of signaling and / or data in the second information exceeds the limit indicated in the first information), the second device stores the second information and / or updates the first information. In this way, if there is sufficient storage space in the satellite, signaling and data sent by terminal devices and / or ground-deployed network elements can still be stored in excess, thereby helping to improve the utilization of storage space on the satellite and helping to improve the success rate of storing and / or forwarding signaling messages and user data.

[0224] In some embodiments, the first device may receive a notification message sent by the second device, or the second device may send a notification message to the first device, wherein the notification message may be used to indicate that the amount of signaling and / or data in the second information exceeds the limit indicated in the first information.

[0225] For example, in a scenario that supports user plane CIoT 5GS optimization, when the second device receives an RRC message, uplink signaling and / or data, or downlink signaling and / or data sent by the first device, if the RRC message, uplink signaling and / or data, or downlink signaling and / or data exceeds the limit indicated in the first information, the second device can send a notification message to the first device.

[0226] For example, in a scenario that supports control plane CIoT 5GS optimization, when the second device receives a NAS message and uplink signaling and / or data or downlink signaling and / or data sent by the first device, if the NAS message and uplink signaling and / or data or downlink signaling and / or data exceed the limit indicated in the first information, the second device may send a notification message to the first device.

[0227] The limit indicated by the first information may include one or more of the aforementioned storage limit, total traffic limit, control plane signaling limit, and user plane data limit.

[0228] The above-mentioned notification message can be used to notify the first device, such as a terminal device or a ground-deployed site, that the signaling and / or data it sends has exceeded the corresponding limit. On the one hand, it can prevent the first device from mistakenly believing that the signaling message or user data has been stored and / or forwarded by the satellite; on the other hand, it can avoid the waste of resources caused by the first device continuously sending signaling messages or user data to the second device.

[0229] In some embodiments, the first information and / or the updated information of the first information may be carried by a newly added signaling message, or may be carried in a signaling message of an existing signaling process. For example, the first information and / or the updated information of the first information may be carried in one or more of the following: a registration accept message in a registration process; a PDU session establishment request message in a PDU session establishment process; a PDU session modification command in a PDU session modification process; an RRC connection reconfiguration message in a service request process; an attach accept message in an attach process; a tracking area update accept message in a TAU process; and a PDN connectivity accept message in a PDN connection request process of a terminal device.

[0230] In some embodiments, the update information of the first information may be carried in the notification message mentioned above.

[0231] As mentioned above, the first device may be a terminal device, or the first device may be a network element or server deployed on the ground. In the case of different deployment of devices in the communication system, the first device may include different devices. In some embodiments, the first device may be any one of the following: a mobility management entity MME; an access and mobility management function AMF; a session management function SMF; a serving gateway SGW; a packet data network gateway (PGW); a home user server HSS; an authentication service function AUSF; a unified data management UDM; a network data analysis function NWDAF; an Internet protocol multimedia service IMS server; and an application function AF.

[0232] As mentioned above, the second device may be a device deployed on a satellite. Depending on the deployment of the devices in the communication system, the second device may include different devices. In some embodiments, the second device may be any of the following: an access network device; an MME; an AMF; an SMF; an SGW; a PGW; an HSS; an AUSF; an UDM; an NWDAF; an IMS server; or an AF.

[0233] It should be noted that the operations mentioned above performed by the satellite can be replaced by operations performed by functional entities on the satellite.

[0234] It should be noted that the interaction between the first device and the second device must be performed when the link between the first device and the second device is available. For example, if the first device is a terminal device and the second device is a functional entity on a satellite, the interaction between the first device and the second device must be performed when the service link is available. For another example, if the first device is a network element deployed on the ground and the second device is a functional entity on a satellite, the interaction between the first device and the second device must be performed when the feeder link is available.

[0235] For ease of understanding, the wireless communication method provided by the embodiments of the present application is described below in conjunction with Examples 1 to 6. The storage and / or forwarding related parameters and flow control related parameters mentioned below may be the parameters in the first information mentioned above. For example, the storage and / or forwarding related parameters may refer to parameters such as the storage limit, storage time, and priority in the first information; the flow control related parameters may refer to parameters such as the total flow limit, control plane signaling limit, and user plane data limit in the first information.

[0236] Example 1: Functional entity on satellite configures first information

[0237] As mentioned above, the satellite is in store-and-forward mode, meaning that the connection between the terminal device and the satellite and the connection between the satellite and the network element deployed on the ground cannot be available at the same time. If the first information is configured by a functional entity on the satellite (i.e., a second device), then when the connection between the satellite and the terminal device is available, the functional entity on the satellite can send the first information to the terminal device; and when the connection between the satellite and the network element deployed on the ground is available, the functional entity on the satellite can send the first information to the network element or server deployed on the ground.

[0238] The above process is described in detail below with reference to Figure 5. The process shown in Figure 5 may include steps S510 to S530.

[0239] In step S510, the terminal device establishes a connection with a functional entity on the satellite.

[0240] When the terminal device has uplink data or signaling messages to send, or receives a paging signal from the satellite access network device, the terminal device can establish a connection with the functional entity on the satellite, such as establishing an RRC connection with the access network device.

[0241] In some embodiments, the RRC connection establishment message may carry request information of the first device. For example, the message may carry at least one of the following information:

[0242] UE identification information: subscription permanent identifier (SUPI), subscription concealed identifier (SUCI), permanent equipment identifier (PEI), temporary mobile subscriber identity (TMSI), globally unique temporary UE identity (GUTI), 5G-S-TMSI, globally unique AMF identifier (GUAMI), etc.

[0243] UE address information: IPv6 and / or IPv4 address, media access control (MAC) address, etc.

[0244] Requested UE priority: The store and / or forward priority that the UE wants to obtain. For example, after knowing that the satellite is in store and forward mode, the UE can request the satellite to assign it a higher priority;

[0245] Service flow description information: Information used to identify service flows, such as the PDU session ID, QoS flow identifier (QFI), and IP quintuple (source / destination address, source / destination identifier, and protocol identifier).

[0246] Requested service priority: the storage and / or forwarding priority that a service wants to obtain;

[0247] The priority can be in numerical form, such that the smaller the value, the higher the priority, or the larger the value, the higher the priority.

[0248] Requested data quota: The data quota requested by the UE. For example, when the satellite-allocated data quota is about to be or has been exhausted, the UE can request the satellite to reallocate the data quota based on subsequent service needs.

[0249] Data traffic limits, i.e. the total traffic limits mentioned above, may include: 1) the upper limit of the sum of signaling data packets and user-plane data packets that can be transmitted by a UE or a certain type of service within a unit time, such as a maximum of 10Mbits of data per minute, or a maximum of 10 data packets within 10 minutes; 2) the maximum amount of data that a UE or a certain service can store on a satellite, such as the total traffic limit can be the upper limit of the maximum data and signaling, or it can be expressed as the maximum data volume and the maximum signaling volume respectively; in this case, the total traffic limit can be expressed in units of data volume such as bytes and bits, such as a maximum data volume of 100Mbits, or in the form of the number of data packets, such as a maximum data volume of 10 data packets that can be stored.

[0250] Requested control plane signaling quota: The signaling quota requested by the UE. For signaling messages that require storage and / or forwarding by the network entity on the satellite or data transmitted via the control plane, the UE needs to request the satellite to allocate a certain amount of storage space, i.e., the control plane signaling quota;

[0251] The control plane signaling limit can be 1) the maximum signaling data size or number of signaling packets that can be transmitted per unit time; 2) the maximum signaling data size or number of signaling packets allowed to be transmitted.

[0252] Requested user plane data quota: The user plane data quota requested by the UE. For UL / DL data, satellite storage and / or forwarding is generally required. Even if the UPF is deployed on the satellite, the satellite needs to store and / or forward the data to the terrestrial data network (i.e., application server).

[0253] The user plane data limit may be 1) the maximum user plane data packet size or the number of user plane data packets that can be transmitted per unit time; 2) the maximum user plane data packet size or the number of user plane data packets allowed to be transmitted.

[0254] In some embodiments, the information involved in step S510 can be carried by the following information: registration request in the registration process, PDU session establishment accept in the PDU session establishment process, PDU session modification request in the PDU session modification process, service request in the service request process, attach request in the attach process, TAU request in the tracking area update process, PDN connectivity request in the PDN connection request process of the terminal device; it can also be the information or process used by the new UE to request the satellite to allocate the first information.

[0255] In step S520, the functional entity on the satellite may send first information to the terminal device.

[0256] When the satellite functional entity is in the store-and-forward mode, the satellite network entity notifies the UE that the satellite is in the store-and-forward mode, configures storage and / or forwarding related parameters and flow control related parameters (i.e., first information) for the UE or a service related to the UE based on local configuration, subscription information, current satellite load, storage space usage, service link / feeder link availability time, and other information, and sends the parameters to the UE. Specifically, the information (i.e., first information) sent by the satellite network entity to the UE includes at least one of the following parameters:

[0257] UE identification information;

[0258] Address information;

[0259] ●Business flow description information;

[0260] ● Store and forward indication: used to inform the UE that the current satellite is in store and forward mode;

[0261] ●Store and / or forward relevant parameters;

[0262] The storage and / or forwarding related parameters may include, for example, the priority, storage time, and storage limit mentioned above. The configuration granularity of one or more of the storage and / or forwarding related parameters may be user granularity, UE granularity, PDU session granularity (PDN connection granularity), QoS flow granularity, or service flow granularity.

[0263] Flow control related parameters;

[0264] Flow control related parameters may include, for example, the aforementioned total flow limit, control plane signaling limit, and user plane data limit. Flow control related parameters may be user-granular, UE-granular, PDU session-granular (PDN connection-granular), QoS flow-granular, or service flow-granular.

[0265] ● The validity period of storage and / or forwarding parameters, such as the validity period of priority, storage time, and storage limit; when the validity period expires, the UE can request the satellite to reallocate the parameters;

[0266] ● Validity period of flow control related parameters, such as the validity period of the total flow limit, control plane signaling limit, and user plane data limit; after the validity period expires, the UE can request the satellite to reallocate the parameters.

[0267] These parameters can be configured by the satellite when the UE initially establishes a connection with the satellite, or they can be updated by the satellite. For example, when the UE has exhausted its current quota, it can request an update of flow control parameters from the satellite. These parameters can be sent to the UE upon receipt of signaling requiring store and / or forwarding by the satellite.

[0268] The UE may generate a number of signaling messages or data packets less than a threshold based on the above flow control related parameters.

[0269] The above parameters can be carried in the signaling message sent to the UE by the newly added satellite network entity, or in the signaling process sent to the UE in the existing signaling process. For example, they can be carried in one or more of the following: registration accept in the registration process, PDU session establishment request in the PDU session establishment process, PDU session modification command in the PDU session modification process, RRC connection reconfiguration in the service request process, attach accept in the attach process, TAU accept in the tracking area update process, and PDN connectivity accept in the UE requested PDN connectivity process.

[0270] In step S530, the functional entity on the satellite may send first information to the network element deployed on the ground.

[0271] The network element may generate a signaling message and a data packet based on the first information, such as a flow control parameter. The first information sent to the ground-deployed network element may include at least one of the following parameters:

[0272] UE identification information;

[0273] Address information;

[0274] ●Business flow description information;

[0275] ● Store and forward indication: used to inform the UE that the current satellite is in store and forward operation mode;

[0276] ●Store and / or forward relevant parameters;

[0277] Flow control related parameters;

[0278] ● Validity period of storage and / or forwarding related parameters: After the validity period expires, the UE can request the satellite to reallocate the parameters;

[0279] ● Validity period of flow control related parameters: After the validity period expires, the UE can request the satellite to reallocate the parameters.

[0280] The validity period of the above parameters is generally related to the ephemeris information. Generally speaking, for uplink data and signaling messages, when the service link is available (the feeder link is not available at this time), the signaling and data need to be stored on the satellite. At this time, the flow control-related parameters are used to limit the UE from generating and sending data. When the feeder link is available (the service link is not available at this time), the satellite can forward the stored data to the ground-deployed network element. At this time, the forwarded signaling or data can be cleared, so that there is space to re-update the flow control-related parameters for the UE. Therefore, under the condition that the feeder link transmission bandwidth is large enough or the availability time is long enough, it can be considered that the storage space on the satellite can be cleared. When the service link is available again, the satellite can allocate new flow control parameters to the UE. The same is true for downlink data and signaling messages.

[0281] The functional entities on the satellite can be any combination of access network equipment and core network elements such as MME, AMF, SMF, SGW, PGW, HSS, AUSF, UDM, NWDAF, IMS servers, AF and other application functions.

[0282] Taking into account that different network elements will lead to different solutions when deployed on satellites, this solution will discuss the configuration and execution methods of the above parameters under four deployment architectures: RAN on satellite (deployed on satellite), RAN+AMF on satellite, RAN+SMF on satellite, and RAN+UPF on satellite.

[0283] i. When only access network equipment is deployed on the satellite, the access network equipment needs to manage the UE's context information, including storage limit, storage time, forwarding priority and other storage and / or forwarding related information, to manage the satellite's storage space. At the same time, the access network equipment needs to notify the UE, UPF, AF and other network elements that subscribe to this information of the UE's storage limit information. The UE controls and manages uplink traffic based on this information. For example, when the data volume of a certain satellite exceeds the limit, it stops sending uplink data. Similarly, the UPF can also manage downlink traffic based on this information. In addition, if the application server subscribes to this information, the amount of data generated can be limited from the source. In addition, for CIoT 5GS optimization, data flow control can also be performed on SMF and NEF by sending limit information; for CIoT 4GS optimization, data flow control can also be performed from MME, SGW, SPW, and service creation environment function (SCEF).

[0284] ii. When the access network equipment and the access and mobility management function (MME or AMF) are co-located on the satellite, the access network equipment and / or the AMF or MME may manage the UE's context information, including storage limits, storage duration, forwarding priority, and other storage and / or forwarding related information. Since the access network equipment and the access and mobility management function are co-located, the access and mobility management function and / or the access network equipment are required to configure data flow control related information to the UE, other core network elements, application servers, etc.

[0285] iii. For access network equipment and session management functions deployed on satellites (SMF or MME, SGW, PGW), the access network equipment and / or session management functions can perform the formulation of storage and / or forwarding related parameters, and configure flow control related parameters to UE, other core network elements, application servers, etc.

[0286] iv. For access network equipment and user plane functions (UPF or SGW, PGW) deployed on the satellite, the access network equipment and / or functions can perform the formulation of storage and / or forwarding related parameters and flow control related parameters, and configure the parameters to UE, other core network elements, application servers, etc.

[0287] Implementation 1 can be applied to scenarios where UEs exchange signaling and data with ground-based network elements and data servers via a satellite in store-and-forward mode. In this embodiment of the present application, the establishment of UE and service priorities facilitates the orderly allocation of satellite communication resources, such as air interface resources, and avoids congestion caused by simultaneously processing signaling and data for multiple services from multiple UEs. It also helps ensure that the transmission of signaling messages and user data for high-priority UEs and services is prioritized. Establishing storage time prevents the long-term storage of signaling and / or data for low-priority UEs and services, as well as signaling messages and user data for UEs that have left satellite coverage, have disabled satellite communication functions, or are in flight mode, on the satellite, thereby ensuring efficient storage space utilization on the satellite. Establishing storage limits prevents data from a particular UE or service from being stored indefinitely on the satellite, thereby squeezing out storage resources available for other UEs and services and impacting other services. Flow control parameters help reduce the probability of congestion by establishing user data limits, signaling message limits, and total data limits per unit time. For example, a UE can transmit uplink data to the satellite within the available service link time. Alternatively, if fewer UEs are accessing the satellite simultaneously, the transmission rate can be increased to transmit all data to the satellite in a shorter period of time. The UE or ground-based network equipment can adjust the data transmission rate based on the satellite's configured flow control parameters and select the appropriate data transmission method, either via the CP or the UP, based on user plane data limits and control plane signaling limits.

[0288] Example 2: Configuring the first information based on the contract message

[0289] In some embodiments, the network entity on the satellite may configure storage and / or forwarding related parameters and flow control related parameters (i.e., first information) based on pre-configured information, or UE requests, or information such as storage space occupancy, the number of UEs accessing the satellite, or the number of bearer data service flows. In some embodiments, the network entity on the satellite may also configure the first information based on a subscription message.

[0290] For example, the subscription message can be stored in the UDM (5G system) or HSS (4G system). When the UDM (5G) or HSS (4G) is deployed on the satellite, or when the subscription message of the UE authorized to access the satellite is stored on the satellite, the satellite can directly formulate storage and / or forwarding related parameters and flow control related parameters based on the subscription message. In other deployment architectures, the UDM / UDR and HSS are deployed on the ground, or the UE subscription message is stored at the ground site. At this time, the functional entity on the satellite needs to interact with the UDM, HSS or other network functional entities deployed on the ground that store the UE subscription message. After obtaining the UE subscription message, the corresponding storage and / or forwarding and flow control related parameters are configured for the UE or the session or QoS flow requested by the UE.

[0291] The above process is described in detail below with reference to Figure 6. The process shown in Figure 6 may include steps S610 to S660.

[0292] In step S610, the terminal device establishes a connection with a functional entity on the satellite.

[0293] This step may be the same as step S510 in the first embodiment, and will not be described again here for the sake of brevity.

[0294] In step S620, the functional entity on the satellite sends a subscription message query request to the network element (the network element storing the subscription message).

[0295] The network element that receives the subscription information query request may be a network element that stores subscription information, such as a UDM, HSS, or other network element that stores UE subscription information. The query request may include at least one of the following information:

[0296] UE identification information: SUPI, GPSI and other UE IDs;

[0297] QFI: QoS flow identifier;

[0298] PDU session ID: used to identify the PDU session;

[0299] IP quintuple: used to identify a service data flow;

[0300] The functional entity on the satellite can be an access network device, and it can also be any network element among AMF, MME, SMF, SGW, PGW, and UPF.

[0301] In step S630, the network element may return the subscription message to the functional entity on the satellite.

[0302] The contract message may be the contracted UE priority (for example, NB-IoT UE priority), the contracted UE storage limit, the contracted UE storage time, the contracted service priority (for example, it can be derived from the ARP in the QoS overview of the 5GS subscription), the contracted service storage limit, and the contracted service storage time.

[0303] In step S640 , a functional entity on the satellite determines first information.

[0304] The functional entity on the satellite can determine storage and / or forwarding related parameters, flow control related parameters (i.e., first information) based on the received subscription message, and / or the current load status (such as the number of access UEs, the number of carried service flows), storage space utilization, and / or pre-configuration information, and configure the validity period of the above parameters in combination with the satellite ephemeris information.

[0305] In step S650, the functional entity on the satellite forwards the first information to the network element deployed on the ground.

[0306] When the feeder link is available, the functional entity on the satellite can send the above parameters to the network elements deployed on the ground.

[0307] In step S660, the functional entity on the satellite forwards the first information to the terminal device.

[0308] When the service link is available, the satellite functional entity may send the above-mentioned storage and / or forwarding related parameters and flow control related parameters to the UE. If the terminal device has not yet established a connection with the satellite functional entity, the target UE may be paged to establish a connection with the satellite network entity, or when the UE has uplink data or signaling to send, after establishing a connection with the satellite functional entity (for example, the UE establishes an RRC connection with the satellite access network device), the satellite functional entity may send the above-mentioned storage and / or forwarding related parameters and flow control related parameters to the UE.

[0309] Embodiment 2 is primarily applicable to scenarios where UDM / UDR and HSS are deployed on the ground, or where UE subscription messages are stored at ground sites. The network function entity on the satellite must first interact with the network elements and servers deployed on the ground to obtain information used to formulate storage and / or forwarding-related parameters and flow control-related parameters, such as subscription messages, before formulating reasonable parameters. Generally, the subscription messages of all users are very large. Storing them in network elements deployed on the ground for satellite access can save a large amount of storage space for user data and signaling messages.

[0310] It should be noted that Example 1 and Example 2 mainly describe the configuration of storage and / or forwarding and flow control parameters triggered by the UE. For the signaling process or downlink data triggered by the network side, it can also trigger the network entity on the satellite to configure the above parameters for the network elements and UE deployed on the ground.

[0311] Example 3: Ground deployment network element configuration first information

[0312] In some deployment scenarios, for example, when session management-related network elements and access and mobility management network elements are deployed on the ground, network functions on the satellite, such as access network equipment, can send storage space occupancy information to network elements deployed on the ground. The network elements deployed on the ground configure storage and / or forwarding related parameters and flow control related parameters (i.e., first information) based on the UE context and the subscription message, and send the above parameters to the functional entity on the satellite and the UE.

[0313] The above process is described in detail below with reference to Figure 7. The process shown in Figure 7 may include steps S710 to S750.

[0314] In step S710, a ground-based network element establishes a connection with a functional entity on a satellite.

[0315] When downlink data or signaling needs to be sent to the UE, the ground-based network elements, such as AMF, MME, SMF, SGW, PGW, and UPF, establish a connection with the satellite functional entity when the feeder link is available. The connection establishment message may carry at least one of the following information:

[0316] UE identification information: SUPI, SUCI, PEI, TMSI, GUTI, 5G-S-TMSI, GUAMI, etc.

[0317] UE address information: IPv6 and / or IPv4 address, MAC address, etc.

[0318] ●Business flow description information: information used to identify business flows, such as QFI, IP five-tuple (source / destination address, source / destination identifier, protocol identifier).

[0319] In step S720, the functional entity on the satellite sends satellite-related information to the ground-deployed network element.

[0320] The satellite-associated information may include, for example, storage space usage and load status of the satellite, and the ground-deployed network element may determine the first information based on the satellite-associated information.

[0321] For example, if the functional entity on the satellite is in the store-and-forward mode, it can notify the ground-deployed network element that it is in the store-and-forward mode, and send the satellite storage space occupancy status (i.e., satellite-associated information) to the ground-deployed network element. As an example, the satellite-associated information may include at least one of the following information:

[0322] ● Store and forward indication: used to inform the UE that the current satellite is in store and forward operation mode;

[0323] Storage space usage: For example, it can be the remaining storage space or the available storage space. For example, if the available storage space is 1TB, the available storage space can store 3,000 data packets.

[0324] The identity of the UE accessing the satellite;

[0325] ●The address of the UE accessing the satellite;

[0326] ●Description information of the data stream carried by the satellite: such as IP five-tuple, PDU session identifier, QFI, etc.

[0327] In step S730, the ground deployment network element determines first information.

[0328] Ground-deployed network elements, such as session management-related network elements and access and mobility management network elements, can determine the first information based on one or more of the following: received satellite storage space occupancy, pre-configuration information, UE context information stored in the access and mobility management function, session-related information (QoS parameters, N4 rules, etc.) stored in the session management function, and subscription messages stored in the HSS and UDM / UDR. The first information includes at least one of the following information:

[0329] UE identification information;

[0330] Address information;

[0331] ●Business flow description information;

[0332] ● Store and forward indication: used to inform the UE that the current satellite is in store and forward operation mode;

[0333] ●Store and / or forward relevant parameters;

[0334] Flow control related parameters;

[0335] ● Validity period of storage and / or forwarding related parameters: After the validity period expires, the UE can request the satellite to reallocate the parameters.

[0336] ● Validity period of flow control related parameters: After the validity period expires, the UE can request the satellite to reallocate the parameters.

[0337] It should be noted that the above message may be multiple sets of parameters configured for multiple service flows of multiple UEs accessing multiple satellites at the same time, or multiple sets of first information.

[0338] In step S740, the ground-deployed network element sends the first information to the functional entity on the satellite.

[0339] In step S750, the functional entity on the satellite forwards the first information to the terminal device.

[0340] Embodiment 3 is primarily applicable to scenarios where session management-related network elements and access and mobility management network elements are deployed on the ground. Signaling and data interactions between ground-based network elements and UEs must be executed when a feeder link is available. In this case, ground-based network elements and application servers can assist the satellite in formulating storage and / or forwarding-related parameters and flow control-related parameters, and sending them to the satellite and UE. This can further simplify the satellite's logical functions, improve the utilization of satellite storage resources, and enable lightweight satellite-borne communication services.

[0341] Example 4: Data storage and / or forwarding and flow control under CIoT UP optimization

[0342] Example 4 takes the connection resume in CM-IDLE with suspend and MO EDT procedure as an example, and describes the uplink data transmission, signaling storage and forwarding, and flow control initiated by the mobile terminal in the satellite storage and forwarding mode in combination with Figure 8.

[0343] The process shown in FIG8 may include steps 1 to 9.

[0344] In step 1, the terminal device sends an RRC message to the access network device.

[0345] When uplink data is to be transmitted, a UE in the CM-IDLE suspended state sends an RRC signaling message to the satellite access network equipment, initiating the transition from the suspended RRC idle state to the RRC connected state. This message may include AS release assistance information, which indicates the following two situations: no subsequent uplink or downlink data transmission; or only a single downlink data transmission after the uplink transmission.

[0346] When the UE sends the above data or signaling, if the first information is configured, the terminal device needs to determine whether the number of data packets sent and the amount of data exceeds the limit. Specifically, it can be divided into the following three situations:

[0347] i. If the number of signaling message packets sent per unit time by the UE exceeds the control plane signaling quota, the UE may suspend generating or delay sending signaling messages or carrying user data via signaling messages, and wait for the next unit time to send signaling messages or carry user data via signaling messages; or the UE may apply for or wait for the satellite to update the control plane signaling quota, thereby increasing the number of signaling messages allowed to be transmitted.

[0348] ii. If the number of user plane data packets sent by the UE per unit time exceeds the user plane data limit, the UE suspends the generation or delays the sending of user plane data and waits for the next unit time to send the user plane data packet; or the UE applies for or waits for the satellite to update the user plane data limit, thereby increasing the additional user plane data allowed to be transmitted.

[0349] iii. If the number of signaling message packets and user-plane packets sent by the UE per unit time exceeds the data traffic limit (i.e., the total traffic limit), the UE suspends the generation or delays the sending of signaling or user packets and waits for the next unit time to send the signaling or user packets; or the UE applies for or waits for the satellite to update the user-plane data limit, thereby increasing the number of additional signaling or user packets allowed to be transmitted.

[0350] If the above limits are not exceeded, the UE can send signaling messages and data packets to functional entities on the satellite, such as access network equipment, when the feeder link is available.

[0351] The above limits can be at the user granularity (i.e., the data packets of all UEs under a certain user name or allocated to a certain user group exceed the limit), or at the UE granularity (i.e., all data packets of a certain UE exceed the limit), or at the PDU session granularity (PDN connection granularity) (i.e., the data packets of a certain PDU session or PDN connection exceed the above limit), or at the QoS flow granularity (i.e., the data packets of a certain QoS flow exceed the above limit), or at the service flow granularity (i.e., the data packets filtered out by the same IP quintuple exceed the above limit).

[0352] If the data from the UE is data packets for one or more service flows of multiple UEs, or data packets for multiple service flows of a single UE, a network entity (e.g., an access network device) on the satellite may store the data in order based on UE priority and service priority, and determine whether the data from the UE exceeds a limit indicated by the first information based on locally stored first information associated with one or more of the user, UE group, UE, PDU session, PDN connection, QoS flow, and service data flow. If the data from the UE exceeds the limit indicated by the first information, step 2a is executed.

[0353] In step 2a, the access network device sends a notification message to the terminal device.

[0354] In some embodiments, the access network device may discard or refuse to receive data packets from the UE and send a notification message to inform the UE. The notification message may be used to indicate that the signaling and / or data sent by the UE exceeds the corresponding limit, thereby preventing the UE from continuously sending signaling and data to the satellite.

[0355] In other embodiments, the access network device may receive a data packet from the UE. For example, if sufficient storage space is available on the satellite and / or if there are message requests or uplink data from other UEs in the short term or at the same time, the access network device may store the data packet from the UE and update the corresponding first information. For example, the new first information may be configured for the UE in a notification message.

[0356] If the satellite stores signaling messages or data exceeding the limit, or the data from the UE does not exceed the limit indicated by the first information, step 2b is executed.

[0357] In step 2b, the access network equipment sends signaling and data to the network elements deployed on the ground.

[0358] When the feeder link is available, the access network equipment can send signaling and data to the network elements on the ground. For example, user plane data can be forwarded to the UPF, SGW, and PGW. Signaling and / or data can be forwarded to the AMF or MME (if deployed on the ground), SMF (if the AMF is in the satellite and the SMF is deployed on the ground), or PCF (if the AMF and SMF are deployed in the satellite and the PCF is deployed on the ground).

[0359] In addition, if the access network equipment receives multiple UE requests simultaneously or in a short period of time when the service link is available, it can sort the UE requests based on UE priority and service priority, and process and store the signaling messages and user data to be forwarded in sequence. And when the feeder link is available, the signaling messages or user data of different services of different UEs (or the same UE) can be forwarded to the ground network elements, such as UPF, in the order of priority data.

[0360] In step 3, the access network device sends an N2 recovery request to the AMF.

[0361] The N2 resume request may include the reason for resuming the connection and N2 session management information. If the AS release assistance information sent by the UE in step 1 indicates that there is no subsequent uplink or downlink data transmission, the access network device may request an immediate transition to the suspended RRC idle state.

[0362] In step 4, AMF establishes an N3 connection with SMF.

[0363] Unless the AMF receives a request to transition to the suspended RRC idle state, or the AMF does not perceive any downlink data or signaling to be sent, the AMF establishes an N3 connection with the SMF.

[0364] In step 5, the AMF sends an N2 recovery response to the access network device.

[0365] If the AMF receives a request to immediately transition to the suspended RRC idle state in step 3 and there is no downlink data or signaling to be sent, the AMF includes a suspension indication in the response message to keep the UE in the suspended CM-IDLE state. Otherwise, the AMF sends an N2 resume response to the access network device after the N3 connection is established and transitions the UE to CM-CONNECTED. If the AMF knows that the mobile terminal data or signaling is pending, the AMF may include an extended connected time value in the message sent to the access network device.

[0366] If the N2 recovery response contains different messages, the operations performed by the access network device are different. If the AMF includes a suspend indication in the response message, proceed to step 6a. If the AMF does not include a suspend indication and the UE does not provide an AS release assistance indication, or the AMF provides an extended connected time value, proceed to step 6b. If the AMF does not provide an extended connected time value, or the AS release assistance indication provided by the UE indicates only a single downlink data transmission after an uplink transmission, proceed to step 6c.

[0367] In step 6a, the access network device sends an RRC release message to the UE.

[0368] The access network device releases the suspended RRC connection and skips subsequent processes.

[0369] In step 6b, the access network device and the UE establish an RRC connection.

[0370] The AMF sends RRC resume to the UE, and the UE transitions to the CM-CONNECTED and RRC connected states and skips subsequent procedures.

[0371] Step 6c: UPF sends a downlink message to the access network device.

[0372] If the first information is configured, before the UPF (or SGW, PGW) sends a downlink message to the access network device, it is necessary to determine whether the number of data packets sent exceeds the limit.

[0373] The access network device determines whether the downlink message exceeds the limit indicated by the first information based on the locally stored flow control parameters corresponding to this user, and / or UE group, and / or UE, and / or PDU session, and / or PDN connection, and / or QoS flow, and / or service data flow.

[0374] If the downlink message exceeds the limit indicated by the first information, the access network device sends a notification message (i.e., step 7) to the UPF (or SGW, PGW, AMF, SMF, MME) to inform the ground-based network element UPF (or SGW, PGW) that the data packet sent exceeds the corresponding limit. Sending the notification message helps prevent the UPF (or SGW, PGW) from continuously sending signaling and data to the satellite.

[0375] If there is sufficient free storage space on the satellite and the downlink message exceeds the limit indicated by the first information, the satellite can store the data packets exceeding the limit, update the corresponding flow control parameters, and configure the updated parameters to the UPF (or SGW, PGW).

[0376] In addition, if the network entity on the satellite (such as the access network device) receives different service data and / or signaling sent to different UEs, the network entity on the satellite (such as the access network device) can receive and store the received signaling messages and / or user data in sequence based on the UE priority and service priority.

[0377] It should be noted that, since this embodiment does not involve signaling messages sent to the UE, the above steps only determine whether the user plane data limit and data traffic limit are exceeded. For scenarios involving satellite storage and / or forwarding of signaling messages to the UE, it is necessary to 1) determine whether the control plane signaling limit is exceeded before the ground-deployed network element sends the signaling message to the UE. If it exceeds the limit, the sending of the signaling message needs to be delayed. Wait until the ground-deployed network element requests an update or the entity on the satellite updates the flow control parameters before sending the above-mentioned signaling message that needs to be stored and / or forwarded to the UE by the satellite; 2) The network entity on the satellite determines whether it needs to discard the signaling message that exceeds the control plane signaling limit. If it exceeds the limit, it notifies the ground-deployed network element (such as MME, AMF, SMF, etc.). The message indicates that the ground-deployed core network element has sent a data packet that exceeds the corresponding limit.

[0378] In step 8, the N3 connection is released.

[0379] In step 9, the access network device sends the downlink data to the terminal device.

[0380] When a service link is available, the access network device sends downlink data in an RRC message to the UE. Signaling messages or user data for different services for different UEs (or the same UE) can be forwarded to the UE in priority order. If only a single downlink data transmission is required, the access network device can include the downlink data in an RRC release message.

[0381] Example 4 describes the execution method for data storage and forwarding and flow control under CIoT UP optimization, which makes up for the deficiencies in the relevant standards and enables satellites in store-and-forward mode to support CIoT UP optimization. Example 4 provides the execution conditions for each step of the connection resume in CM-IDLE with suspend and MO EDT procedure. For example, in the scenario where the access network equipment is deployed on the satellite, the steps related to the interaction between the access network equipment and the UE should be executed under the condition that the service link is available, and the steps related to the interaction between the access network equipment and core network elements such as the UPF should be executed under the condition that the feeder link is available.

[0382] The newly added notification message can be used to notify UE and ground-deployed sites that the signaling and / or data they have sent has exceeded the corresponding limit, preventing the UE and ground-deployed network elements from thinking that the satellite has not received the corresponding signaling message or user data and continuing to send information to the satellite. It also prevents the UE and ground-deployed network elements from thinking that the signaling message or user data has been stored and / or forwarded by the satellite. In addition, the newly added notification message can be used to update the flow control parameters for the UE and ground-deployed network elements, thereby ensuring that the satellite can still store excess signaling and data sent by the UE and ground-deployed network elements when there is surplus storage space, thereby improving the utilization of the storage space on the satellite and the success rate of storing and / or forwarding signaling messages and user data. The execution of flow control by the UE and ground-deployed network elements can prevent the UE and ground-deployed network elements from sending excessive signaling messages and user data, which may cause them to be discarded, thereby causing unnecessary waste of resources. In addition, the network entity on the satellite performs storage and / or forwarding of received signaling messages and user data, which can prevent some untrusted UEs and ground sites from excessively sending signaling messages and user data, thereby occupying too much storage resources on the satellite, thereby causing the storage and / or forwarding of other UEs and other services to be unable to be performed normally.

[0383] Example 5: Data Storage and / or Forwarding and Traffic Control under CIoT CP Optimization (5GS)

[0384] Taking the control plane-initiated uplink data transmission under CIoT CP optimization as an example, Figure 9 illustrates the uplink data transmission, signaling storage and forwarding, and flow control initiated by a mobile terminal in satellite storage and forwarding mode. The process shown in Figure 9 may include steps 0 to 13.

[0385] In step 0, the UE sends a NAS message to the access network device.

[0386] If the UE is in CM-CONNECTED, it may send a NAS signaling message carrying the encrypted PDU session ID (EPS bearer ID) and the encrypted uplink data. If the UE is in IDLE state, the UE first establishes an RRC connection or sends an RRC Early Data Request carrying a NAS data packet. The UE may send a NAS RAI in a NAS message to indicate that no further uplink and downlink data transmissions are expected, or that only a single downlink data transmission (e.g., an acknowledgment or response to uplink data) is expected after the uplink data transmission.

[0387] When the UE sends the above data or signaling, if it is configured with first information, such as flow control related parameters, it is necessary to determine whether the number of NAS data packets sent by the UE does not exceed the control plane signaling limit or the data flow limit. For details, please refer to step 1 of embodiment 4.

[0388] In step 1a, the access network device sends a notification message to the terminal device.

[0389] In some embodiments, the access network device may discard or refuse to receive data packets from the UE and send a notification message to inform the UE. The notification message may be used to indicate that the signaling and / or data sent by the UE exceeds the corresponding limit, thereby preventing the UE from continuously sending signaling and data to the satellite.

[0390] In other embodiments, the access network device may receive a data packet from the UE. For example, if sufficient storage space is available on the satellite and / or if there are message requests or uplink data from other UEs in the short term or at the same time, the access network device may store the data packet from the UE and update the corresponding first information. For example, the new first information may be configured for the UE in a notification message.

[0391] If the satellite stores signaling messages or data exceeding the limit, or the data from the UE does not exceed the limit indicated by the first information, step 1b is executed.

[0392] In step 1b, the access network device obtains UE related information.

[0393] In NB-IoT scenarios, access network devices can obtain information such as UE priority, expected UE behavior, and UE radio capabilities from the AMF (or MME). If the AMF (MME) is deployed on the ground, it is necessary to wait until the feeder link is available before executing steps 1b, 2, and 3a.

[0394] In step 2, the access network device forwards the NAS message to the AMF (or MME).

[0395] If the RRC early data request message is received in step 0, the access network device includes the EDT session indication in the N2initial UE (S1-AP initial UE) message.

[0396] In step 3, decryption and integrity protection.

[0397] The AMF (MME) checks the integrity of the received NAS message and decrypts the PDU session ID and uplink data.

[0398] In step 3a, the AMF sends an N2 message to the access network device.

[0399] If the AMF receives an EDT session indication in step 2, the AMF sends an N2 message to the access network device:

[0400] i. If the RAI indicates that no downlink data is expected and the AMF expects no further data or signalling to be exchanged with the UE, the AMF shall include an end indication in the N2 downlink NAS message to indicate that no further data or signalling messages will be exchanged with the UE.

[0401] ii. If the AMF determines that there is more data or signalling to be sent, the AMF does not include an end indication in the N2 downlink NAS transport information or the initial context setup request message.

[0402] In step 3b, the RRC early data is completed or an RRC connection is established.

[0403] If step 3a has been executed, the access network device completes the RRC early data procedure as follows:

[0404] i. For case i in step 3a, the access network device sends the RRC Early Data Complete to the UE when the service link becomes available. The entire process ends in step 5.

[0405] ii. For case ii in step 3a, the access network device performs the RRC connection establishment process when the service link is available.

[0406] If the AMF is deployed on the ground, step 3b needs to wait until the service link is available, so it needs to be executed after step 9.

[0407] In step 4, AMF sends the PDU session ID and data to SMF.

[0408] The AMF determines the (V-)SMF based on the PDU session ID and sends the PDU session ID and data to the SMF.

[0409] If the RAI in the NAS message sent by the UE in step 1 indicates that no downlink data is expected and the AMF is not aware of downlink data to be sent, the AMF does not wait for step 7 but proceeds to step 12.

[0410] If the AMF (MME) is deployed on the satellite and the SMF (SGW, PGW) is deployed on the ground, this step needs to be performed when the feeder link is available.

[0411] In step 5, the SMF forwards the data to the UPF.

[0412] If header compression is applied to the PDU session, the (V-)SMF decompresses the header and forwards the data to the UPF. Further, the UPF sends the data to the DN based on the data forwarding rules.

[0413] If the SMF is deployed on the satellite and the UPF is deployed on the ground, this step needs to be performed when the feeder link is available.

[0414] In step 6, the UPF sends the downlink data to the SMF.

[0415] If the SMF is deployed on the satellite and the UPF is deployed on the ground, this step needs to be performed when the feeder link is available. If the UPF is configured with flow control parameters, the UPF also needs to determine whether the data to be sent exceeds the control plane signaling limit. If so, it will suspend the generation or delay of signaling or user data packets.

[0416] If the SMF is deployed on the satellite, the SMF performs storage and / or forwarding and flow control, and the specific implementation method is shown in step 6c of embodiment 4. If the downlink data exceeds the limit indicated by the first information, the SMF sends a notification message to the UPF (i.e., step 6a of embodiment 5).

[0417] In step 7, SMF sends the downlink data to AMF.

[0418] If header compression is applied to the PDU session, SMF compresses the packet header and sends the downlink data and PDU session ID to AMF.

[0419] If the AMF (MME) is deployed on the satellite and the SMF (SGW, PGW) is deployed on the ground, this step needs to be performed when the feeder link is available. The SMF (SGW, PGW) performs flow control. Accordingly, the AMF (or MME) also needs to perform flow control when receiving downlink data. If the downlink data exceeds the limit indicated by the first information, the AMF (or MME) can send a notification message to the network element deployed on the ground (step 7a). The flow control method mentioned here and the content of the notification message can be referred to the previous description and will not be repeated here.

[0420] In step 8, the AMF performs data encryption and integrity protection.

[0421] The AMF creates a DL NAS transport message carrying downlink data and PDU session ID, and performs encryption and integrity protection on the NAS message.

[0422] In step 9, the AMF sends the NAS message to the access network device.

[0423] The AMF sends the DL NAS transport message to the access network device. If the NAS RAI indicates a single uplink and a single downlink data packet, and the AMF has determined that the data transmission is for a single uplink and a single downlink data packet, the AMF may also include an end indication in the DL NAS transport message to indicate that there is no more signaling or data to be exchanged with the UE.

[0424] If the AMF is deployed on the ground, this step needs to be performed when the feeder link is available, and the access network device needs to perform flow control. If the NAS message exceeds the limit indicated by the first information, the access network device can send a notification message to the network element deployed on the ground (step 9a). The flow control method mentioned here and the content of the notification message can be referred to the description above and will not be repeated here.

[0425] In step 10, the access network device transmits the NAS message to the UE.

[0426] When the service link is available, the access network device transmits the NAS payload to the UE via an RRC message. When the access network device is deployed on a satellite, step 10 is performed after step 13.

[0427] In step 11, the AMF triggers the AN release procedure.

[0428] If there is no pending data or signaling and the AMF receives a NAS RAI indicating a single downlink data transmission, the AMF triggers the AN release procedure and the process shown in Figure 9 stops after this step.

[0429] In step 12, further activity detection is performed.

[0430] The access network device performs further activity detection. If the access network device does not detect further activity, the access network device triggers the AN release process when the service link is available, that is, executes step 13.

[0431] When the service link is available, the UE's logical NG-AP (S1-AP) is released.

[0432] Example 5 provides the execution method of data storage and forwarding and flow control under CIoT CP optimization, which makes up for the deficiencies in the relevant standards and enables satellites in store-and-forward mode to support CIoT CP optimization. Example 5 provides the timing of sending notification messages and the execution order and execution conditions of each process step for different network elements deployed on the satellite, so that the control plane-initiated uplink data transmission process under CIoT CP optimization can normally execute storage and / or forwarding and flow control in various network element deployment architectures.

[0433] In Examples 4 and 5, the storage and / or forwarding of signaling messages and user data, as well as flow control, are described using CIoT 5GS optimization as an example. The corresponding storage and / or forwarding and flow control execution mechanisms can also be used for CIoT EPS optimization. The corresponding 5GS network elements, such as AMF, SMF, and UPF, can be replaced with EPS network elements, such as MME, SGW, and PGW.

[0434] Example 6: Data Storage and / or Forwarding and Flow Control (EPS) under CIoT CP Optimization

[0435] The following uses the MO data transmission in the P-GW connected state under CIoT CP optimization as an example, and combines Figure 10 to illustrate the uplink data transmission, signaling storage and forwarding, and flow control in the satellite storage and forwarding mode of the EPS system.

[0436] It should be understood that the method provided in the embodiments of the present application can also be applied to other scenarios of EPS. For specific implementation methods, please refer to the methods in other scenarios provided in the embodiments of the present application.

[0437] The process shown in FIG10 may include steps 0 to 15 .

[0438] In step 0, the UE is in EPS connection management (ECM)-IDLE state.

[0439] In step 1, the UE sends a NAS message to the access network device.

[0440] The UE may establish an RRC connection with the access network device or send an RRC Early Data Request message and send an integrity-protected NAS PDU (NAS Data Packet) as part of it. The NAS PDU carries the EPS bearer ID and encrypted uplink data. For PDN connections of IP PDN type configured to support header compression, the UE shall apply header compression before encapsulating the data into the NAS message. The UE may also indicate in the NAS RAI in the NAS PDU whether no further uplink or downlink data transmission is expected, or whether only a single downlink data transmission is expected after this uplink data transmission (e.g., for uplink data confirmation or response).

[0441] This step may be performed when the service link is available. The access network device mentioned in this embodiment is deployed on a satellite, for example, it may be an eNodeB.

[0442] When the UE sends the above data or signaling, if it is configured with first information, such as flow control related parameters, it is necessary to determine whether the number of NAS data packets sent by the UE does not exceed the control plane signaling limit or the data flow limit. For details, please refer to step 1 of embodiment 4.

[0443] In step 1a, the access network device sends a notification message to the terminal device.

[0444] In some embodiments, the access network device may discard or refuse to receive data packets from the UE and send a notification message to inform the UE. The notification message may be used to indicate that the signaling and / or data sent by the UE exceeds the corresponding limit, thereby preventing the UE from continuously sending signaling and data to the satellite.

[0445] In other embodiments, the access network device may receive a data packet from the UE. For example, if sufficient storage space is available on the satellite and / or if there are message requests or uplink data from other UEs in the short term or at the same time, the access network device may store the data packet from the UE and update the corresponding first information. For example, the new first information may be configured for the UE in a notification message.

[0446] If the satellite stores signaling messages or data exceeding the limit, or the data from the UE does not exceed the limit indicated by the first information, step 1b is executed.

[0447] In step 1b, the access network device obtains UE related information.

[0448] In the NB-IoT scenario, the eNodeB can retrieve the EPS negotiated QoS profile from the MME (if not retrieved previously) according to the configuration. Before triggering step 2 and throughout the RRC connection, the eNodeB can apply priority between requests from different UEs.

[0449] If the MME is deployed on the ground, execute steps 1b to 11 when the feeder link is available. If the MME is deployed on the satellite, execute steps 1 to 3 when the service link is available, and execute steps 4 to 10 when the feeder link is available.

[0450] In step 2, the access network device forwards the NAS data packet to the MME.

[0451] The NAS PDU sent in step 1 may be relayed by the eNodeB to the MME using the S1-AP Initial UE message. If an RRC Early Data Request message is received in step 1, the eNodeB carries the EDT Session indication in the S1-AP Initial UE message.

[0452] In step 3, decryption and integrity protection.

[0453] The MME checks the integrity of the received NAS PDU and decrypts the data it contains. When robust header compression (ROHC) is configured, the MME shall decompress the IP header if header compression is applied to the PDN connection.

[0454] The following steps 4-7 are used to modify or establish a connection for data transmission.

[0455] In step 4, the MME sends a modify bearer request to the S-GW.

[0456] In step 5, the S-GW sends a modify bearer request to the P-GW.

[0457] In step 6, the P-GW sends a modify bearer response to the S-GW.

[0458] In step 7, the S-GW sends a modify bearer response to the MME.

[0459] In step 8, the MME sends uplink data to the P-GW through the S-GW.

[0460] If no downlink data is expected based on the NAS RAI indication from the UE in step 1, this means that all application layer data exchanges have completed UL data transmission, and if the MME is not aware of pending MT data and the S1-U bearer is not established, steps 9 and 10 are skipped and step 11 is executed. If downlink data arrives, step 9 is executed. If no data is received, steps 9-12 are skipped and the eNodeB may trigger step 14 after detecting no activity in step 13.

[0461] In step 9, the P-GW sends the downlink data to the MME through the S-GW.

[0462] If the first information is configured and the MME is deployed on a satellite, a determination is made as to whether the limit is exceeded before downlink data is sent to the MME. This determination is performed by the ground-based network elements of the P-GW and S-GW. If both the P-GW and S-GW are deployed on the ground, the S-GW may perform this determination. For details on how this determination is performed, see step 6c of Example 4.

[0463] Accordingly, when a functional entity on the satellite, such as an S-GW or MME, receives the downlink data, it needs to determine whether the limit is exceeded. If the limit is exceeded, the functional entity on the satellite sends a notification message to the ground network element.

[0464] When the P-GW and S-GW are deployed on the ground, if the downlink data exceeds the limit indicated by the first information, the MME sends a notification message to the S-GW, i.e., step 9a in Example 6. Optionally, in this case, the S-GW may forward the notification message to the P-GW, i.e., step 9b in Example 6.

[0465] When the P-GW is deployed on the ground and the S-GW is deployed on the satellite, if the downlink data exceeds the limit indicated by the first information, the S-GW may send a notification message to the P-GW. Optionally, before the S-GW sends the notification message to the P-GW, the S-GW may receive a notification message from the MME.

[0466] In step 10, the MME performs data encryption and integrity protection.

[0467] If downlink data is received in step 9, the MME ciphers and integrity protects the downlink data.

[0468] In step 11, the MME sends the downlink data to the access network device.

[0469] If step 10 is performed, the downlink data is encapsulated in a NAS PDU and sent to the eNodeB in an S1-AP downlink NAS message. If the configuration in the MME indicates that the eNodeB supports acknowledgment of downlink NAS data PDUs and if acknowledgment of downlink NAS data PDUs is enabled in the UE's subscription information, the MME indicates an acknowledgment request from the eNodeB in the S1-AP downlink NAS message. For PDN connections of type IP PDN configured to support header compression, the MME shall apply header compression before encapsulating the data in the NAS message.

[0470] If step 10 is not performed, or the NAS service accept message is not sent, the MME sends a connection establishment indication message to the eNodeB to complete the establishment of the logical S1 connection associated with the UE. The connection establishment indication message can be used to establish a logical connection between the AMF corresponding to a UE and the access network device. The message may contain information such as the UE radio capabilities and END indication.

[0471] If NAS Release Assistance Message is received along with uplink data and indicates that downlink data is required, this means that the next downlink data packet after sending the NAS Release Assistance Message is the last data packet of the application layer data exchange. In this case, unless the MME is aware of additional pending MT traffic and unless an S1-U bearer is established, the MME sends an S1 UE Context Release Command (UE Context Release Command) immediately following the S1-AP message, containing downlink data encapsulated in a NAS PDU, to indicate that the eNodeB should release the RRC connection immediately after successfully sending data to the UE. Alternatively, if an "EDT Session" indication is received in step 2, the MME may include an end indication for no further data in the S1-AP message, including the downlink data encapsulated in the NAS PDU.

[0472] If the MME includes an end indication indicating that there is no further data, and the eNodeB does not continue with the RRC connection establishment, the eNodeB skips step 12a and initiates step 12b.

[0473] If the received NAS release assistance message indicates that no downlink data is expected, meaning that all application layer data exchanges have completed UL data transfer, then for this case, unless the MME is aware of additional pending MT traffic and unless an S1-U bearer is established, then the following actions are taken:

[0474] -MME sends S1AP UE context release command:

[0475] - then after S1AP DL NAS TRANSPORT (NAS Service Accept), in which case steps 12b and 14 will be skipped, or

[0476] - after an S1AP connection establishment indication, in which case steps 12a, 12b, 13 and 14 are skipped;

[0477] Alternatively, if the MME receives an "EDT Session" indication from the eNodeB in step 2, the MME shall include an end indication with no further data in the S1AP DL NAS TRANSPORT (NAS Service Accept) or S1AP Connection Establishment Indication. If the eNodeB does not proceed with establishing the RRC connection, the eNodeB skips step 12a and initiates step 12b.

[0478] If the MME is deployed on the ground and the access network device is deployed on the satellite, then step 11 is executed when the feeder link is available. In addition, before the MME sends a message to the access network device, it needs to determine whether the limit indicated by the first information is exceeded. Correspondingly, when the access network device receives the message sent by the MME, it also needs to determine whether the limit indicated by the first information is exceeded. For specific execution methods, please refer to step 6c of Example 4. If the access network device determines that the message sent by the MME exceeds the limit indicated by the first information, then the access network device can send a notification message to the MME. The notification message can be executed immediately as a new signaling message after step 11 (such as step 11a of Example 6), or it can be carried in the message of step 13.

[0479] In step 12a, the access network device sends downlink data to the UE.

[0480] The eNodeB sends an RRC Downlink Data message containing the downlink data encapsulated in a NAS PDU. If, in step 11, the S1-AP message with the NAS Data PDU is followed by an S1UE Context Release Command, then step 15 is completed immediately after sending the downlink data NAS PDU to the UE and an acknowledgement to the MME. The eNodeB does not need to proceed to step 14. If header compression is applied by the PDN, the UE will perform header decompression to reconstruct the IP header.

[0481] In step 12b, the access network device sends an RRC early data complete message to the UE.

[0482] If an end indication of no further data is received in the S1AP message from the MME, the eNodeB may send an RRC Early Data Complete message (NAS Data PDU or NAS Service Accept) with any NAS payload received from step 11. In this case, step 14 will be skipped.

[0483] In step 13, the access network device sends a delivery notification message to the MME.

[0484] In the case of requesting the eNodeB to send a NAS delivery indication to the MME, if the eNodeB reports unsuccessful delivery through the S1-AP NAS non-delivery indication, the MME should wait for a period of time until the UE may change cells and re-establish contact with the MME, at which time the MME should resend the downlink S1-AP message to the eNodeB, otherwise in the case of the T6a procedure, the MME reports the unsuccessful delivery to the SCEF. If the eNodeB reports successful delivery through the S1-AP NAS delivery indication and if downlink data is received over the T6a interface, the MME should respond to the SCEF.

[0485] If the eNodeB does not support S1-AP NAS delivery indication, the MME indicates the cause code "Successful Unconfirmed Delivery" to the SCEF, otherwise it indicates "Successful Confirmed Delivery" so that the SCEF knows whether reliable delivery is possible.

[0486] In step 14, further activity detection is performed.

[0487] The access network device performs further activity detection. If the access network device does not detect further activity, the access network device triggers the S1 release process, that is, executes step 15.

[0488] In step 15, the access network device or MME triggers the S1 release process.

[0489] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 10. The device embodiment of the present application is described in detail below in conjunction with Figures 11 to 13. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0490] FIG11 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device shown in FIG11 may be the first device mentioned above. The communication device 1100 may include: a determining unit 1110 .

[0491] The determining unit 1110 is configured to determine first information, where the first information is associated with the transmission of second information, where the second information includes signaling and / or data stored and / or forwarded via a satellite.

[0492] In some embodiments, the first information includes one or more of the following: a storage limit, used to indicate the maximum amount of signaling and / or data stored by the satellite; a storage time, used to indicate the maximum time for the satellite to store signaling and / or data; a priority, used to determine the order in which the satellite stores and / or forwards multiple pieces of second information; a total traffic limit, used to indicate the maximum total amount of signaling and data transmitted by the satellite per unit time; a control plane signaling limit, used to indicate the maximum amount of control plane signaling transmitted by the satellite per unit time; and a user plane data limit, used to indicate the maximum amount of user plane data transmitted by the satellite per unit time.

[0493] In some embodiments, the configuration granularity of the first information includes one or more of the following: device granularity; service type granularity; user granularity; protocol data unit (PDU) session granularity; quality of service (QoS) flow granularity; and service flow granularity.

[0494] In some embodiments, the determination unit is used to determine the first information based on one or more of the following: pre-configuration information; subscription message; storage space usage of the satellite; load status of the satellite; request message of the first device; available time of the service link of the satellite; and available time of the feeder link of the satellite; wherein the request message of the first device is used to request the first information expected by the first device.

[0495] In some embodiments, the request message includes one or more of the following: a device identifier of the first device; address information of the first device; the requested priority; the requested storage limit; the requested storage time; the requested total traffic limit; the requested control plane signaling limit; and the requested user plane data limit.

[0496] In some embodiments, the signing message is stored in a device deployed on the ground.

[0497] In some embodiments, the first information further includes one or more of the following: first indication information; validity period of part or all of the information in the first information; device identification of the device associated with the first information; device address of the device associated with the first information; and description information of the service flow associated with the first information; wherein the first indication information is used to indicate that the satellite is in storage and forwarding mode.

[0498] In some embodiments, the validity period of part or all of the first information is determined based on the ephemeris information of the satellite.

[0499] In some embodiments, the first information is updated based on one or more of the following: expiration of the validity period of some or all of the information in the first information; an update request message from the first device; establishment of a connection between the first device and the satellite; and the amount of signaling and / or data in the second information exceeds the limit indicated by the first information.

[0500] In some embodiments, the device further includes: an execution unit, configured to cause the first device to execute one or more of the following if the amount of signaling and / or data in the second information exceeds the limit indicated in the first information: suspending the generation or delaying the sending of the second information; and sending an update request message for the first information.

[0501] In some embodiments, the device further includes: a receiving unit configured to receive a notification message sent by a second device, wherein the notification message is configured to indicate that the amount of signaling and / or data in the second information exceeds a limit indicated in the first information.

[0502] In some embodiments, the second information is one or more of the following: radio resource control RRC message; downlink signaling and / or data; uplink signaling and / or data; non-access stratum NAS signaling message, or NAS data packet carried in RRC early data request or RRC connection establishment message; and downlink NAS transmission information.

[0503] In some embodiments, the first device is a terminal device, or the first device is a network element or server deployed on the ground.

[0504] In some embodiments, the first device is any one of the following: mobility management entity MME; access and mobility management function AMF; session management function SMF; service gateway SGW; packet data network gateway PGW; home user server HSS; authentication service function AUSF; unified data management UDM; network data analysis function NWDAF; Internet protocol multimedia service IMS server; and application function AF.

[0505] In some embodiments, the second device is deployed on the satellite.

[0506] In some embodiments, the second device is any one of the following: access network device; MME; AMF; SMF; SGW; PGW; HSS; AUSF; UDM; NWDAF; IMS server; and AF.

[0507] FIG12 is a schematic diagram of another communication device according to an embodiment of the present application. The communication device 1200 shown in FIG12 may be the second device mentioned above, and includes: a first sending unit 1210 .

[0508] The first sending unit 1210 is configured to send first information to a first device, where the first information is associated with transmission of second information, where the second information includes signaling and / or data stored and / or forwarded via a satellite.

[0509] In some embodiments, the first information includes one or more of the following: a storage limit, used to indicate the maximum amount of signaling and / or data stored by the satellite; a storage time, used to indicate the maximum time for the satellite to store signaling and / or data; a priority, used to determine the order in which the satellite stores and / or forwards multiple pieces of second information; a total traffic limit, used to indicate the maximum total amount of signaling and data transmitted by the satellite per unit time; a control plane signaling limit, used to indicate the maximum amount of control plane signaling transmitted by the satellite per unit time; and a user plane data limit, used to indicate the maximum amount of user plane data transmitted by the satellite per unit time.

[0510] In some embodiments, the configuration granularity of the first information includes one or more of the following: device granularity; service type granularity; user granularity; protocol data unit (PDU) session granularity; quality of service (QoS) flow granularity; and service flow granularity.

[0511] In some embodiments, the first information is determined based on one or more of: pre-configuration information; subscription message; storage space usage of the satellite; load status of the satellite; request message of the first device; available time of the service link of the satellite; and available time of the feeder link of the satellite; wherein the request message of the first device is used to request the first information desired by the first device.

[0512] In some embodiments, the request message includes one or more of the following: a device identifier of the first device; address information of the first device; the requested priority; the requested storage limit; the requested storage time; the requested total traffic limit; the requested control plane signaling limit; and the requested user plane data limit.

[0513] In some embodiments, the signing message is stored in a device deployed on the ground.

[0514] In some embodiments, the first information further includes one or more of the following: first indication information; validity period of part or all of the information in the first information; device identification of the device associated with the first information; device address of the device associated with the first information; and description information of the service flow associated with the first information; wherein the first indication information is used to indicate that the satellite is in storage and forwarding mode.

[0515] In some embodiments, the validity period of part or all of the first information is determined based on the ephemeris information of the satellite.

[0516] In some embodiments, the first information is updated based on one or more of the following: expiration of the validity period of some or all of the information in the first information; an update request message from the first device; establishment of a connection between the first device and the satellite; and the amount of signaling and / or data in the second information exceeds the limit indicated by the first information.

[0517] In some embodiments, the device further includes: a first processing unit configured to cause the second device to discard or delete part or all of the second information if the amount of signaling and / or data in the second information exceeds a limit indicated in the first information.

[0518] In some embodiments, the device further includes: a second processing unit, configured to store the second information and / or update the first information if the amount of signaling and / or data in the second information exceeds the limit indicated in the first information, when there is remaining storage space in the satellite.

[0519] In some embodiments, the device further includes: a second sending unit, configured to send a notification message to the first device, wherein the notification message is configured to indicate that the amount of signaling and / or data in the second information exceeds a limit indicated in the first information.

[0520] In some embodiments, the second information is one or more of the following: radio resource control RRC message; downlink signaling and / or data; uplink signaling and / or data; non-access stratum NAS signaling message, or NAS data packet carried in RRC early data request or RRC connection establishment message; and downlink NAS transmission information.

[0521] In some embodiments, the first device is a terminal device, or the first device is a network element or server deployed on the ground; and / or the second device is deployed on the satellite.

[0522] In some embodiments, the first device is any one of the following: mobility management entity MME; access and mobility management function AMF; session management function SMF; service gateway SGW; packet data network gateway PGW; home user server HSS; authentication service function AUSF; unified data management UDM; network data analysis function NWDAF; Internet protocol multimedia service IMS server; and application function AF.

[0523] In some embodiments, the second device is any one of the following: access network device; MME; AMF; SMF; SGW; PGW; HSS; AUSF; UDM; NWDAF; IMS server; and AF.

[0524] Figure 13 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 13 indicate that the unit or module is optional. Apparatus 1300 may be used to implement the method described in the above method embodiment. Apparatus 1300 may be a chip, a terminal device, or a network device.

[0525] The device 1300 may include one or more processors 1310. The processor 1310 may support the device 1300 to implement the method described in the method embodiment above. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0526] The apparatus 1300 may further include one or more memories 1320. The memories 1320 store programs that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the above method embodiments. The memories 1320 may be independent of the processor 1310 or integrated into the processor 1310.

[0527] The apparatus 1300 may further include a transceiver 1330. The processor 1310 may communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 may transmit and receive data with other devices or chips via the transceiver 1330.

[0528] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0529] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

[0530] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method executed by the communication device in each embodiment of the present application.

[0531] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0532] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0533] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0534] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0535] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0536] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0537] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0538] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0539] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0540] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0541] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0542] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0543] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that, Including: A first device determines first information, which is associated with the transmission of second information, and the second information includes signaling and / or data stored and / or relayed via a satellite.

2. The method according to claim 1, wherein The first information includes one or more of the following: A storage limit, which is used to indicate the maximum quantity of signaling and / or data stored by the satellite; A storage time, which is used to indicate the longest time for which the satellite stores signaling and / or data; A priority, which is used to determine the order in which the satellite stores and / or relays multiple pieces of the second information; An overall traffic limit, which is used to indicate the maximum value of the total quantity of signaling and data transmitted by the satellite per unit time; A control plane signaling limit, which is used to indicate the maximum value of the quantity of the control plane signaling transmitted by the satellite per unit time; And A user plane data limit, which is used to indicate the maximum value of the quantity of the user plane data transmitted by the satellite per unit time.

3. The method according to claim 2, characterized in that The configuration granularity of the first information includes one or more of the following: Device granularity; Service type granularity; User granularity; Protocol data unit (PDU) session granularity; Quality of service (QoS) flow granularity; and Traffic flow granularity.

4. The method according to claim 2 or 3, characterized in that, The first device determines the first information, including: The first device determines the first information based on one or more of the following: Pre-configured information; Subscription messages; The usage of the storage space of the satellite; The load status of the satellite; A request message of the first device; The available time of the service link of the satellite; and The available time of the feeder link of the satellite; Wherein, the request message of the first device is used to request the first information desired by the first device.

5. The method according to claim 4, characterized in that The request message includes one or more of the following: The device identifier of the first device; The address information of the first device; The requested priority; The requested storage limit; The requested storage time; The requested overall traffic limit; The requested control plane signaling limit; And The requested user plane data limit.

6. The method according to claim 4 or 5, characterized in that The subscription message is stored in a device deployed on the ground.

7. The method according to any one of claims 2-6, characterized in that The first information further includes one or more of the following: First indication information; The validity period of some or all of the information in the first information; The device identifier of the device associated with the first information; The device address of the device associated with the first information; and The description information of the traffic flow associated with the first information; Wherein, the first indication information is used to indicate that the satellite is in the storage and relay mode.

8. The method according to claim 7, wherein The validity period of some or all of the information in the first information is determined based on the ephemeris information of the satellite.

9. The method according to any one of claims 1-8, characterized in that, The first information is updated based on one or more of the following: The expiration of the validity period of some or all of the information in the first information; An update request message of the first device; The first device establishes a connection with the satellite; and The signaling and / or data in the second information exceed the limit indicated by the first information.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: If the signaling and / or data in the second information exceed the limit indicated in the first information, the first device performs one or more of the following: Suspending the generation or delaying the transmission of the second information; and Sending an update request message of the first information.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: The first device receives a notification message sent by the second device, where the notification message is used to indicate that the signaling and / or data in the second information exceeds the limit indicated in the first information.

12. The method according to claim 10 or 11, characterized in that The second information is one or more of the following: Radio Resource Control (RRC) message; Downlink signaling and / or data; Uplink signaling and / or data; Non-Access Stratum (NAS) signaling message, or a NAS data packet carried in an RRC early data request or an RRC connection establishment message; And Downlink NAS transmission information.

13. The method according to any one of claims 1 to 12, characterized in that, The first device is a terminal device, or the first device is a network element or a server deployed on the ground.

14. The method according to claim 13, wherein The first device is any one of the following: Mobility Management Entity (MME); Access and Mobility Management Function (AMF); Session Management Function (SMF); Serving Gateway (SGW); Packet Data Network Gateway (PGW); Home Subscriber Server (HSS); Authentication Server Function (AUSF); Unified Data Management (UDM); Network Data Analytics Function (NWDAF); Network Protocol Multimedia Service (IMS) server; And Application Function (AF).

15. The method according to claim 11, wherein The second device is deployed on the satellite.

16. The method according to claim 15, wherein The second device is any one of the following: access network device; MME; AMF; SMF; SGW; PGW; HSS; AUSF; UDM; NWDAF; IMS server; and AF.

17. A wireless communication method, characterized in that, Including: The second device sends first information to the first device, where the first information is associated with the transmission of the second information, and the second information includes signaling and / or data stored and / or forwarded via the satellite.

18. The method according to claim 17, characterized in that, The first information includes one or more of the following: Storage limit, used to indicate the maximum quantity of signaling and / or data stored by the satellite; Storage time, used to indicate the longest time for which the satellite stores signaling and / or data; Priority, used to determine the order in which the satellite stores and / or forwards multiple pieces of the second information; Total traffic limit, used to indicate the maximum value of the total quantity of signaling and data transmitted by the satellite per unit time; Control plane signaling limit, used to indicate the maximum value of the quantity of control plane signaling transmitted by the satellite per unit time; And User plane data limit, used to indicate the maximum value of the quantity of user plane data transmitted by the satellite per unit time.

19. The method according to claim 18, wherein The configuration granularity of the first information includes one or more of the following: Device granularity; Service type granularity; User granularity; Protocol Data Unit (PDU) session granularity; Quality of Service (QoS) flow granularity; and Traffic flow granularity.

20. The method according to claim 18 or 19, characterized in that, The first information is determined based on one or more of the following: Pre-configured information; Subscription message; The storage space usage of the satellite; The load status of the satellite; The request message of the first device; The available time of the service link of the satellite; And The available time of the feeder link of the satellite; Wherein, the request message of the first device is used to request the first information desired by the first device.

21. The method according to claim 20, wherein The request message includes one or more of the following: The device identifier of the first device; The address information of the first device; The requested priority; The requested storage limit; The requested storage time; The requested total traffic limit; The requested control plane signaling limit; And The requested user plane data limit.

22. The method according to claim 20 or 21, characterized in that, The subscription message is stored in a device deployed on the ground.

23. The method according to any one of claims 18-22, characterized in that, The first information further includes one or more of the following: First indication information; The validity period of some or all of the information in the first information; The device identifier of the device associated with the first information; The device address of the device associated with the first information; and The description information of the traffic flow associated with the first information; Wherein, the first indication information is used to indicate that the satellite is in the store-and-forward mode.

24. The method according to claim 23, characterized in that The validity period of some or all of the information in the first information is determined based on the ephemeris information of the satellite.

25. The method according to any one of claims 17 - 24, characterized in that, The first information is updated based on one or more of the following: The validity period of some or all of the information in the first information expires; The update request message of the first device; The first device establishes a connection with the satellite; and The signaling and / or data in the second information exceed the limit indicated by the first information.

26. The method according to any one of claims 17-25, characterized in that, The method further includes: If the signaling and / or data in the second information exceed the limit indicated in the first information, the second device discards or deletes some or all of the information in the second information.

27. The method according to any one of claims 17 - 25, characterized in that, The method further includes: When there is remaining storage space in the satellite, if the signaling and / or data in the second information exceed the limit indicated in the first information, the second device stores the second information and / or updates the first information.

28. The method according to any one of claims 17 - 27, characterized in that The method further includes: The second device sends a notification message to the first device, and the notification message is used to indicate that the signaling and / or data in the second information exceed the limit indicated in the first information.

29. The method according to any one of claims 26-28, characterized in that, The second information is one or more of the following: Radio Resource Control (RRC) message; Downlink signaling and / or data; Uplink signaling and / or data; Non-Access Stratum (NAS) signaling message, or NAS data packet carried in the RRC early data request or RRC connection establishment message; And Downlink NAS transmission information.

30. The method according to any one of claims 17-29, characterized in that, The first device is a terminal device, or the first device is a network element or server deployed on the ground; and / or, the second device is deployed on the satellite.

31. The method according to claim 30, wherein The first device is any one of the following: Mobility Management Entity (MME); Access and Mobility Management Function (AMF); Session Management Function (SMF); Serving Gateway (SGW); Packet Data Network Gateway (PGW); Home Subscriber Server (HSS); Authentication Server Function (AUSF); Unified Data Management (UDM); Network Data Analytics Function (NWDAF); Network Protocol Multimedia Service (IMS) server; And Application Function (AF).

32. The method according to claim 30 or 31, wherein The second device is any one of the following: access network device; MME; AMF; SMF; SGW; PGW; HSS; AUSF; UDM; NWDAF; IMS server; and AF.

33. A communication device, characterized in that, The communication device is the first device, and the device includes: A determining unit, configured to determine first information, where the first information is associated with the transmission of second information, and the second information includes signaling and / or data stored and / or relayed via a satellite.

34. The apparatus according to claim 33, wherein, The first information includes one or more of the following: A storage quota, used to indicate the maximum quantity of signaling and / or data stored by the satellite; A storage time, used to indicate the maximum time for which the satellite stores signaling and / or data; A priority, used to determine the order in which the satellite stores and / or relays multiple pieces of the second information; An overall traffic quota, used to indicate the maximum value of the total quantity of signaling and data transmitted by the satellite per unit time; A control plane signaling quota, used to indicate the maximum value of the quantity of the control plane signaling transmitted by the satellite per unit time; And A user plane data quota, used to indicate the maximum value of the quantity of the user plane data transmitted by the satellite per unit time.

35. The device according to claim 34, characterized in that, The configuration granularity of the first information includes one or more of the following: Device granularity; Service type granularity; User granularity; Protocol data unit (PDU) session granularity; Quality of service (QoS) flow granularity; and Traffic flow granularity.

36. The device according to claim 34 or 35, characterized in that, The determining unit is configured to: Determine the first information based on one or more of the following: Pre-configured information; Subscription messages; The usage status of the storage space of the satellite; The load status of the satellite; A request message of the first device; The available time of the service link of the satellite; And The available time of the feeder link of the satellite; Wherein, the request message of the first device is used to request the first information desired by the first device.

37. The device according to claim 36, wherein The request message includes one or more of the following: The device identifier of the first device; The address information of the first device; The requested priority; The requested storage quota; The requested storage time; The requested overall traffic quota; The requested control plane signaling quota; And The requested user plane data quota.

38. The device according to claim 36 or 37, characterized in that, The subscription message is stored in a device deployed on the ground.

39. The device according to any one of claims 34 - 38, characterized in that, The first information further includes one or more of the following: First indication information; The validity period of some or all of the information in the first information; The device identifier of the device associated with the first information; The device address of the device associated with the first information; and The description information of the traffic flow associated with the first information; Wherein, the first indication information is used to indicate that the satellite is in the storage and relay mode.

40. The device according to claim 39, characterized in that, The validity period of some or all of the information in the first information is determined based on the ephemeris information of the satellite.

41. The device according to any one of claims 33-40, characterized in that, The first information is updated based on one or more of the following: The expiration of the validity period of some or all of the information in the first information; An update request message of the first device; The establishment of a connection between the first device and the satellite; and The signaling and / or data in the second information exceed the quota indicated by the first information.

42. The device according to any one of claims 33 - 41, characterized in that, The device further includes: An execution unit, configured to, if the signaling and / or data in the second information exceed the quota indicated in the first information, the first device performs one or more of the following: Suspend generating or delay sending the second information; and Send an update request message of the first information.

43. The device according to any one of claims 33 - 42, characterized in that, The device further includes: A receiving unit, configured to receive a notification message sent by a second device, where the notification message is used to indicate that the signaling and / or data in the second information exceeds the limit indicated in the first information.

44. The device according to claim 42 or 43, characterized in that, The second information is one or more of the following: Radio Resource Control (RRC) message; Downlink signaling and / or data; Uplink signaling and / or data; Non-Access Stratum (NAS) signaling message, or a NAS data packet carried in an RRC early data request or an RRC connection establishment message; And Downlink NAS transmission information.

45. The device according to any one of claims 33 - 44, characterized in that, The first device is a terminal device, or the first device is a network element or a server deployed on the ground.

46. The device according to claim 45, characterized in that, The first device is any one of the following: Mobility Management Entity (MME); Access and Mobility Management Function (AMF); Session Management Function (SMF); Serving Gateway (SGW); Packet Data Network Gateway (PGW); Home Subscriber Server (HSS); Authentication Server Function (AUSF); Unified Data Management (UDM); Network Data Analytics Function (NWDAF); Network Protocol Multimedia Service (IMS) server; And Application Function (AF).

47. The apparatus according to claim 43, characterized in that, The second device is deployed on the satellite.

48. The device according to claim 47, characterized in that, The second device is any one of the following: an access network device; MME; AMF; SMF; SGW; PGW; HSS; AUSF; UDM; NWDAF; IMS server; and AF.

49. A communication device, characterized in that, The communication device is the second device, and the device includes: A first sending unit, configured to send first information to a first device, where the first information is associated with the transmission of second information, and the second information includes signaling and / or data stored and / or forwarded via a satellite. The apparatus according to claim 49, characterized in that The first information includes one or more of the following: A storage limit, used to indicate the maximum quantity of signaling and / or data stored by the satellite; A storage time, used to indicate the longest time for which the satellite stores signaling and / or data; A priority, used to determine the order in which the satellite stores and / or forwards multiple pieces of the second information; A total traffic limit, used to indicate the maximum value of the total quantity of signaling and data transmitted by the satellite per unit time; A control plane signaling limit, used to indicate the maximum value of the quantity of control plane signaling transmitted by the satellite per unit time; And A user plane data limit, used to indicate the maximum value of the quantity of user plane data transmitted by the satellite per unit time.

51. The device according to claim 50, characterized in that, The configuration granularity of the first information includes one or more of the following: Device granularity; Service type granularity; User granularity; Protocol Data Unit (PDU) session granularity; Quality of Service (QoS) flow granularity; and Traffic flow granularity.

52. The device according to claim 50 or 51, characterized in that, The first information is determined based on one or more of the following: Pre-configured information; Subscription message; The storage space usage of the satellite; The load status of the satellite; The request message of the first device; The available time of the service link of the satellite; And The available time of the feeder link of the satellite; Wherein, the request message of the first device is used to request the first information desired by the first device.

53. The device according to claim 52, characterized in that, The request message includes one or more of the following: The device identifier of the first device; The address information of the first device; The requested priority; The requested storage limit; The requested storage time; The requested total traffic limit; The requested control plane signaling limit; And The requested user plane data limit.

54. The device according to claim 52 or 53, characterized in that, The subscribed message is stored in a device deployed on the ground.

55. The device according to any one of claims 50 - 54, characterized in that, The first information further includes one or more of the following: First indication information; The validity period of some or all of the information in the first information; The device identifier of the device associated with the first information; The device address of the device associated with the first information; and The description information of the traffic flow associated with the first information; Wherein, the first indication information is used to indicate that the satellite is in the store-and-forward mode.

56. The apparatus according to claim 55, wherein The validity period of some or all of the information in the first information is determined based on the ephemeris information of the satellite.

57. The device according to any one of claims 49-56, characterized in that, The first information is updated based on one or more of the following: The validity period of some or all of the information in the first information expires; The update request message of the first device; The first device establishes a connection with the satellite; and The signaling and / or data in the second information exceed the limit indicated by the first information.

58. The device according to any one of claims 49 - 57, characterized in that, The device further includes: A first processing unit, configured to discard or delete some or all of the information of the second information if the signaling and / or data in the second information exceed the limit indicated in the first information.

59. The device according to any one of claims 49 - 57, characterized in that, The device further includes: A second processing unit, configured to store the second information and / or update the first information if there is remaining storage space in the satellite and the signaling and / or data in the second information exceed the limit indicated in the first information.

60. The apparatus according to any one of claims 49 - 59, characterized in that, The device further includes: A second sending unit, configured to send a notification message to the first device, where the notification message is used to indicate that the signaling and / or data in the second information exceed the limit indicated in the first information.

61. The device according to any one of claims 58-60, characterized in that, The second information is one or more of the following: Radio Resource Control (RRC) message; Downlink signaling and / or data; Uplink signaling and / or data; Non-Access Stratum (NAS) signaling message, or, a NAS data packet carried in an RRC early data request or an RRC connection establishment message; And Downlink NAS transmission information.

62. The device according to any one of claims 49 - 61, characterized in that, The first device is a terminal device, or, the first device is a network element or server deployed on the ground; and / or, the second device is deployed on the satellite.

63. The apparatus according to claim 62, wherein, The first device is any one of the following: Mobility Management Entity (MME); Access and Mobility Management Function (AMF); Session Management Function (SMF); Serving Gateway (SGW); Packet Data Network Gateway (PGW); Home Subscriber Server (HSS); Authentication Server Function (AUSF); Unified Data Management (UDM); Network Data Analytics Function (NWDAF); Network Protocol Multimedia Service (IMS) server; And Application Function (AF).

64. The device according to claim 62 or 63, characterized in that, The second device is any one of the following: access network device; MME; AMF; SMF; SGW; PGW; HSS; AUSF; UDM; NWDAF; IMS server; and AF.

65. A communication device, characterized in that, It includes a memory and a processor. The memory is used for storing a program, and the processor is used for calling the program in the memory to execute the method according to any one of claims 1-16 or 17-32.

66. A communication device, characterized in that, It includes a processor for calling a program from a memory to execute the method according to any one of claims 1-16 or 17-32.

67. A chip, characterized in that, It includes a processor for calling a program from a memory such that a device installed with the chip executes the method according to any one of claims 1-16 or 17-32.

68. A computer-readable storage medium, characterized in that, A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1-16 or 17-32.

69. A computer program product, characterized in that, It includes a program that causes a computer to execute the method according to any one of claims 1-16 or 17-32.

70. A computer program, characterized in that, The computer program causes a computer to execute the method according to any one of claims 1-16 or 17-32.

Images