Communication method and communication apparatus

Abstract

A communication method and a communication apparatus, relating to the technical field of communications. The method comprises: sending first indication information to a second network element, the first indication information being used for indicating that when a terminal device moves to a terrestrial communication network (TN), the second network element sends a first notification message to a first network element; receiving the first notification message sent by the second network element, the first notification message being used for indicating that the terminal device has moved to the TN; and on the basis of the first notification message, the first network element releasing resources of the terminal device. According to the method provided in the present application, the first network element can obtain, on the basis of the first notification message, a message indicating that the terminal device has moved to the TN, so as to release resources of the terminal device in a timely manner, thereby avoiding waste of network resources.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese patent application No. 202411280745.8, filed with the State Intellectual Property Office of China on September 12, 2024, entitled "Communication Method and Communication Device", and Chinese patent application No. 202511248746.9, filed with the State Intellectual Property Office of China on September 1, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0003] Currently, in nonterrestrial networks (NTN) systems, terminal devices communicate with satellites via service links, satellites communicate with ground stations via feeder links, and satellites communicate with each other via inter-satellite links.

[0004] Store-and-forward (S&F) mode is a technology used in satellite communications that allows satellites to temporarily store data when no direct link is available and forward the data to its destination when appropriate. In S&F mode, proxy network elements on the satellite and ground proxy network elements store and forward the data.

[0005] When terminal devices move from the NTN network to the terrestrial network, how to enable terrestrial proxy network elements to promptly detect when the terminal devices exit the store-and-forward mode, thereby releasing the terminal devices' resources and avoiding waste of network resources, has become an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method and a communication device, which can avoid wasting network resources.

[0007] In a first aspect, a communication method is provided, the method comprising: sending a first indication information to a second network element, the first indication information being used to indicate that when a terminal device moves to a terrestrial communication network (TN), the second network element sends a first notification message to a first network element; receiving the first notification message, the first notification message being used to indicate that the terminal device moves to the TN; and, based on the first notification message, the first network element releasing resources of the terminal device.

[0008] Secondly, a communication method is provided, the method comprising: sending a first indication message to a second network element, the first indication message being used to indicate that when a terminal device moves to a terrestrial communication network (TN), the second network element sends a first notification message to a third network element; and when the first network element and the third network element disconnect, the first network element releases the resources of the terminal device.

[0009] For example, the above communication method can be implemented by a first network element, or by modules, units, processors, circuits, chips or chip systems included in the first network element. Optionally, the first network element can be a ground agent network element, which is used to store and forward data or signaling of terminal equipment in the storage and forwarding satellite operation.

[0010] It should be understood that the resources of the terminal device are used to support the storage and forwarding mode of the terminal device, or in other words, the resources of the terminal device are used to support the storage and forwarding of data or signaling in storage and forwarding satellite operations.

[0011] It should be noted that the second network element is used to store the user's subscription data and authentication information. In the 4G network architecture, this second network element can be the home subscriber server (HSS), while in the 5G network architecture, it can be the unified data management (UDM), or it can be other network elements that perform the same function. This application does not make any specific limitations on this.

[0012] It should also be noted that the third network element refers to the network element that manages third-party applications. For example, the third network element can be a service capability server (SCS), an application server (AS), or other network elements that perform the same function. This application does not make any specific limitations on this.

[0013] In this embodiment, the first indication information is used to instruct a first network element or a third network element to notify the terminal device when it moves to the TN. In the first scenario, when the first network element instructs the second network element to send a first notification message to the first network element, the first network element can receive the message that the terminal device has moved to the TN (i.e., the first notification message), thereby promptly releasing the terminal device's resources and avoiding network resource waste. In the second scenario, when the first network element instructs the second network element to send a first notification message to the third network element, the second network element sends the first notification message to the third network element (the form of this first notification message is not specifically limited; for example, it could be a message indicating that the third network element has disconnected from the first network element). Then, the first network element obtains the message that the terminal device has moved to the TN based on the first notification message, thereby promptly releasing the terminal device's resources and avoiding network resource waste.

[0014] In some possible implementations, the first indication information includes: the status information of the terminal device, which indicates that the terminal device is in store-and-forward mode.

[0015] In this embodiment, the first indication information may be the status information of the terminal device, which may indicate that the terminal device is in store-and-forward mode. Thus, the second network element may know that the terminal device is currently in store-and-forward mode. When the second network element senses that the terminal device is moving, it may promptly notify the first network element.

[0016] In some possible implementations, the status information of the terminal device includes at least one of the following: the terminal device is in store-and-forward mode, the identifier of the terminal device, or the information of the first network element.

[0017] For example, the information of the first network element can be the ID of the first network element or the address of the first network element.

[0018] In this embodiment of the application, when the status information of a terminal device using store-and-forward satellite services includes the identifier of the terminal device and the information of the first network element, the first network element currently serving the terminal device can be identified.

[0019] Optionally, the first network element may send the status information of the terminal device to the second network element when it first receives the mobile initiation data of the terminal device, or it may send the status information of the terminal device to the second network element periodically. This application does not specifically limit the timing of the first network element sending the status information of the terminal device.

[0020] In some possible implementations, the first indication is a monitoring request.

[0021] In this embodiment of the application, the first indication information may be a monitoring request, which may instruct the second network element to send a first notification message to the first network element or the third network element when the terminal device moves to the TN.

[0022] In some possible implementations, the monitoring request includes at least one of the following: a monitoring event, the identifier of the terminal device, or information of the first network element, wherein the monitoring event is used to monitor the terminal device moving to the TN.

[0023] In this embodiment of the application, when the monitoring request includes the identifier of the terminal device and the information of the first network element, the first network element currently serving the terminal device can be identified.

[0024] Optionally, the first network element may send a monitoring request to the second network element when the first network element receives the mobile-initiated data from the terminal device for the first time. This application does not specify the timing for the first network element to send the monitoring request.

[0025] In some possible implementations, the first network element releases the resources of the terminal device, including at least one of the following: deleting the terminal device context information or status information, releasing the address allocated to the terminal device, disconnecting the connection established between the terminal device and the third network element, or disconnecting the connection established between the terminal device and the fourth network element on the satellite, wherein the fourth network element is used to store and forward the data or signaling of the terminal device in the store-and-forward satellite operation.

[0026] In some possible implementations, the first notification message includes at least one of the following: a movement indication of the terminal device, an identifier of the terminal device, or an address of the terminal device, wherein the movement indication is used to indicate that the terminal device has now moved into the TN.

[0027] In this embodiment of the application, when the first notification message contains the identifier of the terminal device, the first network element can release the resources of the terminal device based on the identifier of the terminal device, thereby avoiding waste of network resources; when the first notification message also contains the address of the terminal device, the first network element can send the cached mobility termination data to the terminal device based on the address of the terminal device.

[0028] In some possible implementations, the method further includes: determining whether mobile termination data of the terminal device is cached, and sending the mobile termination data based on the first notification message.

[0029] In this embodiment of the application, when the first notification message contains the address of the terminal device, the first network element can send the cached mobile terminal data to the terminal device based on the address of the terminal device, thereby avoiding the waste of network resources.

[0030] In some possible implementations, the method further includes: determining whether mobile termination data of the terminal device is cached; sending a second indication message to a third network element, the second indication message being used to instruct the third network element to send cached data to the terminal device, the cached data including: mobile termination data of the terminal device cached by the first network device, the second indication message carrying information of the mobile termination data.

[0031] In this embodiment of the application, when the first notification message does not contain the address of the terminal device, the first network element sends the second instruction information to the third network element, and at the same time sends the cached mobility termination data to the third network element. The third network element is the network element that manages the third application, so the third network element can send the mobility termination data of the terminal device to the terminal device.

[0032] Thirdly, a communication method is provided, the method comprising: receiving first indication information sent by a first network element, the first indication information being used to indicate that when the terminal device moves to a terrestrial communication network (TN), a second network element sends a first notification message to the first network element or a third network element, the first network element being used to store and forward data or signaling of the terminal device in a store-and-forward satellite operation, and the third network element being used to manage third-party applications; and sending a first notification message to the first network element or the third network element based on the first indication message, the first notification message being used to indicate that the terminal device moves to the TN.

[0033] For example, the communication method can be implemented by a second network element, or by modules, units, processors, circuits, chips, or chip systems included in the second network element. The second network element is used to store the user's subscription data and authentication information. In a 4G network architecture, the second network element can be an HSS; in a 5G network architecture, the fourth network element can be a UDM, or it can be other network elements that implement the same function. This application does not specifically limit this.

[0034] In this embodiment, the first indication information is used to indicate that when the terminal device moves to the TN, the second network element can notify the first network element or the third network element. In the first scenario, when the first network element instructs the second network element to send a notification message to the first network element, the first network element can receive the message that the terminal device has moved to the TN (i.e., the first notification message), thereby promptly releasing the terminal device's resources and avoiding network resource waste. In the second scenario, when the first network element instructs the second network element to send a notification message to the third network element, the third network element sends the first notification message to the first network element (the form of this first notification message is not specifically limited; for example, it could be a message indicating that the third network element has disconnected from the first network element). Then, the first network element obtains the message that the terminal device has moved to the TN based on the first notification message, promptly releasing the terminal device's resources and avoiding network resource waste.

[0035] In some possible implementations, the first indication information includes: the status information of the terminal device, which indicates that the terminal device is in store-and-forward mode.

[0036] In this embodiment, the first indication information may be the status information of the terminal device, which may indicate that the terminal device is in store-and-forward mode. Thus, the second network element may know that the terminal device is currently in store-and-forward mode. When the second network element senses that the terminal device is moving, it may promptly notify the first network element.

[0037] In some possible implementations, the status information of the terminal device includes at least one of the following: the terminal device is in store-and-forward mode, the identifier of the terminal device, or the information of the first network element.

[0038] For example, the information of the first network element can be the ID of the first network element or the address of the first network element.

[0039] In this embodiment of the application, when the status information of a terminal device using store-and-forward satellite services includes the identifier of the terminal device and the information of the first network element, the first network element currently serving the terminal device can be identified.

[0040] In some possible implementations, the method also includes updating the context of the terminal device based on the state information of the terminal device.

[0041] For example, updating the context of a terminal device includes: recording that the terminal device is in store-and-forward mode, or recording that the terminal device is in store-and-forward mode and information about the first network element.

[0042] In this embodiment of the application, when the first indication information is the status information of the terminal device, the second network element records that the terminal device is in the store and forward mode according to the status information of the terminal device. When the second network element senses that the terminal device has moved to the TN, the second network element can notify the first network element or the third network element.

[0043] In some possible implementations, the first indication is a monitoring request.

[0044] In this embodiment of the application, the first indication information may be a monitoring request, which may instruct the second network element to send a first notification message to the first network element or the third network element when the terminal device moves to the TN.

[0045] In some possible implementations, the monitoring request includes at least one of the following: a monitoring event, the identifier of the terminal device, or information of the first network element; wherein the monitoring event is used to monitor the terminal device moving to the TN.

[0046] In this embodiment of the application, when the monitoring request includes the identifier of the terminal device and the information of the first network element, the first network element currently serving the terminal device can be identified.

[0047] In some possible implementations, the first notification message includes at least one of the following: a movement indication of the terminal device, an identifier of the terminal device, or an address of the terminal device, wherein the movement indication is used to indicate that the terminal device is currently moved into the TN.

[0048] In this embodiment of the application, when the first notification message contains the identifier of the terminal device, the first network element can release the resources of the terminal device based on the identifier of the terminal device, thereby avoiding waste of network resources; when the first notification message also contains the address of the terminal device, the first network element can send the cached mobile terminal data to the terminal device based on the address of the terminal device.

[0049] In some possible implementations, before sending the first notification message, the method further includes: sending a first request message to a fifth network element, the first request message being used to request the address of the terminal device, the address of the terminal device being the address allocated to the terminal device by the TN, the fifth network element being used for mobility management of the terminal device; and receiving the address of the terminal device sent by the fifth network element.

[0050] For example, in a 4G network architecture, this fifth network element is an MME network element, and in a 5G network architecture, this fifth network element is an AMF network element. Alternatively, it could be other network elements that perform the same function; this application does not specifically limit its application in this regard.

[0051] In this embodiment of the application, the second network element sends a first request message to the fifth network element, requesting the address of the terminal device, so that the second network element can send the cached mobile termination data to the terminal device based on the address of the terminal device.

[0052] Fourthly, a communication method is provided, the method comprising: receiving a first notification message sent by a second network element, the first notification message being used to instruct a terminal device to move to a terrestrial communication network (TN), the first notification message including: a movement indication of the terminal device and an identifier of the terminal device, the movement indication being used to indicate that the terminal device is currently moved to the TN, the second network element being used to store user subscription data and authentication information; disconnecting from a first network element based on the first notification message, wherein the disconnection state between the first network element and the second network element is used to trigger the first network element to release the resources of the terminal device, the first network element being used to store and forward data or signaling of the terminal device in a store-and-forward satellite mode.

[0053] For example, the communication method can be implemented by a third network element, or by the modules, units, processors, circuits, chips, or chip systems included in the third network element. For instance, the third network element can be an SCS, an application server AS, or other network elements that implement the same function; this application does not specifically limit this.

[0054] In some possible implementations, the method further includes: determining data that needs to be retransmitted to the terminal device, the data including mobility termination data; and sending the mobility termination data.

[0055] In this embodiment, the third network element can directly determine whether there is cached motion termination data. If it is determined that there is data that needs to be retransmitted to the terminal device, the cached motion termination data is directly sent to the terminal device, thereby avoiding the waste of network resources.

[0056] In some possible implementations, the data that needs to be retransmitted to the terminal device includes: receiving second indication information sent by a first network element, determining the data that needs to be retransmitted to the terminal device based on the second indication information, wherein the second indication information is used to instruct the second network element to send retransmitted data to the terminal device, and the retransmitted data includes: mobility termination data of the terminal device cached by the first network element, wherein the second indication information carries information about the mobility termination data.

[0057] In this embodiment of the application, the third network element does not directly determine whether there is data to be retransmitted to the terminal device. Instead, it receives a second indication information sent by the first network element, which indicates that there is data to be retransmitted to the terminal device and instructs the third network element to send the cached mobile termination data to the terminal device.

[0058] Fifthly, a communication device is provided, comprising: a module (e.g., including a processing module and a communication module) for performing the steps of the first aspect or any possible implementation thereof; or a module for performing the steps of the second aspect or any possible implementation thereof; or a module for performing the steps of the third aspect or any possible implementation thereof; or a module for performing the steps of the third aspect or any possible implementation thereof. For example, the communication device may be a first network element or a first network element may include the communication device; or the communication device may be a second network element or a second network element may include the communication device; or the communication device may be a third network element or a third network element may include the communication device; or the communication device may be a fourth network element or a fourth network element may include the communication device.

[0059] A sixth aspect provides a communication apparatus comprising at least one processor, the at least one processor being configured to execute the method of the first aspect or any possible implementation thereof; or to execute the method of the second aspect or any possible implementation thereof; or to execute the method of the third aspect or any possible implementation thereof; or to execute the method of the fourth aspect or any possible implementation thereof.

[0060] In one possible implementation, the communication device may further include a memory storing a computer program, and at least one processor executes the method of the first aspect or any possible implementation thereof, or the method of the second aspect or any possible implementation thereof, or the method of the third aspect or any possible implementation thereof, or the method of the fourth aspect or any possible implementation thereof, by executing the computer program stored in the memory. Optionally, the processor and the memory may be integrated together.

[0061] In one possible implementation, at least one processor executes the method of the first aspect or any possible implementation of the first aspect, or the method of the second aspect or any possible implementation of the second aspect, or the method of the third aspect or any possible implementation of the third aspect, or the method of the fourth aspect or any possible implementation of the fourth aspect, through logic circuits or processing circuits.

[0062] In one possible implementation, the communication device may further include interface circuitry for performing specific signal transmission and reception. For example, the communication device may be a terminal, a component within the terminal (a chip, chip system, or processor), or a logic module or software capable of implementing all or part of the terminal's functions.

[0063] For example, the communication device can be a network device, a component (chip, chip system, or processor) in a network device, or a logical node, logical module, or software that can implement all or part of the functions of a network device. Attached Figure Description

[0064] Figure 1 is a schematic diagram of a 4G network architecture applicable to the communication method provided in the embodiments of this application.

[0065] Figure 2 is a schematic diagram of a 5G network architecture applicable to the communication method provided in the embodiments of this application.

[0066] Figure 3 shows a schematic diagram of an example S&F scenario provided in an embodiment of this application.

[0067] Figure 4 shows a schematic diagram of an example S&F network architecture for full-core network satellite navigation.

[0068] Figure 5 shows the data transmission flowchart in the S&F scenario.

[0069] Figure 6 shows a schematic interaction diagram of an example communication method provided in an embodiment of this application.

[0070] Figure 7 shows a schematic interaction diagram of another communication method provided in an embodiment of this application.

[0071] Figure 8 shows a schematic interaction diagram of an example communication method provided in an embodiment of this application.

[0072] Figure 9 shows a schematic interaction diagram of another communication method provided in an embodiment of this application.

[0073] Figure 10 shows a schematic interaction diagram of another communication method provided in an embodiment of this application.

[0074] Figure 11 shows a schematic interaction diagram of another communication method provided in an embodiment of this application.

[0075] Figure 12 shows a schematic block diagram of a communication device provided in an embodiment of this application.

[0076] Figure 13 shows a schematic block diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0077] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0078] The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, “one or more” means one or more (including two); “and / or” describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character “ / ” generally indicates that the preceding and following related objects are in an “or” relationship.

[0079] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0080] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0081] Figure 1 is a schematic diagram of a 4G network architecture applicable to the communication method provided in the embodiments of this application. As shown in Figure 1, the network architecture of the embodiments of this application may include the following:

[0082] 1. User Equipment (UE): Also known as terminal equipment, terminal, access terminal, handheld terminal, laptop, subscriber unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. UE can also be a cellular phone, smartphone, wireless data card, tablet computer, wireless modem, handheld device, laptop computer, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), machine type communication (MTC) terminal, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle equipment, wearable device, terminal equipment in 5G networks, or terminal equipment in future communication systems, etc. The UE can also be an end device, logical entity, or smart device, such as a mobile phone, smart terminal, or other terminal device; or a server, gateway, base station, controller, or other communication device; or an Internet of Things (IoT) device, such as a sensor, electricity meter, water meter, or other IoT device. The UE can also be a wired device, such as a computer or laptop. This application embodiment does not limit this. The embodiments of this application are described below using the UE as an example of a terminal device. Alternatively, it can be any other device capable of accessing the network.

[0083] 2. E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and EPC (Evolved Packet Core). E-UTRAN is the radio access part of the 4G network. It consists of eNodeB (evolved Node B), which is responsible for handling radio interface functions, including radio resource management and air interface control.

[0084] 3. MME (Mobility Management Entity): Responsible for mobility management, including tracking the UE's location and managing its status. This includes performing authentication and access control, initiating paging processes to locate the UE, controlling the UE's handover process, and interacting with the HSS to obtain user subscription information.

[0085] 4. S-GW (Serving Gateway): As a data gateway between the UE and the network, it is responsible for forwarding and routing user data packets, enforcing charging and QoS policies, and supporting data packet buffering during UE mobility management.

[0086] 5. P-GW (PDN Gateway): As a gateway to external networks, it connects to the Internet or other service provider networks, and is responsible for IP address allocation, policy enforcement, etc.

[0087] 6. HSS (Home Subscriber Server): Stores user subscription data and authentication information, provides user data to MME and S-GW / P-GW, saves user identity, authentication keys and other information, and supports user location registration and updates.

[0088] 7. SCEF (Service Capability Exposure Function): This is a functional entity in 4G LTE networks, primarily used to support non-IP data delivery services, especially in Machine-to-Machine (M2M) communication and Internet of Things (IoT) applications. SCEF acts as an interface, enabling application servers to interact with the core network without directly navigating the IP network.

[0089] 8. AS (Application Server): The application server is the part of the network architecture responsible for providing specific services and application logic. The main functions of the application server include: providing specific services to users, such as messaging services, location services, and billing services; application logic processing: the AS is responsible for handling logic related to applications, including the execution of business rules and data processing; interaction with other network components: the AS interacts with other components in the core network through standardized interfaces, such as SCEF and PCRF; policy control: the AS can interact with PCRF to implement specific policies and billing rules to ensure that services meet expected requirements; and interaction between the AS and the core network: the application server interacts with other components in the core network through specific interfaces.

[0090] 9. PCRF (Policy and Charging Rules Function): Responsible for formulating and implementing network policies and charging rules.

[0091] In the aforementioned 4G network, terminal equipment can establish an air interface connection with E-UTRAN via the Uu interface. E-UTRAN establishes a user plane data connection with SGW via the S1-U interface, and SGW establishes a control plane signaling connection with MME via S11. S1-MME is the interface between MME and eNodeB, used for control plane information. S6a is the interface between MME and HSS. Rx is the interface between PCRF and Application Function (AF). T6a is the interface between MME and SCEF. The Gx interface is the interface between PCRF and P-GW. SGW establishes a user plane data connection with PGW via the S5 / S8 interface, and PGW connects to the data network via the SGi interface.

[0092] It should be noted that Figure 1 is only an exemplary architecture diagram. In addition to the functional units shown in Figure 1, the network architecture may also include other functional units or functional entities, and the embodiments of the present invention do not limit this.

[0093] Figure 2 is a schematic diagram of a 5G network architecture applicable to the communication method provided in the embodiments of this application. As shown in Figure 2, the network architecture of the embodiments of this application may include the following:

[0094] 1. User Equipment (UE): Also known as terminal equipment, terminal, access terminal, handheld terminal, laptop, subscriber unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. UE can also be a cellular phone, smartphone, wireless data card, tablet computer, wireless modem, handheld device, laptop computer, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), machine type communication (MTC) terminal, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle equipment, wearable device, terminal equipment in 5G networks, or terminal equipment in future communication systems, etc. The UE can also be an end device, logical entity, or smart device, such as a mobile phone, smart terminal, or other terminal device; or a server, gateway, base station, controller, or other communication device; or an Internet of Things (IoT) device, such as a sensor, electricity meter, water meter, or other IoT device. The UE can also be a wired device, such as a computer or laptop. This application embodiment does not limit this. The embodiments of this application are described below using the UE as an example of a terminal device. Alternatively, it can be any other device capable of accessing the network.

[0095] 2. Access network (AN) equipment: For terminal equipment to access the operator's network, it first goes through the access network equipment, and then can connect to the service nodes of the operator's network through the access network equipment.

[0096] 3. Access and Mobility Management Function (AMF) entity: This is a control plane network function provided by the operator's network, responsible for access control and mobility management of terminal devices accessing the operator's network. Functions include mobility state management, allocation of temporary user identities, authentication and authorization of users, etc.

[0097] 4. Security Anchor Function (SEAF): SEAF connects to AMF and acts as a node for security authentication. In practice, AMF and SEAF can be deployed together physically, or they can be configured independently. Furthermore, in some implementations, AMF and SEAF functionalities can be deployed separately, or a combination of AMF and SEAF functionalities can be configured in the same way (e.g., AMF includes SEAF functionality).

[0098] 5. Authentication Server Function (AUSF) entity: Used for authentication. For the home network AUSF, after receiving the initial authentication request from the serving network AMF, it sends an authentication request message to the home network UDM to request the authentication vector.

[0099] 6. Unified Data Management (UDM) Entity: Also known as UDM network function or UDM network function entity. It is a control plane function provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI), credential, security context, and subscription data of subscribed users in the operator's network. The SUPI is encrypted during transmission; the encrypted SUPI is called the subscription concealed identifier (SUCI). This information stored by the UDM entity can be used for authentication and authorization of terminal devices accessing the operator's network. Specifically, the subscribed users in the aforementioned operator's network can be users of services provided by the operator's network, such as users of China Telecom's mobile phone SIM cards or China Mobile's mobile phone SIM cards. The subscriber's SUPI can be the SIM card number, etc. The credential and security context can be small files storing the SIM card's encryption key or information related to the SIM card's encryption, used for authentication and / or authorization. The aforementioned security context can be data (cookies) or tokens stored on the user's local terminal (e.g., a mobile phone). The subscription data of the subscribed user can be the associated services of the mobile phone SIM card, such as the data plan of the mobile phone SIM card or the networks that the subscribed user is allowed to access.

[0100] Optionally, as shown in Figure 2, the network architecture of this embodiment may further include one or more of the following: network exposure function (NEF) entity, network function repository function (NRF) entity, policy control function (PCF) entity, application function (AF) entity, session management function (SMF) entity, or user plane function (UPF) entity. Other functions not described in Figure 2 can be found in the functions defined in the 3GPP standard protocols, and will not be elaborated upon here.

[0101] The naming conventions described above are solely for distinguishing different functions and do not imply that these are independent physical devices. This application does not limit the specific form of the devices described above; for example, they may be integrated into the same physical device or they may be separate physical devices. Furthermore, the naming conventions described above are only for distinguishing different functions and should not constitute any limitation on this application. This application does not exclude the possibility of using other naming conventions in future networks. For example, in 6G networks, some or all of the above-mentioned terms may be used, or other names may be adopted. This is a unified explanation provided here, and will not be repeated below.

[0102] In this network architecture, interface N1 serves as the reference point between the terminal device and the AMF entity; interface N2 serves as the reference point between the AN and AMF entities, used for sending non-access stratum (NAS) messages, etc.; interface N3 serves as the reference point between the (R)AN and UPF entities, used for transmitting user plane data, etc.; and interface N4 serves as the reference point between the SMF and UPF entities, used for transmitting information such as tunnel identification information for the N3 connection, data buffer indication information, and downlink data notification messages, etc. The interface names in Figure 2 are merely examples; in specific implementations, the interface names may differ, and this application does not impose any specific limitations on them.

[0103] It should be understood that the 4G network architecture and 5G network architecture described above in the embodiments of this application are merely illustrative examples of network architectures described from the perspective of service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to these, and any network architecture capable of implementing the functions described above is applicable to the embodiments of this application.

[0104] With the development of communication technology, non-terrestrial networks (NTN) systems are being used more and more widely. Compared with terrestrial network (TN) systems, NTN systems have the advantages of large coverage area and flexible networking.

[0105] Currently, in the NTN system, terminal devices communicate with satellites via service links, satellites communicate with ground stations via feeder links, and satellites communicate with each other via inter-satellite links. The ground station serves as the interface between the satellite and the ground network, and is responsible for data transmission between the satellite and the ground network.

[0106] Due to limitations in ground station deployment costs and geographical conditions, some remote areas, such as deserts and rainforests, lack ground stations or have only sparsely deployed ones. When satellites cover terminal devices in these areas, the satellite cannot connect to ground stations and terrestrial networks via feed links (or inter-satellite links + feed links). For terminal devices in these areas, communication services can be provided through store-and-forward satellite operations. In this case, end-to-end switching of signaling / data services is handled in two steps: when the service link is available, the satellite establishes a connection with the terminal device, accepting and storing data from the terminal device; when the feed link is available, the satellite sends the data to the application server through the ground network equipment. If this is the first time data is received from the terminal device, the ground network equipment creates context information for the terminal device and allocates specific network resources. In subsequent processes, if the application server has data to send to the terminal device, the ground network equipment can accept and store it. When the feed link becomes available, the network equipment sends the data to the appropriate satellite based on the context information.

[0107] If a terminal device moves from the aforementioned remote area to an area covered by the TN, the network equipment on the ground is still maintaining the context information of the terminal device related to the presence of satellite relay operations, and the resources allocated to the terminal device are not released, resulting in a waste of network resources.

[0108] To facilitate understanding of the embodiments of this application, the application scenarios applicable to the embodiments of this application will first be described in detail with reference to Figure 3. Figure 3 shows a schematic diagram of an example S&F scenario provided by an embodiment of this application. As shown in Figure 3, the scenario includes satellites 310a-310c, terminal devices 320a-320e, ground station 330, and ground network element 340. Terminal devices 320a-320e are in Store-and-Forward (S&F) mode.

[0109] First, a brief introduction to S&F mode: S&F mode is a data transmission mode in satellite communications that allows the satellite to temporarily store data when no service link / feed link is available, and then forward the data to its destination at a later, appropriate time. This mode is suitable for communications that need to cover large areas or long distances, especially when terrestrial networks are unavailable or it is difficult to establish a direct link. S&F mode has the following characteristics:

[0110] 1. Data storage: After receiving data, the satellite does not immediately forward it to the destination, but first stores it in the satellite's memory.

[0111] 2. Non-instantaneous transmission: Data transmission is not necessarily instantaneous, but rather the timing of data forwarding is determined based on a predetermined schedule or specific conditions (such as the availability of the destination).

[0112] 3. Wide-range communication: Particularly suitable for communication that needs to span large areas or long distances, such as communication in polar regions or remote areas.

[0113] In the example in Figure 3, terminal devices 320a-320e are connected to satellites 310a-310c via a service link, and satellites 310a-310c are connected to the ground network 340 via a power supply link through ground station 330.

[0114] When the terminal devices are in store-and-forward mode, if terminal devices 320a-320e are connected to satellites 310a-310c via a service link, then satellites 310a-310c cannot connect to the ground network 340 via the ground station 330 via the power supply link. If satellites 310a-310c are connected to the ground network 340 via the ground station 330 via the power supply link, then satellites 310a-310c cannot connect to terminal devices 320a-320e via the service link. That is, in the scenario illustrated in Figure 3, terminal devices 320a-320e and the ground network 340 cannot achieve end-to-end connectivity.

[0115] In the example in Figure 3, satellites 310a-310c can be regenerable satellites, or other types of satellites. A regenerable satellite refers to a satellite based on a regenerable payload, capable of receiving and relaying signals, and processing and regenerating the received signals to improve signal quality and transmission distance. Base stations and other network elements can be deployed on this satellite.

[0116] For example, Figure 4 illustrates a schematic diagram of a full-core network satellite S&F network architecture. As shown in Figure 4, a complete network is deployed on this satellite, including an access network, a core network, and application servers / agents. Taking a 4G network as an example, the access network can be E-UTRAN, and the core network elements specifically include: MME, S-GW, PGW, HSS, PCRF, SCEF, etc. Detailed descriptions of the access network elements and core network elements can be found in Figure 1, and will not be repeated here. It should be noted that in the S&F network architecture, agent network elements are deployed on both the satellite and the ground. These agent network elements are used for application data storage and forwarding. Of course, a 5G network can also be deployed on this satellite, meaning that the access network elements and core network elements can also be 5G network elements.

[0117] Figure 5 shows the data transmission flowchart in the S&F scenario. As shown in Figure 5, the satellite communication system in the S&F scenario includes terminal equipment, satellite 1, proxy network element and application server. Satellite 1 includes eNB, CN and proxy network element.

[0118] Step 1: When satellite 1 provides coverage for the UE, the UE initiates the attach procedure to attach to the network of satellite 1. It should be understood that when satellite 1 provides coverage for the UE, it means that the service link between the UE and satellite 1 is available. Therefore, in the S&F scenario, the feeder link between the ground network element and satellite 1 is unavailable.

[0119] Step 2: The UE sends Mobile Originated (MO) data to the core network on Satellite 1. The core network element on Satellite 1 sends the UE's status information and MO data to the proxy network element on the satellite. The proxy network element on the satellite is used to cache the UE's status information and data from the UE (i.e., MO data). It should be understood that the proxy network element on the satellite is also used for application layer and transport layer signaling processing, as well as the storage and forwarding of application layer data. The proxy network element on the satellite is also called the onboard proxy network element.

[0120] Step 3: When satellite 1 is about to leave the UE's location area, the UE and the network on the satellite perform a detach procedure, and the UE detaches from the network of satellite 1.

[0121] Step 4: When the power supply link is available, the proxy network element on satellite 1 will send the cached UE status information and data from the UE to the ground proxy network element (Proxy-T).

[0122] Step 5: The proxy network element assigns an address to the UE and creates context information (including UE ID, the correspondence between UE ID and IP address, UE location information, etc.).

[0123] Step 6: The ground agent network element uses the IP address assigned to the UE to send the data from the UE to the corresponding application server.

[0124] Step 7: When the AS has mobility termination data to send to the UE, the AS sends the UE's mobility termination data to the ground agent network element.

[0125] It should be noted that this MT data can be understood as downlink data sent by the AS to the UE.

[0126] Step 8: The ground agent network element selects a suitable target satellite for the UE based on the UE context information maintained locally (such as the satellite that can cover the UE's location the fastest, for example, satellite 2).

[0127] Step 9: The ground agent network element sends the UE's MT data to the agent network element on satellite 2.

[0128] Step 10: When satellite 2 provides coverage for the UE, the UE performs the attach procedure to attach to the network on satellite 2. Satellite 2 sends MT data to the UE. When satellite 2 is about to leave the UE's location area, the UE detaches from the network on satellite 2.

[0129] Based on the above data transmission flowchart in the S&F scenario, it can be seen that when the satellite providing services to the UE changes (satellite 1 switches to satellite 2), the ground agent network element can store and forward uplink or downlink data. That is, the ground agent network element can receive the UE's data information sent by the agent network element on satellite 1 and send the UE's data to the corresponding application server. It can also forward the downlink data of the application server to the agent network element on satellite 2.

[0130] It should be understood that when a UE moves from NTN to TN, its communication on the ground does not require the assistance of ground proxy network elements. Ground proxy network elements can promptly release resources occupied by the UE, avoiding resource waste.

[0131] The above scenario primarily occurs when the satellite providing services to the UE changes in a S&F (Surface and Ground) environment. In this scenario, the proxy network element can store and forward data sent or received by the user. When the terminal device moves from S&F mode to a terrestrial network, the proxy network element no longer needs to allocate or store resources for this terminal device. However, because the terrestrial proxy network element cannot detect the UE's mobility (the UE moving to a terrestrial network), the resources allocated to the UE by the terrestrial proxy network element cannot be released in a timely manner, resulting in resource waste.

[0132] In summary, when a UE moves from the S&F network to the TN network, how to enable the terrestrial agent network element to sense the UE's movement and release the occupied resources in a timely manner has become a technical problem that urgently needs to be solved.

[0133] To address the aforementioned technical problems, this application proposes a communication method and a communication device. A ground agent network element can send a first indication message, which instructs the HSS to send a first notification message to the ground agent network element when the terminal device moves to the TN. This first notification message can be the status information of the terminal device or a monitoring request, requesting the HSS to notify the ground agent network element when the terminal device moves to the TN. This allows the ground agent network element to promptly detect the UE's mobility and release the resources allocated to the UE in a timely manner, thus avoiding waste of network resources.

[0134] The communication method provided in this application will be described in detail below with reference to Figure 6. Figure 6 shows a schematic interactive diagram of a communication method provided in an embodiment of this application. This method can be applied in the scenario shown in Figure 3 above, and of course it can also be applied in other communication scenarios. This application embodiment does not limit it here.

[0135] As shown in Figure 6, the method 600 illustrated in Figure 6 may include steps S610 to S630. The steps of method 600 will be described in detail below with reference to Figure 6.

[0136] S610, the first network element sends a first instruction message to the second network element. The first instruction message is used to indicate that when the terminal device moves to the TN, the second network element sends a first notification message to the first network element.

[0137] In this embodiment of the application, the first network element refers to the network element that stores and forwards data or signaling of terminal equipment in the storage and forwarding satellite operation; the second network element refers to the network element that stores user subscription data and authentication information.

[0138] For example, the first network element can be a ground agent network element, which will be referred to as agent network element for ease of description below.

[0139] The second network element can be an HSS in a 4G network architecture, a UDM in a 5G network architecture, or other network elements that perform the same function. This application does not make any specific limitations on this.

[0140] In one possible implementation, the first indication information may refer to the status information of the terminal device, which is used to indicate that the terminal device is in store-and-forward mode.

[0141] The status information of the terminal device may include whether the terminal device is in store-and-forward mode, as well as the identifier of the terminal device and / or the information of the first network element.

[0142] The information of the first network element can be either its identifier or its address.

[0143] It should be noted that the first network element may send the status information of the terminal device to the second network element when it first receives the mobile initiation data of the terminal device, or it may send the status information of the terminal device to the second network element periodically. This application does not make specific restrictions on the timing of the first network element sending the status information of the terminal device.

[0144] In another possible implementation, the first indication information may refer to a monitoring request, which is used to instruct the second network element to send a first notification message to the first network element when the terminal device moves to the TN.

[0145] Optionally, the monitoring request may include monitoring events used to monitor the movement of the terminal device to the TN.

[0146] Furthermore, the monitoring request may also include the identifier of the terminal device and / or information of the first network element.

[0147] In this embodiment of the application, when the monitoring request includes the identifier of the terminal device and the information of the first network element, the first network element currently serving the terminal device can be identified.

[0148] Optionally, the first network element may send a monitoring request to the second network element when the first network element receives the mobile-initiated data from the terminal device for the first time. This application does not specify the timing for the first network element to send the monitoring request.

[0149] It should be noted that the first indication information can also be used to instruct the second network element to send a first notification message to the first network element when the terminal device exits the store-and-forward mode. The exit of the terminal device from the store-and-forward mode includes the terminal device moving to a TN where the feeder link and service link are simultaneously available, or the exit of the terminal device from the store-and-forward mode being determined by the radio access technology type. This application embodiment mainly describes the use of the first indication information to instruct the terminal device to move to the TN, but it does not constitute a limitation on other situations.

[0150] S620, the second network element sends a first notification message to the first network element. The first notification message is used to instruct the terminal equipment to move to the TN.

[0151] In some possible implementations, when the first indication message received by the second network element is the status information of the terminal device, the second network element can update the context of the terminal device based on the status information of the terminal device.

[0152] For example, the second network element can record that the terminal device is in store-and-forward mode. When the terminal device moves to the TN, the second network element sends a first notification message to the first network element.

[0153] Alternatively, the second network element can record the terminal device's status in store-and-forward mode and the information of the first network element. When the terminal device moves to the TN, the second network element sends a first notification message to the first network element.

[0154] In another possible implementation, when the second network element receives the first indication message as a monitoring request, and the terminal device moves to the TN, the second network element sends a first notification message to the first network element.

[0155] It should be understood that in 4G communication, the movement of a terminal device to the TN means that the terminal device attaches to the TN, while in 5G communication, the movement of a terminal device to the TN means that the terminal device registers with the TN.

[0156] In some implementations, the first notification message includes a movement indication for the terminal device, which indicates that the terminal device has now moved into the TN.

[0157] Furthermore, the first notification message may include the identifier of the terminal device.

[0158] In this embodiment of the application, when the first notification message contains the identifier of the terminal device, the first network element can release the resources of the terminal device based on the identifier of the terminal device, thereby avoiding the waste of network resources.

[0159] In other implementations, the first notification message may also include the address of the terminal device.

[0160] In this embodiment of the application, when the first notification message contains the address of the terminal device, the first network element can send the cached mobility termination data to the terminal device based on the address of the terminal device.

[0161] Optionally, before the second network element sends the first notification message to the first network element, the second network element sends a first request message to the fifth network element, which is used to request the address of the terminal device.

[0162] It should be understood that the address of the terminal device refers to the address assigned to the terminal device by the TN, and the fifth network element refers to the network element responsible for the mobility management of the terminal device.

[0163] For example, in a 4G network architecture, this fifth network element is an MME network element, and in a 5G network architecture, this fifth network element is an AMF network element. Alternatively, it could be other network elements that perform the same function; this application does not specifically limit its application in this regard.

[0164] In this embodiment of the application, the second network element sends a first request message to the fifth network element, requesting the address of the terminal device, so that the second network element can send the address of the terminal device to the first network element.

[0165] S630: Based on the first notification message, release the resources of the terminal device.

[0166] In some possible implementations, the first network element releases the resources of the terminal device, including at least one of the following: deleting the terminal device context information or state information, releasing the address allocated to the terminal device, disconnecting the connection established between the terminal device and the third network element, and establishing a connection between the terminal device and the fourth network element on the satellite.

[0167] For example, the third network element can be an AS or an SCS.

[0168] Furthermore, the fourth network element can be an agent network element on the satellite, used to store and forward data or signaling from terminal equipment during satellite storage and forwarding operations.

[0169] In method 600, when the terminal device is in store-and-forward mode, the first network element can send a first indication information to the second network element. The second network element sends a first notification message to the first network element based on the first indication information. The first notification message is used to indicate that the terminal device has moved to the TN, so that the first network element can sense that the terminal device has moved to the TN and release the resources of the terminal device in a timely manner, thereby avoiding the waste of network resources.

[0170] In some possible implementations, the first network element can also determine whether it has cached the mobile termination data of the terminal device. When the first notification message sent by the second network element to the first network element contains the address of the terminal device, the first network element can send the cached mobile termination data to the terminal device based on the address of the terminal device, thereby avoiding the waste of network resources.

[0171] In some other possible implementations, when the first network element determines that it has cached the mobile termination data of the terminal device, but the first notification message sent by the second network element to the first network element does not contain the address of the terminal device, the first network element may send a second indication message to the third network element. The second indication message is used to instruct the third network element to send retransmitted data to the terminal device. The retransmitted data includes: the mobile termination data of the terminal device cached by the first network element, and the second indication message carries information about the mobile termination data.

[0172] In this embodiment, when the first notification message does not contain the address of the terminal device, the first network element sends a second instruction message to the third network element, and simultaneously sends the cached mobility termination data information to the third network element. The third network element is the network element that manages the third application; therefore, the third network element can send the data corresponding to the mobility termination data information cached by the first network element to the terminal device. It should be understood that the mobility termination data information includes: mobility termination data or identification information corresponding to the mobility termination data.

[0173] One possible implementation is that the second indication information can be a NACK message, that is, the agent network element sends a NACK message to the AS, which is used to instruct the AS to send the cached data that needs to be retransmitted to the terminal device.

[0174] Furthermore, the NACK message can carry information about the unsent MT data cached by the agent network element that needs to be retransmitted. For example, the MT data information can be the unsent MT data packets cached by the agent network element or the identification information corresponding to the cached unsent MT data packets, such as the data packet sequence number range.

[0175] In other embodiments of this application, the first network element may also instruct the second network element to notify the third network element that the terminal device has moved to the TN. The third network element disconnecting from the first network element can trigger the first network element to release the terminal device's resources, thereby avoiding waste of network resources. The following describes another example of a communication method provided by this application in detail with reference to Figure 7. Figure 7 shows a schematic interactive diagram of another example of a communication method provided by an embodiment of this application. This method can be applied to the scenario shown in Figure 3 above, and of course, it can also be applied to other communication scenarios. This application embodiment does not impose any limitations here.

[0176] As shown in Figure 7, the method 700 illustrated in Figure 7 may include steps S710 to S740. The steps of method 700 will be described in detail below with reference to Figure 7.

[0177] S710, the first network element sends a first instruction message to the second network element. The first instruction message is used to indicate that when the terminal device moves to the TN, the second network element sends a first notification message to the third network element.

[0178] It should be noted that the third network element refers to the network element that manages third-party applications. For example, the third network element can be a Service Capability Server (SCS), an Application Server (AS), or other network elements that perform the same function. This application does not make any specific limitations on this.

[0179] It should also be noted that the specific content of the first indication information in step S710 is the same as that in step S610. The difference from step S610 is that the first indication information indicates that when the terminal device moves to the TN, the second network element sends a first notification message to the third network element.

[0180] S720, the second network element sends a first notification message to the third network element. The first notification message is used to instruct the terminal equipment to move to the TN.

[0181] In this embodiment of the application, after receiving the first instruction information, when the terminal device moves to the TN, the second network element sends a first notification message to the third network element.

[0182] Furthermore, the first notification message includes a movement indication for the terminal device, which indicates that the terminal device has currently moved into the TN. The first notification message carries an identifier for the terminal device.

[0183] S730 and the third network element disconnect from the first network element based on the first notification message.

[0184] In one possible implementation, after receiving the first notification message sent by the second network element, the third network element associates itself with the first network element associated with the terminal device based on the identifier of the terminal device it carries, and then disconnects from the first network element.

[0185] S740, the first network element releases the resources of the terminal equipment.

[0186] In step S730, after the third network element disconnects from the first network element, the first network element releases the resources of the terminal device.

[0187] This can be understood as the first network element and the third network element being in a disconnected state, which can trigger the first network element to release the resources of the terminal device.

[0188] Furthermore, the description of the first network element releasing the resources of the terminal device can be found in step S630, and will not be repeated here.

[0189] In method 700, when the terminal device is in store-and-forward mode, the first network element can send a first indication information to the second network element. The second network element sends a first notification message to the third network element based on the first indication information. The first notification message is used to instruct the terminal device to move to the TN. The third network element disconnects from the first network element based on the first notification message, thereby triggering the first network element to release the resources of the terminal device and avoiding waste of network resources.

[0190] In some possible implementations, the third network element can also determine whether there is data that needs to be retransmitted to the terminal device, including mobility termination data; when the third network element determines that there is data that needs to be retransmitted to the terminal device, the third network element sends the mobility termination data to the terminal device.

[0191] In this embodiment, the third network element can directly determine whether there is cached motion termination data. If it is determined that there is data that needs to be retransmitted to the terminal device, the cached motion termination data is directly sent to the terminal device, thereby avoiding the waste of network resources.

[0192] In some other possible implementations, when the first network element determines that it has cached the mobile termination data of the terminal device, the first network element can send a second indication information to the third network element. The second indication information is used to instruct the third network element to send retransmitted data to the terminal device. The retransmitted data includes: the mobile termination data of the terminal device cached by the first network element, and the second indication information carries the information of the mobile termination data.

[0193] In this embodiment of the application, the third network element does not directly determine whether there is data to be retransmitted to the terminal device. Instead, it receives a second indication information sent by the first network element, which indicates that there is data to be retransmitted to the terminal device and instructs the third network element to send the cached mobile termination data to the terminal device.

[0194] The communication method provided in this application will be specifically described below using a 4G network architecture as an example, in conjunction with Figures 8-11. In this method, the first network element is a proxy network element, the second network element is an HSS, and the third network element is an AS. As shown in Figure 8, the method 800 illustrated in Figure 8 may include steps S810 to S880. The various steps in method 800 will be described in detail below with reference to Figure 8.

[0195] S810, the terminal equipment sends mobile initiation data to the satellite.

[0196] The terminal device performs Attach in store-and-forward mode and sends MO data to the satellite.

[0197] It should be understood that this MO data mainly refers to data services initiated by users, such as sending text messages, making phone calls, browsing the Internet, and using mobile applications.

[0198] The execution of Attach by a terminal device in store-and-forward mode may include the following two scenarios: one is when the terminal device first accesses a store-and-forward satellite, and the other is when the terminal device reconnects to the network after a long period of non-communication with a store-and-forward satellite.

[0199] It should be understood that the main purpose of performing Attach is to establish a connection between the terminal device and the storage and forwarding satellite; that is, to perform Attach so that the terminal device can access the storage and forwarding satellite.

[0200] It should also be understood that the ability of a terminal device to access, store, and forward satellite signals can refer to the terminal device monitoring the satellite, the terminal device initiating MO signaling or data transmission to the satellite, or the terminal device receiving MT signaling / data from the satellite.

[0201] Optionally, after establishing a connection with a satellite, the terminal device may also establish a connection with other satellites, meaning the terminal device may also register with other satellites, thus enabling the terminal device to perform Detach.

[0202] It should be understood that performing a Detach can refer to the terminal device or satellite actively initiating a Detach process to disconnect the terminal device from the satellite when the terminal device no longer uses satellite services or is about to leave the satellite coverage area. Alternatively, it can refer to the terminal device and satellite performing a local Detach to release context information after the terminal device leaves the satellite coverage area.

[0203] Once the terminal device establishes a connection with the store-and-forward satellite, the satellite caches the MO data initiated by the terminal device, as well as the terminal device's status information. This allows the terminal device to forward its MO data and status information to the ground network element when the feed link between the satellite and the ground network element becomes available.

[0204] Optionally, the status information of the terminal device may include the terminal device's identifier, the terminal device's location information, and the terminal device's storage and forwarding monitoring list.

[0205] The store-and-forward monitoring list refers to the list of store-and-forward satellites that terminal devices can access, and is used to indicate the identifiers of the store-and-forward satellites that the terminal devices can monitor and access.

[0206] In one possible implementation, the store-and-forward satellite can cache MO data and terminal device status information in proxy network elements (also known as onboard proxy network elements) on the satellite. It should be understood that the proxy network elements in the store-and-forward satellite are used to cache and forward relevant information from the terminal devices.

[0207] S820: The satellite sends MO data and terminal equipment status information to the ground agent network element.

[0208] The S830 ground agent network element sends MO data to the application server.

[0209] It should be understood that when the service link is available but the feeder link is unavailable, the satellite receives and stores data from the terminal equipment. When the feeder link becomes available, the satellite transmits the stored data from the terminal equipment to the ground agent network element.

[0210] After receiving MO data and the status information of the terminal device, the ground agent network element assigns an IP address to the terminal device. The ground agent network element can then use the assigned IP address to send data from the terminal device to the application server.

[0211] For example, after receiving the status information of the terminal device, the terrestrial agent network element assigns a corresponding IP address to the terminal device and creates a context for the terminal device based on the terminal device's identifier, the mapping relationship between the terminal device's identifier and IP address, the terminal device's location information, and the storage and forwarding monitoring list.

[0212] S840, the agent network element sends a first indication message to the SCEF network element. The first indication message is used to indicate that when the terminal device moves to the TN, the home subscriber server sends a first notification message to the agent network element.

[0213] The S850 and SCEF network elements send the first instruction information to the HSS network element.

[0214] When a terminal device moves from an area covered by the NTN to an area covered by the TN, in order for the terrestrial agent network element to sense the movement of the terminal device and release the resources allocated to the terminal device in a timely manner, the terrestrial agent network element can send a first indication message to the HSS through the SCEF. The first indication message is used to indicate that when the terminal device moves to the TN, the HSS should notify the agent network element.

[0215] It should be understood that the SCEF network element is the interface between the AS and the core network, ensuring the security and integrity of data transmission. For example, the SCEF can authenticate proxy network elements.

[0216] In one possible implementation, the first indication information may refer to the status information of the terminal device, which is used to indicate that the terminal device is in store-and-forward mode.

[0217] The status information of the terminal device may include whether the terminal device is in store-and-forward mode, as well as the identifier of the terminal device and / or the information of the proxy network element.

[0218] The identifier of the proxy network element can be either the identifier of the proxy network element or the address of the proxy network element.

[0219] It should be noted that the agent network element may send the terminal device status information to the HSS either when it first receives the terminal device's mobility initiation data, or periodically. This application does not specify the timing for the agent network element to send the terminal device status information.

[0220] In another possible implementation, the first indication information may refer to a monitoring request, which is used to instruct the HSS to send a first notification message to the agent network element when the terminal device moves to the TN.

[0221] Optionally, the monitoring request may include monitoring events used to monitor the movement of the terminal device to the TN, and the monitoring request may also include the identifier of the terminal device and / or information of the agent network element.

[0222] In this embodiment of the application, when the monitoring request includes the identifier of the terminal device and the information of the proxy network element, the proxy network element currently serving the terminal device can be identified.

[0223] Optionally, the agent network element may send a monitoring request to the HSS when it first receives the mobile initiation data from the terminal device. This application does not specify the timing for the agent network element to send the monitoring request.

[0224] The monitoring request can also be a subscription request, which can be understood as the agent network element subscribing to the HSS for the reachability of the UE. When the terminal device moves to the TN, it requests the HSS to send the first notification message to the agent network element.

[0225] It should be understood that UE reachability refers to the ability to successfully locate and communicate with the UE in the network. UE reachability includes UE status information, UE location updates, paging mechanisms, UE registration, and network configuration. Through effective UE status management, location updates, and paging mechanisms, the network can ensure that the UE can be located and communicated with at any time.

[0226] It should be noted that there is no specific limitation on when the agent network element subscribes to the UE's reachability from the HSS. That is, the agent network element can subscribe to the UE's reachability from the HSS when it first receives the UE's MO data or UE's status information.

[0227] S860 and HSS update the context of terminal devices.

[0228] When the first indication information is the status information of the terminal device, after the HSS receives the status information of the terminal device, the storage UE is currently in storage and forwarding mode.

[0229] The status information of the terminal device includes whether the terminal device is in store-and-forward mode, as well as the identifier of the terminal device and / or the information of the proxy network element.

[0230] It should be noted that step S860 is an optional step. When the first indication information is a monitoring request, step S860 can be omitted.

[0231] S870 and HSS send a first notification message to the agent network element based on the first instruction information.

[0232] In some implementations, the first notification message includes a movement indication for the terminal device, indicating that the terminal device has currently moved into the TN. The first notification message may also include an identifier for the terminal device.

[0233] In this embodiment of the application, when the first notification message contains the identifier of the terminal device, the first network element can release the resources of the terminal device based on the identifier of the terminal device, thereby avoiding the waste of network resources.

[0234] S880, the first network element releases the resources of the terminal equipment.

[0235] To avoid wasting resources, when a ground agent network element senses that a terminal device has moved, the ground agent network element releases the resources allocated to the terminal device.

[0236] In some possible implementations, releasing the resources of the terminal device includes at least one of the following: deleting the terminal device context information or state information, releasing the address allocated to the terminal device, disconnecting the connection established between the terminal device and the AS, and establishing the connection between the terminal device and the agent network element on the satellite.

[0237] It should be understood that the agent network element on the satellite is used to store and forward data or signaling from terminal equipment during satellite operations.

[0238] In the above embodiments, when the terminal device is still in the S&F mode of NTN, the ground agent network element can send a first indication information to the HSS network element. The first indication information is used to instruct the HSS to send a first notification message to the ground agent network element when the UE moves to TN, so that the ground agent network element can sense the movement of the UE and release the resources of the terminal device in a timely manner to avoid resource waste.

[0239] This application also provides another communication method in which, when the terminal device exits store-and-forward mode and moves to TN, the first notification message sent by the HSS to the ground agent network element carries the destination address of the UE, and the ground agent network element can forward the locally cached MT data to the UE based on the UE's address.

[0240] The communication method provided in this application will be described in detail below with reference to Figure 9. Figure 9 shows a schematic interactive diagram of another communication method provided in the embodiment of this application. This method can be applied in the scenario shown in Figure 3 above, and of course it can also be applied in other communication scenarios. This application embodiment does not limit it here.

[0241] As shown in Figure 9, the method 900 illustrated in Figure 9 may include steps S910 to S980. The steps of method 900 will be described in detail below with reference to Figure 9.

[0242] S910, the terminal device sends an attach request message to the MME.

[0243] It should be noted that before step S910, the terminal device is in store-and-forward mode, and the ground agent network element sends the first indication information to the HSS. When the terminal device moves from the NTN to the TN, the terminal device sends an attach request message to the MME, indicating that the terminal device requests to establish a connection.

[0244] Optionally, the attach request message carries a Moving From S&F indication message, which indicates that the UE was last registered in store-and-forward mode.

[0245] S920 and HSS send the terminal device address request to MME.

[0246] When the terminal device moves to the TN, the HSS determines that the terminal device has exited the S&F mode. The HSS sends an address request message to the MME, which is used to request the UE's IP address.

[0247] It should be noted that both the Moving From S&F indication message carried in the attach request message in step S910 and step S920 can trigger the MME to send the UE's IP address to the HSS. Therefore, at least one of the above two methods can be selected for execution.

[0248] S930 and MME send the UE's address to HSS.

[0249] The MME sends the UE's address to the HSS based on the Moving From S&F indication sent by the terminal device or the address request message sent by the HSS.

[0250] S940a and HSS send a first notification message to SCEF, which carries the address of the UE.

[0251] S940b and SCEF send the first notification message to the agent network element.

[0252] Based on the above steps S910-S930, the HSS can obtain the UE's IP address. When the HSS determines that the UE has exited store-and-forward mode and entered the TN cell, the HSS sends a first notification message to the agent network element.

[0253] Furthermore, the first notification message carries the UE ID, the UE's IP address, and the UE mobility indication, wherein the UE IP address is the IP address assigned to the UE by the TN, and the UE mobility indication is used to indicate that the UE is currently attached to the TN.

[0254] Based on the first notification message, the S950 and agent network elements release the resources of the terminal device.

[0255] To avoid wasting resources, the ground agent network element releases the UE-related resources after receiving the first notification message sent by the HSS.

[0256] Releasing UE-related resources includes deleting UE context information or state information, releasing the IP address assigned to the UE, and disconnecting the connection between the UE and the SCS / AS and the agent network elements on the satellite.

[0257] S960, the agent network element determines whether there is cached mobile termination data.

[0258] Before sending the data cached by the UE, the ground agent network element determines whether it has cached the UE's MT data locally. The following two conditions can be used to determine if the UE has cached MT data:

[0259] The first scenario involves MT data that has not yet been transmitted on the ground agent network element.

[0260] The second scenario involves the ground agent network element sending the data cached by the UE to the satellite, but not receiving feedback from the satellite, or the data still being stored locally by the ground agent network element before the estimated delivery time expires. Here, the estimated delivery time is the estimated time required for the MT data sent from the satellite to the ground agent network element to reach the UE when the ground agent network element sends the MT data to the satellite.

[0261] S970, the agent network element sends cached mobility termination data to the PGW.

[0262] S980 and PGW send cached mobility termination data to the terminal device via SWG.

[0263] In one possible implementation, when the data type of the MT cached by the proxy network element is IP data, the proxy network element sends the data directly to the address of the terminal device through IP routing, and the MT data reaches the PGW of the current serving UE in the TN.

[0264] Furthermore, the PGW sends the MT data to the SGW of the currently serving UE, and the SGW sends the data to the UE through the eNB.

[0265] In another possible implementation, when the data type of the MT data cached by the proxy network element is Non-IP, the proxy network element establishes a non-IP data transmission configuration with the SCEF for the Non-IP data transmission of the UE.

[0266] Specifically, the proxy network element sends the cached MT data to the SCEF, the SCEF sends the MT data to the MME via the PGW and SWG, and the MME sends the MT data to the terminal device on a non-access stratum protocol data unit (NAS PDU).

[0267] In the above embodiments, when the ground proxy network element senses that the UE has moved to the TN cell, the proxy network element releases the UE resources in a timely manner, and obtains the address of the terminal device, and sends the cached but unsent MT data to the terminal device.

[0268] This application also provides another communication method where the HSS does not carry the UE's IP address when sending the first notification message to the proxy network element. Therefore, when the proxy network element needs to send cached but unsent MT data to the UE, it can send the MT data information to the AS, which then sends the MT data to the terminal device.

[0269] The following describes in detail another communication method provided by this application with reference to Figure 10. Figure 10 shows a schematic interactive diagram of another communication method provided by the embodiment of this application. This method can be applied in the scenario shown in Figure 3 above, and of course it can also be applied in other communication scenarios. This application embodiment does not limit it here.

[0270] As shown in Figure 10, the method 1000 illustrated in Figure 10 may include steps S1010 to S1050. The various steps in method 1000 will be described in detail below with reference to Figure 10.

[0271] S1010, The terminal device executes the attachment process.

[0272] S1020a and HSS send the first notification message to SCEF.

[0273] S1020b and SCEF send the first notification message to the agent network element.

[0274] When the HSS determines that the UE has exited store-and-forward mode and entered the TN cell, the HSS sends a first notification message to the agent network element, which carries the UE ID.

[0275] S1030 and the agent network element release UE-related resources based on the first notification message.

[0276] S1040, the agent network element determines whether there is cached mobile termination data.

[0277] The description of step S1040 can be found in the description of step S960, and will not be repeated here.

[0278] S1050, the agent network element sends a second instruction message to the AS.

[0279] In this embodiment of the application, the second indication information is used to instruct the AS to send retransmission data to the terminal device. The retransmission data includes: the mobility termination data of the terminal device cached by the proxy network element, and the second indication information carries information about the mobility termination data.

[0280] It should be noted that the second indication message can also be interpreted as the MT data cached by the proxy network element not being successfully sent.

[0281] In one possible implementation, the second indication information can be a NACK message, i.e., the agent network element sends a NACK message to the AS, which is used to instruct the AS to send the data that needs to be retransmitted to the terminal device.

[0282] Furthermore, the NACK message can carry information about the data that needs to be retransmitted from the proxy network element cache. For example, the data information can be the MT data cached by the proxy network element or the identification information corresponding to the cached MT data, such as the data packet sequence number range.

[0283] S1060 and AS send MT data to PWG.

[0284] S1070 and PWG send MT data to UE via SWG.

[0285] In one possible implementation, for IP packets, the SCS / AS directly sends the data that needs to be retransmitted to the PGW of the currently serving UE. After the data arrives at the PGW, the PGW sends the data to the SGW of the currently serving UE, and the SGW sends it to the UE through the eNB.

[0286] In another possible implementation, for Non-IP packets, after the AS establishes NIDD configuration with SCEF, it sends the MT data that needs to be retransmitted to the PGW through SCEF, and then sends it to the UE through the SGW and eNB of the current serving UE (not shown in Figure 10).

[0287] In the above embodiments, when the proxy network element senses that the UE has moved to the TN cell, the proxy network element releases the UE resources and sends the cached but unsent MT data to the terminal device through the SCS / AS, thereby avoiding the waste of network resources.

[0288] This application also provides another communication method in which the HSS sends a first notification message to the AS, and the AS disconnects the connection with the agent network element, triggering the agent network element to release the resources of the terminal device, thereby avoiding the waste of network resources.

[0289] The following describes another communication method provided by this application in detail with reference to Figure 11. Figure 11 shows a schematic interactive diagram of a communication method provided by an embodiment of this application. This method can be applied in the scenario shown in Figure 3 above, and of course it can also be applied in other communication scenarios. This application embodiment does not limit it here.

[0290] As shown in Figure 11, method 1100 may include steps S1110 to S1150. The steps of method 1100 will be described in detail below with reference to Figure 11.

[0291] S1110, The terminal device executes the attachment process.

[0292] S1120a and HSS send the first notification message to SCEF.

[0293] S1120b and SCEF send the first notification message to AS.

[0294] S1130 and AS disconnect from the agent network element.

[0295] In this embodiment of the application, the first notification message sent by the HSS to the AS includes the identifier of the terminal device. The AS can associate the connection with the proxy network element based on the identifier of the terminal device and disconnect the connection with the proxy network element.

[0296] S1140, The agent network element releases the UE's resources.

[0297] After the AS disconnects from the agent network element, the agent network element releases the resources of the terminal device.

[0298] This can be understood as the AS and the agent network element being disconnected, which can trigger the agent network element to release the resources of the terminal device.

[0299] S1150, the agent network element determines whether there is cached mobile termination data.

[0300] The description of step S1150 can be found in the description of step S960, and will not be repeated here.

[0301] S1160, the agent network element sends a second instruction message to the AS.

[0302] In some possible implementations of this application, when the proxy network element determines that it has cached the mobile termination data of the terminal device, the proxy network element can send a second indication information to the AS. The second indication information is used to instruct the AS to send retransmitted data to the terminal device. The retransmitted data includes: the mobile termination data of the terminal device cached by the proxy network element. The second indication information carries information about the mobile termination data.

[0303] In this embodiment of the application, the AS does not directly determine whether there is data that needs to be retransmitted to the terminal device. Instead, it receives a second indication information sent by the proxy network element. The second indication information indicates that there is data to be retransmitted to the terminal device and instructs the AS to send the cached mobile termination data to the terminal device.

[0304] In some other possible implementations, the AS can directly determine the data that needs to be retransmitted to the terminal device, including mobility termination data; the AS sends the mobility termination data to the terminal device (not shown in Figure 11).

[0305] For example, the AS determines that the MT data of the terminal device that needs to be retransmitted includes the following three cases:

[0306] 1. AS sends data to the agent network element and receives MT data as NACK from the agent network element;

[0307] 2. AS sends MT data to the agent network element, but does not receive ACK feedback from the agent network element;

[0308] 3. AS sends MT data to the agent network element, and the corresponding estimated delivery time has not yet expired.

[0309] In this embodiment, the AS can directly determine whether there is cached mobile termination data. If it is determined that there is data that needs to be retransmitted to the terminal device, the cached mobile termination data is sent directly to the terminal device, thereby avoiding the waste of network resources.

[0310] S1170 and AS send MT data to PWG.

[0311] S1180 and PWG send MT data to UE via SWG.

[0312] In one possible implementation, for IP packets, the SCS / AS directly sends the MT data that needs to be retransmitted to the PGW of the currently serving UE. After the data arrives at the PGW, the PGW sends the MT data to the SGW of the currently serving UE, and the SGW sends it to the UE through the eNB.

[0313] In another possible implementation, for Non-IP packets, after the AS establishes NIDD configuration with SCEF, it sends the MT data that needs to be retransmitted to the PGW through SCEF, and then sends it to the UE through the SGW and eNB of the current serving UE (not shown in Figure 11).

[0314] The method embodiments provided in this application have been described above. The apparatus embodiments provided in this application will be described below. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, any content not described in detail can be referred to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0315] Figure 12 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 12, the communication device 1200 may include a transceiver unit 1210 and / or a processing unit 1220. The transceiver unit 1210 can implement corresponding communication functions, and the processing unit 1220 is used for data processing. The transceiver unit 1210 may also be referred to as a communication interface or a communication unit. Optionally, the device 1200 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 1220 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiment.

[0316] In one possible design, the device 1200 can be the first network element in the above method embodiments. For example, the device 1200 can be a proxy network element, or it can be a chip, processor, or chip system that implements the proxy network element function. It can also be a logical node, logical module, or software that can implement all or part of the proxy network element function. The device 1200 can be used to execute the steps or processes performed by the first network element in any of the above method embodiments.

[0317] Specifically, the transceiver unit 1210 can be used to receive a first message from the first device and send first indication information. The first indication information is used to instruct the second network element to send a first notification message to the first network element or the third network element when the terminal device moves to the TN. The transceiver unit 1210 is also used to receive the first notification message, which is used to instruct the terminal device to move to the TN; the processing unit 1220 is used to release the resources of the terminal device based on the first notification message.

[0318] Optionally, the first indication information includes: the status information of the terminal device, the status information being used to indicate that the terminal device is in store-and-forward mode.

[0319] Optionally, the status information of the terminal device includes the terminal device being in store-and-forward mode, and also includes the identifier of the terminal device and / or the information of the first network element.

[0320] Optionally, the first indication information includes: a monitoring request, which is used to indicate that when the terminal device moves to the TN, the home subscriber server sends the first notification message to the first network element or the second network element.

[0321] Optionally, the monitoring request includes a monitoring event, which is used to monitor the terminal device moving to the TN. The monitoring request also includes the identifier of the terminal device and / or the information of the first network element.

[0322] Optionally, releasing the resources of the terminal device includes at least one of the following: deleting the context information or status information of the terminal device, releasing the address allocated to the terminal device, disconnecting the connection established between the terminal device and the third network element, and establishing a connection between the terminal device and a fourth network element on the satellite, wherein the fourth network element is used to store and forward the data or signaling of the terminal device in store-and-forward satellite operations.

[0323] Optionally, the first notification message includes a movement indication of the terminal device, and also includes the identifier of the terminal device and / or the address of the terminal device, wherein the movement indication is used to indicate that the terminal device has now moved to the TN.

[0324] Optionally, the processing unit 1220 is further configured to determine whether the terminal device has cached mobile termination data; and to send the mobile termination data based on the first notification message.

[0325] Optionally, the processing unit 1220 is further configured to send a second indication information to the third network element, the second indication information being configured to instruct the second network element to send retransmission data to the terminal device, the retransmission data including: the mobility termination data of the terminal device cached by the first network element, the second indication information carrying information of the mobility termination data.

[0326] In one possible design, the device 1200 can be a second network element in the above method embodiments. For example, the device 1200 can be an HSS network element, or it can be a chip, processor, or chip system that implements the HSS network element function. It can also be a logical node, logical module, or software that can implement all or part of the HSS network element function. The device 1200 can be used to execute the steps or processes performed by the second network element in any of the above method embodiments.

[0327] Specifically, the transceiver unit 1210 can be used to receive first indication information, which is used to indicate that when the terminal device moves to the terrestrial communication network TN, the second network element sends a first notification message to the first network element or the third network element. The first network element is used to store and forward the data or signaling of the terminal device in the storage and forwarding satellite operation. The transceiver unit 1210 is also used to send a first notification message based on the first indication message, which is used to indicate that the terminal device moves to the TN.

[0328] Optionally, the first indication information includes: the status information of the terminal device, the status information being used to indicate that the terminal device is in store-and-forward mode.

[0329] Optionally, the status information of the terminal device includes the terminal device being in store-and-forward mode, and also includes the identifier of the terminal device and / or the information of the first network element.

[0330] Optionally, the processing unit 1220 is used to update the context of the terminal device based on the status information of the terminal device.

[0331] Optionally, the processing unit 1220 is further configured to record that the terminal device is in store-and-forward mode, or to record that the terminal device is in store-and-forward mode and the information of the first network element.

[0332] Optionally, the first indication information includes: a monitoring request, which is used to indicate that when the terminal device moves to the TN, the second network element sends a first notification message to the first network element or the third network element.

[0333] Optionally, the monitoring request includes a monitoring event, which is used to monitor the terminal device moving to the TN. The monitoring request also includes the identifier of the terminal device and / or the information of the first network element.

[0334] Optionally, the first notification message includes a movement indication of the terminal device, and also includes the identifier of the terminal device and / or the address of the terminal device, wherein the movement indication is used to indicate that the terminal device has now moved to the TN.

[0335] Optionally, the transceiver unit 1210 is further configured to send a first request message to the fifth network element, the first request message being used to request the address of the terminal device, the address of the terminal device being the address allocated to the terminal device by the TN, and the fifth network element being used for mobility management of the terminal device; the transceiver unit 1210 is further configured to receive the address of the terminal device sent by the fifth network element.

[0336] In one possible design, the device 1200 can be the first network element in the above method embodiments. For example, the device 1200 can be an AS network element, or it can be a chip, processor, or chip system that implements the AS network element function. It can also be a logical node, logical module, or software that can implement all or part of the AS network element function. The device 1200 can be used to execute the steps or processes performed by the third network element in any of the above method embodiments.

[0337] Specifically, the transceiver unit 1210 can be used to receive a first notification message, which is used to instruct the terminal device to move to the terrestrial communication network (TN). The first notification message includes: a movement indication of the terminal device and an identifier of the terminal device. The movement indication is used to indicate that the terminal device is currently moving to the TN. Based on the first notification message, the connection with a first network element is disconnected. The disconnection between the first network element and the third network element is used to trigger the first network element to release the resources of the terminal device. The first network element is used to store and forward the data or signaling of the terminal device in the store-and-forward satellite operation.

[0338] Optionally, the transceiver unit 1210 can also be used to determine data that needs to be retransmitted to the terminal device, the data including mobility termination data; the transceiver unit 1210 can also send the mobility termination data.

[0339] Optionally, the transceiver unit 1210 can also be used to receive second indication information, which instructs the second network element to send retransmitted data to the terminal device. The retransmitted data includes: mobility termination data of the terminal device buffered by the first network element, and the second indication information carries information about the mobility termination data. The processing unit 1220 is used to determine the data that needs to be retransmitted to the terminal device based on the second indication information.

[0340] It should be understood that the "unit" in device 1200 can be implemented in hardware, software, or by hardware executing corresponding software. For example, the "unit" can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components supporting the described functions. As another example, transceiver unit 1210 can be replaced by transceiver circuitry (e.g., may include receiving and transmitting circuitry), and processing unit 1220 can be replaced by a processor or processing circuitry.

[0341] Figure 13 shows a schematic block diagram of another communication device provided in an embodiment of this application. The communication device 1300 may be a first network element, a second network element, or a third network element, or it may be a chip, chip system, or processor, etc., within the first network element, second network element, or third network element that implements the above-described method. This device can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0342] The communication device 1300 may include one or more processors 1310, which may also be referred to as processing units, and can implement certain control functions. The processor 1310 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0343] In an alternative design, the processor 1310 may also store instructions and / or data that can be executed by the processor 1310 to cause the communication device 1300 to perform the methods described in the above method embodiments.

[0344] In another alternative design, the communication device 1300 may include a communication interface 1320 for implementing receiving and transmitting functions. For example, the communication interface 1320 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0345] Optionally, the communication device 1300 may include one or more memories 1330, which may store instructions that can be executed on the processor 1310, causing the communication device 1300 to perform the methods described in the above method embodiments. Optionally, the memories 1330 may also store data. Optionally, the processor 1310 may also store instructions and / or data. The processor 1310 and the memories 1330 may be provided separately or integrated together.

[0346] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0347] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0348] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0349] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to execute the various steps or processes performed by the network element / device in any of the above method embodiments.

[0350] This application also provides a computer-readable storage medium storing program code that, when run on a computer, causes the computer to execute the various steps or processes performed by the network element / device in any of the above method embodiments.

[0351] This application also provides a communication device, including a processor and an interface, the interface being used to send and / or receive signals, causing the processor to execute the various steps or processes performed by the network element / device in any of the above method embodiments.

[0352] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

[0353] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. The embodiments of this application do not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0354] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0355] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0356] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be based on the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0357] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0358] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0359] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0360] In the above embodiments, the functions of each functional unit can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. 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. 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 wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0361] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or parts of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0362] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method characterized by comprising: The method is applied to a first network element, which is used to store and forward data or signaling from terminal equipment during store-and-forward satellite operations. The method includes: Send a first instruction message to the second network element. The first instruction message is used to instruct the second network element to send a first notification message to the first network element when the terminal device moves to the terrestrial communication network (TN). The second network element is used to store the user's subscription data and authentication information. The terminal device receives a first notification message sent by the second network element, the first notification message being used to instruct the terminal device to move to the TN; Based on the first notification message, the first network element releases the resources of the terminal device, which are used to support the storage and forwarding modes of the terminal device.

2. A communication method characterized by comprising: The method is applied to a first network element, which is used to store and forward data or signaling from terminal equipment during store-and-forward satellite operations. The method includes: Send a first instruction message to the second network element. The first instruction message is used to instruct the second network element to send a first notification message to the third network element when the terminal device moves to the terrestrial communication network (TN). The second network element is used to store the user's subscription data and authentication information. The third network element is used to manage third-party applications. When the first network element and the third network element disconnect, the first network element releases the resources of the terminal device, which are used to support the storage and forwarding modes of the terminal device.

3. The method according to claim 1 or 2, characterized in that, The first indication information includes: the status information of the terminal device, which indicates that the terminal device is in store-and-forward mode.

4. The method of claim 3, wherein, The status information of the terminal device includes at least one of the following: the terminal device is in store-and-forward mode, the identifier of the terminal device, or the information of the first network element.

5. The method according to claim 1 or 2, characterized in that, The first indication is a monitoring request.

6. The method of claim 5, wherein, The monitoring request includes at least one of the following: a monitoring event, the identifier of the terminal device, or information of the first network element; The monitoring event is used to monitor the terminal device moving to the TN.

7. The method according to any one of claims 1 to 6, characterized in that, The first network element releases the resources of the terminal device, including at least one of the following: Delete the context information or status information of the terminal device, release the address allocated to the terminal device, disconnect the connection established between the terminal device and the third network element, or disconnect the connection established between the terminal device and the fourth network element on the satellite; The fourth network element is used to store and forward data or signaling from terminal equipment during satellite storage and forwarding operations.

8. The method of claim 1, wherein, The first notification message includes at least one of the following: The terminal device's movement indication, the terminal device's identifier, or the terminal device's address; The movement indication is used to indicate that the terminal device is currently moving into the TN.

9. The method of claim 8, wherein, The method further includes: Determine whether the terminal device's mobile termination data is cached; The mobility termination data is sent based on the first notification message.

10. The method according to any one of claims 1-7, characterized in that, The method further includes: Determine whether the terminal device's mobile termination data is cached; A second instruction message is sent to a third network element, which instructs the third network element to send retransmitted data to the terminal device. The retransmitted data includes: the mobility termination data of the terminal device cached by the first network element. The second instruction message carries information about the mobility termination data. The third network element is used to manage third-party applications.

11. A communication method characterized by comprising: The method is applied to a second network element, which stores the user's subscription data and authentication information. The method includes: The first network element receives a first instruction message sent by a first network element. The first instruction message is used to instruct the second network element to send a first notification message to the first network element or the third network element when the terminal device moves to the terrestrial communication network (TN). The first network element is used to store and forward the data or signaling of the terminal device in the storage and forwarding satellite operation. The third network element is used to manage third-party applications. Based on the first instruction message, the second network element sends a first notification message to the first network element or the third network element, the first notification message being used to instruct the terminal device to move to the TN.

12. The method of claim 11, wherein, The first indication information includes: the status information of the terminal device, which indicates that the terminal device is in store-and-forward mode.

13. The method of claim 12, wherein, The status information of the terminal device includes at least one of the following: the terminal device is in store-and-forward mode, the identifier of the terminal device, or the information of the first network element.

14. The method according to any one of claims 11-13, characterized in that, The method further includes: Update the context of the terminal device based on its status information.

15. The method of claim 14, wherein, Updating the context of the terminal device includes: Record that the terminal device is in store-and-forward mode, or record that the terminal device is in store-and-forward mode and the information of the first network element.

16. The method of claim 11, wherein, The first indication information includes a monitoring request.

17. The method of claim 16, wherein, The monitoring request includes at least one of the following: a monitoring event, the identifier of the terminal device, or information of the first network element; The monitoring event is used to monitor the terminal device moving to the TN.

18. The method according to any one of claims 11-17, characterized by, The first notification message includes at least one of the following: The terminal device's movement indication, the terminal device's identifier, or the terminal device's address; The movement indication is used to indicate that the terminal device is currently moving into the TN.

19. The method according to any one of claims 11-18, characterized in that, Before sending the first notification message, the method further includes: Send a first request message to the fifth network element. The first request message is used to request the address of the terminal device. The address of the terminal device is the address assigned to the terminal device by the TN. The fifth network element is used for the mobility management of the terminal device. Receive the address of the terminal device sent by the fifth network element.

20. A communication method, the method being applied to a third network element, the third network element being used to manage third-party applications, the method comprising: The terminal device receives a first notification message sent by a second network element. The first notification message is used to instruct the terminal device to move to the terrestrial communication network (TN). The first notification message includes: a movement indication of the terminal device and an identifier of the terminal device. The movement indication is used to indicate that the terminal device is currently moving to the TN. The second network element is used to store the user's subscription data and authentication information. The connection with the first network element is disconnected based on the first notification message. The disconnection between the first network element and the third network element is used to trigger the first network element to release the resources of the terminal device. The first network element is used to store and forward the data or signaling of the terminal device in the storage and forwarding satellite operation.

21. The method of claim 20, wherein, The method further includes: The data that needs to be retransmitted to the terminal device is determined, including motion termination data; Send the movement termination data.

22. The method of claim 21, wherein, The data that needs to be retransmitted to the terminal device includes: The third network element receives a second instruction information sent by the first network element. The second instruction information is used to instruct the third network element to send retransmitted data to the terminal device. The retransmitted data includes: the mobility termination data of the terminal device cached by the first network element. The second instruction information carries information about the mobility termination data. Based on the second indication information, the data that needs to be retransmitted to the terminal device is determined.

23. A communications device, characterized by include: A module or unit for performing the method as described in any one of claims 1 to 10, or a module or unit for performing the method as described in any one of claims 11 to 19, or a module or unit for performing the method as described in any one of claims 20 to 22.

24. A communications device, characterized by include: A processor and a memory, the processor being coupled to the memory for storing a computer program, the computer program being executed by the processor causing the apparatus to perform the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 19, or the method as claimed in any one of claims 20 to 22.

25. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on a computer, causes the computer to perform the method as described in any one of claims 1 to 10, or the method as described in any one of claims 11 to 19, or the method as described in any one of claims 20 to 22.

26. A computer program product, characterised in that, include: A computer program, when run on a computer, causes the computer to perform the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 19, or the method as claimed in any one of claims 20 to 22.

Images