A communication method, a communication device, and a system

Abstract

The application provides a communication method, a communication device and a system. The method comprises the following steps: a first device receives a first list sent by a first satellite, the first list indicating a satellite needing to synchronize subscription data of a terminal device; and the first device sends a first message to a second satellite, wherein the second satellite is located in the first list, and the first message is used to instruct the second satellite to acquire the subscription data of the terminal device. According to the embodiment of the application, the second satellite can synchronize the subscription data of the terminal device, so that the terminal device can successfully establish a communication connection with any second satellite.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, communication device and system. Background Technology

[0002] In a non-terrestrial network (NTN), satellites communicate with users via service links, with ground stations via feeder links, and with other satellites via inter-satellite links (ISL). Typically, when a user accesses the network through an NTN, they can utilize these links to achieve end-to-end connectivity between the user, satellite, and ground station, receiving timely network services.

[0003] In some remote areas without ground stations, there is a limitation of discontinuous feeder links. When satellites cover users in these areas (i.e., the service link is available), the lack of a ground station prevents the satellite from connecting. After the satellite moves, once it covers a ground station and establishes a connection with the terrestrial network (i.e., the feeder link is available), the satellite cannot cover users in these areas. Therefore, in scenarios with discontinuous feeder links, satellite service to users depends on the satellite storing users' subscription data. However, due to limited satellite storage resources, storing unnecessary user subscription data can easily waste network resources.

[0004] Therefore, how to enable users to successfully access the network via NTN is a problem we need to solve. Summary of the Invention

[0005] This application provides a communication method, communication device, and system. The method can send the subscription data to satellites that need to synchronize the subscription data, enabling terminal devices to successfully establish connections with these satellites. At the same time, by recording the storage status of the subscription data on the satellite, the method can update the subscription data stored on the satellite in a timely manner, reducing resource waste caused by unnecessary storage of subscription data.

[0006] In a first aspect, a communication method is provided. This method can be executed by a communication device (i.e., a computer device, such as a server) or by a module (e.g., a processor, chip, or chip system) applied to the communication device. It can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the communication device. In this communication method, a first device receives a first list from a first satellite, which indicates satellites whose subscribed data of a terminal device needs to be synchronized. The first device is used to store and forward data or signaling of the terminal device in a store-and-forward satellite operation. The first device sends a first message to a second satellite, which instructs the second satellite to acquire the subscribed data of the terminal device. The second satellite is located in the first list.

[0007] As can be seen from the above embodiments, the first device can send the subscription data to the satellites that need to synchronize the subscription data of the terminal device, as indicated by the first list sent by the first satellite, so that when the terminal device sends a connection request to the satellites indicated by the first list, it can successfully access the network and obtain satellite services.

[0008] In conjunction with the first aspect, in one possible implementation, after the first device sends a first message to the second satellite, the first device receives response information from the second satellite regarding the first message, which is used to instruct the second satellite on the acquisition / update of the terminal device's subscribed data.

[0009] For example, after receiving the response information of the first message, the first device can determine that the second satellite has acquired the contracted data of the terminal device.

[0010] As can be seen from the above implementation, the first device obtains the subscription data of the second satellite by responding to the first message, ensuring that the second satellite synchronizes the subscription data, thereby ensuring that the terminal device can successfully establish a connection with the second satellite.

[0011] In conjunction with the first aspect, in one possible implementation, the first device records status information of the second satellite storing the subscription data, the status information including at least one of the following: whether the subscription data is saved, and the time information of the last time the subscription data was received.

[0012] For example, the first device can make a record after sending a first message, that is, record that the second satellite has saved the subscription data, and can use the time of sending the first message as the time information of the second satellite most recently receiving the subscription data.

[0013] As can be seen, in the above implementation, the first device records the status information of the contract data stored on the second satellite, which provides a reference for subsequent judgment on whether the contract data stored on the second satellite needs to be updated. This facilitates timely updates of the contract data, ensuring that the terminal device can successfully establish a connection with the second satellite while avoiding resource waste caused by storing the contract data before the update.

[0014] In conjunction with the first aspect, in one possible implementation, the first device sends a second message to the second device, the second message instructing the second device to send a third message to the first device in the event of an update to the subscription data, wherein the second device is used to store the subscription data of the terminal device.

[0015] For example, the first device subscribes to the subscription data update event from the second device, that is, sends a second message. When the subscription data on the second device changes, it sends a third message to the first device. When the first device receives the third message, it knows that the subscription data has changed.

[0016] As can be seen from the above implementation, the first device can obtain the update status of the contract data through the second and third messages, providing a reference for subsequent judgment on whether the contract data stored in the second satellite needs to be updated; when the contract data changes, the first device can notify the second satellite to obtain the contract data again, thereby ensuring the smooth connection between the terminal device and the second satellite.

[0017] In conjunction with the first aspect, in one possible implementation, the first device determines to send a first message to the second satellite based on at least one of the following: the second satellite stores status information of the subscription data; and a third message indicating that the subscription data has been updated.

[0018] As can be seen from the above implementation, the first device can send a first message to the second satellite in a timely manner to notify the second satellite to obtain the contracted data, thus ensuring a smooth connection between the terminal device and the second satellite.

[0019] In conjunction with the first aspect, in one possible implementation, the first device determines to send a first message to the second satellite, which may include at least one of the following situations: the second satellite does not store the subscription data; the second satellite last received the subscription data before the first device received the third message.

[0020] For example, if there is no record of the second satellite acquiring the subscription data on the first device, a first message can be sent to the second satellite to notify it to acquire the subscription data.

[0021] For example, after the first device records the time information of the second satellite's most recent receipt of the contract data, it receives a third message from the second device indicating that the contract data has changed after the second satellite acquired it. At this time, the first device can send a first message to the second satellite to notify the second satellite to acquire the contract data again, that is, to update the contract data.

[0022] As can be seen from the above implementation, when the subscription data changes or the subscription data does not exist on the second satellite, the first device sends a first message to the second satellite to notify the second satellite to obtain the subscription data, ensuring that the second satellite stores the subscription data available to the terminal device, so that when the terminal device requests a connection from the second satellite, it can successfully establish a connection with the second satellite and obtain satellite services.

[0023] Secondly, a communication method is provided. This method can be executed by a communication device (i.e., a computer device, such as a server) or by a module (e.g., a processor, chip, or chip system) applied to the communication device. It can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the communication device. In this communication method, a second device receives a first list or a fourth message sent by a second satellite. The second device stores the subscription data of a terminal device. The first list indicates satellites whose subscription data of the terminal device needs to be synchronized. The fourth message instructs the second device to send the subscription data of the terminal device to the second satellite. The second satellite is located in the first list.

[0024] For example, the second device receives the first list and sends the terminal device's subscription data to the satellites indicated by the first list.

[0025] For another example, the second device receives a fourth message sent by the second satellite, and responds to the fourth message by sending the subscription data back to the second satellite.

[0026] As can be seen from the above implementation, the second device sends the subscription data to the second satellite, so that the satellites indicated by the first list synchronize the subscription data. When the terminal device sends a connection request to the satellites indicated by the first list, it can successfully access the network and obtain satellite services.

[0027] In conjunction with the second aspect, in one possible implementation, the second device records the status information of the second satellite storing the subscription data, the status information including at least one of the following: whether the subscription data is stored, and the time information of the most recent receipt of the subscription data.

[0028] As can be seen from the above implementation, the second device records the status information of the contract data stored on the second satellite, which provides a reference for subsequent judgment on whether the contract data stored on the second satellite needs to be updated. This facilitates timely updates of the contract data stored on the second satellite, ensures the availability of the contract data, and enables the terminal device to connect smoothly with the second satellite.

[0029] In conjunction with the second aspect, in one possible implementation, the second device determines to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite, or a fourth message.

[0030] As can be seen from the above implementation, the second device can update the contract data on the second satellite in a timely manner, ensuring the availability of the contract data and enabling the terminal device to connect smoothly with the second satellite.

[0031] In conjunction with the second aspect, in one possible implementation, the second device determines to send the subscription data to the second satellite based on the status information of the second satellite storing the subscription data in at least one of the following situations: one situation is that the second satellite does not store the subscription data; another situation is that the subscription data has been updated since the second satellite last received the subscription data.

[0032] For example, if there is no record of the second satellite acquiring the contract data on the second device, that is, the second satellite has not acquired the contract data, then the contract data can be sent to the second satellite.

[0033] For another example, after the second device records the time information of the last time the second satellite received the contract data, if the contract data stored locally by the second device changes, the second device will send the contract data to the second satellite again, that is, update the contract data.

[0034] As can be seen from the above implementation, when the subscription data changes or the subscription data does not exist on the second satellite, the second device sends the subscription data stored by the second device to the second satellite to ensure that the second satellite stores usable subscription data, so that when the terminal device requests a connection from the second satellite, it can successfully establish a connection with the second satellite and obtain satellite services.

[0035] Thirdly, a communication method is provided. This method can be executed by a communication device (i.e., a computer device, such as a server) or by a module (e.g., a processor, chip, or chip system) applied to the communication device. It can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the communication device. In this communication method, a second device records status information of the subscription data of a third satellite storage terminal device. The status information includes at least one of the following: whether the subscription data is saved, and the time information of the most recent receipt of the subscription data. Based on the status information, the second device determines to send the subscription data to the third satellite.

[0036] For example, the third satellite may be the second satellite, and the second device records the status information of the contracted data of the terminal device stored on the second satellite.

[0037] As can be seen from the above implementation, the second device records the status information of the contract data stored on the satellite that has transmitted the contract data, which provides a reference for subsequent judgment on whether the contract data needs to be updated, facilitates timely updating of the contract data, and ensures smooth connection between the terminal device and the satellite.

[0038] In conjunction with the third aspect, in one possible implementation, the second device determines to send the subscription data to the third satellite based on the status information of the subscription data stored by the third satellite in at least one of the following situations: one situation is that the third satellite does not store the subscription data; another situation is that the subscription data has been updated since the time when the third satellite last received the subscription data.

[0039] For example, if there is no record of the third satellite acquiring the contract data on the second device, that is, the third satellite has not acquired the contract data, then the contract data can be sent to the third satellite.

[0040] For another example, after the second device records the time information of the third satellite's most recent receipt of the contract data, if the contract data stored locally by the second device changes, it will send the contract data to the third satellite again, that is, update the contract data.

[0041] As can be seen from the above implementation, when the contract data changes or the contract data does not exist on the third satellite, the second device sends the contract data stored on the second device to the third satellite to ensure the availability of the contract data stored on the third satellite. This allows the terminal device to successfully establish a connection with the third satellite and obtain satellite services when it requests a connection from the second device.

[0042] Fourthly, a communication method is provided. This method can be executed by a communication device (i.e., a computer device, such as a server) or applied to a module of the communication device (e.g., a processor, chip, or chip system). It can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the communication device. In this communication method, a first satellite receives a fifth message from a terminal device, the fifth message being used to request network access; the first satellite determines a first list, the first list indicating satellites that need to synchronize the subscribed data of the terminal device; when the communication link between the first satellite and the ground network is available, the first satellite sends the first list to a ground device, the ground device including a first device or a second device, the first device being used to store and forward the data or signaling of the terminal device in store-and-forward satellite operations, and the second device being used to store the subscribed data of the terminal device.

[0043] As can be seen from the above implementation, the first satellite sends the first list to the ground equipment, enabling the ground equipment to obtain information about the satellites that need to synchronize the contracted data, providing a basis for the synchronization of the contracted data, so that the satellites indicated by the first list can synchronize the contracted data, and when the terminal device requests a connection again, the first satellite can successfully establish a connection with the terminal device and provide satellite services to the terminal device.

[0044] In conjunction with the fourth aspect, in one possible implementation, the first list includes a store-and-forward monitoring list, which indicates satellites that have established connections with the terminal device, including satellites that have established connections and are required to synchronize the contracted data of the terminal device.

[0045] For example, when the first satellite does not have cells in the first list, the store-and-forward monitoring list generated by the first satellite can be used directly as the first list.

[0046] As can be seen from the above implementation, satellites that can establish a connection with the terminal device can be directly identified as satellites that need to synchronize the contracted data of the terminal device, so that all satellites that can establish a connection with the terminal device can obtain the contracted data, ensuring that the terminal device can successfully access the network when it sends a connection request to these satellites again.

[0047] In conjunction with the fourth aspect, in one possible implementation, the first satellite determines a second list, which includes a store-and-forward monitoring list indicating satellites with which the terminal device has established a connection. That is, in addition to the store-and-forward monitoring list, a first list is determined.

[0048] As can be seen, the above implementation method can determine the satellites that need to synchronize the contracted data based on more system performance, which is more in line with the system requirements.

[0049] In conjunction with the fourth aspect, in one possible implementation, the first satellite may determine the first list based on first information, which may include at least one of the following: the current location information of the terminal device, the power saving requirements of the terminal device, the movement trajectory of the terminal device, the mapping relationship between the satellite's coverage area and time, and network policy information.

[0050] In conjunction with the fourth aspect, in one possible implementation, the ground equipment includes a first device, namely, a first satellite sends a first list to the first device, and the first satellite receives the subscription data of the terminal device sent by the second device; if the communication link between the first satellite and the terminal device is available, the first satellite establishes a connection with the terminal device based on the subscription data of the terminal device and performs data transmission.

[0051] As can be seen from the above implementation, the first satellite synchronized the contract data, enabling the terminal device to connect smoothly with the first satellite.

[0052] In conjunction with the fourth aspect, in one possible implementation, the ground equipment includes a first device, namely, a first satellite sends a first list to the first device, the first satellite receives a first message sent by the first device, the first message being used to instruct the first satellite to acquire the subscription data of the terminal device; the first satellite sends a sixth message to the second device, the sixth message being used to instruct the second device to send the subscription data of the terminal device to the first satellite, the first satellite receives the subscription data of the terminal device sent by the second device; if the communication link between the first satellite and the terminal device is available, the first satellite establishes a connection with the terminal device based on the subscription data of the terminal device and performs data transmission.

[0053] As can be seen from the above implementation, when the first satellite receives the first information from the first device, it instructs the first satellite to request the subscription data from the second device, that is, to send the sixth message, so that the first satellite synchronizes the subscription data; when the terminal device sends an access request to the first satellite again, the first satellite can successfully connect with the terminal device.

[0054] In conjunction with the fourth aspect, in one possible implementation, the ground equipment includes a second device, and the first satellite sends the terminal device identifier and the first list to the second device, that is, the first satellite directly sends the first list to the second device.

[0055] As can be seen from the above implementation, the second device directly obtains the list of satellites that need to synchronize the subscription data, and can actively send the subscription data to the satellites that need to synchronize the subscription data, so that the satellites can synchronize the subscription data in a timely manner and ensure that the terminal device can successfully access the network.

[0056] In conjunction with the fourth aspect, in one possible implementation, the first satellite receives the subscription data of the terminal device sent by the second device; if the communication link between the first satellite and the terminal device is available, the first satellite establishes a connection with the terminal device based on the subscription data of the terminal device and performs data transmission.

[0057] As can be seen from the above implementation, the first satellite synchronized the contract data, enabling the terminal device to connect smoothly with the first satellite.

[0058] Fifthly, a communication method is provided. This method can be executed by a communication device (i.e., a computer device, such as a server) or applied to a module of the communication device (e.g., a processor, chip, or chip system). It can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the communication device. In this communication method, when a communication link between a second satellite and a ground network is available, the second satellite receives subscription data from a terminal device of the second device. The second device stores the subscription data of the terminal device. The second satellite is located in a first list, which indicates satellites that need to synchronize the subscription data. When a communication link between the second satellite and the terminal device is available, the second satellite establishes a connection with the terminal device based on the subscription data and performs data transmission.

[0059] As can be seen from the above implementation, all satellites that need to synchronize the subscription data have obtained the subscription data, and when the terminal device sends an access request to any one of the satellites, it can successfully obtain satellite services.

[0060] In conjunction with the fifth aspect, in one possible implementation, the second satellite receives a first message sent by the first device, the first message instructing the second satellite to acquire the subscription data of the terminal device; the second satellite sends a fourth message to the second device, the fourth message instructing the second device to send the subscription data of the terminal device to the second satellite.

[0061] As can be seen from the above implementation, when the second satellite receives the first information from the first device, it is instructed to request the subscription data from the second device, i.e., to send the fourth message, so that the second satellite synchronizes the subscription data; when the terminal device sends an access request to the second satellite, the second satellite can successfully connect with the terminal device.

[0062] Sixthly, this application provides a communication device, which may be a network device or a chip / circuit therein. The communication device is used to perform the method in the first aspect or any possible implementation thereof. The communication device includes units having the ability to perform the method in the first aspect or any possible implementation thereof.

[0063] In a seventh aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions that, when executed, cause a computer to perform a method as described in any of the possible embodiments of the first to second aspects.

[0064] Eighthly, a computer program product is provided, comprising: computer program code, which, when executed by a computer, causes the computer to perform a method as described in any of the possible implementations of the first to second aspects.

[0065] A ninth aspect provides a chip including at least one processor and an interface, the processor being configured to read and execute instructions stored in a memory, wherein when the instructions are executed, the chip causes the chip to perform a method as described in any of the possible implementations of the first to second aspects.

[0066] It is understood that the communication device provided in the sixth aspect, the computer-readable storage medium provided in the seventh aspect, the computer program product provided in the eighth aspect, and the chip provided in the ninth aspect are all used to execute the methods provided in the embodiments of this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. Attached Figure Description

[0067] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0068] Figure 1 This is a schematic diagram of a full-core online satellite payload architecture provided in an embodiment of this application;

[0069] Figure 2 This is a schematic diagram illustrating a process for a user equipment to access an NTN network, as provided in an embodiment of this application.

[0070] Figure 3 This is a schematic diagram illustrating an application scenario provided in an embodiment of this application;

[0071] Figure 4A This is a schematic diagram of a 4G system architecture provided in an embodiment of this application;

[0072] Figure 4B This is a schematic diagram of a 5G system architecture provided in an embodiment of this application;

[0073] Figure 5 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0074] Figure 6a This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0075] Figure 6b This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0076] Figure 7 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0077] Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0078] Figure 9 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0079] Figure 10 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0080] Figure 11 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0081] Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0082] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0083] In the description of the embodiments of this application, unless otherwise stated, " / " means "or", for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, B exists alone, and A and B exist simultaneously. In addition, in the description of the embodiments of this application, "multiple" means two or more, and "multiple types" means two or more.

[0084] It should be understood that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0085] In the description of this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design that is described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0086] It is understood that in the description of this application, "when," "if," and "if" all refer to the device performing a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action when it is implemented, nor do they imply any other limitations. The device performing a corresponding action under certain objective circumstances includes: satisfying the objective circumstances, i.e., being able to perform the corresponding action; or satisfying both the objective circumstances and other circumstances, in order to perform the corresponding action.

[0087] Furthermore, it is understood that in the various embodiments of this application, expressions such as "A corresponds to B," "A and B correspond," "A corresponds to B," or similar expressions indicate that B is associated with A, and B can be determined based on A. Determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0088] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0089] In a non-terrestrial network (NTN), satellites communicate with user equipment via service links, with ground stations via feeder links, and with other satellites via inter-satellite links (ISL). Typically, when a user accesses the network via an NTN, they can utilize these links to achieve end-to-end connectivity between the user, satellite, and ground station, receiving timely network services.

[0090] However, in some remote areas without ground stations, such as deserts and oceans, there is a limitation due to discontinuous feeder links. In scenarios with discontinuous feeder links, for a given satellite, the service link and the feeder link are not simultaneously available. That is, when user equipment is connected to the satellite via the service link, the satellite cannot connect to the ground network via the feeder link; conversely, when the satellite is connected to the ground network via the feeder link, it cannot connect to the user equipment via the service link. In other words, when a satellite covers users in this area, it cannot connect to a ground station because there is no ground station deployed in that area. After the satellite moves, when it covers a ground station and establishes a connection with the ground network, it has already left its location where it could cover the aforementioned area, meaning it can no longer cover the users and cannot establish a connection with them.

[0091] In scenarios with discontinuous power supply links, on the one hand, since the satellite cannot connect to the terrestrial network while connecting to the user, the satellite's ability to serve the user depends on the satellite storing the user's subscription data; on the other hand, due to limited onboard payload storage resources, it is necessary to avoid storing unnecessary user subscription data, which would waste network resources. Therefore, users may not be able to successfully access the network.

[0092] To support NTN services in scenarios with discontinuous power supply links, a satellite load architecture based on full-core network deployment proposes deploying all core network elements on satellites. For example... Figure 1 As shown, in this network architecture, the satellite possesses all the functions of the access network, core network, and application server (proxy). Taking a 4G network as an example, the access network refers to the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), the core network-onboard (CN-onboard) includes the Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), Home Subscriber Server (HSS), Policy and Charging Rules Function (PCRF), and Service Capability Exposure Function (SCEF), etc. Proxy units are deployed on the satellite and ground stations for receiving, storing, and forwarding user data. In this network architecture, the various network elements are connected through interfaces.

[0093] In a non-connectivity scenario with a power supply link, the flowchart for User Equipment (UE) accessing the NTN network in the satellite payload architecture of a full-core network is as follows: Figure 2 As shown, the proxy entity is a device or module used for receiving, storing, and forwarding user data. The ground-based proxy entity is denoted as Proxy-ground, and the ground-based HSS is denoted as HSS-ground. The specific steps are as follows:

[0094] S201, The UE sends a connection request (Attach Request) to satellite #1.

[0095] Initially, satellite #1 does not store the UE's subscription data. When the service link of satellite #1 becomes available, the UE sends a connection request to the onboard radio base station (such as an eNB). The onboard radio base station forwards the connection request to the onboard MME. This connection request indicates the store-and-forward (S&F) capability. That is, when satellite #1 receives the connection request sent by the UE, satellite #1 is operating in S&F mode. Only by identifying the store-and-forward capability through this connection request can it respond to the connection request sent by the user (such as the onboard MME requesting authentication data from the onboard HHS).

[0096] S202, the onboard MME requests UE authentication data from the onboard HSS.

[0097] After receiving a connection request from a UE and determining whether to respond, the onboard MME requests the UE's authentication data from the onboard HSS. The UE's authentication data is used to verify whether the UE has the right to access the system.

[0098] S203, the onboard HSS sends an authentication data rejection message.

[0099] Since satellite #1 did not save the UE's subscription data in the initial state, after receiving the signal from the onboard MME requesting authentication data, the onboard HSS determined that the UE's subscription data did not exist locally, and therefore sent an authentication data rejection message to the onboard MME.

[0100] S204. The onboard MME determines the store-and-forward monitoring list (S&F Monitoring List).

[0101] After receiving the authentication data rejection message, the onboard MME determines a store-and-forward monitoring list, which is used to indicate the satellites that have established a connection with the terminal device. For example, the store-and-forward monitoring list can instruct the UE to request a connection from the satellite again, or it can be used to instruct the UE to receive downlink data or send uplink data.

[0102] For example, the onboard MME can determine the store-and-forward monitoring list based on the UE's current location information, the power-saving requirements of the communication system, the UE's movement trajectory, and the mapping relationship between the coverage area and time of satellites in the store-and-forward monitoring list. The mapping relationship between coverage area and time can be represented by ephemeris information or satellite coverage availability information. Determining the store-and-forward monitoring list based on the power-saving requirements of the communication system can mean reducing the number of satellites in the store-and-forward monitoring list when the power-saving requirements are high, thereby reducing the interaction between satellites and ground stations and achieving a power-saving effect.

[0103] S205, the onboard MME sends a connection rejection message to the UE, carrying the store-and-forward monitoring list.

[0104] After receiving the authentication data rejection message, the onboard MME learns that the UE cannot connect to the satellite, so it sends a connection rejection message to the UE. The connection rejection message carries the store-and-forward monitoring list determined in step S204.

[0105] S206. The UE saves the store-and-forward monitoring list.

[0106] S207. The onboard MME sends the UE's status data to the onboard Proxy.

[0107] The onboard MME sends the UE's status data to the onboard proxy entity. This UE status data includes the International Mobile Subscriber Identity (IMSI), the UE's latest location information, the store-and-forward monitoring list, etc.

[0108] S208, the onboard proxy sends the UE's status data to the proxy-ground.

[0109] When the power supply link between satellite #1 and ground equipment is available, the onboard proxy entity sends the UE's status data to the ground proxy entity. This UE status data includes the International Mobile Subscriber Identity (IMSI), the UE's latest location information, the store-and-forward monitoring list, etc.

[0110] S209a, the onboard HSS sends a UE subscription data request to the HSS-ground.

[0111] S209b and HSS-ground send UE subscription data responses to the onboard HSS.

[0112] In steps S209a and S209b, the satellite-based HSS obtains the UE's subscription data from the ground-based HSS.

[0113] S210, Execute the connection process and perform data transmission.

[0114] When the service link between satellite #1 and the UE is available, the UE performs the attach procedure and transmits data.

[0115] S211, the onboard proxy stores the relevant data of the UE locally.

[0116] The onboard proxy entity stores relevant UE data locally. This UE data includes UE status data and / or UE application data. The UE status data includes the International Mobile Subscriber Identity (IMSI), the UE's latest location information, and the store-and-forward monitoring list. The UE application data includes data generated by the UE during the process of obtaining satellite services.

[0117] As can be seen from the above process, under a satellite load architecture with the entire core network deployed on satellites, considering the limited onboard payload resources, the satellite may not store the user's subscription data. That is, initially, satellite #1 does not store the UE's subscription data. After the UE fails to access the satellite, the satellite is triggered to retrieve the UE's subscription data from the ground network when the feed link with the ground station becomes available. This subscription data is used to provide service to the UE when it requests access from the satellite again. In this case, for other satellites that can provide services to the user, when the user requests access from another satellite, that satellite may still not have the UE's subscription data and therefore cannot provide service.

[0118] To address this issue, this application proposes a communication method in which, upon receiving an access request from a UE, a satellite determines a satellite list indicating satellites that can provide services to the UE. Based on this satellite list, the UE's subscription data is synchronized to the satellites that can provide services to the UE, thereby ensuring that the UE can successfully access the network and obtain satellite services even in scenarios where the power supply link is discontinuous. At the same time, updating the subscription data stored on the satellite reduces the waste of storage resources.

[0119] Figure 3 The application scenarios of this application are illustrated below. Figure 3The following is a detailed explanation using the NTN satellite access diagram shown in the image, illustrating a scenario with a discontinuous feeder link. Here, the terminal equipment can also be referred to as user equipment, and the regenerable satellite refers to a satellite based on a regenerable payload. The primary application scenario of this application is NTN satellite access under discontinuous feeder link conditions, synchronizing the terminal equipment's subscription data to all satellites that can provide services to the terminal equipment, enabling the terminal equipment to successfully access the network. For example, in the initial stage, if the terminal device 301's subscription data is not stored on the regenerating satellite 303, the terminal device 301 sends a connection request to the regenerating satellite 303. The regenerating satellite 303 cannot establish a connection with the terminal device 301, so it sends a connection rejection message to the terminal device 301. When the regenerating satellite 303 can establish a connection with the ground station 302, the regenerating satellite 303 obtains the terminal device 301's subscription data from the ground station 302, and synchronizes the terminal device 301's subscription data to all satellites that can provide services to the terminal device 301, such as the regenerating satellites 303, 304, and 305, so that the terminal device 301 can successfully access the network and obtain satellite services by sending a connection request to any one of the regenerating satellites 303, 304, and 305 again.

[0120] It should be noted that, Figure 3 The number and types of terminal devices included in the system architecture shown are merely examples, and the embodiments of this application are not limited thereto. For example, it may also include more or fewer terminal devices 301 communicating with the regenerator 303, which are not described one by one in the accompanying drawings for the sake of simplicity. Figure 3 The number and types of satellites included in the system architecture shown are merely examples, and the embodiments of this application are not limited thereto. For example, it may also include more or fewer satellites communicating with the terminal device; for the sake of simplicity, they are not described one by one in the accompanying drawings.

[0121] The embodiments of this application can be applied to a variety of system architectures. That is, the ground network of the ground station and the satellite network on the satellite in the embodiments of this application can use a variety of system architectures, such as the 4th generation mobile communication technology (4G) system architecture or the 5th generation mobile communication technology (5G) system architecture.

[0122] Figure 4A and Figure 4BThe 4G and 5G system architectures are shown respectively. It should be understood that the system architectures applied in this application may have more or fewer network elements than those shown in the figures, may combine two or more network elements, or may distribute the functionality of a single network element across multiple devices. The various network elements shown in the figures can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0123] The following is about Figure 4AThe diagram illustrating the 4G system architecture is provided for detailed explanation. This system architecture primarily involves User Equipment (UE), 4G access network equipment (E-UTRAN), 4G core network equipment (Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), Home Subscriber Server (HSS), Service Capability Server (SCS), Application Server (AS), Service Capability Exposure Function (SCEF), and Policy and Charging Rules Function (PCRF). Among these, the MME is a key control node in the Long Term Evolution (LTE) access network, responsible for UE authentication upon network access, paging of idle-mode UEs, and marking processes including retransmissions. S-GW has functions such as local mobility anchoring for inter-base station handover in LTE, mobility anchoring for inter-3GPP mobility, packet routing and forwarding, transport-level packet marking, and consideration of inter-operator billing.P-GW is used for UE connections to external Public Data Networks (PDNs). A UE can connect to multiple PDN gateways simultaneously to access multiple PDNs. PDN gateways perform policy enforcement, packet filtering for each user, billing support, lawful interception, and packet masking. HSS is the core database storing user information in the home network of IP Multimedia Subsystem (IMS) users. It stores IMS user subscription data in the home network and provides a management interface for operators and end users to customize and modify the subscription data. The main information stored in HSS includes IMS user identifiers, IMS user security contexts, IMS user routing information, and service subscription information. SCS provides functional entities for Open Service Architecture (OSA) interfaces for applications. SCEF provides a method for securely opening 3GPP network interfaces and capabilities, which can be used to transmit non-IP network technologies or protocols through the control plane. SCEF also provides a method for discovering the opened services and capabilities. In this network architecture, various network elements are connected through interfaces. For example, the S1-MME interface connects the E-UTRAN and the MME to transmit signaling information and manage user mobility and session state.

[0124] Next, for Figure 4BThe diagram illustrating the 5G system architecture is provided for detailed explanation. This system architecture primarily involves User Equipment (UE), 5G Access Network (RAN), and 5G Core Network (UDN) equipment, including Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), and Unified Data Management (UDM). Specifically, AMF provides mobility management, lawful monitoring, access authorization, and authentication functions; SMF handles session and bearer management, address allocation, etc.; UPF is primarily responsible for data routing, forwarding, policy enforcement, Quality of Service (QoS) processing, and mobility support; and UDM manages and stores user-related data and subscription information, playing a crucial role in secure access services, user authentication, and providing personalized and context-aware services. In addition, the system architecture also involves application function network elements (AF) and data network (DN). AF is a server that provides a certain type of service to users, so it can also be called an application server or a service server. AF can be an AF deployed by the operator's network itself or a third-party AF. DN includes networks that provide data-centric services such as the Internet, cloud services, and enterprise networks, such as the operator's IP multimedia subsystem, Internet access, or third-party services.

[0125] In some embodiments, both the terrestrial network and the satellite network can use either a 4G or 5G system architecture. If a 4G system architecture is used, a full-core-network-to-satellite architecture can be used on the satellite, meaning all core network elements are deployed on the satellite. Alternatively, only necessary network elements such as the 4G access network device E-UTRAN, the 4G core network device Mobility Management Entity (MME), the Home Subscriber Server (HSS), and the proxy entity responsible for receiving, storing, and forwarding user data can be deployed on the satellite. Similarly, if a 5G system architecture is used, a full-core-network-to-satellite architecture can still be adopted, or a configuration method can be used that deploys only network elements with the same functions as the E-UTRAN, MME, HSS, and proxy entity in the 4G system on the satellite.

[0126] The embodiments of this application do not limit the specific technologies and device forms used in the network devices within the system architecture. For ease of description, this application uses a 4G system architecture for both terrestrial and satellite networks. The user equipment mentioned above can be referred to as terminal equipment, and the network equipment located on the ground can be referred to as terrestrial equipment. In this application, the device or module used in the terrestrial network to store and forward data or signaling of the terminal equipment during storage and forwarding satellite operations is referred to as the first device, such as the aforementioned terrestrial proxy entity; the device or module used in the terrestrial network to store the subscription data of the terminal equipment is referred to as the second device, such as the aforementioned terrestrial HSS. The first and second satellites are both satellites that can provide services to the terminal equipment, and the third satellite includes the first and second satellites.

[0127] Based on the above system architecture, a communication method provided by an embodiment of this application will be described below. This embodiment exemplifies the following: the fifth message is message 1 (for requesting network access), the first message is message 2 (for instructing the second satellite to acquire the terminal device's subscription data), the fourth message is message 3 (for instructing the second device to send the terminal device's subscription data to the second satellite), the second message is message 4 (for requesting a subscription data update notification from the second device), the third message is message 5 (for indicating that the subscription data has been updated), and the sixth message is message 6 (for instructing the second device to send the terminal device's subscription data to the first satellite).

[0128] like Figure 5 As shown, the communication method may include the following steps:

[0129] S501: The first satellite receives message 1 from the terminal equipment.

[0130] Message 1 is used to request network access.

[0131] S502: The first satellite determines the first list.

[0132] The first list indicates the satellites whose contracted data needs to be synchronized with the terminal device.

[0133] In some embodiments, the first list may include a store-and-forward monitoring list (S&F Monitoring List), which may indicate satellites connected to the terminal device. For example, when no cells in the first list exist, the store-and-forward monitoring list can be directly used as the first list. That is, in this embodiment, the satellites that need to synchronize the contracted data of the terminal device may include satellites connected to the terminal device indicated by the store-and-forward monitoring list.

[0134] In other embodiments, the first satellite may also determine a second list, which includes a store-and-forward monitoring list. That is, based on this embodiment, the first satellite can determine two lists: a first list and a second list. The first list indicates satellites whose subscribed data needs to be synchronized with the terminal device, while the second list can be a store-and-forward monitoring list. Exemplarily, the first satellite can determine the first list based on first information, wherein the first information includes at least one of the following: the terminal device's current location information, the terminal device's power-saving requirements, the terminal device's movement trajectory, the mapping relationship between satellite coverage and time, and network policy information. Exemplarily, the mapping relationship between satellite coverage and time can be obtained through ephemeris information or satellite coverage availability information, and the network policy information includes operator policy information.

[0135] S503: The first satellite sends the first list to the first device.

[0136] When the communication link between the first satellite and the ground station is available, the first satellite sends a first list to the first device.

[0137] The first device is a ground-based network device used to store and forward data or signaling from terminal devices during storage and forwarding satellite operations.

[0138] S504: The first device sends message 2 to the second satellite.

[0139] Message 2 is used to instruct the second satellite to obtain the subscription data of the terminal device. The second satellite is located in the first list. Specifically, after receiving the first list sent by the first satellite, the first device determines the second satellite based on the first list, that is, it determines the satellite whose subscription data of the terminal device needs to be synchronized. The first device sends message 2 to the second satellite, which can instruct the second satellite to request the subscription data of the terminal device from the second device.

[0140] For example, if there are multiple satellites in the first list, the first device can send message 2 to all or some of the satellites in the multiple list. Figure 5 The following example illustrates how a first device sends message 2 to one of the satellites (i.e., the second satellite) in the first list.

[0141] In other embodiments, the first device may also record status information of the second satellite storing the subscription data of the terminal device. This status information may include at least one of the following: whether the subscription data is saved, and the time information of the most recent reception of the subscription data of the terminal device. For example, when the first device sends message 2 to the second satellite, the first device makes a record, that is, it records whether the second satellite has saved the subscription data and the time information of the most recent reception of the subscription data of the terminal device by the second satellite. The time information of the most recent reception of the subscription data of the terminal device may be the time when the first device sends message 2 to the second satellite.

[0142] In other embodiments, after the first device sends message 2 to the second satellite and the second satellite obtains the subscription data through subsequent steps S505 and S506, the second satellite may also send message 7 to the first device, which indicates that the second satellite has obtained the subscription data of the terminal device.

[0143] Based on the above embodiments, the first device can record the status information of the second satellite storing the subscription data of the terminal device based on the acquired message 7. This status information may include at least one of the following: whether the subscription data is saved, and the time information of the most recent receipt of the subscription data from the terminal device. For example, when the first device receives message 7 from the second satellite, the first device makes a record, that is, it records whether the second satellite has saved the subscription data and the time information of the most recent receipt of the subscription data from the terminal device by the second satellite. The time information of the most recent receipt of the subscription data from the terminal device may be the time when the first device received message 7.

[0144] In other embodiments, the first device may also send message 4 to the second device, message 4 being used to instruct the second device to send message 5 to the first device in the event of an update to the subscription data; wherein message 5 is used to indicate that the subscription data has been updated, and the second device may be used to store the subscription data of the terminal device.

[0145] For example, message 4 may be a contract data update notification request, and message 5 may be a contract data update notification. When the first device sends the contract data update notification request to the second device, causing the contract data stored on the second device to change, the second device sends a contract data update notification to the first device to notify the first device that the contract data has been updated.

[0146] In another embodiment, the first device may determine to send message 2 to the second satellite based on at least one of the following: the status information of the subscription data stored on the second satellite, and message 5. For example, if the first device receives message 5 from the second device, indicating that the subscription data has been updated, it sends message 2 to the second satellite, notifying the second satellite to request the subscription data of the terminal device from the second device again, i.e., to update the subscription data on the second satellite.

[0147] Based on the above embodiments, the first device determines that sending message 2 to the second satellite includes at least one of the following: the second satellite does not store the subscription data, or the second satellite last received the subscription data before the first device received message 5. For example, the second satellite not storing the subscription data could mean it has never received the subscription data, or the first device knows that the second satellite has deleted the subscription data; the second satellite last receiving the subscription data before the first device received message 5 could indicate that the subscription data has changed.

[0148] When the first device sends message 2 to the second satellite, the first device can also send message 2 to the first satellite. After receiving message 2, the first satellite knows that it needs to obtain the subscription data of the terminal device. The first satellite then sends message 6 to the second device. After receiving message 6 sent by the first satellite, the second device sends the subscription data to the first satellite.

[0149] S505: The second device receives message 3 sent by the second satellite.

[0150] Message 3 can be used to instruct the second device to send the terminal device's subscription data to the second satellite. After receiving message 2 from the first device following step S504, the second satellite learns that it needs to obtain the terminal device's subscription data. Therefore, the second satellite sends message 3 to the second device. Upon receiving message 3, the second device knows that the second satellite needs to obtain the subscription data. The second device is a ground-based network device used to store the terminal device's subscription data.

[0151] S506: The second device sends the subscription data of the terminal device to the second satellite.

[0152] Among them, the contracted data is the data required for establishing a connection between the satellite and the terminal equipment.

[0153] In other embodiments, the second device records status information of the second satellite storing the subscription data. This status information includes at least one of the following: whether the subscription data is stored, and the time information of the most recent reception of the subscription data. For example, when the second device sends subscription data to the second satellite, the first device makes a record, namely, recording whether the second satellite has stored the subscription data and the time information of the most recent reception of the subscription data from the terminal device by the second satellite. The time information of the most recent reception of the subscription data from the terminal device may be the time when the second device sent the subscription data to the second satellite.

[0154] In other embodiments, the second device may also determine to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite or message 3. For example, if the second device determines that the subscription data stored locally has changed, and determines that the subscription data stored on the second satellite needs to be updated based on the status information of the subscription data stored on the second satellite, then it can send the subscription data to the second satellite, i.e., update the subscription data stored on the second satellite; alternatively, if the second device receives message 3 again from the second satellite requesting the subscription data of the terminal device, it can send the subscription data to the second satellite, i.e., update the subscription data stored on the second satellite.

[0155] Based on the above embodiments, the second device determines to send the subscription data to the second satellite based on the status information of the subscription data stored by the second satellite, which may include at least one of the following: the second satellite has not saved the subscription data, or the subscription data has been updated after the time when the second satellite last received the subscription data. For example, the second satellite not saving the subscription data may mean that it has never received the subscription data, or that the second device knows that the second satellite has deleted the subscription data. S507: If the communication link between the second satellite and the terminal device is available, the second satellite establishes a connection with the terminal device based on the subscription data and performs data transmission.

[0156] Obviously, the first satellite is also the satellite that needs to synchronize the subscription data of the terminal device; that is, the first satellite is also the second satellite that the first device needs to send message 2 to. Therefore, in one embodiment, the first satellite receives the subscription data of the terminal device sent by the second device. If the communication link between the first satellite and the terminal device is available, the first satellite establishes a connection with the terminal device based on the subscription data of the terminal device and performs data transmission.

[0157] above Figure 5 The method embodiments shown include many possible implementation schemes, which will be discussed below. Figures 6a to 6b Some of the implementation schemes will be illustrated with examples. It should be noted that... Figures 6a to 6b For related concepts, operations, or logical relationships not explained in the text, please refer to... Figure 5 The corresponding description in the illustrated embodiment.

[0158] In this application, Figures 6a to 6b The illustrated embodiment can be considered as a standalone embodiment. Figures 6a to 6b The illustrated embodiments may be independent of Figure 5 The technical solution; Figures 6a to 6b Some of the steps in the illustrated embodiments can also be used as separate embodiments.

[0159] Figure 6a and Figure 6b This is a flowchart illustrating another communication method provided in an embodiment of this application, specifically based on... Figure 5 The illustrated embodiment presents a detailed implementation diagram. In this implementation, a 4G system architecture is used as an example, where the 4G access network equipment E-UTRAN consists of multiple eNBs. On the first and second satellites, the main components involved are the access network equipment eNB, MME, HSS, and a proxy entity. In the terrestrial network, the first device can be the proxy entity, and the second device can be the Home Subscriber Server (HSS). It should be noted that the proxy entity can be deployed on different devices from the HSS, or it can be deployed on the same device as the HSS. In the latter case, the interaction between the first and second devices takes place on the same device. Neither of these implementations should be considered beyond the scope of this application. The proxy entity is a device or module used for receiving, storing, and forwarding user data.

[0160] This application embodiment is exemplified by using a User Equipment (UE) as the terminal device, a satellite list as the first list, satellite #1 as the first satellite, and satellite #i as the second satellite (i can be equal to 1); a ground-based proxy entity as the first device, denoted as Proxy-ground; a ground-based HSS as the second device, denoted as HSS-ground; a connection request as message 1, a UE subscription information availability query as message 2, a UE subscription data request as message 3, a UE subscription update request as message 4, and a UE subscription update notification as message 5. Specifically, in the first and second satellites, the HSS is denoted as the onboard HSS, the proxy entity as the onboard Proxy, the eNB as the onboard eNB, and the MME as the onboard MME; the status information of the second satellite storing the subscription data recorded by the first device can be the storage status of the UE's subscription data on each satellite in the satellite list, and the status information of the second satellite storing the subscription data recorded by the second device can be the UE subscription status recorded by HSS-ground and synchronized with the onboard HSS.

[0161] Next, combined Figures 6a to 6b A detailed description of one of the above-mentioned methods Figure 5The implementation method corresponding to the embodiment is as follows: Figures 6a to 6b As shown, the specific process is as follows:

[0162] If the communication link between satellite #1 and the UE is available, the UE requests a connection to satellite #1. If satellite #1 does not contain the UE's subscribed data, the connection request is rejected, and a list of satellites whose subscribed data needs to be synchronized for the UE is determined. Detailed steps are shown in steps S601 to S607 below:

[0163] S601: The UE sends a connection request to the onboard eNB, which then forwards it to the onboard MME.

[0164] Assume that satellite #1 initially does not store the UE's subscription data. When the communication link between satellite #1 and the UE is available, the UE sends an attach request to satellite #1. This attach request indicates store-and-forward (S&F) capability. That is, when satellite #1 receives the attach request from the UE, it is operating in S&F mode. Only by identifying store-and-forward capability through this attach request can satellite #1 respond to the user's attach request (e.g., the onboard MME requests authentication data from the onboard HSS).

[0165] S602: The onboard MME requests UE authentication data from the onboard HSS.

[0166] S603: The onboard HSS sends an authentication data rejection message to the onboard MME.

[0167] After receiving the UE authentication data request sent by the onboard MME, the onboard HHS determines that the UE's subscription data does not exist locally on satellite #1, and therefore sends a UE authentication data rejection message to the onboard MME.

[0168] S604: Onboard MME determines the list of satellites.

[0169] After receiving a UE authentication data rejection message, the onboard MME determines a satellite list, which indicates the satellites from which the UE's subscribed data needs to be synchronized. For example, the onboard MME can determine the satellite list based on at least one of the following: the UE's location information, the power-saving requirements of the communication system, the UE's movement trajectory, the mapping relationship between satellite coverage area and time, and network policy information. The mapping relationship between satellite coverage area and time can be represented by ephemeris information or satellite coverage availability information, and the network policy information can be the operator's policy.

[0170] In some embodiments, the onboard MME needs to determine a store-and-forward monitoring list (S&F Monitoring List), which can indicate satellites that have established connections with the terminal device. For example, the onboard MME can determine the store-and-forward monitoring list based on at least one of the following: the UE's current location information, the power-saving requirements of the communication system, the UE's motion trajectory, and the mapping relationship between satellite coverage area and time. The mapping relationship between satellite coverage area and time can be represented by ephemeris information or satellite coverage availability information. The onboard MME determining the store-and-forward monitoring list based on the power-saving requirements of the communication system can mean reducing the number of satellites in the store-and-forward monitoring list when the power-saving requirements of the communication system are high, thereby reducing the interaction between satellites and ground stations and achieving a power-saving effect.

[0171] In one possible implementation, the satellite list includes satellites from the store-and-forward monitoring list, which indicates satellites whose subscribed data for the UE needs to be synchronized. In another possible implementation, the store-and-forward monitoring list can be a satellite list used to indicate satellites whose subscribed data for the UE needs to be synchronized.

[0172] S605: The onboard MME sends a connection rejection message to the UE, carrying the store-and-forward monitoring list.

[0173] After receiving the UE authentication data rejection message and determining the store-and-forward monitoring list, the onboard MME sends an Attach Reject message to the UE, carrying the store-and-forward monitoring list.

[0174] S606: UE saves the store-and-forward monitoring list.

[0175] After receiving the Attach Reject message and the store-and-forward monitoring list, the UE can save the store-and-forward monitoring list locally on the UE.

[0176] S607: The onboard MME sends the UE's status data to the onboard Proxy.

[0177] The onboard MME sends the UE's status data to the onboard proxy for subsequent forwarding. This status data may include UE identifiers such as the International Mobile Subscriber Identity (IMSI), the UE's latest location information, and the store-and-forward monitoring list.

[0178] It should be noted that there is no specific order between steps S605 and S607, and this application does not impose any restrictions on this.

[0179] When the communication link between satellite #1 and the ground station is available, satellite #1 sends the UE's status data to the ground station and requests the UE's subscription data from the ground station. Satellite #1 can directly request the UE's subscription data from the ground station, or it can wait for the ground station to send a UE subscription information availability query before requesting the UE's subscription data from the ground network. Therefore, steps S609 and S611 are optional steps, and their execution can be determined based on the actual situation. This application embodiment does not limit this. Detailed steps are shown in steps S608 to S611 below:

[0180] S608: The onboard proxy sends the UE's status data to the proxy-ground.

[0181] The UE's status data includes this list of satellites.

[0182] When the communication link between satellite #1 and the ground station is available, the onboard proxy sends the UE's status data to the ground-based proxy entity Proxy-ground.

[0183] S609: Proxy-ground sends UE subscription data availability query information to the onboard HSS.

[0184] Proxy-ground determines the satellites from which the UE's subscription data needs to be synchronized based on the satellite list, and satellite #1 is in the list. Proxy-ground sends a UE subscription information availability query to the onboard HSS on satellite #1, which instructs the onboard HSS to retrieve the UE's subscription data.

[0185] S610a: The onboard HSS sends a UE subscription data request to the HSS-ground.

[0186] S610b: HSS-ground sends the UE's subscription data response to the onboard HSS.

[0187] Based on steps S610a and S610b, the onboard HSS on satellite #1 obtains the UE's subscription data from the ground network's HSS-ground.

[0188] S611: The onboard HSS sends a UE subscription availability response message to the Proxy-ground.

[0189] When step S609 is executed, i.e., satellite #1 receives the UE subscription information availability query information sent by Proxy-ground, the onboard HSS of satellite #1, after receiving the subscription data of the UE sent by HSS-ground, can also send a UE subscription availability information response message to Proxy-ground. This UE subscription availability information response message is used to indicate the status of the satellite's acquisition of the UE's subscription data. Specifically, this UE subscription availability information response message can indicate a list of UE identifiers (IDs) that successfully acquired subscription data, and / or a list of UE identifiers (IDs) that failed to acquire subscription data.

[0190] When a communication link can be established between satellite #i in the satellite list and the ground station, the ground station sends the UE's subscription data to satellite #i. Detailed steps are shown in steps S612 to S615 below:

[0191] S612: Proxy-ground determines whether satellite #i is in the satellite list.

[0192] After receiving the UE's status data from the onboard proxy, Proxy-ground determines the satellites whose subscription data for the UE needs to be synchronized based on the satellite list. In other words, Proxy-ground determines that satellite #i is in the satellite list.

[0193] S613: Proxy-ground sends UE subscription data availability query information to the onboard HSS.

[0194] After determining that satellite #i is in the satellite list, Proxy-ground sends a UE subscription information availability query to the onboard HSS on satellite #i. This UE subscription information availability query is used to trigger the onboard HSS to obtain the UE's subscription data.

[0195] S614a: The onboard HSS sends a UE subscription data request to the HSS-ground.

[0196] S614b: HSS-ground sends the UE's subscription data response to the onboard HSS.

[0197] Based on steps S614a and S614b, the onboard HSS on satellite #i obtains the UE's subscription data from the ground network's HSS-ground.

[0198] S615: The onboard HSS sends a UE subscription availability response message to the Proxy-ground.

[0199] After receiving the subscription data of the UE obtained by HSS-ground, the onboard HSS of satellite #i can also send a UE subscription availability information response message to Proxy-ground. This UE subscription availability information response message is used to indicate the status of obtaining the UE's subscription data. Specifically, the UE subscription availability information response message can indicate a list of UE identifiers (IDs) that successfully obtained subscription data, and / or a list of UE identifiers (IDs) that failed to obtain subscription data.

[0200] Optionally, if the UE's subscription data is updated, any one or more of steps S616 to S618 (including S618a and S618b) can also be executed, as detailed below:

[0201] S616: HSS-ground records and satellite-borne HSS synchronization UE subscription status.

[0202] The information regarding UE subscription synchronization may include the UE's identifier (ID), the satellite identifier (ID) for synchronizing the UE's subscription data, and the time information for synchronizing the UE's subscription data.

[0203] In some embodiments, HSS-ground can record the synchronization of UE subscription information when sending UE subscription data to satellite #i, that is, record the UEID, satellite ID, and the time of sending the UE subscription data as the time information for synchronizing the UE subscription data.

[0204] S617: Proxy-ground records the storage status of UE subscription data on each satellite in the satellite list.

[0205] For example, the storage status includes whether the UE's subscription data is stored on each satellite in the satellite list, and / or the time when the UE's subscription data is stored / updated on each satellite in the satellite list.

[0206] S618a: Proxy-ground sends a UE subscription update request to HSS-ground.

[0207] The UE's subscription data update request indicates that, in the event of an update to the UE's subscription data on the HSS-ground, the HSS-ground sends a notification to the Proxy-ground.

[0208] S618b: HSS-ground sends a UE subscription update notification to Proxy-ground.

[0209] The subscription update notification for this UE is used by Proxy-ground to determine whether it is necessary to re-trigger each satellite in the satellite list to obtain or update the UE's subscription data.

[0210] In one embodiment, after the Proxy-ground determines that it is necessary to re-trigger each satellite in the satellite list to obtain the UE's subscription data, it can execute the method shown in steps S612 to S615 again, and send UE subscription information availability query information to satellite #i through the Proxy-ground to trigger the onboard HSS of satellite #i to re-obtain the UE's subscription data.

[0211] The above steps have completed the synchronization of the UE's subscription data on satellite #i. When the UE sends a connection request to any satellite #i in the satellite list again, it can successfully establish a connection with the satellite and obtain satellite services. At this time, the satellite saves the UE's relevant data locally. Detailed steps are shown in steps S619 and S620:

[0212] S619: Execute the connection process and perform data transmission.

[0213] When the service link of satellite #i becomes available, the UE performs the attach procedure and transmits data.

[0214] S620: The onboard proxy stores the UE's relevant data locally.

[0215] The onboard proxy of satellite #i stores the UE's relevant data locally. This UE-related data includes the UE's status data and / or the UE's application data. The UE's application data includes data generated by the UE during the process of obtaining satellite services.

[0216] In this embodiment, by sending signals to satellites in the satellite list, the onboard HSS of each satellite is triggered to acquire the UE's subscription data. This subscription data is then synchronized to all satellites capable of providing services to the UE, enabling the UE to successfully access the NTN satellite even in scenarios with discontinuous power supply links. Simultaneously, the subscription status of satellites in the satellite list is recorded. When the UE's subscription data changes, the original subscription data is promptly replaced, which helps reduce the waste of network resources caused by storing unnecessary user subscription data.

[0217] The following describes another communication method provided by an embodiment of this application. This embodiment exemplifies the following: the fifth message is message 1 (for requesting network access), the first message is message 2 (for instructing the second satellite to acquire the terminal device's subscription data), the fourth message is message 3 (for instructing the second device to send the terminal device's subscription data to the second satellite), the second message is message 4 (for requesting a subscription data update notification from the second device), and the third message is message 5 (for indicating that the subscription data has been updated).

[0218] like Figure 7 As shown, the communication method may include the following steps:

[0219] S701: The first satellite receives message 1 from the terminal equipment.

[0220] This step can be referred to as step S501, and will not be repeated here.

[0221] S702: The first satellite confirms the first list.

[0222] This step can be referred to as step S502, and will not be repeated here.

[0223] S703: The first satellite sends the first list to the first device.

[0224] This step can be referred to as step S503, and will not be repeated here.

[0225] S704: The first device sends the first list to the second device.

[0226] Both the first device and the second device are ground-based network devices. The first device can be used to store and forward data or signaling from terminal devices during satellite storage and forwarding operations, while the second device can be used to store the contracted data of terminal devices.

[0227] After receiving the first list sent by the first satellite, the first device forwards the first list to the second device.

[0228] S705: The second device sends the terminal device's subscription data to the second satellite.

[0229] When the second device receives the first list sent by the first device, it determines the second satellite based on the first list and sends the subscription data of the terminal device to the second satellite. That is, it synchronizes the subscription data of the terminal device on the second satellite for the connection between the second satellite and the terminal device.

[0230] In other embodiments, the second device records status information of the second satellite storing the subscription data. This status information includes at least one of the following: whether the subscription data is stored, and the time information of the most recent receipt of the subscription data. For example, when the second device sends subscription data to the second satellite, the second device makes a record, that is, it records whether the second satellite has stored the subscription data and the time information of the most recent receipt of the subscription data from the terminal device. The time information of the most recent receipt of the subscription data from the terminal device may be the time when the second device sent the subscription data to the second satellite.

[0231] In other embodiments, the second device may also determine to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite or message 3, wherein message 3 comes from the second satellite and is used to instruct the second device to send the terminal device's subscription data to the second satellite. For example, if the second device determines that the subscription data stored locally has changed, and determines that the subscription data stored on the second satellite needs to be updated based on the status information of the subscription data stored on the second satellite, it can then send the subscription data to the second satellite, i.e., update the subscription data stored on the second satellite; alternatively, if the second device receives message 3 again from the second satellite requesting the terminal device's subscription data, it can also send the subscription data to the second satellite, i.e., update the subscription data stored on the second satellite.

[0232] Based on the above embodiments, the second device determines to send the subscription data to the second satellite based on the status information of the subscription data stored by the second satellite, which may include at least one of the following: the second satellite does not store the subscription data, or the subscription data is updated after the time when the second satellite last received the subscription data.

[0233] S706: When the communication link between the second satellite and the terminal device is available, the second satellite establishes a connection with the terminal device based on the contracted data and performs data transmission.

[0234] This step can be referred to as step S507, and will not be repeated here.

[0235] above Figure 7 The method embodiments shown include many possible implementation schemes, which will be discussed below. Figure 8 Some of the implementation schemes will be illustrated with examples. It should be noted that... Figure 8 For related concepts, operations, or logical relationships not explained in the text, please refer to... Figure 7 The corresponding description in the illustrated embodiment.

[0236] In this application, Figure 8 The illustrated embodiment can be considered as a standalone embodiment. Figure 8 The illustrated embodiments may be independent of Figure 7The technical solution; Figure 8 Some of the steps in the illustrated embodiments can also be used as separate embodiments.

[0237] Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application, specifically based on... Figure 7 The illustrated embodiment presents a detailed implementation diagram. In this implementation, a 4G system architecture is used as an example, where the 4G access network equipment E-UTRAN consists of multiple eNBs. On the first and second satellites, the main components involved are the access network equipment eNB, MME, HSS, and a proxy entity. In the ground station, the first device can be the proxy entity, and the second device can be the Home Subscriber Server (HSS). It should be noted that the proxy entity can be deployed on different devices from the HSS, or it can be deployed on the same device as the HSS. In the latter case, the interaction between the first and second devices takes place on the same device. Neither of these implementations should be considered beyond the scope of this application. The proxy entity is a device or module used for receiving, storing, and forwarding user data.

[0238] This application embodiment is exemplified by using a user equipment (UE) as the terminal device, a satellite list as the first list, satellite #1 as the first satellite, and satellite #i as the second satellite (i can be equal to 1); a ground station's proxy entity as the first device, denoted as Proxy-ground; a ground station's HSS as the second device, denoted as HSS-ground; a connection request as message 1, a UE subscription information availability query as message 2, a UE subscription data request as message 3, a UE subscription update request as message 4, and a UE subscription update notification as message 5. Specifically, in the first and second satellites, the HSS is denoted as the onboard HSS, the proxy entity as the onboard Proxy, the eNB as the onboard eNB, and the MME on the first or second satellite as the onboard MME. The status information of the second satellite storing the subscription data recorded by the first device can be the storage status of the UE's subscription data on each satellite in the satellite list, and the status information of the second satellite storing the subscription data recorded by the second device can be the situation where the HSS-ground records and the onboard HSS synchronize the UE's subscription.

[0239] Next, combined Figure 8 This document details one implementation method corresponding to the above embodiments, and the flow of the communication method is as follows: Figure 8 As shown, the specific process is as follows:

[0240] If the communication link between satellite #1 and the UE is available, the UE requests a connection to satellite #1. If satellite #1 does not contain the UE's subscribed data, the connection request is rejected, and a list of satellites whose subscribed data needs to be synchronized for the UE is determined. Detailed steps are shown in steps S801 to S807 below:

[0241] S801: The UE sends a connection request to the onboard eNB, which then forwards it to the onboard MME.

[0242] This step can be referred to as step S601, and will not be repeated here.

[0243] S802: The onboard MME requests UE authentication data from the onboard HSS.

[0244] S803: The onboard HSS sends an authentication data rejection message to the onboard MME.

[0245] This step can be referred to as step S603, and will not be repeated here.

[0246] S804: Onboard MME determines the list of satellites.

[0247] This step can be referred to as step S604, and will not be repeated here.

[0248] S805: The onboard MME sends a connection rejection message to the UE, carrying the store-and-forward monitoring list.

[0249] This step can be referred to as step S605, and will not be repeated here.

[0250] S806: UE saves the store-and-forward monitoring list.

[0251] This step can be referred to as step S606, and will not be repeated here.

[0252] S807: The onboard MME sends the UE's status data to the onboard Proxy.

[0253] This step can be referred to as step S607, and will not be repeated here.

[0254] It should be noted that there is no specific order between steps S805 and S807, and this application does not impose any restrictions on this.

[0255] When the communication link between satellite #1 and the ground station is available, satellite #1 sends the UE's status data to the ground station, and the ground station actively sends the UE's subscription data to satellite #1. The detailed steps are shown in steps S808 to S811 below:

[0256] S808: The onboard proxy sends the UE's status data to the proxy-ground.

[0257] This step can be referred to as step S608, and will not be repeated here.

[0258] S809: Proxy-ground sends a list of satellites to HSS-ground.

[0259] The Proxy-ground receives the UE's status data from the onboard Proxy, obtains the satellite list, and then forwards the satellite list to the HSS-ground. For example, the Proxy-ground can send this data via the Service Capability Exposure Function (SCEF).

[0260] In some embodiments, HSS-ground may also save the list of satellites locally.

[0261] S810: HSS-ground determines the satellites that need to synchronize the UE's subscribed data based on the satellite list.

[0262] HSS-ground uses a satellite list to determine which satellite #i is the one whose subscription data for the UE needs to be synchronized. Clearly, satellite #1 is the satellite whose subscription data for the UE needs to be synchronized.

[0263] S811: HSS-ground sends UE subscription data to the onboard HSS of satellite #1.

[0264] HSS-ground determines that satellite #1 is in the satellite list and proactively sends the UE's subscription data to the onboard HSS of satellite #1.

[0265] When a communication link can be established between satellite #i in the satellite list and the ground station, the ground station actively sends the UE's subscription data to satellite #i. The detailed steps are shown in step S812 below.

[0266] S812: HSS-ground sends UE subscription data to the onboard HSS of satellite #i.

[0267] After receiving the satellite list from the Proxy-ground, the HSS-ground determines the satellites whose subscribed data for the UE needs to be synchronized based on the satellite list. That is, if the Proxy-ground determines that satellite #i is in the satellite list, it sends the UE's subscribed data to the onboard HSS of satellite #i.

[0268] Optionally, the second device may also perform step S813.

[0269] S813: HSS-ground records and satellite-borne HSS synchronization UE subscription status.

[0270] HSS-ground records the synchronization of the UE's subscribed data between the onboard HSS of satellite #i and the satellite's identification code (ID), the UE's identification code (ID) for synchronized subscribed data, and the time of synchronization. For example, when HSS-ground sends the UE's subscribed data to the onboard HSS of satellite #i, it records the satellite's identification code, the UE's identification code, and the time of sending the UE's subscribed data as the time of synchronization.

[0271] In other embodiments, when the UE's subscription data is updated, the HSS-ground sends the updated UE subscription data to a satellite. For example, this satellite could be one that previously synchronized the UE's subscription data with the HSS-ground, or it could be a satellite listed in a satellite list.

[0272] In other embodiments, if HSS-ground determines that the UE's subscription data has changed, it can execute the method shown in steps S810 to S812 again to send the updated subscription data of the UE to the satellites in the satellite list.

[0273] The above steps have completed the synchronization of the UE's subscribed data on satellite #i. When the UE sends a connection request to any satellite #i in the satellite list again, it can establish a connection with the satellite and obtain satellite services. At this time, the satellite saves the UE's relevant data locally. Detailed steps are shown in steps S814 and S815:

[0274] S814: Executes the connection process and performs data transmission.

[0275] When the service link of satellite #i becomes available, the UE performs the attach procedure and transmits data.

[0276] S815: The onboard proxy stores the UE's relevant data locally.

[0277] The onboard proxy of satellite #i stores the UE's relevant data locally. This UE-related data includes the UE's status data and / or the UE's application data. The UE's application data includes data generated by the UE during the process of obtaining satellite services.

[0278] In this embodiment, the satellite sends a satellite list to the Proxy-ground, which then forwards the list to the HSS-ground. The HSS-ground identifies the satellites whose subscription data for the UE needs to be synchronized from the satellite list and proactively sends the UE's subscription data to those satellites. This synchronizes the UE's subscription data to all satellites that can provide services to the UE, enabling the UE to successfully access the NTN satellite even in scenarios with discontinuous power supply links. Simultaneously, the subscription status of the satellites in the satellite list is recorded. When the UE's subscription data changes, the original subscription data is promptly replaced, which helps reduce the waste of network resources caused by storing unnecessary user subscription data.

[0279] The following describes another communication method provided by an embodiment of this application. This embodiment exemplifies the following: the fifth message is message 1 (for requesting network access), the first message is message 2 (for instructing the second satellite to acquire the terminal device's subscription data), the fourth message is message 3 (for instructing the second device to send the terminal device's subscription data to the second satellite), the second message is message 4 (for requesting a subscription data update notification from the second device), and the third message is message 5 (for indicating that the subscription data has been updated).

[0280] like Figure 9 As shown, the communication method may include the following steps:

[0281] S901: The first satellite receives message 1 from the terminal equipment.

[0282] This step can be referred to as step S501, and will not be repeated here.

[0283] S902: The first satellite confirms the first list.

[0284] This step can be referred to as step S502, and will not be repeated here.

[0285] S903: The first satellite sends the first list to the second device.

[0286] When the communication link between the first satellite and the ground station is available, the first satellite directly sends the first list to the second device. The second device is a ground-based network device used to store the subscription data of the terminal devices.

[0287] S904: The second device sends the terminal device's subscription data to the second satellite.

[0288] When the second device receives the first list sent by the first device, it determines the second satellite based on the first list and sends the subscription data of the terminal device to the second satellite. That is, it synchronizes the subscription data of the terminal device on the second satellite for the connection between the second satellite and the terminal device.

[0289] In other embodiments, the second device records status information of the second satellite storing the subscription data. This status information includes at least one of the following: whether the subscription data is stored, and the time information of the most recent receipt of the subscription data. For example, when the second device sends subscription data to the second satellite, the second device makes a record, that is, it records whether the second satellite has stored the subscription data and the time information of the most recent receipt of the subscription data from the terminal device. The time information of the most recent receipt of the subscription data from the terminal device may be the time when the second device sent the subscription data to the second device.

[0290] In other embodiments, the second device may also determine to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite or message 3, wherein message 3 comes from the second satellite and instructs the second device to send the terminal device's subscription data to the second satellite. For example, if the second device determines that the subscription data stored locally has changed, and determines that the subscription data stored on the second satellite needs to be updated based on the status information of the subscription data stored on the second satellite, it can send the subscription data to the second satellite, i.e., update the subscription data stored on the second satellite; alternatively, if the second device receives message 3 again from the second satellite requesting the terminal device's subscription data, it can send the subscription data to the second satellite to update the subscription data stored on the second satellite.

[0291] Based on the above embodiments, the second device determines to send the subscription data to the second satellite based on the status information of the subscription data stored by the second satellite, which may include at least one of the following: the second satellite does not store the subscription data, or the subscription data is updated after the time when the second satellite last received the subscription data.

[0292] S905: When the communication link between the second satellite and the terminal device is available, the second satellite establishes a connection with the terminal device based on the contracted data and performs data transmission.

[0293] This step can be referred to as step S507, and will not be repeated here.

[0294] above Figure 9 The method embodiments shown include many possible implementation schemes, which will be discussed below. Figure 10 Some of the implementation schemes will be illustrated with examples. It should be noted that... Figure 10 For related concepts, operations, or logical relationships not explained in the text, please refer to... Figure 9The corresponding description in the illustrated embodiment.

[0295] In this application, Figure 10 The illustrated embodiment can be considered as a standalone embodiment. Figure 10 The illustrated embodiments may be independent of Figure 9 The technical solution; Figure 10 Some of the steps in the illustrated embodiments can also be used as separate embodiments.

[0296] Figure 10 This is a flowchart illustrating another communication method provided in an embodiment of this application, specifically based on... Figure 9 The illustrated embodiment presents a detailed implementation diagram. In this implementation, a 4G system architecture is used as an example, where the 4G access network equipment E-UTRAN consists of multiple eNBs. On the first and second satellites, the main components involved are the access network equipment eNB, MME, HSS, and a proxy entity. In the ground station, the first device can be the proxy entity, and the second device can be the Home Subscriber Server (HSS). It should be noted that the proxy entity can be deployed on different devices from the HSS, or it can be deployed on the same device as the HSS. In the latter case, the interaction between the first and second devices takes place on the same device. Neither of these implementations should be considered beyond the scope of this application. The proxy entity is a device or module used for receiving, storing, and forwarding user data.

[0297] This application embodiment is exemplified by using a user equipment (UE) as the terminal device, a satellite list as the first list, satellite #1 as the first satellite, and satellite #i as the second satellite (i can be equal to 1); a ground station's proxy entity as the first device, denoted as Proxy-ground; a ground station's HSS as the second device, denoted as HSS-ground; a connection request as message 1, a UE subscription information availability query as message 2, a UE subscription data request as message 3, a UE subscription update request as message 4, and a UE subscription update notification as message 5. Specifically, in the first and second satellites, the HSS is denoted as the onboard HSS, the proxy entity as the onboard Proxy, the eNB as the onboard eNB, and the MME on the first or second satellite as the onboard MME. The status information of the second satellite storing the subscription data recorded by the first device can be the storage status of the UE's subscription data on each satellite in the satellite list, and the status information of the second satellite storing the subscription data recorded by the second device can be the situation where the HSS-ground records and the onboard HSS synchronize the UE's subscription.

[0298] Next, combined Figure 10 This document details one implementation method corresponding to the above embodiments, and the flow of the communication method is as follows: Figure 10As shown, the specific process is as follows:

[0299] If the communication link between satellite #1 and the UE is available, the UE requests a connection to satellite #1. If satellite #1 does not contain the UE's subscribed data, the connection request is rejected, and a list of satellites whose subscribed data needs to be synchronized for the UE is determined. Detailed steps are shown in steps S1001 to S1008 below:

[0300] S1001: The UE sends a connection request to the onboard eNB, which then forwards it to the onboard MME.

[0301] This step can be referred to as step S601, and will not be repeated here.

[0302] S1002: The onboard MME requests UE authentication data from the onboard HSS.

[0303] S1003: The onboard HSS sends an authentication data rejection message to the onboard MME.

[0304] This step can be referred to as step S603, and will not be repeated here.

[0305] S1004: Onboard MME determines the list of satellites.

[0306] This step can be referred to as step S604, and will not be repeated here.

[0307] S1005: The onboard MME sends the generated satellite list and UE identification code to the onboard HSS.

[0308] The satellite-borne MME of satellite #1 sends the generated satellite list and the corresponding UE identification code (ID) to the satellite-borne HSS, and the satellite-borne HSS saves the UE identification code (ID) and the corresponding satellite list locally.

[0309] S1006: The onboard MME sends a connection rejection message to the UE, carrying the store-and-forward monitoring list.

[0310] This step can be referred to as step S605, and will not be repeated here.

[0311] S1007: UE saves the store-and-forward monitoring list.

[0312] This step can be referred to as step S606, and will not be repeated here.

[0313] S1008: The onboard MME sends the UE's status data to the onboard Proxy.

[0314] This step can be referred to as step S607, and will not be repeated here.

[0315] It should be noted that steps S1005, S1006 and S1008 are not in any particular order, and this application does not impose any restrictions on this.

[0316] When the communication link between satellite #1 and the ground station is available, satellite #1 sends the UE's status data to the Proxy-ground station and directly sends the UE's identification code (ID) and the corresponding satellite list to the HSS-ground station. The HSS-ground station determines that satellite #1 is the satellite indicated in the satellite list and proactively sends the UE's subscription data to satellite #1. The detailed steps are as follows: steps S1009 (including S1009a and S1009b) to S1011:

[0317] S1009a: The onboard proxy sends the UE's status data to the proxy-ground.

[0318] This step can be referred to as step S608, and will not be repeated here.

[0319] S1009b: The onboard HSS sends the UE's identification code and the corresponding satellite list to the HSS-ground.

[0320] After receiving the UE's identification code (ID) and the corresponding satellite list from the onboard MME, the onboard HSS will send the UE's identification code (ID) and the corresponding satellite list to HSS-ground, provided that the communication link between satellite #1 and the ground station is available.

[0321] S1010: HSS-ground determines the satellites that need to synchronize the UE's subscribed data based on the satellite list.

[0322] HSS-ground uses a satellite list to determine which satellite #i is the one whose subscription data for the UE needs to be synchronized. For example, satellite #1 is the satellite whose subscription data for the UE needs to be synchronized.

[0323] S1011: HSS-ground sends UE subscription data to the onboard HSS of satellite #1.

[0324] HSS-ground determines that satellite #1 is in the satellite list and proactively sends the UE's subscription data to the onboard HSS of satellite #1.

[0325] When the communication link between satellite #i in the satellite list and HSS-ground is available, HSS-ground actively sends the UE's subscription data to satellite #i. Detailed steps are shown in step S1012 below.

[0326] S1012: HSS-ground sends the UE's subscription data to the onboard HSS of satellite #i.

[0327] After receiving the satellite list sent by the onboard HSS, HSS-ground determines the satellites that need to synchronize the UE's subscription data based on the satellite list. That is, if Proxy-ground determines that satellite #i is in the satellite list, it sends the UE's subscription data to the onboard HSS of satellite #i.

[0328] Optionally, the second device may also perform step S1013.

[0329] S1013: HSS-ground records and satellite-borne HSS synchronization UE subscription status.

[0330] HSS-ground records the synchronization of the UE's subscribed data between the onboard HSS of satellite #i and the satellite's identification code (ID), the UE's identification code (ID) for synchronized subscribed data, and the time of synchronization. For example, when HSS-ground sends the UE's subscribed data to the onboard HSS of satellite #i, it records the satellite's identification code, the UE's identification code, and the time of sending the UE's subscribed data as the time of synchronization.

[0331] In some embodiments, when the UE's subscription data is updated, HSS-ground sends the updated UE subscription data to a satellite. For example, this satellite could be one that previously synchronized the UE's subscription data with HSS-ground, or it could be a satellite listed in a satellite list.

[0332] The above steps have completed the synchronization of the UE's subscribed data on satellite #i. When the UE sends a connection request to any satellite #i in the satellite list again, it can establish a connection with the satellite and obtain satellite services. At this time, the satellite saves the UE's relevant data locally. Detailed steps are shown in steps S1014 and S1015:

[0333] S1014: Execute the connection process and perform data transmission.

[0334] When the service link of satellite #i becomes available, the UE performs the attach procedure and transmits data.

[0335] S1015: The onboard proxy stores the UE's relevant data locally.

[0336] The onboard proxy of satellite #i stores the UE's relevant data locally. This UE-related data includes the UE's status data and / or the UE's application data. The UE's application data includes data generated by the UE during the process of obtaining satellite services.

[0337] In this embodiment, the satellite directly sends a satellite list to the ground network's HSS-ground via its onboard HSS. The HSS-ground uses this list to determine the satellites from which the UE's subscription data needs to be synchronized and proactively sends the UE's subscription data to these satellites. This synchronizes the UE's subscription data to all satellites that can provide services to the UE, enabling the UE to successfully access the NTN satellite even in scenarios with discontinuous power supply links. Simultaneously, the subscription status of the satellites in the satellite list is recorded. When the UE's subscription data changes, the original subscription data is promptly replaced, reducing the waste of network resources caused by storing unnecessary user subscription data.

[0338] Figure 11 This is a flowchart illustrating another communication method provided in this application embodiment. By recording the status information of the subscription data stored on the satellite, the method determines to send the subscription information to the satellite, enabling the satellite to promptly acquire or update the subscription data. This communication method may include the following steps:

[0339] S1101: The second device records the status information of the contracted data of the third satellite storage terminal device.

[0340] The second device records the status information of the contracted data of the third satellite storage terminal device. The status information includes at least one of the following: whether the contracted data is stored, and the time information of the most recent receipt of the contracted data.

[0341] The third satellite may include the first satellite and the second satellite, and the second device is a ground-based network device used to store the subscription data of the terminal device.

[0342] For example, when the second device sends subscription data to the third satellite, the second device makes a record, that is, records that the third satellite has saved the subscription data and the time information of the most recent receipt of the subscription data from the terminal device. The time information of the most recent receipt of the subscription data from the terminal device can be the time when the second device sends the subscription data to the third satellite.

[0343] S1102: The second device determines to send the subscription data to the third satellite based on the status information of the subscription data stored in the third satellite storage terminal device.

[0344] In some embodiments, the second device determines to send the subscription data to the third satellite based on the status information of the subscription data of the third satellite storage terminal device, including at least one of the following: the third satellite does not have the stored subscription data; the subscription data was updated after the time when the third satellite last received the subscription data.

[0345] In this embodiment, the second device records the status information of the subscription data of the third satellite storage terminal device, so as to facilitate the timely replacement of the subscription data stored on the third satellite when the subscription data is updated, thereby reducing the waste of network resources caused by storing unnecessary subscription data. At the same time, it ensures the availability of the subscription data when the terminal device sends a connection request to the third satellite, so that the terminal device can successfully establish a connection with the third satellite and obtain satellite services.

[0346] The foregoing details the method provided in this application. To facilitate the implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided in the embodiments of this application.

[0347] This application embodiment can divide the communication device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and is only a logical functional division. In actual implementation, there may be other division methods.

[0348] See Figure 12 , Figure 12 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 12 can be applied to the above-described... Figures 5 to 11 In any of the embodiments shown in the method, such as Figure 12 As shown, the communication device 12 includes a processing module 120 and a transceiver module 121. The processing module 120 may be one or more processors, and the transceiver module 121 may be a transceiver or a communication interface. This communication device can be used to implement the steps involved in the communication device execution in the above method embodiments. Optionally, the communication device 12 may further include a storage module 122 for storing the program code and data of the communication device 12.

[0349] In one example, the communication device acts as a chip in the first device and performs the steps executed by the first device in the above method embodiments. The transceiver module 121 is used for specific execution. Figures 5 to 11The sending and / or receiving actions performed by the first device in any of the embodiments shown herein may be, for example, the first device performing other processes of the techniques described herein. The processing module 120 may be used to support the communication device 12 in performing the processing actions in the above method embodiments, for example, to support the first device in performing other processes of the techniques described herein.

[0350] For example, storage module 122 is used to record status information of the second satellite storage contract data.

[0351] The processing module 120 is configured to determine to send a first message to the second satellite based on at least one of the following: the second satellite stores the status information of the subscription data, or a third message; and to determine to send a first message to the second satellite if at least one of the following conditions is met: the second satellite does not store the subscription data, or the second satellite last received the subscription data before the first device received the third message.

[0352] The transceiver module 121 is used to receive a first list sent by a first satellite; to send a first message to a second satellite; to send a second message to a second device; and to receive a third message sent by the second device.

[0353] In one possible embodiment, transceiver module 121 receives a first list sent by a first satellite, the first list indicating satellites that need to synchronize the subscribed data of the terminal device, the first device being used to store and forward the data or signaling of the terminal device in a store-and-forward satellite operation; transceiver module 121 sends a first message to a second satellite, the first message being used to instruct the second satellite to obtain the subscribed data of the terminal device, the second satellite being located in the first list.

[0354] In one possible embodiment, the storage module 122 records the status information of the second satellite storage subscription data, which includes at least one of the following: whether the subscription data is saved, and the time information of the last time the subscription data was received.

[0355] In one possible embodiment, the transceiver module 121 sends a second message to the second device, which instructs the second device to send a third message to the transceiver module 121 in the event of an update to the subscription data. The second device is used to store the subscription data of the terminal device.

[0356] In one possible embodiment, the processing module 120 determines to send a first message to the second satellite based on at least one of the following: the second satellite stores status information of the subscription data; and a third message indicating that the subscription data has been updated.

[0357] In one possible embodiment, the processing module 120 determines to send a first message to the second satellite, including at least one of the following: the second satellite does not store the subscription data; the second satellite last received the subscription data before the transceiver module 121 received the third message.

[0358] In one example, the communication device acts as a chip in a second device and performs the steps executed by the second device in the above method embodiments. The transceiver module 121 is used for specific execution. Figures 5 to 11 The sending and / or receiving actions performed by the second device in any of the embodiments shown herein may be, for example, the second device performing other processes of the techniques described herein. The processing module 120 may be used to support the communication device 12 in performing the processing actions in the above method embodiments, for example, to support the second device in performing other processes of the techniques described herein.

[0359] For example, storage module 122 is used to record status information of the second satellite storage subscription data, the status information including at least one of the following: whether the subscription data is stored and the time information of the last time the subscription data was received; and is used to record status information of the third satellite storage subscription data, the status information including at least one of the following: whether the subscription data is stored and the time information of the last time the subscription data was received.

[0360] Processing module 120 is configured to: determine to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite, or a fourth message; determine to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite, when at least one of the following conditions is met: the second satellite does not store the subscription data, or the subscription data was updated after the time when the second satellite last received the subscription data; determine to send the subscription data to the third satellite based on the status information of the subscription data of the terminal device stored on the third satellite; and determine to send the subscription data to the third satellite based on the status information of the subscription data of the terminal device stored on the third satellite, when at least one of the following conditions is met: the third satellite does not store the subscription data, or the subscription data was updated after the time when the third satellite last received the subscription data.

[0361] The transceiver module 121 is used to receive a fourth message sent by a first list or a second satellite; to send the subscription data of the terminal device to the second satellite; and to send the subscription data of the terminal device to a third satellite.

[0362] In one possible embodiment, the transceiver module 121 receives a fourth message sent by a first list or a second satellite. The second device is used to store the subscription data of the terminal device. The first list indicates the satellites that need to synchronize the subscription data of the terminal device. The fourth message is used to instruct the second satellite to obtain the subscription data of the terminal device. The transceiver module 121 sends the subscription data of the terminal device to the second satellite, which is located in the first list.

[0363] In one possible embodiment, the storage module 122 records the status information of the second satellite storing the subscription data, which includes at least one of the following: whether the subscription data is stored, and the time information of the last time the subscription data was received.

[0364] In one possible embodiment, the processing module 120 determines to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite, or a fourth message.

[0365] In one possible embodiment, the processing module 120 determines to send the subscription data to the second satellite based on the status information of the second satellite storing the subscription data, including at least one of the following: the second satellite does not store the subscription data; the subscription data was updated after the time when the second satellite last received the subscription data.

[0366] In one possible embodiment, the storage module 122 records the status information of the subscription data of the third satellite storage terminal device, which includes at least one of the following: whether the subscription data is stored and the time information of the last time the subscription data was received; the processing module 120 determines to send the subscription data to the third satellite based on the status information of the subscription data of the third satellite storage terminal device.

[0367] In one possible embodiment, the processing module 120 determines to send the subscription data to the third satellite based on the status information of the third satellite storing the subscription data, including at least one of the following: the third satellite does not store the subscription data; the subscription data was updated after the time when the third satellite last received the subscription data.

[0368] In one example, the communication device functions as a chip in a first satellite and performs the steps executed by the first satellite in the above method embodiments. The transceiver module 121 is used for specific execution. Figures 5 to 11 The transmitting and / or receiving actions performed by the first satellite in any of the embodiments shown herein may be, for example, other processes of the technology described herein performed by the first satellite. The processing module 120 may be used to support the communication device 12 in performing the processing actions in the above method embodiments, for example, to support the first satellite in performing other processes of the technology described herein.

[0369] For example, the transceiver module 121 is configured to receive a fifth message from a terminal device; send a first list to a ground device when the communication link between the first satellite and the ground network is available; receive a first message sent by the first device; send a fourth message to a second device; send the terminal device identifier and the first list to the second device; receive the subscription data of the terminal device sent by the second device; and establish a connection with the terminal device based on the subscription data of the terminal device and perform data transmission when the communication link between the first satellite and the terminal device is available.

[0370] The processing module 120 is used to determine a first list; to determine a second list; and, when a communication link between the first satellite and the terminal device is available, to establish a connection with the terminal device based on the subscription data of the terminal device and to perform data transmission.

[0371] In one possible embodiment, transceiver module 121 receives a fifth message from the terminal device, the fifth message being a request to access the network; processing module 120 determines a first list, the first list indicating satellites for which the terminal device's subscribed data needs to be synchronized; if the communication link between the first satellite and the ground network is available, transceiver module 121 sends the first list to ground equipment, the ground equipment including a first device or a second device, the first device being used to store and forward the terminal device's data or signaling in store-and-forward satellite operations, and the second device being used to store the terminal device's subscribed data.

[0372] In one possible embodiment, the first list includes a store-and-forward monitoring list, which indicates satellites that have established connections with the terminal device, and the satellites that need to synchronize the contracted data of the terminal device include the satellites that have established connections.

[0373] In one possible embodiment, the processing module 120 determines a second list, which includes a store-and-forward monitoring list that indicates satellites that have established connections with the terminal device.

[0374] In one possible embodiment, the processing module 120 determines a first list based on first information, which includes at least one of the following: the current location information of the terminal device, the power saving requirements of the terminal device, the movement trajectory of the terminal device, the mapping relationship between the coverage area and time of satellites, and network policy information.

[0375] In one possible embodiment, the ground equipment includes a first device, and a transceiver module 121 receives the subscription data of the terminal device sent by the second device; when the communication link between the first satellite and the terminal device is available, the transceiver module 121 and the processing module 120 establish a connection with the terminal device based on the subscription data of the terminal device and perform data transmission.

[0376] In one possible embodiment, the transceiver module 121 receives a first message sent by the first device, the first message being used to instruct the first satellite to acquire the subscription data of the terminal device; the transceiver module 121 sends a fourth message to the second device, the fourth message being used to instruct the second device to send the subscription data of the terminal device to the first satellite.

[0377] In one possible embodiment, the ground equipment includes a second device, to which the transceiver module 121 sends the terminal device identifier and the first list.

[0378] In one possible embodiment, the transceiver module 121 receives the subscription data of the terminal device sent by the second device; if the communication link between the first satellite and the terminal device is available, the transceiver module 121 and the processing module 120 establish a connection with the terminal device based on the subscription data of the terminal device and perform data transmission.

[0379] In one example, the communication device functions as a chip in a second satellite and performs the steps executed by the second satellite in the above method embodiments. The transceiver module 121 is used for specific execution. Figures 5 to 11 The transmitting and / or receiving actions performed by the second satellite in any of the embodiments shown herein may be, for example, the second satellite performing other processes of the techniques described herein. The processing module 120 may be used to support the communication device 12 in performing the processing actions in the above method embodiments, for example, to support the second satellite in performing other processes of the techniques described herein.

[0380] For example, the transceiver module 121 is configured to receive subscription data from the terminal device of the second device when the communication link between the second satellite and the ground network is available; to establish a connection with the terminal device based on the subscription data and perform data transmission when the communication link between the second satellite and the terminal device is available; to receive a first message sent by the first device; and to send a fourth message to the second device.

[0381] The processing module 120 is used to establish a connection with the terminal device based on the subscribed data and perform data transmission when the communication link between the second satellite and the terminal device is available.

[0382] In one possible embodiment, when the communication link between the second satellite and the ground network is available, the transceiver module 121 receives subscription data from the terminal device of the second device, the second device being used to store the subscription data of the terminal device, and the second satellite being located in a first list, the first list being used to indicate satellites that need to synchronize the subscription data; when the communication link between the second satellite and the terminal device is available, the transceiver module 121 and the processing module 120 establish a connection with the terminal device based on the subscription data and perform data transmission.

[0383] In one possible embodiment, the transceiver module 121 receives a first message sent by the first device, the first message being used to instruct the second satellite to acquire the subscription data of the terminal device; the transceiver module 121 sends a fourth message to the second device, the fourth message being used to instruct the second device to send the subscription data of the terminal device to the second satellite.

[0384] Processing module 120 may be a processor, which can execute computer execution instructions stored in the storage module to cause the chip to perform... Figures 5 to 11 The method involved in any of the embodiments shown in the figures. Further, the processor may include a controller, an arithmetic logic unit (ALU), and registers. For example, the controller is primarily responsible for instruction decoding and issuing control signals for the operations corresponding to the instructions. The ALU is primarily responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations, and can also perform address operations and conversions. The registers are primarily responsible for storing register operands and intermediate operation results temporarily stored during instruction execution. In specific implementations, the processor's hardware architecture can be an ASIC architecture, a microprocessor without interlocked piped stages architecture (MIPS), an advanced reduced instruction set machine (RISC) machine (ARM) architecture, or a network processor (NP) architecture, etc. The processor can be single-core or multi-core. The storage module can be an in-chip storage module, such as a register or cache. The storage module can also be an external storage module, such as ROM or other types of static storage devices that can store static information and instructions, RAM, etc.

[0385] It should be noted that the functions of the processor and interface can be implemented through hardware design, software design, or a combination of both; no restrictions are imposed here.

[0386] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0387] In summary, the above description is merely an embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the disclosure of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: The first device receives a first list sent by a first satellite, the first list indicating satellites whose contracted data of the terminal device needs to be synchronized, and the first device is used to store and forward data or signaling of the terminal device in the storage and forwarding satellite operation; The first device sends a first message to the second satellite, which instructs the second satellite to acquire the subscription data of the terminal device. The second satellite is located in the first list.

2. The method according to claim 1, characterized in that, The method further includes: The first device records the status information of the second satellite storing the contracted data. The status information includes at least one of the following: whether the contracted data is saved, and the time information of the last time the contracted data was received.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The first device sends a second message to the second device, the second message being used to instruct the second device to send a third message to the first device in the event that the subscription data is updated, the second device being used to store the subscription data of the terminal device.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The first device determines to send the first message to the second satellite based on at least one of the following: the second satellite stores status information of the subscription data; and a third message indicating that the subscription data has been updated.

5. The method according to claim 4, characterized in that, The first device determines to send the first message to the second satellite, including at least one of the following: The second satellite did not store the contract data; The second satellite last received the contracted data before the first device received the third message.

6. A communication method, characterized in that, include: The second device receives a fourth message sent by a first list or a second satellite. The second device is used to store the subscription data of the terminal device. The first list indicates satellites that need to synchronize the subscription data of the terminal device. The fourth message is used to instruct the second device to send the subscription data of the terminal device to the second satellite. The second device sends the terminal device's subscription data to the second satellite, which is located in the first list.

7. The method according to claim 6, characterized in that, The method further includes: The second device records the status information of the second satellite storing the contracted data. The status information includes at least one of the following: whether the contracted data is stored, and the time information of the most recent receipt of the contracted data.

8. The method according to any one of claims 6 or 7, characterized in that, The method further includes: The second device determines to send the contract data to the second satellite based on the status information of the contract data stored in the second satellite, or a fourth message.

9. The method according to claim 8, characterized in that, The second device determines to send the subscription data to the second satellite based on the status information of the subscription data stored on the second satellite, including at least one of the following: The second satellite did not store the contract data; The contract data is updated after the time when the second satellite last received the contract data.

10. A communication method, characterized in that, include: The second device records the status information of the subscription data of the third satellite storage terminal device. The status information includes at least one of the following: whether the subscription data is stored, and the time information of the last time the subscription data was received. The second device determines to send the subscription data to the third satellite based on the status information of the subscription data of the terminal device stored in the third satellite.

11. The method according to claim 10, characterized in that, The second device determines to send the subscription data to the third satellite based on the status information of the subscription data of the terminal device stored in the third satellite, including at least one of the following: The third satellite did not store the contract data; The contract data is updated after the time when the third satellite last received the contract data.

12. A communication method, characterized in that, include: The first satellite receives a fifth message from the terminal device, the fifth message being used to request network access. The first satellite determines a first list, which indicates satellites whose contracted data needs to be synchronized with the terminal device; When the communication link between the first satellite and the ground network is available, the first satellite sends the first list to ground equipment, which includes a first device or a second device. The first device is used to store and forward the data or signaling of the terminal device in a store-and-forward satellite operation, and the second device is used to store the subscription data of the terminal device.

13. The method according to claim 12, characterized in that, The first list includes a store-and-forward monitoring list, which indicates satellites that have established connections with the terminal device. The satellites that need to synchronize the contracted data of the terminal device include the satellites that have established connections.

14. The method according to claim 12, characterized in that, The method further includes: The first satellite determines a second list, which includes a store-and-forward monitoring list that indicates satellites that have established connections with the terminal device.

15. The method according to any one of claims 12-14, characterized in that, The first satellite determines the first list, which includes: The first satellite determines the first list based on first information, which includes at least one of the following: the location information of the terminal device, the power saving requirements of the terminal device, the movement trajectory of the terminal device, the mapping relationship between the satellite's coverage area and time, and network policy information.

16. The method according to any one of claims 12-15, characterized in that, The ground equipment includes a first device, and the method further includes: The first satellite receives the subscription data of the terminal device sent by the second device; When the communication link between the first satellite and the terminal device is available, the first satellite establishes a connection with the terminal device based on the terminal device's subscription data and performs data transmission.

17. The method according to claim 16, characterized in that, The method further includes: The first satellite receives a first message sent by the first device, the first message being used to instruct the first satellite to acquire the subscription data of the terminal device; The first satellite sends a sixth message to the second device, the sixth message being used to instruct the second device to send the subscription data of the terminal device to the first satellite.

18. The method according to any one of claims 12-15, characterized in that, The ground equipment includes a second device, and the first list sent by the first satellite to the ground equipment includes: The first satellite sends the terminal device identifier and the first list to the second device.

19. The method according to claim 18, characterized in that, The method further includes: The first satellite receives the subscription data of the terminal device sent by the second device; When the communication link between the first satellite and the terminal device is available, the first satellite establishes a connection with the terminal device based on the terminal device's subscription data and performs data transmission.

20. A communication method, characterized in that, include: When the communication link between the second satellite and the ground network is available, the second satellite receives subscription data from the terminal device of the second device, the second device is used to store the subscription data of the terminal device, and the second satellite is located in a first list, the first list is used to indicate satellites that need to synchronize the subscription data; When the communication link between the second satellite and the terminal device is available, the second satellite establishes a connection with the terminal device based on the subscribed data and performs data transmission.

21. The method according to claim 20, characterized in that, The method further includes: The second satellite receives a first message sent by the first device, the first message being used to instruct the second satellite to acquire the subscription data of the terminal device; The second satellite sends a fourth message to the second device, the fourth message being used to instruct the second device to send the terminal device's subscription data to the second satellite.

22. A communication device, characterized in that, Includes units or modules for implementing the method as described in any one of claims 1 to 21.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed, cause the computer to perform the method as described in any one of claims 1 to 21.

24. A computer program product, characterized in that, The computer program product includes: computer program code, which, when executed by a computer, causes the computer to perform the method as described in any one of claims 1 to 21.

25. A chip, characterized in that, The chip includes at least one processor and an interface, the processor being configured to read and execute instructions stored in a memory, which, when executed, cause the chip to perform the method as described in any one of claims 1 to 21.

Images