Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first network element receiving first information sent by a second network element, the first information comprising one or more of the following: state information of a first terminal device; context information of the first terminal device; security context information of the first terminal device; wherein the second network element is configured to perform mobility management on the terminal device.

Description

Wireless communication method and communication device Technical Field

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

[0002] In satellite communication scenarios, how to improve the communication quality of terminal equipment is a problem that needs to be solved.

[0003] Summary of the Invention

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

[0005] In a first aspect, a wireless communication method is provided, including: a first network element receives first information sent by a second network element, the first information including one or more of the following information: status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; wherein the second network element is used to perform mobility management on the terminal device.

[0006] According to a second aspect, a wireless communication method is provided, comprising: a second network element sends first information to a first network element, wherein the first information comprises one or more of the following information: status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; wherein the second network element is used to perform mobility management on the terminal device.

[0007] According to a third aspect, a wireless communication method is provided, including: a third network element receives second information sent by a first network element, the second information including one or more of the following information: subscription data of a second terminal device; security parameters related to authentication and authorization of the second terminal device; wherein the third network element is used to store the subscription data of the terminal device, the second terminal device is a terminal device that fails to register or attach to the second network element, the second network element is used to perform mobility management on the terminal device, and the second network element is associated with the third network element.

[0008] In a fourth aspect, a wireless communication method is provided, comprising: a first terminal device sends an attachment or registration request to a second network element, and the second network element is used to perform mobility management on the terminal device.

[0009] In a fifth aspect, a wireless communication method is provided, including: a first access network device sends broadcast information, the first access network device is located on a first satellite, and the broadcast information is used to indicate one or more of the following: an identifier of a terminal device served by the first satellite; an identifier of the first satellite.

[0010] In the sixth aspect, a communication device is provided, which is a first network element, and the communication device includes: a first communication module, used to receive first information sent by a second network element, the first information including one or more of the following information: status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; wherein the second network element is used to perform mobility management on the terminal device.

[0011] In the seventh aspect, a communication device is provided, which is a second network element, and the communication device includes: a first communication module, used to send first information to the first network element, the first information including one or more of the following information: status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; wherein the second network element is used to perform mobility management on the terminal device.

[0012] In an eighth aspect, a communication device is provided, which is a third network element, and the communication device includes: a first communication module, used to receive second information sent by the first network element, the second information including one or more of the following information: contract data of the second terminal device; security parameters related to authentication and authorization of the second terminal device; wherein, the third network element is used to store the contract data of the terminal device, the second terminal device is a terminal device that fails to register or attach to the second network element, the second network element is used to perform mobility management on the terminal device, and the second network element is associated with the third network element.

[0013] In a ninth aspect, a communication device is provided, which is a first terminal device, and the communication device includes: a first communication module, used to send an attachment or registration request to a second network element, and the second network element is used to perform mobility management on the terminal device.

[0014] In the tenth aspect, a communication device is provided, which is a first access network device, and the communication device includes: a first communication module for sending broadcast information, the first access network device is located on a first satellite, and the broadcast information is used to indicate one or more of the following: an identifier of a terminal device served by the first satellite; an identifier of the first satellite.

[0015] In the eleventh aspect, a communication device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes the method described in any one of the first to fifth aspects.

[0016] In a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to execute the method described in any one of the first to fifth aspects.

[0017] In the thirteenth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to execute the method described in any one of the first to fifth aspects.

[0018] In the fourteenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement the method described in any one of the first to fifth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1A shows a wireless communication system according to an embodiment of the present application.

[0020] FIG1B is a wireless communication system according to another embodiment of the present application.

[0021] FIG1C shows a wireless communication system according to another embodiment of the present application.

[0022] FIG2 is a flow chart of a wireless communication method provided by the related art.

[0023] FIG3 is an example diagram of a communication scenario to which embodiments of the present application can be applied.

[0024] FIG4 is a flowchart of a wireless communication method provided in an embodiment of the present application.

[0025] FIG5 is a flowchart of a wireless communication method provided in an embodiment of the present application.

[0026] FIG6 is a flowchart of a wireless communication method provided in an embodiment of the present application.

[0027] FIG7 is a flowchart of a wireless communication method provided in an embodiment of the present application.

[0028] FIG8 is a flowchart of a wireless communication method provided in an embodiment of the present application.

[0029] FIG9 is a flowchart of a wireless communication method provided in an embodiment of the present application.

[0030] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0031] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0032] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0033] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0034] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

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

[0036] Communication system architecture

[0037] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, non-terrestrial network (NTN) system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), wireless fidelity (WLAN), etc. fidelity, WiFi), fifth-generation communication (5G) systems or other communication systems, such as future communication systems, such as sixth-generation mobile communication systems, and satellite communication systems.

[0038] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, and the embodiments of the present application can also be applied to these communication systems.

[0039] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0040] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as a dedicated spectrum.

[0041] The embodiments of the present application can be applied to NTN systems as well as terrestrial networks (TN) systems. As an example and not a limitation, NTN systems include NR-based NTN systems and IoT-based NTN systems.

[0042] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, where the terminal device 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 communication device, user agent or user device, etc.

[0043] In an embodiment of the present application, the terminal device may be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a next-generation communication system such as a terminal device in an NR network, or a terminal device in a future-evolved public land mobile network (PLMN) network, etc.

[0044] In an embodiment of the present application, a terminal device may be 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 capabilities, an in-vehicle device, etc. The terminal device in the embodiment of the present application may 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 scheduling entity that provides sidelink signals between terminal devices in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. Cellular phones and smart home devices communicate with each other without relaying the communication signal through a base station.

[0045] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (for example, on an airplane, balloon, and satellite, etc.).

[0046] In the embodiments of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc. The terminal device involved in the embodiments of the present application may also be referred to as a terminal, user equipment (UE), an access terminal device, a vehicle-mounted terminal, an industrial control terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal device, a mobile device, a UE, a wireless communication device, a UE agent, or a UE device, etc. The terminal device may also be fixed or mobile.

[0047] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0048] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. 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 station MeNB, secondary station 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. The base station may also refer to a communication module, modem or chip provided in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, a network side device in a 6G network, a device that performs the base station function in a future communication system, etc. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.

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

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

[0051] The network equipment 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 the network equipment and terminal devices are located.

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

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

[0054] For example, Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1A, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or also referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices located within the coverage area.

[0055] Figure 1A exemplarily shows a network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[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, the communication system may include multiple network devices 1102, and each network device 1102 may include other numbers 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] Related art proposes a solution for a UE to perform an attach procedure in store and forward (S&F) mode when the MME and home subscriber server (HSS) are deployed on a satellite. The basic assumptions are as follows:

[0067] The eNB, MME, and HSS are placed on the same satellite;

[0068] The onboard eNB broadcasts that it is in S&F satellite operation mode;

[0069] The UE has subscription and credentials in the onboard HSS, and when the feeder link is available, the onboard HSS is synchronized with the terrestrial HSS;

[0070] Single-satellite deployment use case, where the UE accesses only one satellite, which maintains the UE's non-access stratum (NAS) and access stratum (AS) states;

[0071] Roaming is not supported.

[0072] Considering the above assumptions, regardless of the feeder link status, when the service link is available, the following process involving the eNB, MME, and HSS can be completed:

[0073] Negotiation between the UE and MME regarding the capability to support S&F satellite operations;

[0074] When the service link is available, identity verification and NAS security authentication can be completed.

[0075] Therefore, if the UE sets "Support attachment without packet data network (PDN) connection" in the preferred network behavior during the attachment procedure and the network has confirmed its support for the UE, the initial attachment procedure without PDN connection can be completed when the serving link is available.

[0076] If the UE also wants to establish a PDN connection during the attachment process, the related art proposes to attach the UE to the MME and complete the NAS process without establishing a general packet radio service tunneling protocol-control (GTP-C) tunnel between the MME and the serving gateway (SGW) / packet data network gateway (PGW) when the serving link is available. Once the feeder link is available, the GTP-C tunnel can be established. In this case, only cellular internet of things control plane optimization (CIoT CP optimization) is considered, and the PDN connection is optimized using only the control plane CIoT EPS, that is, the MME includes only the control plane PDN connection indicator in the create session request.

[0077] Figure 2 shows the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) attachment process in the S&F scenario of the MME and HSS being connected to a satellite. The specific process is as follows:

[0078] In step S202, when the serving link is available, the eNB broadcasts that it is in store-and-forward mode (S&F satellite operation mode).

[0079] In step S204, if the UE is capable of supporting the store-and-forward mode, it transmits an Attach Request message to the eNB to initiate the Attach procedure. In addition to the parameters specified in TS 23.401 Section 5.3.2.1, the UE also indicates its capability to support S&F satellite operations in the Attach Request message.

[0080] In step S206, the eNB forwards the Attach Request message to the MME in accordance with Section 5.3.2.1 of TS23.401. The MME checks whether the UE is capable of supporting S&F satellite operations, and if not, rejects the Attach Request with an appropriate cause value.

[0081] In step S208, authentication and NAS security procedures are performed in accordance with Section 5.3.2.1 of TS23.401.

[0082] In step S210, the MME sends an Attach Accept message to the eNB in ​​an S1 application protocol (S1-AP) Initial Context Setup Request message or a DL NAS transport message. In addition to the parameters specified in TS23.401 section 5.3.2.1, the MME indicates its ability to support S&F satellite operations in the Attach Accept message. The eNB then forwards the Attach Accept message to the UE. If the UE does not include an EPS session management (ESM) message container in the Attach Request in step S204, the following steps are skipped. If the UE has included an ESM message container in the Attach Request in step S204, the MME assigns an Evolved Packet System (EPS) bearer identifier for the default bearer associated with the UE. The EPS quality of service (QoS) information may be set to the default value received from the HSS.

[0083] In step S212, the UE sends an attach complete message to the MME.

[0084] In step S214, if the UE includes an ESM message container in the attach request in step S204, when the feeder link is available, the MME sends a create session request message and a modify bearer request message to the SGW in accordance with the provisions in section 5.3.2.1 of TS23.401.

[0085] In step S216, the SGW sends a create session request message and an adjust bearer request message to the PGW in accordance with section 5.3.2.1 of TS23.401.

[0086] In step S218, the PGW returns a create session request message and an adjust bearer request message to the SGW in accordance with section 5.3.2.1 of TS23.401.

[0087] In step S220, the SGW returns a create session request message and an adjust bearer request message to the MME in accordance with section 5.3.2.1 of TS23.401.

[0088] In step S222, downlink data may be sent from the S / PGW to the MME. The MME receives and stores the downlink data of the UE.

[0089] In step S224, when the service link is available, that is, when the satellite covers the tracking area where the UE is registered, the MME sends a paging message to the eNB. If the eNB receives the paging message from the MME, the UE is paged by the eNB.

[0090] In step S226, the UE establishes a radio bearer for downlink data transmission.

[0091] In step S228, an S1-MME path is established for downlink data transmission.

[0092] In step S230, the MME sends downlink data to the UE.

[0093] In step S232, the UE sends uplink data to the MME.

[0094] The above solution only provides an implementation method for the attachment process in a single-satellite deployment scenario, and does not address how the attachment process should be implemented in a multi-satellite deployment scenario. In addition, due to limited storage space on the satellite, it is impossible to store all UE subscription data in the HSS on the satellite. The HSS on each satellite needs to interact with the HSS deployed on the ground based on the target user group (target UE) being served to obtain the required UE subscription data. However, how the HSS on the satellite should synchronize with the HSS on the ground has not yet been resolved. For example, which UE subscription data should the HSS on the satellite and the HSS on the ground obtain during each interaction. For example, when the UE initiates an attachment request, if the satellite in the sky does not store the corresponding UE subscription data, how should it be handled? For example, when multiple satellites serve the UE, does the UE need to interact with each satellite to complete the attachment process? For example, how should the UE access stratum (AS) and non-access stratum (NAS) status on multiple satellites be synchronized? For example, when the UE detaches from the core network, how should the UE-related information stored on multiple satellites be released synchronously?

[0095] As shown in Figure 3, satellite companies or operators can deploy multiple satellites in S&F mode to serve terminal devices. Due to limited storage space on satellites, it is unrealistic to directly store the subscription data of all terminal devices in the HSS on each satellite, and this is difficult to manage and maintain. Therefore, it is more reasonable to store the subscription data of only one set of terminal devices on each satellite. The management of terminal device subscription data on satellites can be divided into two methods: static configuration and dynamic configuration:

[0096] Static configuration: Each satellite stores only the subscription data of a specific set of terminal devices, and these satellites only serve this specific set of terminal devices.

[0097] Dynamic configuration: A terminal device can be served by each satellite. The satellite needs to interact with the HSS deployed on the ground in a timely manner to obtain the required terminal device subscription data.

[0098] Furthermore, when multiple satellites serve the same terminal device, the terminal device can register with the network through only one satellite. However, the terminal device's AS and NAS states are maintained only on the satellite with which it interacts. To support multiple satellites serving a single terminal device, either the terminal device must register with each satellite or each satellite must synchronize the terminal device's AS and NAS states, as well as the terminal device context.

[0099] To address one or more of the above-mentioned issues, embodiments of the present application propose deploying a new network element on the ground. This embodiment of the present application refers to this new network element as a first network element. This first network element can be used to store one or more of the following information: terminal device subscription data, terminal device authentication information, terminal device context, and terminal device status information (AS / NAS status).

[0100] For example, when the connection between the satellite and the network element is available, the first network element can record the AS / NAS status information of the terminal device that has completed registration on the satellite, and when other satellites pass over the first network element and establish a connection with the first network element, synchronize the AS / NAS status information of the terminal device that has completed registration recorded by the first network element, and store the context, subscription data, security context (for example, authentication vector), etc. of the terminal device on the satellite (if the above information is not stored on the satellite).

[0101] In some implementations, the first network element may also be referred to as a local subscription server (LSS) to distinguish it from an HSS deployed on a satellite. The first network element may be an enhanced HSS deployed on the ground, or a network entity deployed on the ground with MME functions and HSS functions. The first network element may be a network element in a 5G system, such as a unified data management (UDM) / unified data repository (UDR), or AMF+UDM / UDR.

[0102] In addition, in some implementations, the first network element may also store satellite ephemeris information.

[0103] Based on the introduction of the above-mentioned first network element, the wireless communication method provided in the embodiment of the present application is described in detail below in conjunction with Figure 4.

[0104] Figure 4 is a flow chart of the wireless communication method provided in an embodiment of the present application. The method in Figure 4 is described from the perspective of the interaction between the first network element and the second network element. The first network element can refer to the description above. The second network element is used to perform mobility management on the terminal device, for example, the second network element is an MME or AMF. The second network element can be deployed on a satellite, or the second network element can be a functional entity on a satellite (the satellite mentioned in each embodiment of the present application can also be replaced by other types of non-ground equipment).

[0105] Referring to Figure 4, in step S410, a first network element receives first information related to a first terminal device from a second network element. The first terminal device may be a terminal device that has been registered or attached to the second network element. Alternatively, the first terminal device may be a terminal device that has transitioned from an unregistered or unattached state to a registered or attached state.

[0106] The first information may be information related to the first terminal device stored or maintained by the second network element after the first terminal device registers or attaches to the second network element. For example, the first information may include one or more of the following information: status information of the first terminal device, context information of the first terminal device, and security context information of the first terminal device.

[0107] In some implementations, the status information of the first terminal device may indicate the AS and / or NAS status of the first terminal device. For example, the status information of the first terminal device may indicate that the first terminal device is in one or more of the following states: EMM-REGISTERED, EMM-DEREGISTERED, ECM_IDLE, or ECM_CONNECTED. For another example, the status information of the first terminal device may indicate that the first terminal device is in one or more of the following states: RM-DEREGISTERED, RM-REGISTERED, CM_IDLE, or CM_CONNECTED.

[0108] In some implementations, the context information (UE context) of the first terminal device may, for example, include an identifier for paging the first terminal device, such as a 5G globally unique temporary UE identity (5G-GUTI).

[0109] In some implementations, the security context information of the first terminal device may include AS security context information and / or NAS security context information. Exemplarily, the security context information of the first terminal device includes one or more security-related parameters such as one or more keys, encryption algorithms, and security capabilities of the first terminal device.

[0110] In some implementations, taking the example of the first network element being located on the ground and the second network element being located on a satellite, step S410 may be performed when the feeder link is available. Accordingly, the first terminal device may be a terminal device that registers with the second network element when the service link is available.

[0111] In some implementations, the first network element may send the second information to a third network element. The third network element is configured to store the subscription data of the terminal device. The third network element may be located on a satellite. In some implementations, the third network element and the second network element may be the same network element, or the third network element may be replaced by the second network element. The third network element may, for example, be a mobility management network element, such as an MME or AMF. In other implementations, the third network element may also be an HSS on the satellite. The second information may be used to update the subscription data stored on the third network element.

[0112] The second information may include one or more of the following:

[0113] contract data of the second terminal device;

[0114] Security parameters related to authentication and authorization of the second terminal device.

[0115] The second terminal device mentioned above is a terminal device that failed to register or attach to the second network element. The reason for the second terminal device's registration or attachment failure may be that the third network element does not store the second terminal device's subscription data and / or security parameters related to authentication and authorization. In this case, the third network element can obtain the second terminal device's subscription data and / or security parameters related to authentication and authorization through the first network element.

[0116] In some implementations, the first network element may send the first information when a feeder link of the satellite is available.

[0117] In some implementations, the second information may be sent based on a request. For example, before the first network element sends the second information to the third network element, the first network element receives third information sent by the third network element. The third information is used to request the second information.

[0118] In some implementations, the third information may include one or more of the following:

[0119] The identifier of the second terminal device;

[0120] The identifier of the satellite where the third network element is located;

[0121] The area in which the second terminal device is located when it initiates the attach request or registration request, such as a tracking area indicator (TAI), cell ID, or latitude and longitude information. This area may be provided by the first terminal device or determined by the satellite based on the coverage area or service area when the attach or registration request is received from the first terminal device;

[0122] The duration that the second terminal device stays in the area.

[0123] In some implementations, a first access network device (which may be located on the same satellite as the second network element mentioned above, hereinafter referred to as the first satellite) sends broadcast information. Accordingly, the first terminal device receives the broadcast information from the first network device. For example, when the service link between the first terminal device and the first access network device is available, the first terminal device receives the broadcast information from the first network device.

[0124] The broadcast information may be used to indicate one or more of the following: indication information (S&F satellite operation indication), indicating that the first satellite is in a storage and forwarding mode or that the first satellite supports a storage mode; an identifier of a terminal device served by the first satellite; an identifier of the first satellite.

[0125] In some implementations, before step S410, the first terminal device sends an attach or registration request to the second network element. This step may be performed when a service link to the satellite on which the second network element resides is available. Step S410 may be performed under certain conditions, for example, when the first terminal device supports store-and-forward mode.

[0126] The first terminal device may send an attachment or registration request to all satellites, or the first terminal device may send an attachment or registration request only to a satellite that provides service for the first terminal device (such as the satellite where the second network element is located). If the first terminal device sends an attachment or registration request only to a satellite that provides service for the first terminal device, the first terminal device may identify a satellite as a satellite that provides service for the first terminal device in the following manner:

[0127] Method 1: The first terminal device is locally configured with serving satellite identification information (serving satellite ID list). If the satellite identification monitored by the first terminal device from the broadcast message of the first satellite belongs to the locally pre-configured serving satellite ID list, the first terminal device determines that the first satellite is the serving satellite.

[0128] Method 2: The first terminal device monitors the identification of the first terminal device or the identification information of the group to which the first terminal device belongs through the first satellite (the satellite can broadcast the identification of the terminal device or terminal device group it serves through broadcast information).

[0129] Method 3: The first terminal device receives a serving satellite ID list (the satellite ID list mentioned in the embodiment of the present application may also be referred to as or replaced by a satellite ID set) sent by the second network element, and the first terminal device determines that the first satellite is the satellite providing service for it. The satellite ID list may be sent by the second network element to the first terminal device in a downlink NAS message. The downlink NAS message mentioned here may include one or more of the following: attach reject message, attach request message, attach accept message, service accept message, tracking area update accept (TAU accept) message, registration accept message, registration reject message, PDU session establishment accept message, etc. The first terminal device may determine the satellite that can provide service for it (or the satellite that can provide service for it next) based on the satellite ID list. The satellites in the satellite ID list may be satellites that store one or more of the following information: the context of the first terminal device, the subscription message of the first terminal device, and the security context of the first terminal device (such as authentication vector and / or security key, etc.). After receiving the downlink NAS message, the first terminal device may send an uplink NAS message (such as the next uplink NAS message) only to the satellites in the satellite identification list. The uplink NAS message mentioned here may include one or more of the following: attach request message, registration request message, service request message, TAU request message, PDU session establishment request message, etc. The first terminal device may send an uplink NAS message before receiving the downlink NAS message. The downlink NAS message may correspond to the uplink NAS message. For example, the downlink NAS message may be an attach reject message, an attach request message or an attach accept message, and the uplink NAS message may be an attach request message. For another example, the downlink NAS message may be a service accept message, and the uplink NAS message may be a service request message.For another example, the downlink NAS message may be a registration accept message or a registration reject message, and the uplink NAS message may be a registration request message. For another example, the downlink NAS message may be a TAU accept message, and the uplink NAS message may be a TAU request message. For another example, the downlink NAS message may be a PDU session establishment accept message or a PDU session establishment accept message, and the uplink NAS message may be a PDU session establishment request message. In some implementations, the second network element may also provide one or more of the following information when providing the satellite identifier list: the valid time and applicable area of ​​the satellite identifier list. The applicable area of ​​the satellite identifier list may include one or more of the following: the registration area of ​​the first terminal device, the first area (the first area may be associated with one or more of the following (or determined based on one or more of the following): PLMN ID, TAI, cell ID). After receiving the valid time and / or applicable area of ​​the satellite identifier list, the first terminal device may use the satellite identifier list within the valid time and / or applicable area.

[0130] In some implementations, the attach or registration request sent by the first terminal device may include one or more of the following information:

[0131] Indication information (S&F satellite operation indication), indicating whether the first terminal device supports the storage mode;

[0132] The identifier of the first terminal device, such as subscription permanent identifier (SUPI), subscription concealed identifier (SUCI), permanent equipment identifier (PEI), temporary mobile subscriber identity (TMSI), GUTI, 5G-S-TMSI or globally unique AMF identifier (GUAMI);

[0133] An identifier of the group to which the first terminal device belongs;

[0134] The identifier of the service satellite of the first terminal device, where the satellite identifier may refer to a single satellite identifier or a group of satellite identifiers.

[0135] In some implementations, the first terminal device receives response information to the attachment or registration request, where the response information is used to indicate acceptance of the attachment or registration request of the first terminal device.

[0136] In some implementations, the first terminal device receives a response message to the attachment or registration request, where the response message indicates a rejection of the attachment or registration request of the first terminal device. The response message may include one or more of the following:

[0137] A reason for rejecting the attachment or registration of the first terminal device (for example, the reason may include that the third network element does not store the subscription data of the first terminal device and / or security parameters related to authentication and authorization. The third network element mentioned here may be located on a satellite (e.g., on the same satellite as the second network element). In some implementations, the third network element and the second network element may be the same network element, or the third network element may be replaced by the second network element. The third network element may be, for example, a mobility management network element, such as an MME or an AMF. In other implementations, the third network element may also be an HSS on a satellite);

[0138] an identifier of the first terminal device;

[0139] The identifier of the satellite where the second network element is located.

[0140] In some implementations, after receiving the attach complete message, the first terminal device may report the area in which it is located and / or the expected stay time of the first terminal device in the area. The above information may be sent, for example, when the second network element rejects the attach request of the first terminal device.

[0141] The following describes the embodiments of the present application in more detail with reference to specific examples. In the example of Figure 5, the first network element mentioned above is the LSS on the ground, the second network element, the third network element and the first access network are the MME, HSS, and eNB deployed on the same satellite, and the first terminal device is the UE. It should be noted that the example of Figure 5 is only to help those skilled in the art understand the embodiments of the present application, and is not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the example of Figure 5, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0142] In this example, when the service link is available, the UE interacts with the satellite to complete the attachment process, and when the feeder link is available, the satellite interacts with the ground station to complete the synchronization of UE status information, context information and subscription data.

[0143] As shown in Figure 5, the UE can interact with the satellite to complete the attachment process based on the satellite's broadcast information when the service link is available. The terminal device can complete the attachment without PDN connectivity in the following two situations. First: the UE initiates an attachment request, and the HSS on the satellite happens to store the UE's subscription data, authentication and authorization-related security parameters (such as authentication vectors, security keys); Second: the UE learns from the satellite's broadcast message that this satellite is the satellite that serves its terminal device group, that is, the satellite stores the necessary information required for the UE to complete the attach without PDN connectivity, thereby initiating the attachment process. The specific process of Figure 5 is as follows:

[0144] In step S502, when the service link between the satellite and the UE is available, the satellite broadcasts one of the following messages to the target area:

[0145] aS&F satellite operation indication, indicating that the satellite is in store-and-forward mode, or that the satellite supports store-and-forward mode;

[0146] b. Satellite identification information;

[0147] c. UE group identifier or UE identifier information served by the satellite.

[0148] In step S504, if the UE supports the store-and-forward mode, the UE sends an attach request message to the satellite. The UE may send an attach request message to all satellites or only to the satellite that provides service to the UE. The UE may identify a satellite as providing service to the UE by:

[0149] a. The UE is locally configured with all the satellite identification information (serving satellite ID list) that serves it. When the UE monitors the satellite identification from the broadcast message, it is in the locally pre-configured serving satellite ID list.

[0150] b. Or the UE monitors its identification information or the identification information of the terminal device group to which it belongs.

[0151] The attach request message includes one or more of the following information:

[0152] a. Whether S&F satellite operation is supported;

[0153] b. UE identification information, such as SUPI, SUCI, PEI, TMSI, GUTI, 5G-S-TMSI, GUAMI, etc., used to identify the UE;

[0154] c. Group identification information, identification information of the terminal device group where the UE is located;

[0155] d. Satellite identification information, which may be identification information of the UE's serving satellite, may be a satellite identification or a group of satellite identifications.

[0156] In step S506, the access network device on the satellite sends an attach request message to the MME deployed on the satellite. The MME checks whether the UE is capable of supporting S&F satellite operations. If not, it rejects the attach request with an appropriate cause value.

[0157] In step S508, the UE interacts with the satellite network entity to complete the authentication and NAS security process. If the satellite HSS does not store the UE's subscription data and authentication and authorization security parameters (e.g., authentication vectors (AVs) and security keys), the process fails.

[0158] In step S510, the MME sends an attach accept message to the access network device in an S1-AP Initial Context Setup Request message or a DL NAS transport message. The MME indicates one or more of the following in the attach accept message: its ability to support S&F satellite operation, and a serving satellite ID list. In addition, when the attach accept message indicates a serving satellite ID list, the attach accept message may further indicate one or more of the following information of the serving satellite ID list: valid time, applicable area. The access network device then forwards the attach accept message to the UE. If the UE does not include an ESM message container in the attach request in step S504, the following steps are skipped. If the UE has included an ESM message container in the attach request in step S504, the MME allocates an EPS bearer identifier for the default bearer associated with the UE. The EPS QoS information may be set to the default value received from the HSS. If the authentication and NAS security procedures in step S508 fail to execute, the MME sends an attach reject message to the UE through the access network device, and the message includes one or more of the following information:

[0159] a.attach reject instruction;

[0160] b. Attach rejection reason, for example, the satellite does not store the UE-related subscription data and security parameters related to authentication and authorization;

[0161] c.UE identification information;

[0162] d. Satellite identification information;

[0163] e. Serving satellite ID list (may further include the valid time and / or applicable area of ​​the serving satellite ID list).

[0164] In step S512, the UE sends an attach complete message to the MME. If the UE receives an attach reject message, step S514 is not performed. Optionally, the UE may report the area information in which it is located and / or the expected stay time of the UE in the area.

[0165] In step S514, when the feeder link is available, the HSS on the satellite interacts with the LSS on the ground to update one or more of the UE-related subscription data and authentication and authorization-related security parameters stored in the HSS on the satellite. Specifically, the network entity (MME or HSS) on the satellite records the UE identifier that failed to attach due to the lack of valid UE-related subscription data and authentication and authorization-related security parameters. When the feeder link is available, the satellite interacts with the ground site to obtain the UE's subscription data and authentication and authorization-related security parameters from the LSS on the ground. For example, the HSS on the satellite can send a UE subscription data acquisition request to the LSS on the ground, and the request message includes one or more of the following information:

[0166] a.UE identification information;

[0167] b. Satellite identification information;

[0168] c. The area information where the UE is located when it initiates registration: TAI, cell ID or latitude and longitude information. The area information can be provided by the UE or derived by the satellite based on the coverage area or service area when receiving the UE's attachment request;

[0169] d. The UE's stay time in the area.

[0170] The LSS on the ground may record the information in the above request information (or may not record it), and send the requested UE subscription data, authentication and authorization-related security parameters to the HSS on the satellite.

[0171] In step S516, when the feeder link is available, the functional entity on the satellite may also send relevant information of the UE that has completed registration to the LSS deployed on the ground. The registered UE relevant information includes at least one of the following:

[0172] a.UE AS and NAS status information (e.g., UE is in ECM_IDLE state, UE is in EMM-REGISTERED state);

[0173] b. UE context (UE context); for example, including UE identity information GUTI used for paging.

[0174] c. Security context, such as AS security context and NAS security context; specifically, it may include some security-related parameters such as keys, encryption algorithms, and UE security capabilities.

[0175] It should be noted that the UE enters the EMM-REGISTERED state through a successful Attach procedure to E-UTRAN or GERAN / UTRAN. The MME enters the EMM-REGISTERED state through a successful Tracking Area Update procedure where the UE selects an E-UTRAN cell from GERAN / UTRAN or through an Attach procedure via E-UTRAN. In the EMM-REGISTERED state, the UE can receive services that require registration with the EPS.

[0176] It should also be noted that when there is no NAS signaling connection between the UE and the network, the UE is in the ECM-IDLE state.

[0177] It should also be noted that there is no strict order between step S514 and step S516.

[0178] In step S518, if the UE includes an ESM message container in the attach request in step S504, then when the feeder link is available, the MME sends a create session request message and an adjust bearer request message to the SGW.

[0179] In step S520, the SGW sends a create session request message and an adjust bearer request message to the PGW.

[0180] In step S522, the PGW returns a create session request response and an adjust bearer request response to the SGW.

[0181] In step S524, the SGW returns a create session request response and an adjust bearer request response to the MME.

[0182] In step S526, the downlink data may be sent from the S / PGW to the MME. The MME receives and stores the downlink data of the UE.

[0183] In step S528, when the service link is available, that is, when the satellite covers the tracking area where the UE is registered, the MME sends a paging message to the eNB. If the eNB receives the paging message from the MME, the UE is paged by the eNB.

[0184] In step S530, the UE establishes a radio bearer for downlink data transmission.

[0185] In step S532, an S1-MME path is established for downlink data transmission.

[0186] In step S534, the MME sends downlink data to the UE.

[0187] In step S536, uplink data may also be sent to the MME.

[0188] The example in Figure 5 illustrates how the satellite HSS and the ground-based LSS synchronize UE subscription data and security parameters. It also provides network processing flows for both cases where the satellite network function entity stores UE subscription and security parameters, and when it does not. In the example in Figure 5, the new LSS manages and maintains UE status information across the entire network. It also synchronizes UE subscription data and security parameters for the satellite HSS, enabling multiple satellites to serve the same UE without requiring the UE to repeatedly register with each satellite, improving the overall satellite network's service efficiency for UEs.

[0189] In some implementations, the first network element sends the first information mentioned above to the fourth network element. The fourth network element can be used to perform mobility management for the terminal device. For example, the fourth network element can be an MME, and the fourth network element does not store the first information. Exemplarily, the fourth network element and the second network element mentioned above can be deployed on two different satellites respectively. The satellite where the second network element is located can be called the first satellite, and the satellite where the fourth network element is located can be called the second satellite. That is, after the first network element obtains the status information, context information, etc. of the registered first terminal device from the first satellite, it can send the first information to the second satellite that does not store the first information. In this way, the first terminal device does not need to send an attachment or registration request to the mobility management network element on the second satellite again.

[0190] The first network element may send the first information to the fourth network element when the feeder link of the second satellite is available. In some implementations, the first network element stores the ephemeris information of the satellite, and the satellite where the fourth network element is located is determined based on the ephemeris information. For example, the first network element may determine, based on the ephemeris information, that the coverage area of ​​the second satellite (or the access network device of the second satellite) includes the registration area of ​​the first terminal device. In this case, the first network element may determine that the fourth network element may provide services for the first terminal device. Therefore, the first network element may send the first information to the fourth network element.

[0191] In some implementations, the first network element sends fourth information (including the subscription data of the first terminal device and / or security parameters related to the authentication and authorization of the first terminal device) to the fifth network element. The fifth network element is used to store the subscription data of the terminal device, and the fifth network element does not store the fourth information. For example, the second network element mentioned above is the MME located on the first satellite, and the fifth network element mentioned here is the HSS located on the second satellite. The first network element can determine that the coverage of the second satellite (or the access network device of the second satellite) includes the registration area of ​​the first terminal device based on the ephemeris information. In this case, the first network element can determine that the fifth network element may provide services for the first terminal device. Since the fifth network element does not store the subscription data of the first terminal device and / or the security parameters related to the authentication and authorization of the first terminal device, the first network element can send the fourth information to the fifth network element.

[0192] The embodiments of the present application are described in more detail below with reference to specific examples. In the example of Figure 6, the fourth network element and the fifth network element are MME and HSS respectively located on the same satellite (the satellite is different from the satellite where the first network element mentioned above is located), and the first terminal device is UE. It should be noted that the example of Figure 6 is only to help those skilled in the art understand the embodiments of the present application, and is not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the example of Figure 6 given, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0193] In the example of Figure 6, if the next satellite passing over the ground site where the data network is located (or the next satellite with an available feeder link) does not have UE status information, UE context information, subscription data, or security parameters, the LSS needs to interact with the HSS and MME on the satellite. In addition, if there is downlink data to be sent at this time, it is also necessary to send the data to the satellite when the feeder link is available, and store the data in the network entity on the satellite, waiting for the service link to become available before sending the data to the UE. The specific process is as follows:

[0194] In step S602, when the feeder link is available, the LSS interacts with the MME on the satellite. If the UE status in the LSS deployed on the ground is registered, for example, EMM-REGISTERED, and the MME on the satellite does not have the UE context and status information of the UE, the LSS sends the AS / NAS status information of the registered UE (for example, the UE is in ECM_IDLE state, the UE is in EMM-REGISTERED), and / or UE context (UE context), and / or security context to the MME deployed on the satellite.

[0195] In step S604, when the feeder link is available, the LSS interacts with the HSS on the satellite. If the MME on the satellite does not have the subscription data and security parameters of the registered UE, the LSS sends the subscription data, authentication and authorization-related security parameters of the registered UE to the HSS deployed on the satellite.

[0196] Based on the satellite's ephemeris information, the LSS can select satellites that will cover the UE registration area in the future and synchronize the UE status information, UE context, security context, and UE subscription data and security parameters of the registered UE.

[0197] It should be noted that step S604 may also occur before step S602.

[0198] It should also be noted that if there is no downlink data to be sent, there is no need to perform subsequent steps.

[0199] In step S606, when downlink data is sent, if the context of the SGW indicates that there is no downlink user plane tunnel endpoint identifier (TEID) toward the MME, the SGW buffers the data.

[0200] In step S608 , the SGW sends a downlink data notification message to the MME on the satellite. The message includes an allocation and retention priority (ARP) and an EPS bearer ID.

[0201] In step S610, steps S610 to S628 may refer to steps S518 to S536 in FIG. 5 .

[0202] The example in Figure 6 solves the problem of synchronizing the AS / NAS status, UE context, UE subscription data, and security parameters of the UE for a satellite that has not interacted with the UE, so that the UE status on the satellite that has not interacted with the UE is registered, for example, EMM-REGISTERED, so that the satellite that has not interacted with the UE can also support the storage and forwarding of data of UEs that have completed registration on other satellites.

[0203] In some implementations, the first terminal device sends uplink data to the second network element, which then stores the uplink data. Furthermore, in some implementations, after storing the uplink data, the second network element triggers the first access network device to release the RRC connection of the first terminal device. The following describes the process of sending uplink data from a registered first terminal device, in conjunction with Figure 7.

[0204] As shown in Figure 7, when uplink data needs to be sent, a registered UE can establish an RRC connection with the satellite access network device when a serving link is available, store the uplink data in the satellite network entity, and then release the RRC connection. When a feeder link is available, a general packet radio service tunneling protocol (GTP) tunnel is established between the MME and the SGW / PGW for uplink data transmission. The specific process is as follows:

[0205] In step S702, when a serving link is available and uplink data needs to be sent, the UE establishes an RRC connection with the satellite-based access device or sends an RRC Early Data Request (RRCEarlyDataRequest) containing an integrity-protected NASDATA PDU. The NASDATA PDU carries the EPS bearer ID and encrypted uplink data. For IP PDN type PDN connections configured to support header compression, the UE shall apply header compression before encapsulating the data in a NAS message.

[0206] In step S704, the NASDATA PDU sent in step S702 is forwarded by the access network device to the MME using the S1-AP Initial UE message. If the RRCEarlyDataRequest message is received in step S402, the access network device includes an "early data transmission (EDT) session" indication in the S1-AP Initial UE message.

[0207] In step S706, the MME checks the integrity of the incoming NASDATA PDU and decrypts the data it contains.

[0208] In step S708, after the UL data transmission is completed, the UL data is stored in a network entity on the satellite, such as the MME. The MME on the satellite sends an S1AP UE Context Release Command to the access network device.

[0209] In step S710, the access network device releases the RRC connection between the access network device and the UE.

[0210] In steps S712 to S718, a GTP tunnel is established between the MME and the SGW / PGW for transmission of uplink data.

[0211] In step S720, uplink data is transmitted.

[0212] The process in the example of Figure 7 differs from the traditional Mobile Originated Data Transport in Control Plane CIoT EPS Optimization with P-GW connectivity process in that after completing uplink data transmission, the UE first releases the RRC connection and stores the data on the satellite. Then, when the feeder link is available, a GTP tunnel is established between the MME and the S / PGW for uplink data transmission. In the traditional process, the RRC connection and GTP tunnel are first established, and after completing uplink and downlink data transmission, the RRC connection between the UE and the access network device is released. The example of Figure 7 can be used by a UE to forward uplink data to a remote ground-based data network via any satellite that stores the UE's UE status information, UE context, security context, and subscription data. For example, a ship sailing on the ocean can report its navigation status to a shore-based management agency. The example of Figure 7 allows multiple satellites to take turns transmitting data to the UE, increasing the probability of successful storage and forwarding of UE data and reducing the latency of related services.

[0213] In some implementations, the first terminal device sends a detachment or deregistration request to the second network element. The first terminal device then receives detachment or deregistration acceptance information from the first access network device. This information can, for example, be included in a paging message. Including the detachment or deregistration acceptance information in the paging message can simplify the detachment or deregistration process.

[0214] In some implementations, after the first terminal device detaches or deregisters, the second network element may send fifth information (e.g., a detachment or deregistration request) to the first network element. The fifth information may be used to indicate that the state of the first terminal device has switched from a registered state to a deregistered state. After receiving the fifth information, the first network element performs one or more of the following operations: updates the state of the first terminal device stored in the first network element to a deregistered state, and deletes the context information and / or security context information of the first terminal device.

[0215] In some implementations, after the first terminal device detaches or deregisters, the third network element may delete the second information, thereby saving storage space on the satellite. The third network element may be located on the satellite (e.g., on the same satellite as the second network element). In some implementations, the third network element and the second network element may be the same network element, or the third network element may be replaced by the second network element. The third network element may be, for example, a mobility management network element, such as an MME or an AMF. In other implementations, the third network element may also be an HSS on the satellite.

[0216] In some implementations, if the state of the first terminal device switches from a registered state to a deregistered state, and the first network element has synchronized the state of the first terminal device, but the fourth network element (such as an MME located on a different satellite from the second network element) has not yet synchronized the state of the first terminal device, the first network element may send sixth information (the seventh information may be, for example, a detachment request) to the fourth network element, where the sixth information is used to indicate that the state of the first terminal device has switched from a registered state to a deregistered state. In response to the sixth information, the fourth network element switches the state of the first terminal device stored in itself from a registered state to a deregistered state.

[0217] The following describes the embodiments of the present application in more detail with reference to specific examples. It should be noted that the examples of Figures 7 to 8 are merely intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. It is apparent that those skilled in the art can make various equivalent modifications or changes based on the examples of Figures 8 to 9 provided, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0218] FIG8 is a schematic diagram of a UE-initiated detachment process according to an embodiment of the present application.

[0219] As shown in Figure 8, when the UE no longer needs to be registered with the network, it can initiate a detach process:

[0220] In step S802, when the service link is available, the UE sends an attach request message to the MME via the access network device on the satellite. The message includes UE identification information such as GUTI.

[0221] In step S804, the MME sends a detach accept message to the UE.

[0222] In step S806, the connection between the UE and the satellite access network device, as well as the S1-MME signaling connection established for the UE, is released.

[0223] In step S808, when the feeder link becomes available, the MME sends a detach request to the LSS. The LSS deletes locally stored UE-related information, such as the UE context and security context. It also switches the UE to a deregistered state. While waiting for other satellites to connect to it, it triggers the other satellites to detach the UE. For a detailed process, see the example in Figure 9.

[0224] In step S810, the HSS on the satellite deletes the subscription data and security parameters of the UE. This behavior mainly occurs when the LSS needs to update the subscription data and security parameters of the UE in the registered state for the HSS on the satellite, resulting in insufficient satellite storage space.

[0225] Figure 8, along with the example shown in Figure 9 below, illustrates how a UE can deregister from all serving satellites using a single satellite. Figure 8 primarily addresses the synchronization of UE status information with the LSS after the UE initiates the detach procedure. Deregistration is accomplished by the LSS interacting with the UE's serving satellite on its behalf, eliminating the signaling overhead caused by repeated interactions with all satellites. Furthermore, the UE does not need to continuously monitor all serving satellites and can cease operations (e.g., shut down or enter analysis mode) after interacting with any satellite, thereby reducing UE energy consumption.

[0226] FIG9 is a schematic diagram of an LSS-initiated detachment process according to an embodiment of the present application.

[0227] In the example of Figure 9, when a ground-based LSS interacts with any satellite, it can initiate a detachment process to synchronize the UE status on the satellite, or the operator node can register the UE. The specific process is as follows:

[0228] In step S902, when the feeder link is available, the LSS sends a detach request to the MME on the satellite, where the detach request includes UE identification information such as GUTI.

[0229] Step S904 is the same as step S810 in the embodiment of FIG. 8 .

[0230] In step S906, the MME sends a detach request to the access network device.

[0231] In step S908, the access network device uses the UE identifier (GUTI) of the UE in the deregistered state to page the UE. After the UE establishes a connection with the access network device on the satellite, it receives a detach request message. The paging message can directly carry the attach request message, which includes the UE identifier and the reason for detachment, such as the UE's outstanding payment or the UE having completed the detachment process on another satellite.

[0232] In step S910, the UE returns a detachment acceptance message to the MME on the satellite. Of course, the UE may also not execute step S910 and implicitly accept the detachment.

[0233] In the example of Figure 9, the ground-deployed LSS can interact with satellites (such as all satellites), initiate a detachment process from the network side, and delete the context information, subscription data, and security parameters of the detached UE based on the storage space usage on the satellite, freeing up the storage space on the satellite for storing relevant information of UEs in the registered state, thereby ensuring the utilization of the storage space on the satellite. Carrying a detachment request in a paging message can further simplify the detachment process, allowing the detachment process to be completed in a shorter time, avoiding the signaling overhead and power consumption caused by the UE receiving a paging message, establishing a connection with the network, receiving a detachment request message, and then releasing the connection with the network. This is especially suitable for scenarios where low-orbit satellites serve UEs. Due to their fast movement speed, the service link is available for a relatively short time, and it is even more necessary to complete the interaction with the UE in a shorter time.

[0234] As can be seen from the examples in Figures 5 to 9, in order to support the scenario where multiple satellites serve UEs in the deployment architecture of HSS and MME on satellite, this solution introduces a new network element deployed on the ground, LSS, to manage and maintain UE status information, UE context, security context, UE subscription data, authentication and authorization-related security parameters, and other information in the network. The following enhancements are made to the existing attach / detach process:

[0235] First, when a UE initiates an attach / detach procedure, the satellite executing the attach / detach procedure needs to interact with the ground-based LSS when the feeder link is available. The LSS needs to store and synchronize local UE status information, UE context, security context, and other information.

[0236] Second: When any satellite is available in the feeder link with the LSS deployed on the ground, the LSS needs to synchronize the relevant information of the registered UE to the satellite whose future coverage includes the UE registration area, and update the relevant status notification of the unregistered UE to all satellites that maintain the status of the UE, and release the UE subscription data, authentication and authorization-related security parameters, etc. based on the satellite storage space occupancy and operator policy.

[0237] In addition, a satellite that does not directly interact with the UE but stores the above-mentioned UE-related information can directly support the storage and forwarding of uplink and downlink data for the UE.

[0238] It should be noted that the network elements mentioned in the above embodiments may all refer to core network elements.

[0239] The above describes the method embodiment of the present application in detail, and the following describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so for parts not described in detail, reference can be made to the previous method embodiment.

[0240] FIG10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1000 shown in FIG10 may be the first network element 1010 mentioned above. The communication device 1000 includes a first communication module 1010, which is configured to receive first information sent by a second network element, wherein the first information includes one or more of the following information: status information of the first terminal device; context information of the first terminal device; and security context information of the first terminal device; wherein the second network element is configured to perform mobility management on the terminal device.

[0241] In some implementations, the first network element is deployed on the ground; and / or the second network element is deployed on a satellite.

[0242] In some implementations, the first communication module is also used to: send second information to a third network element, the second information including one or more of the following information: subscription data of the second terminal device; security parameters related to authentication and authorization of the second terminal device; wherein the third network element is used to store the subscription data of the terminal device, and the second terminal device is a terminal device that failed to register or attach to the second network element.

[0243] In some implementations, the third network element is located on a satellite.

[0244] In some implementations, the first communication module is further used to: before the first network element sends the second information to the third network element, receive third information sent by the third network element, where the third information is used to request the second information.

[0245] In some implementations, the third information includes one or more of the following:

[0246] an identifier of the second terminal device;

[0247] The identifier of the satellite where the third network element is located;

[0248] The area where the second terminal device is located when initiating the attachment request or registration request;

[0249] The residence time of the second terminal device in the area.

[0250] In some implementations, the reason for the failure of registration or attachment of the second terminal device is that the third network element does not store the subscription data and / or security parameters related to authentication and authorization of the second terminal device.

[0251] In some implementations, the first communication module is further configured to:

[0252] The first information is sent to a fourth network element, where the fourth network element is used to perform mobility management on the terminal device, and the fourth network element does not store the first information.

[0253] In some implementations, the fourth network element and the second network element are located on different satellites.

[0254] In some implementations, the first network element stores ephemeris information of a satellite, and the satellite where the fourth network element is located is determined based on the ephemeris information.

[0255] In some implementations, the coverage of an access network device located on the same satellite as the fourth network element includes a registration area of ​​the first terminal device.

[0256] In some implementations, the first communication module is further configured to:

[0257] Sending fourth information to the fifth network element, where the fourth information includes one or more of the following:

[0258] the subscription data of the first terminal device;

[0259] security parameters related to authentication and authorization of the first terminal device;

[0260] The fifth network element is used to store the contract data of the terminal device, and the fifth network element does not store the fourth information.

[0261] In some implementations, the fifth network element and the second network element are located on different satellites.

[0262] In some implementations, the first communication module is further configured to:

[0263] Receive the fifth information sent by the second network element, where the fifth information is used to indicate that the state of the first terminal device is switched from a registered state to a deregistered state.

[0264] In some implementations, the communication device further includes:

[0265] an execution module, configured to, in response to the fifth information, perform one or more of the following operations:

[0266] Updating the state of the first terminal device stored in the first network element to a deregistered state;

[0267] Delete the context information and / or security context information of the first terminal device.

[0268] In some implementations, the first communication module is further configured to:

[0269] Send sixth information to a fourth network element, where the fourth network element is used to perform mobility management on the terminal device, and the sixth information is used to instruct the fourth network element to switch the state of the first terminal device from a registered state to a deregistered state.

[0270] In some implementations, the fourth network element and the second network element are located on different satellites.

[0271] In some implementations, the first network element is one of the following:

[0272] HSS;

[0273] MME and HSS;

[0274] UDM / UDR;

[0275] AMF and UDM / UDR.

[0276] In some implementations, the security context information includes an authentication vector.

[0277] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1100 shown in Figure 11 can be a second network element, and the communication device 1100 includes: a first communication module 1110, configured to send first information to the first network element, the first information including one or more of the following information: status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; wherein the second network element is configured to perform mobility management on the terminal device.

[0278] In some implementations, the first network element is deployed on the ground; and / or the second network element is deployed on a satellite.

[0279] In some implementations, the first communication module is further configured to:

[0280] Receiving uplink data of the first terminal device;

[0281] The communication device 1100 further includes: a storage module, configured to store the uplink data.

[0282] In some implementations, the first communication module is further configured to:

[0283] After the state of the first terminal device is switched to the deregistered state, fifth information is sent to the first network element, where the fifth information is used to indicate that the state of the first terminal device is the deregistered state.

[0284] In some implementations, the first communication module is further configured to:

[0285] receiving seventh information sent by the first network element, where the seventh information is used to indicate that the state of the third terminal device is switched from a registered state to a deregistered state;

[0286] The communication device further includes:

[0287] A switching module is used to switch the state of the third terminal device stored in the second network element from a registered state to a deregistered state in response to the seventh information.

[0288] In some implementations, the first communication module is further configured to:

[0289] Before the second network element sends the first information to the first network element, it receives an attachment or registration request sent by the first terminal device, where the attachment or registration request includes an identifier of a serving satellite of the first terminal device.

[0290] In some implementations, the first communication module is further configured to:

[0291] If the third network element does not store the subscription data and / or security parameters related to authentication and authorization of the first terminal device, a response message of the attachment or registration request is sent to the first terminal device, and the response message is used to reject the attachment or registration request of the first terminal device. The third network element is used to store the subscription data of the terminal device, and the third network element is associated with the second network element.

[0292] In some implementations, the second network element and the third network element are located on the same satellite.

[0293] In some implementations, the response information includes one or more of the following:

[0294] a reason for rejecting attachment or registration of the first terminal device;

[0295] an identifier of the first terminal device;

[0296] The identifier of the satellite where the second network element is located.

[0297] In some implementations, the rejection reason includes that the third network element does not store the subscription data of the first terminal device and / or security parameters related to authentication and authorization.

[0298] In some implementations, the security context information includes an authentication vector.

[0299] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1200 shown in Figure 12 can be a third network element, and the communication device 1200 includes: a first communication module 1210, which is used to receive second information sent by the first network element, and the second information includes one or more of the following information: subscription data of the second terminal device; security parameters related to authentication and authorization of the second terminal device; wherein the third network element is used to store the subscription data of the terminal device, the second terminal device is a terminal device that fails to register or attach to the second network element, the second network element is used to perform mobility management on the terminal device, and the second network element is associated with the third network element.

[0300] In some implementations, the first network element is deployed on the ground; and / or the second network element and the third network element are located on the same satellite.

[0301] In some implementations, the first communication module is further configured to: before the third network element receives the second information sent by the first network element, send third information to the first network element, where the third information is used to request the second information.

[0302] In some implementations, the third information includes one or more of the following:

[0303] an identifier of the second terminal device;

[0304] The identifier of the satellite where the third network element is located;

[0305] The area where the second terminal device is located when initiating the attachment request or registration request;

[0306] The residence time of the second terminal device in the area.

[0307] In some implementations, the communication device further includes:

[0308] A deleting module is configured to delete the second information if the state of the second terminal device is switched from a registered state to a deregistered state.

[0309] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1300 shown in Figure 13 can be a first terminal device, and the communication device 1300 includes a first communication module 1310 for sending an attachment or registration request to a second network element, which is used to perform mobility management on the terminal device.

[0310] In some implementations, the second network element is located on a satellite.

[0311] In some implementations, the attach or registration request includes an identification of a serving satellite for the first terminal device.

[0312] In some implementations, the first communication module is further configured to:

[0313] Receive response information to the attachment or registration request, where the response information is used to reject the attachment or registration request of the first terminal device.

[0314] In some implementations, the response information includes one or more of the following:

[0315] a reason for rejecting attachment or registration of the first terminal device;

[0316] an identifier of the first terminal device;

[0317] The identifier of the satellite where the second network element is located.

[0318] In some implementations, the rejection reason includes that the third network element does not store the subscription data of the first terminal device and / or security parameters related to authentication and authorization.

[0319] In some implementations, the third network element is used to store subscription data of the terminal device, and the third network element is associated with the second network element.

[0320] In some implementations, the second network element and the third network element are located on the same satellite.

[0321] In some implementations, the first communication module is further configured to:

[0322] Before the first terminal device sends an attach or registration request to the second network element, receive broadcast information from the first access network device, where the broadcast information includes one or more of the following information:

[0323] an identifier of a first satellite where the first access network is located;

[0324] An identifier of a terminal device or a terminal device group served by the first satellite.

[0325] In some implementations, the first communication module is used to: receive broadcast information of the first access network device when a service link between the first terminal device and the first access network device is available.

[0326] In some implementations, the first access network and the second network element are located on the same satellite.

[0327] In some implementations, the first satellite where the second network element is located is determined to be a serving satellite for the first terminal device based on one or more of the following:

[0328] Information of the service satellite configured for the first terminal device;

[0329] The broadcast information of the access network device on the first satellite is used to indicate the identifier of the terminal device served by the first satellite and / or the identifier of the first satellite.

[0330] In some implementations, the first communication module is further configured to:

[0331] Sending uplink data of the first terminal device to the first access network device;

[0332] After the uplink data is stored in the satellite where the first access network device is located, the first terminal device receives an RRC connection release message sent by the first access network device.

[0333] In some implementations, the first communication module is further configured to:

[0334] The first terminal device sends a detach or deregistration request to the second network element;

[0335] The first terminal device receives a paging message sent by the first access network device, where the paging message is used to indicate acceptance of the detachment or deregistration request;

[0336] The first access network device and the second network element are located on the same satellite.

[0337] FIG14 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1400 shown in FIG14 may be a first access network device, and the communication device 1400 includes a first communication module 1410 for sending broadcast information. The first access network device is located on a first satellite, and the broadcast information is used to indicate one or more of the following:

[0338] an identifier of a terminal device served by the first satellite;

[0339] The identifier of the first satellite.

[0340] In some implementations, the first communication module is further configured to:

[0341] After the first terminal device sends the detach or deregistration request, a paging message is sent to the first terminal device, where the paging message is used to indicate acceptance of the detach or deregistration request.

[0342] Figure 15 is a schematic block diagram of a communication device according to an embodiment of the present application. Dashed lines in Figure 15 indicate that the unit or module is optional. Device 1500 may be used to implement the method described in the above method embodiment. Device 1500 may be a chip, a terminal device, or a core network device.

[0343] The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. The processor 1510 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.

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

[0345] The apparatus 1500 may further include a transceiver 1530. The processor 1510 may communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 may transmit and receive data with other devices or chips via the transceiver 1530.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0361] 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 this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The first network element receives first information sent by the second network element, where the first information includes one or more of the following information: Status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; The second network element is used to perform mobility management on the terminal device.

2. The method according to claim 1, wherein: The first network element is deployed on the ground; and / or The second network element is deployed on a satellite.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first network element sends second information to the third network element, where the second information includes one or more of the following information: contract data of the second terminal device; Security parameters related to authentication and authorization of the second terminal device; The third network element is used to store the subscription data of the terminal device, and the second terminal device is a terminal device that fails to register or attach to the second network element.

4. The method according to claim 3, characterized in that The third network element is located on the satellite.

5. The method according to claim 3 or 4, characterized in that Before the first network element sends the second information to the third network element, the method further includes: The first network element receives third information sent by the third network element, where the third information is used to request the second information.

6. The method according to claim 5, characterized in that The third information includes one or more of the following: an identifier of the second terminal device; The identifier of the satellite where the third network element is located; The area where the second terminal device is located when initiating the attachment request or registration request; The residence time of the second terminal device in the area.

7. The method according to any one of claims 3 to 6, characterized in that The reason for the failure of registration or attachment of the second terminal device is that the third network element does not store the subscription data and / or security parameters related to authentication and authorization of the second terminal device.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The first network element sends the first information to a fourth network element, the fourth network element is used to perform mobility management on the terminal device, and the fourth network element does not store the first information.

9. The method according to claim 8, characterized in that The fourth network element and the second network element are located on different satellites.

10. The method according to claim 8 or 9, characterized in that The first network element stores ephemeris information of a satellite, and the satellite where the fourth network element is located is determined based on the ephemeris information.

11. The method according to any one of claims 8 to 10, characterized in that The coverage range of the access network device located on the same satellite as the fourth network element includes the registration area of the first terminal device.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: The first network element sends fourth information to the fifth network element, where the fourth information includes one or more of the following: the subscription data of the first terminal device; security parameters related to authentication and authorization of the first terminal device; The fifth network element is used to store the contract data of the terminal device, and the fifth network element does not store the fourth information.

13. The method according to claim 12, characterized in that The fifth network element and the second network element are located on different satellites.

14. The method according to any one of claims 1 to 13, characterized in that The method further comprises: The first network element receives fifth information sent by the second network element, where the fifth information is used to indicate that the state of the first terminal device is switched from a registered state to a deregistered state.

15. The method according to claim 14, characterized in that The method further comprises: In response to the fifth information, the first network element performs one or more of the following operations: Updating the state of the first terminal device stored in the first network element to a deregistered state; Delete the context information and / or security context information of the first terminal device.

16. The method according to claim 14 or 15, characterized in that The method further comprises: The first network element sends sixth information to a fourth network element, where the fourth network element is used to perform mobility management on the terminal device. The sixth information is used to instruct the fourth network element to switch the state of the first terminal device from a registered state to a deregistered state.

17. The method according to claim 16, characterized in that The fourth network element and the second network element are located on different satellites.

18. The method according to any one of claims 1 to 17, characterized in that The first network element is one of the following: Home Subscriber Server HSS; Mobility management entity MME and HSS; Unified Data Management (UDM) / Unified Data Storage (UDR); Access and mobility management functions AMF and UDM / UDR.

19. The method according to any one of claims 1 to 18, characterized in that The security context information includes an authentication vector.

20. A wireless communication method, characterized in that: include: The second network element sends first information to the first network element, where the first information includes one or more of the following information: Status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; The second network element is used to perform mobility management on the terminal device.

21. The method according to claim 20, characterized in that: The first network element is deployed on the ground; and / or The second network element is deployed on a satellite.

22. The method according to claim 20 or 21, characterized in that The method further comprises: The second network element receives uplink data of the first terminal device; The second network element stores the uplink data.

23. The method according to any one of claims 20 to 22, characterized in that The method further comprises: After the state of the first terminal device is switched to the deregistered state, the second network element sends fifth information to the first network element, where the fifth information is used to indicate that the state of the first terminal device is the deregistered state.

24. The method according to any one of claims 20 to 23, characterized in that The method further comprises: The second network element receives seventh information sent by the first network element, where the seventh information is used to indicate that the state of the third terminal device is switched from a registered state to a deregistered state; In response to the seventh information, the second network element switches the state of the third terminal device stored in the second network element from a registered state to a deregistered state.

25. The method according to any one of claims 20 to 24, characterized in that Before the second network element sends the first information to the first network element, the method further includes: The second network element receives an attachment or registration request sent by the first terminal device, where the attachment or registration request includes an identifier of a serving satellite of the first terminal device.

26. The method according to claim 25, characterized in that The method further comprises: If the third network element does not store the subscription data and / or security parameters related to authentication and authorization of the first terminal device, the second network element sends a response message of the attachment or registration request to the first terminal device, and the response message is used to reject the attachment or registration request of the first terminal device. The third network element is used to store the subscription data of the terminal device, and the third network element is associated with the second network element.

27. The method according to claim 26, characterized in that The second network element and the third network element are located on the same satellite.

28. The method according to claim 26 or 27, characterized in that The response information includes one or more of the following: a reason for rejecting attachment or registration of the first terminal device; an identifier of the first terminal device; The identifier of the satellite where the second network element is located.

29. The method according to claim 28, characterized in that The rejection reason includes that the third network element does not store the subscription data of the first terminal device and / or security parameters related to authentication and authorization.

30. The method according to any one of claims 20 to 29, characterized in that The security context information includes an authentication vector.

31. The method according to any one of claims 20 to 30, characterized in that The first network element is one of the following: Home Subscriber Server HSS; Mobility management entity MME and HSS; Unified Data Management (UDM) / Unified Data Storage (UDR); Access and mobility management functions AMF and UDM / UDR.

32. A wireless communication method, characterized in that: include: The third network element receives second information sent by the first network element, where the second information includes one or more of the following information: contract data of the second terminal device; Security parameters related to authentication and authorization of the second terminal device; Among them, the third network element is used to store the contract data of the terminal device, the second terminal device is a terminal device that fails to register or attach to the second network element, the second network element is used to perform mobility management on the terminal device, and the second network element is associated with the third network element.

33. The method according to claim 32, wherein: The first network element is deployed on the ground; and / or The second network element and the third network element are located on the same satellite.

34. The method according to claim 32 or 33, characterized in that Before the third network element receives the second information sent by the first network element, the method further includes: The third network element sends third information to the first network element, where the third information is used to request the second information.

35. The method according to claim 34, wherein The third information includes one or more of the following: an identifier of the second terminal device; The identifier of the satellite where the third network element is located; The area where the second terminal device is located when initiating the attachment request or registration request; The residence time of the second terminal device in the area.

36. The method according to any one of claims 32 to 35, characterized in that The method further comprises: If the state of the second terminal device is switched from a registered state to a deregistered state, the third network element deletes the second information.

37. The method according to any one of claims 32 to 36, characterized in that The first network element is one of the following: Home Subscriber Server HSS; Mobility management entity MME and HSS; Unified Data Management (UDM) / Unified Data Storage (UDR); Access and mobility management functions AMF and UDM / UDR.

38. A wireless communication method, characterized in that: include: The first terminal device sends an attachment or registration request to a second network element, where the second network element is used to perform mobility management on the terminal device.

39. The method according to claim 38, characterized in that The first terminal device sending an attach or registration request to the second network element includes: When the first terminal device supports the store-and-forward mode, the first terminal device sends the attachment or registration request to the second network element.

40. The method according to claim 38 or 39, characterized in that The second network element is located on the satellite.

41. The method according to any one of claims 38 to 40, characterized in that The attach or registration request includes an identification of a serving satellite of the first terminal device.

42. The method according to any one of claims 38 to 41, characterized in that The method further comprises: The first terminal device receives response information of the attachment or registration request, where the response information is used to reject the attachment or registration request of the first terminal device.

43. The method according to claim 42, characterized in that The response information includes one or more of the following: a reason for rejecting attachment or registration of the first terminal device; an identifier of the first terminal device; The identifier of the satellite where the second network element is located.

44. The method according to claim 43, wherein The rejection reason includes that the third network element does not store the subscription data of the first terminal device and / or security parameters related to authentication and authorization.

45. The method according to claim 44, wherein The third network element is used to store the subscription data of the terminal device, and the third network element is associated with the second network element.

46. The method according to claim 45, characterized in that The second network element and the third network element are located on the same satellite.

47. The method according to any one of claims 38 to 46, characterized in that Before the first terminal device sends an attach or registration request to the second network element, the method further includes: The first terminal device receives broadcast information from the first access network device, where the broadcast information includes one or more of the following information: an identifier of a first satellite where the first access network is located; An identifier of a terminal device or a terminal device group served by the first satellite.

48. The method according to claim 47, wherein The first terminal device receiving broadcast information of the first access network device includes: When the service link between the first terminal device and the first access network device is available, the first terminal device receives broadcast information of the first access network device.

49. The method according to claim 47 or 48, characterized in that The first access network and the second network element are located on the same satellite.

50. The method according to any one of claims 38 to 49, characterized in that The first satellite where the second network element is located is determined to be a serving satellite for the first terminal device based on one or more of the following: Information of the service satellite configured for the first terminal device; The broadcast information of the access network device on the first satellite is used to indicate the identifier of the terminal device served by the first satellite and / or the identifier of the first satellite.

51. The method according to any one of claims 38 to 50, characterized in that The method further comprises: The first terminal device sends uplink data of the first terminal device to the first access network device; After the uplink data is stored in the satellite where the first access network device is located, the first terminal device receives a radio resource control RRC connection release message sent by the first access network device.

52. The method according to any one of claims 38 to 51, characterized in that The method further comprises: The first terminal device sends a detach or deregistration request to the second network element; The first terminal device receives a paging message sent by the first access network device, where the paging message is used to indicate acceptance of the detachment or deregistration request; The first access network device and the second network element are located on the same satellite.

53. A wireless communication method, characterized in that: include: A first access network device sends broadcast information, where the first access network device is located on a first satellite. The broadcast information indicates one or more of the following: an identifier of a terminal device served by the first satellite; The identifier of the first satellite.

54. The method according to claim 53, wherein The method further comprises: After the first terminal device sends a detach or deregistration request, the first access network device sends a paging message to the first terminal device, where the paging message is used to indicate acceptance of the detach or deregistration request.

55. A communication device, characterized in that The communication device is a first network element, and the communication device includes: The first communication module is configured to receive first information sent by the second network element, where the first information includes one or more of the following information: Status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; The second network element is used to perform mobility management on the terminal device.

56. The communication device according to claim 55, characterized in that: The first network element is deployed on the ground; and / or The second network element is deployed on a satellite.

57. The communication device according to claim 55 or 56, characterized in that The first communication module is further configured to: Sending second information to the third network element, where the second information includes one or more of the following information: contract data of the second terminal device; Security parameters related to authentication and authorization of the second terminal device; The third network element is used to store the subscription data of the terminal device, and the second terminal device is a terminal device that fails to register or attach to the second network element.

58. The communication device according to claim 57, characterized in that The third network element is located on the satellite.

59. The communication device according to claim 57 or 58, characterized in that The first communication module is further configured to: Before the first network element sends the second information to the third network element, the first network element receives third information sent by the third network element, where the third information is used to request the second information.

60. The communication device according to claim 59, wherein The third information includes one or more of the following: an identifier of the second terminal device; The identifier of the satellite where the third network element is located; The area where the second terminal device is located when initiating the attachment request or registration request; The residence time of the second terminal device in the area.

61. The communication device according to any one of claims 57 to 60, characterized in that The reason for the failure of registration or attachment of the second terminal device is that the third network element does not store the subscription data and / or security parameters related to authentication and authorization of the second terminal device.

62. The communication device according to any one of claims 55 to 61, characterized in that The first communication module is further configured to: The first information is sent to a fourth network element, where the fourth network element is used to perform mobility management on the terminal device, and the fourth network element does not store the first information.

63. The communication device according to claim 62, characterized in that The fourth network element and the second network element are located on different satellites.

64. The communication device according to claim 62 or 63, characterized in that The first network element stores ephemeris information of a satellite, and the satellite where the fourth network element is located is determined based on the ephemeris information.

65. The communication device according to any one of claims 62 to 64, characterized in that The coverage range of the access network device located on the same satellite as the fourth network element includes the registration area of the first terminal device.

66. The communication device according to any one of claims 55 to 65, characterized in that The first communication module is further configured to: Sending fourth information to the fifth network element, where the fourth information includes one or more of the following: the subscription data of the first terminal device; security parameters related to authentication and authorization of the first terminal device; The fifth network element is used to store the contract data of the terminal device, and the fifth network element does not store the fourth information.

67. The communication device according to claim 66, characterized in that The fifth network element and the second network element are located on different satellites.

68. The communication device according to any one of claims 55 to 67, characterized in that The first communication module is further configured to: Receive the fifth information sent by the second network element, where the fifth information is used to indicate that the state of the first terminal device is switched from a registered state to a deregistered state.

69. The communication device according to claim 68, characterized in that The communication device further includes: an execution module, configured to, in response to the fifth information, perform one or more of the following operations: Updating the state of the first terminal device stored in the first network element to a deregistered state; Delete the context information and / or security context information of the first terminal device.

70. The communication device according to claim 68 or 69, characterized in that The first communication module is further configured to: Send sixth information to a fourth network element, where the fourth network element is used to perform mobility management on the terminal device, and the sixth information is used to instruct the fourth network element to switch the state of the first terminal device from a registered state to a deregistered state.

71. The communication device according to claim 70, wherein: The fourth network element and the second network element are located on different satellites.

72. The communication device according to any one of claims 55 to 71, characterized in that The first network element is one of the following: Home Subscriber Server HSS; Mobility management entity MME and HSS; Unified Data Management (UDM) / Unified Data Storage (UDR); Access and mobility management functions AMF and UDM / UDR.

73. The communication device according to any one of claims 55 to 72, characterized in that The security context information includes an authentication vector.

74. A communication device, characterized in that The communication device is a second network element, and the communication device includes: The first communication module is configured to send first information to the first network element, where the first information includes one or more of the following information: Status information of the first terminal device; context information of the first terminal device; security context information of the first terminal device; The second network element is used to perform mobility management on the terminal device.

75. The communication device according to claim 74, characterized in that: The first network element is deployed on the ground; and / or The second network element is deployed on a satellite.

76. The communication device according to claim 74 or 75, characterized in that The first communication module is further configured to: Receiving uplink data of the first terminal device; The communication device further includes: A storage module is used to store the uplink data.

77. The communication device according to any one of claims 74 to 76, characterized in that The first communication module is further configured to: After the state of the first terminal device is switched to the deregistered state, fifth information is sent to the first network element, where the fifth information is used to indicate that the state of the first terminal device is the deregistered state.

78. The communication device according to any one of claims 74 to 77, characterized in that The first communication module is further configured to: receiving seventh information sent by the first network element, where the seventh information is used to indicate that the state of the third terminal device is switched from a registered state to a deregistered state; The communication device further includes: A switching module is configured to change the state of the third terminal device stored in the second network element from the registered state to the Switch to the deregistered state.

79. The communication device according to any one of claims 74 to 78, characterized in that The first communication module is further configured to: Before the second network element sends the first information to the first network element, it receives an attachment or registration request sent by the first terminal device, where the attachment or registration request includes an identifier of a serving satellite of the first terminal device.

80. The communication device according to claim 79, wherein The first communication module is further configured to: If the third network element does not store the subscription data and / or security parameters related to authentication and authorization of the first terminal device, a response message of the attachment or registration request is sent to the first terminal device, and the response message is used to reject the attachment or registration request of the first terminal device. The third network element is used to store the subscription data of the terminal device, and the third network element is associated with the second network element.

81. The communication device according to claim 80, wherein: The second network element and the third network element are located on the same satellite.

82. The communication device according to claim 80 or 81, characterized in that The response information includes one or more of the following: a reason for rejecting attachment or registration of the first terminal device; an identifier of the first terminal device; The identifier of the satellite where the second network element is located.

83. The communication device according to claim 82, characterized in that The rejection reason includes that the third network element does not store the subscription data of the first terminal device and / or security parameters related to authentication and authorization.

84. The communication device according to any one of claims 74 to 83, characterized in that The security context information includes an authentication vector.

85. The communication device according to any one of claims 74 to 84, characterized in that The first network element is one of the following: Home Subscriber Server HSS; Mobility management entity MME and HSS; Unified Data Management (UDM) / Unified Data Storage (UDR); Access and mobility management functions AMF and UDM / UDR.

86. A communication device, characterized in that The communication device is a third network element, and the communication device includes: The first communication module is configured to receive second information sent by the first network element, where the second information includes one or more of the following information: contract data of the second terminal device; Security parameters related to authentication and authorization of the second terminal device; Among them, the third network element is used to store the contract data of the terminal device, the second terminal device is a terminal device that fails to register or attach to the second network element, the second network element is used to perform mobility management on the terminal device, and the second network element is associated with the third network element.

87. The communication device according to claim 86, characterized in that: The first network element is deployed on the ground; and / or The second network element and the third network element are located on the same satellite.

88. The communication device according to claim 86 or 87, characterized in that The first communication module is further configured to: Before the third network element receives the second information sent by the first network element, the third network element sends third information to the first network element, where the third information is used to request the second information.

89. The communication device according to claim 88, characterized in that The third information includes one or more of the following: an identifier of the second terminal device; The identifier of the satellite where the third network element is located; The area where the second terminal device is located when initiating the attachment request or registration request; The residence time of the second terminal device in the area.

90. The communication device according to any one of claims 86 to 89, characterized in that The communication device further includes: A deleting module is configured to delete the second information if the state of the second terminal device is switched from a registered state to a deregistered state.

91. The communication device according to any one of claims 86 to 90, characterized in that The first network element is one of the following: Home Subscriber Server HSS; Mobility management entity MME and HSS; Unified Data Management (UDM) / Unified Data Storage (UDR); Access and mobility management functions AMF and UDM / UDR.

92. A communication device, characterized in that The communication device is a first terminal device, and the communication device includes: The first communication module is used to send an attachment or registration request to a second network element, and the second network element is used to perform mobility management on the terminal device.

93. The communication device according to claim 92, characterized in that The first communication module is used for: When the first terminal device supports the store-and-forward mode, the attachment or registration request is sent to the second network element.

94. The communication device according to claim 92 or 93, characterized in that The second network element is located on the satellite.

95. The communication device according to any one of claims 92 to 94, characterized in that The attach or registration request includes an identification of a serving satellite of the first terminal device.

96. The communication device according to any one of claims 92 to 95, characterized in that The first communication module is further configured to: Receive response information to the attachment or registration request, where the response information is used to reject the attachment or registration request of the first terminal device.

97. The communication device according to claim 96, characterized in that The response information includes one or more of the following: a reason for rejecting attachment or registration of the first terminal device; an identifier of the first terminal device; The identifier of the satellite where the second network element is located.

98. The communication device according to claim 97, characterized in that The rejection reason includes that the third network element does not store the subscription data of the first terminal device and / or security parameters related to authentication and authorization.

99. The communication device according to claim 98, characterized in that The third network element is used to store the subscription data of the terminal device, and the third network element is associated with the second network element.

100. The communication device according to claim 99, wherein: The second network element and the third network element are located on the same satellite.

101. The communication device according to any one of claims 93 to 100, characterized in that The first communication module is further configured to: Before the first terminal device sends an attach or registration request to the second network element, receive broadcast information from the first access network device, where the broadcast information includes one or more of the following information: an identifier of a first satellite where the first access network is located; An identifier of a terminal device or a terminal device group served by the first satellite.

102. The communication device according to claim 101, characterized in that The first communication module is used for: When the service link between the first terminal device and the first access network device is available, the broadcast information of the first access network device is received.

103. The communication device according to claim 101 or 102, characterized in that The first access network and the second network element are located on the same satellite.

104. The communication device according to any one of claims 92 to 103, characterized in that The first satellite where the second network element is located is determined to be a serving satellite for the first terminal device based on one or more of the following: Information of the service satellite configured for the first terminal device; The broadcast information of the access network device on the first satellite is used to indicate the identifier of the terminal device served by the first satellite and / or the identifier of the first satellite.

105. The communication device according to any one of claims 92 to 104, characterized in that The first communication module is further configured to: Sending uplink data of the first terminal device to the first access network device; After the uplink data is stored in the satellite where the first access network device is located, the first terminal device receives a radio resource control RRC connection release message sent by the first access network device.

106. The communication device according to any one of claims 92 to 105, characterized in that The first communication module is further configured to: The first terminal device sends a detach or deregistration request to the second network element; The first terminal device receives a paging message sent by the first access network device, where the paging message is used to indicate acceptance of the detachment or deregistration request; The first access network device and the second network element are located on the same satellite.

107. A communication device, characterized in that The communication device is a first access network device, and the communication device includes: A first communication module is configured to send broadcast information, where the first access network device is located on a first satellite, and the broadcast information is configured to indicate one or more of the following: an identifier of a terminal device served by the first satellite; The identifier of the first satellite.

108. The communication device according to claim 107, characterized in that The first communication module is further configured to: After the first terminal device sends the detach or deregistration request, a paging message is sent to the first terminal device, where the paging message is used to indicate acceptance of the detach or deregistration request.

109. A communication device, characterized in that The system comprises 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 to execute the method according to any one of claims 1 to 54.

110. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 54.

111. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 54.

112. A computer program product, characterized in that A program is included, the program causing a computer to execute the method according to any one of claims 1 to 54.

113. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 54.

Images