Communication method and device, communication equipment, storage medium and program product

Abstract

The invention relates to a communication method and device, communication equipment, a storage medium and a program product, and relates to the technical field of mobile communication. The method is applied to a terminal and comprises the following steps: receiving a first response message sent by a satellite network element in a TAU (Tracking Area Update) process; wherein the first response message comprises first information; the first information comprises a satellite identifier monitoring list; and performing communication processing based on the satellite identifier monitoring list. According to the technology of the invention, when terminal access is carried out in a multi-satellite scene, load balancing among different satellites can be realized, and the condition of network congestion or communication waiting is avoided, so that the request response efficiency of the terminal is improved.

Description

Technical Field

[0001] This application relates to the field of mobile communication technology, and in particular to a communication method, apparatus, communication device, storage medium, and program product. Background Technology

[0002] IoT-NTN (IoT over Non-Terrestrial Networks) is a mobile communication system that supports LTE (Long Term Evolution) network access via satellite, based on the NB-IoT (Narrow Band Internet of Things) technology standard. The satellite access method can be either satellite pass-through mode or satellite regeneration mode.

[0003] For IoT-NTN in satellite regeneration mode, the system focuses on supporting satellite IoT services for low-complexity eMTC (LTE enhanced Machine Type Communication) and IoT terminals, providing reliable data transmission services for various low-rate, low-frequency, and low-cost IoT applications.

[0004] For IoT-NTN technology in low- and medium-Earth orbit (LEO), in order to overcome the problem that the satellite's service link and power supply link cannot be available simultaneously, resulting in the inability to provide communication services to terminals within the satellite's coverage area at certain times, the LEO satellite regeneration mode IoT-NTN store-and-forward technology has emerged. However, this store-and-forward technology suffers from uneven satellite load in multi-satellite scenarios. Summary of the Invention

[0005] Therefore, it is necessary to provide a communication method, device, equipment, storage medium, and program product to improve satellite load balancing in multi-satellite scenarios, addressing the aforementioned technical problems.

[0006] In a first aspect, this application provides a communication method applied to a terminal, the method comprising:

[0007] During attachment or TAU, a first response message is received from the satellite network element; wherein, the first response message includes first information; the first information includes a satellite identifier listening list;

[0008] Communication processing is performed based on the satellite identifier listening list.

[0009] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0010] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0011] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0012] In one embodiment, the communication processing based on the satellite identifier listening list includes: starting the first timer; after the first timer expires, establishing a communication connection with the satellites in the satellite identifier listening list, and performing data transmission, TAU, or de-attachment processes.

[0013] In one embodiment, establishing a communication connection with a satellite in the satellite identifier listening list includes: listening to a first system information block (SIB) message; wherein the first SIB message includes the satellite identifier of the first satellite; the satellite identifier of the first satellite exists in the satellite identifier listening list; and establishing a communication connection with the satellite network element of the first satellite.

[0014] In one embodiment, the attach or TAU request includes first indication information, which allows the satellite network element to generate the first response message based on the first indication information; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0015] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0016] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0017] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0018] In one embodiment, if the first response message includes the second timer, then the communication processing based on the satellite identifier listening list includes: starting the second timer; after the second timer expires, and if the terminal has not successfully attached to another PLMN network or a satellite network element of the same PLMN network in non-store-and-forward mode, re-sending an attach or TAU request to the satellites in the satellite identifier listening list; wherein, the other PLMN network is a PLMN network different from the one to which the terminal last attached or TAUed; and the same PLMN network is the PLMN network to which the terminal last attached or TAUed.

[0019] In one embodiment, before the second timer expires, the method further includes: if the terminal attaches to another PLMN network or the same PLMN network in non-store-and-forward mode, then stopping the timing of the second timer; wherein the other PLMN network is a PLMN network different from the one to which the terminal last attached or TAU; and the same PLMN network is the PLMN network to which the terminal last attached or TAU.

[0020] In one embodiment, resending or continuing to send attach or TAU requests to satellites in the satellite identifier listening list includes:

[0021] Listen for the second SIB message; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier listening list; resend or continue to send the attach or TAU request to the satellite network element of the second satellite.

[0022] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0023] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the current satellite or the next satellite to re-execute or continue the attachment or TAU process; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0024] In one embodiment, if the first response message includes the third timer, the communication processing based on the satellite identifier listening list includes: starting the third timer; and after the third timer expires, if the terminal has not successfully attached to another PLMN network or a satellite network element of the same PLMN network in non-store-forward mode, re-sending an attach or TAU request to the current satellite or the next satellite; wherein, the other PLMN network is a PLMN network different from the one to which the terminal last attached or TAUed; and the same PLMN network is the PLMN network to which the terminal last attached or TAUed. In one embodiment, before the third timer expires, the method further includes: if the terminal attaches to another PLMN network or the same PLMN network in non-store-forward mode, stopping the timing of the third timer; wherein, the other PLMN network is a PLMN network different from the one to which the terminal last attached or TAUed; and the same PLMN network is the PLMN network to which the terminal last attached or TAUed.

[0025] In one embodiment, retransmitting the attach or TAU request to the current satellite or the next satellite includes: listening to a third SIB message; wherein the third SIB message includes the satellite identifier of the third satellite; the satellite identifier of the third satellite exists in the satellite identifier listening list; and retransmitting the attach or TAU request to the satellite network element of the third satellite.

[0026] Secondly, this application also provides a communication method applied to an on-board mobility management entity (MME), the method comprising:

[0027] During the attachment or TAU process, a first response message is sent to the terminal;

[0028] The first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

[0029] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0030] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0031] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0032] In one embodiment, before the first timer expires, the method further includes: synchronizing data with other devices; wherein the synchronized data includes at least one of the following: context information of the terminal, terminal location, and satellite identifier monitoring list.

[0033] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0034] In one embodiment, the method further includes: generating the first response message if the first indication information is not present in the attach or TAU request; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0035] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0036] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0037] In one embodiment, the method further includes generating the first response message if at least one of the following conditions is met during the initial attachment process or TAU process: access to the feeder link connection for authentication and security mode process is unavailable; the onboard home subscriber server (HSS) does not store the terminal's preset authentication vector or preset subscription information.

[0038] In one embodiment, the method further includes: generating a satellite identifier listening list with the same PLMN information, so that the terminal can re-execute the initial attachment process or TAU process; wherein the same PLMN information is the PLMN information of the network to which the terminal last attached or TAUed.

[0039] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0040] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the terminal to re-execute the attachment or TAU process for the current satellite or the next satellite; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0041] In one embodiment, if the first response message includes the third timer and the on-board MME corresponds to a ground MME, then before the third timer expires, the method further includes: sending the satellite identifier listening list to the ground MME so that the ground MME can reach the terminal's satellite in the shortest time through the satellite identifier listening list and authenticate with the terminal.

[0042] In one embodiment, sending the first response message to the terminal includes: generating a first response message if the on-board MME corresponds to a ground-based MME; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for the terminal to re-execute or continue an incomplete previous attach or TAU process; and sending the first response message to the terminal. In another embodiment, sending the first response message to the terminal includes: authenticating with the terminal if the on-board MME corresponds to an on-board HSS, and generating the first response message based on the authentication result; and sending the first response message to the terminal.

[0043] In one embodiment, generating the first response message based on the authentication result includes: if authentication is successful, generating the first response message; the first response message is an attach accept message or a TAU accept message; the first response message includes a satellite identifier listening list for terminal data transmission, TAU, or deattachment process; if authentication fails, generating the first response message; the first response message is an attach reject message or a TAU reject message; the first response message includes a satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0044] In one embodiment, the method further includes: obtaining a default configured satellite identifier listening list; or, generating the satellite identifier listening list based on at least one of terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0045] Thirdly, this application also provides a communication method applied to a ground-based MME corresponding to an on-board MME, the method comprising:

[0046] During the attach or TAU process, a first response message is received; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process;

[0047] The terminal is identified by the fourth satellite in the satellite identifier monitoring list that can reach it in the shortest time, and an authentication response message is obtained by authenticating with the terminal.

[0048] In one embodiment, the method further includes: generating an authentication response verification result based on the expected authentication response value carried in the authentication response message; determining a fifth satellite that can reach the terminal in the shortest time according to the satellite identifier listening list; generating a second response message based on the authentication response verification result; the second response message includes second information; the second information includes a first satellite identifier listening list; and sending the second response message to the terminal through the onboard MME of the fifth satellite; wherein the first satellite identifier listening list is used for communication processing by the terminal.

[0049] In one embodiment, generating a second response message based on the authentication response verification result includes: generating the second response message if the authentication response verification is successful; wherein the second response message is an attach accept message or a TAU accept message; the second response message includes a first satellite identifier listening list for terminal data transmission, TAU, or detach process.

[0050] In one embodiment, the second response message further includes a fourth timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment.

[0051] In one embodiment, the method further includes: synchronizing data with other devices before the fourth timer expires; wherein the synchronized data includes at least one of the following: context information of the terminal, terminal location, and the first satellite identifier listening list.

[0052] In one embodiment, generating a second response message based on the authentication response verification result includes: generating a second response message if the authentication response verification fails; wherein the second response message is an attach rejection message or a TAU rejection message; the second response message includes a first satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0053] In one embodiment, the second response message further includes a fourth indication message and / or a fifth timer; wherein the fourth indication message is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the fifth timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0054] In one embodiment, the method further includes: obtaining a first satellite identifier listening list with a default configuration; or, generating the first satellite identifier listening list based on at least one of terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0055] In one embodiment, the step of authenticating with the terminal using the fourth satellite in the satellite identifier listening list that is reachable from the terminal in the shortest time and obtaining an authentication response message includes: sending an authentication vector request to the ground HSS; wherein the authentication vector request includes a request time for an attach or TAU request; receiving an authentication vector sent by the ground HSS if no other MME has sent a location update request before the request time; and authenticating with the terminal using the fourth satellite in the satellite identifier listening list that is reachable from the terminal in the shortest time and the authentication vector to obtain an authentication response message.

[0056] Fourthly, this application provides a communication device configured in a terminal, the device comprising:

[0057] The first receiving module is configured to receive a first response message sent by the satellite network element during the attach or TAU process; wherein the first response message includes first information; the first information includes a satellite identifier listening list;

[0058] The first processing module is used to perform communication processing based on the satellite identifier listening list.

[0059] Fifthly, this application provides another communication device configured on an onboard MME, the device comprising:

[0060] A first sending module is configured to send a first response message to a terminal during the attach or TAU process; wherein the first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

[0061] Sixthly, this application provides another communication device configured on a ground-based MME corresponding to an on-board MME, the device comprising:

[0062] The second receiving module is used to receive a first response message during the attachment or TAU process; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previous unfinished attachment or TAU process;

[0063] The first authentication module is used to authenticate with the terminal by listening to the fourth satellite in the satellite identifier monitoring list that can reach the terminal in the shortest time and obtain an authentication response message.

[0064] In a seventh aspect, this application also provides a communication device, which includes a memory, a transceiver, and a processor. The memory stores a computer program, the transceiver is used to receive or send data under the control of the processor, and the processor executes the computer program to implement the communication methods in the embodiments provided in the first, second, and third aspects.

[0065] Eighthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the communication methods in the embodiments provided in the first, second, and third aspects.

[0066] Ninthly, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the communication methods in the embodiments provided in the first, second, and third aspects.

[0067] The aforementioned communication method, apparatus, communication equipment, storage medium, and program product, by receiving a first response message sent by a satellite network element during the attachment or TAU process, and introducing first information including a satellite identifier listening list into the first response message, enable the terminal to perform communication processing based on the satellite identifier listening list. This allows for load balancing among different satellites when the terminal accesses the network in a multi-satellite scenario, avoiding network congestion or communication waiting, thereby improving the terminal request response efficiency. Attached Figure Description

[0068] Figure 1 This is a flowchart illustrating a communication method in one embodiment;

[0069] Figure 2 This is a flowchart illustrating the communication method in another embodiment;

[0070] Figure 3 This is a flowchart illustrating the steps for generating the first response message in one embodiment;

[0071] Figure 4 This is a flowchart illustrating the steps for generating the first response message in another embodiment;

[0072] Figure 5 This is a flowchart illustrating the communication method in another embodiment;

[0073] Figure 6 This is a flowchart illustrating the communication method in another embodiment;

[0074] Figure 7 This is a flowchart illustrating the communication method in another embodiment;

[0075] Figure 8This is a flowchart illustrating the communication method in another embodiment;

[0076] Figure 9 This is a structural block diagram of a communication device in one embodiment;

[0077] Figure 10 This is a structural block diagram of the communication device in another embodiment;

[0078] Figure 11 This is a structural block diagram of the communication device in another embodiment;

[0079] Figure 12 This is an internal structural diagram of a communication device in one embodiment. Detailed Implementation

[0080] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0081] To facilitate understanding, before introducing the embodiments of this application, some relevant functional network elements and technical terms involved in this application will be introduced first.

[0082] UE (User Equipment), also known as a terminal, is the basic unit in a mobile communication network. Users access the network, conduct communication, and transmit data through the UE. The UE needs to interact with other nodes in the network (such as base stations and core network nodes) to achieve communication functions. Specifically, the UE supports network access and data transmission functions in NTN (Non-Terrestrial Network) store-and-forward scenarios.

[0083] Satellite base stations are base station equipment deployed on satellites to provide wireless communication services.

[0084] The Mobility Management Entity (MME) is a key control node in wireless communication networks under the 3GPP (3rd Generation Partnership Project) protocol. It is responsible for UE location in idle mode, paging processes (including relaying), and bearer activation / deactivation processes. The MME plays a crucial role in mobile communication networks, handling signaling processing, security control, cross-CN (Core Network) signaling support, and reachability management for idle UEs. The MME is also involved in user attach and detach procedures, as well as bearer management.

[0085] The onboard MME, a mobility management function entity located on the satellite, is a subset of the mobility management function entity's functions. Its functions include receiving and forwarding NAS signaling / data messages, and buffering NAS signaling / data messages. When the serving link is available, it receives and buffers uplink NAS signaling / data messages from the terminal, and forwards the buffered downlink NAS signaling / data messages to the terminal. When the power supply link is available, it forwards the buffered uplink NAS signaling / data messages to the ground MME, and receives and buffers downlink NAS signaling / data messages from the ground MME.

[0086] The terrestrial MME, located on the ground, is a mobility management function entity that has all the functions of a mobility management function entity. It is responsible for terminal mobility management, access control, bearer management, session management, and NAS signaling processing.

[0087] The Home Subscriber Server (HSS) is an essential component of LTE wireless networks, acting as the "brain" of the mobile core network and providing users with various services. Its main functions include user authentication, user authorization, and the storage and retrieval of user information. During user access, the HSS verifies the user's identity and allocates appropriate network resources based on the user's different permissions. In this application, the HSS can be understood as the Home Subscriber Server used for store-and-forward services.

[0088] Attachment is a fundamental concept in mobile communication networks, referring to the process by which a UE registers its existence with the network and requests services when it powers on or enters a network coverage area.

[0089] Detachment, the reverse of the attachment process, refers to the UE actively informing the network that it no longer needs service, or the network recognizing the device as "left" when it has been inactive for an extended period, its battery is depleted, or the user turns off the device. During detachment, the network clears information associated with the device and the resources allocated to it, making those resources available for other devices. Detachment ensures efficient management of network resources and continuity of service for user devices.

[0090] Tracking Area Update (TAU) is used to update a user's location information. When a user moves from one tracking area to another, the TAU procedure is executed to notify the network of the user's new location. The TAU procedure ensures that the network accurately knows the user's location information, thereby providing better mobility management and services. Through the TAU procedure, the network can allocate appropriate resources to the user, ensuring smooth communication and data transmission.

[0091] NAS (Non-Access Stratum Message) messages are used to transmit control information between the UE and the mobility management entity (such as the MME). NAS messages include attach requests, detach requests, and location update requests, and are used to manage user mobility, session establishment, and authentication processes. NAS messages play a crucial role in mobile communication networks, responsible for transmitting necessary control information between the user and the network to enable functions such as user mobility management, session establishment, and authentication.

[0092] A PLMN (Public Land Mobile Network) is an identifier for a combination of wireless communication services provided by a specific operator in a particular country / region. A PLMN typically consists of multiple cellular technologies, providing users with wireless communication services that enable voice calls, data transmission, and other communication activities within a specific geographical area. The PLMN also interconnects with other PLMNs and the public switched telephone network to achieve cross-network communication services.

[0093] System Information Block (SIB) messages are an important part of the LTE (Long Term Evolution) system used to transmit system information. These messages are transmitted in two categories: Master Information Block (MIB) and System Information Block (SIB).

[0094] A 3GPP network refers to a network that conforms to the 3GPP standard. Furthermore, a 3GPP network is not limited to the 5G network defined by 3GPP; it can also include 2G, 3G, and 4G networks. Typically, 3GPP networks are operated by mobile operators.

[0095] In one alternative embodiment, such as Figure 1 As shown, a communication method is provided for use in a terminal. The method includes:

[0096] S110, during the attach or TAU process, receives a first response message sent by the satellite network element; wherein, the first response message includes first information; the first information includes a satellite identification listening list.

[0097] The on-board base station sends (e.g., broadcasts) an SIB message; upon receiving the SIB message, the terminal sends an attach or TAU request to the corresponding satellite network element of the on-board base station; the satellite network element accepts or rejects the attach or TAU request based on its own circumstances and receives a first response message; the satellite network element sends the first response message to the terminal. For example, the attach or TAU request and / or the first response message can be a NAS message.

[0098] The SIB message may include at least one of the following: the PLMN information to which the satellite belongs, satellite identification information, and valid satellite cell information. The first response message may be a rejection message or an acceptance message. The satellite identification listening list includes satellite identifications corresponding to at least one satellite, and satellites in this list are capable of communicating with the terminal.

[0099] For example, based on the valid satellite cell information carried in the SIB message, it can be determined whether the satellite cell corresponding to the satellite network element allows UE access; if it allows, an attach or TAU request is sent to the satellite network element; otherwise, no attach or TAU request is sent to the satellite network element.

[0100] Optionally, the first response message can be an attach rejection message or a TAU rejection message; correspondingly, the first information may include a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process, or the first information may include a satellite identifier listening list for the terminal to re-attach after an attach failure, or to re-TAU after a TAU failure. Alternatively, the first response message can be an attach accept message or a TAU accept message; correspondingly, the first information may include a satellite identifier listening list for the terminal data transmission, TAU, or detach process.

[0101] Understandably, in order to facilitate subsequent communication processing by the terminal, the terminal may save the first response message, the first information, or the satellite identifier listening list.

[0102] It is worth noting that if the terminal already stores other satellite identifier monitoring lists, the newly received satellite identifier monitoring list can overwrite the original satellite identifier monitoring list, avoiding errors in list usage and improving the rationality and accuracy of satellite resource allocation.

[0103] Optionally, the attach or TAU request may include first indication information, which allows the satellite network element to generate a first response message based on the first indication information; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0104] For example, during the attach or TAU process, the terminal sends an attach or TAU request to the onboard MME. The onboard MME determines whether the attach or TAU request carries first indication information; if not, it generates a first response message indicating rejection, that is, an attach rejection message or a TAU rejection message.

[0105] S120 performs communication processing based on a satellite identifier listening list.

[0106] For example, the terminal can determine the target satellite for which communication processing operations will actually be performed based on the satellite identifier listening list; and perform communication processing based on the satellite network elements on the target satellite. It is worth noting that the target satellite can be determined by actively initiating paging or listening to SIB messages, and this application does not impose any limitations on this.

[0107] It is worth noting that the communication processing operations corresponding to different satellite identification listening lists are usually at least partially different.

[0108] Optionally, if the first information includes a satellite identifier listening list for the terminal to re-execute or continue a previously incomplete attach or TAU procedure, or a satellite identifier listening list for re-attaching or re-TAU after a failed attach attempt, then the communication processing performed may include re-executing or continuing the attach or TAU procedure. For example, this can be achieved by re-sending attach or TAU requests to satellites in the satellite identifier listening list.

[0109] Alternatively, if the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment procedures, the communication processing performed may include establishing a communication connection with satellites in the satellite identifier listening list and performing data transmission, TAU, or de-attachment procedures.

[0110] In one optional implementation, the SIB message received by the terminal from the on-board base station may also carry a satellite identifier listening list. If the on-board network element generates a first response message indicating rejection (i.e., an attach rejection request or a TAU rejection request), the first response message may contain either a satellite identifier listening list or not.

[0111] Optionally, if the first response message carries a satellite identifier listening list, communication can be performed directly based on that satellite identifier listening list. Alternatively, if the first response message does not carry a satellite identifier listening list, communication can be performed based on the satellite identifier listening list carried in the SIB message.

[0112] It is worth noting that the method of communication processing based on the satellite identifier listening list carried in the SIB message is the same as the method of communication processing based on the satellite identifier listening list carried in the first response message. The satellite identifier listening list carried in the SIB message can be directly used as the satellite identifier listening list carried in the first response message for processing. This application will only use the satellite identifier listening list carried in the first response message as an example to illustrate the communication processing process, and should not be construed as a specific limitation on the satellite identifier listening list used in the communication processing.

[0113] This application embodiment receives a first response message sent by a satellite network element during the attach or TAU process, and introduces first information including a satellite identifier listening list into the first response message, enabling the terminal to perform communication processing based on the satellite identifier listening list. This allows for load balancing among different satellites when the terminal accesses the network in a multi-satellite scenario, avoiding network congestion or communication waiting, thereby improving the terminal request response efficiency.

[0114] For ease of understanding, the message content and response method of the first response message corresponding to different access conditions of the terminal are described in detail below.

[0115] In an optional embodiment, if the first response message is an acceptance message (i.e., an attach acceptance message or a TAU acceptance message), and if the first information includes a satellite identifier listening list for terminal data transmission, TAU, or detachment processes, the first response message may also include a first timer to indicate the waiting time required for terminal data transmission, TAU, or detachment processes.

[0116] If the first timer is not included in the first response message, a communication connection is directly established with the satellite in the satellite identifier listening list, and data transmission, TAU, or de-attachment procedures are performed. The satellite with which the communication connection is established can be the current satellite or the next satellite, and the corresponding satellite's satellite identifier must be present in the satellite identifier listening list.

[0117] When the first response message includes a first timer, communication processing based on the satellite identifier listening list may include: starting the first timer; after the first timer expires, establishing a communication connection with satellites in the satellite identifier listening list, and performing data transmission, TAU, or detachment procedures. It is worth noting that during the first timer's duration, terminal context information can be synchronized with satellites in the satellite identifier listening list, laying the foundation for satellites in the list to provide network services to the terminal.

[0118] For example, the terminal does not actively trigger data transmission, TAU, or detachment procedures before the first timer expires. Further, after the first timer expires, the terminal may actively trigger data transmission, TAU, or detachment procedures.

[0119] In one optional embodiment, after the first timer expires, establishing a communication connection with a satellite in the satellite identifier listening list may include: listening to a first SIB message; wherein the first SIB message includes the satellite identifier of the first satellite; the satellite identifier of the first satellite exists in the satellite identifier listening list; and establishing a communication connection with the satellite network element of the first satellite.

[0120] For example, after the first timer expires, the terminal starts listening for SIB messages; it determines whether the satellite identification information in the listened SIB message, i.e., the satellite identification of the first satellite, exists in the satellite identification listening list; if so, it actively triggers a network connection to the satellite's network element and performs data transmission, TAU, or detach process. To distinguish it from the aforementioned SIB messages, the SIB message here can be referred to as the first SIB message.

[0121] In the case where the first response message is a rejection message (i.e., an attach rejection message or a TAU rejection message), in an optional embodiment, if the first information includes a satellite identifier listening list for reattaching after a terminal attach failure or re-TAU after a TAU failure, the first response message may also include second indication information, which is used to indicate that the current satellite does not support the terminal attaching or TAU at this moment.

[0122] Optionally, the first response message may also include a second timer; the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0123] If the second timer is not included in the first response message, the terminal can directly resend or continue sending attach or TAU requests to satellites in the satellite identifier listening list. The communicating satellite can be the current satellite or the next satellite, and the corresponding satellite's identifier must be present in the satellite identifier listening list.

[0124] When the first response message includes a second timer, communication processing based on the satellite identifier listening list may include: starting the second timer; and after the second timer expires, if the terminal has not successfully attached to another PLMN network or a satellite network element of the same PLMN network in non-store-and-forward mode, re-sending attach or TAU requests to satellites in the satellite identifier listening list. Here, "other PLMN networks" refers to PLMN networks different from the terminal's last attach or TAU; "same PLMN network" refers to the PLMN network to which the terminal last attached or TAUed. The advantage of this approach is that by introducing the second timer, terminal power consumption can be saved, and signaling interaction between the terminal and the network can be reduced.

[0125] It is worth noting that before the second timer expires, the terminal will not attempt to initiate an attach or TAU request to the same PLMN network in store-and-forward mode; alternatively, the terminal may attempt to attach to other PLMN networks or to the same PLMN network in non-store-and-forward mode. Here, "other PLMN networks" refers to PLMN networks different from the terminal's last attach or TAU; "same PLMN network" refers to the PLMN network the terminal last attached or TAUed.

[0126] In one alternative embodiment, if the terminal attaches to another PLMN network or the same PLMN network in non-store-forward mode before the second timer expires, the timing of the second timer is stopped. Accordingly, the terminal communicates normally with the successfully attached network.

[0127] In another optional embodiment, if the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode after the second timer expires, it listens for the second SIB message; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier listening list; and it resends or continues to send attach or TAU requests to the satellite network element of the second satellite.

[0128] In another specific implementation, after the second timer expires, if the terminal fails to attach to another PLMN network or a network of the same PLMN in non-store-and-forward mode, it listens for SIB messages; it checks whether the satellite identifier information in the listened SIB message, i.e., the satellite identifier of the second satellite, exists in the satellite identifier listening list; if so, it attempts to resend the attach or TAU request message to the satellite network element of the second satellite; otherwise, it continues to listen for other SIB messages. To distinguish it from the aforementioned SIB messages, the SIB messages here can be referred to as the second SIB messages.

[0129] This application embodiment introduces second indication information into the first response message, enabling the terminal to promptly obtain the response results and reasons from satellite network elements to attach or TAU requests after acquiring the satellite identifier listening list. This avoids communication errors and improves the accuracy of communication services. Optionally, a second timer is introduced into the first response message, allowing the terminal to attempt network attach during the second timer's duration, avoiding prolonged waiting times and improving response efficiency. Furthermore, if attachment is still unsuccessful after the second timer expires, the first request message is sent to other satellites in the satellite identifier listening list, preventing communication failures and ensuring the availability of terminal communication services.

[0130] In another optional embodiment, if the first response message is a rejection message (i.e., an attachment rejection message or a TAU rejection message), and if the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previous unfinished attachment or TAU process, the first response message may also include third indication information, which is used to indicate that the current satellite cannot immediately complete the attachment or TAU process.

[0131] Optionally, the first response message may also include a third timer, which indicates the waiting time required for the current or next satellite to re-execute or continue the attachment or TAU process; the satellite identifier of the current or next satellite is present in the satellite identifier listening list.

[0132] If the third timer is not included in the first response message, the terminal can directly resend the attach or TAU request to the current satellite or the next satellite. The communicating satellite can be the current satellite or the next satellite, and the satellite identifier of the corresponding satellite must be present in the satellite identifier listening list.

[0133] When the first response message includes a third timer, communication processing based on the satellite identifier listening list may include: starting the third timer; and after the third timer expires, if the terminal has not successfully attached to another PLMN network or a satellite network element of the same PLMN network in non-store-and-forward mode, re-sending an attach or TAU request to the current satellite or the next satellite; wherein, other PLMN networks are PLMN networks different from the terminal's last attach or TAU; the same PLMN network is the PLMN network to which the terminal last attached or TAU; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list. The advantage of this approach is that by introducing the third timer, terminal power consumption can be saved, and signaling interaction between the terminal and the network can be reduced.

[0134] It is worth noting that before the third timer expires, the terminal will not attempt to initiate an attach or TAU request to the same PLMN network in store-and-forward mode; alternatively, the terminal may attempt to attach to other PLMN networks or to the same PLMN network in non-store-and-forward mode. Here, "other PLMN networks" refers to PLMN networks different from the terminal's last attach or TAU; "same PLMN network" refers to the PLMN network where the terminal last attached or TAUed.

[0135] In one alternative embodiment, if the terminal attaches to another PLMN network or the same PLMN network in non-store-forward mode before the third timer expires, the timing of the third timer is stopped. Accordingly, the terminal communicates normally with the successfully attached network.

[0136] In another specific implementation, before the third timer expires, if a paging message is received from the satellite's network element, it is determined whether the satellite identifier exists in the satellite identifier listening list. If it exists, and the PLMN information in the corresponding SIB message is consistent with the PLMN information at the time of the last attachment or TAU, an RRC (Radio Resource Control) connection is established with the satellite's network element, and the unfinished attachment or TAU process is re-executed or continued according to the saved context information of the attachment or TAU process.

[0137] In another optional embodiment, after the third timer expires and the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal can also listen to the third SIB message; wherein the third SIB message includes the satellite identifier of the third satellite; the satellite identifier of the third satellite exists in the satellite identifier listening list; and resend attach or TAU requests to the satellite network element of the third satellite.

[0138] For example, after the third timer expires, if the terminal fails to attach to another PLMN network or a network of the same PLMN in non-store-and-forward mode, it listens for SIB messages; it determines whether the satellite identification information in the listened SIB message, i.e., the satellite identification of the third satellite, exists in the satellite representation listening list; if so, it attempts to resend or continue to send an attach or TAU request to the satellite network element of the third satellite; otherwise, it continues to listen for other SIB messages. To distinguish it from the aforementioned SIB messages, the SIB messages here can be referred to as the third SIB messages.

[0139] This application embodiment introduces third indication information into the first response message, enabling the terminal to promptly obtain the response results and reasons from the satellite network element to the attach or TAU request after acquiring the satellite identifier listening list. This avoids communication errors and improves the accuracy of the communication service. Optionally, a third timer is introduced into the first response message, allowing the terminal to attempt network attach during the timer's duration, avoiding long waiting times and improving response efficiency. Furthermore, if attachment is still unsuccessful after the third timer expires, an attach or TAU request is sent to the current or next satellite, preventing communication failures and ensuring the availability of the terminal's communication service.

[0140] Based on the technical solutions of the above embodiments, further, after the terminal completes the attach or TAU process, it sends an attach or TAU completion message to the attached satellite network element; wherein, the attach or TAU completion message includes fifth indication information; the fifth indication information is used to instruct the terminal to transmit data based on the satellite identifier listening list. Optionally, the attach or TAU completion message can be a NAS message. It is understood that by sending an attach or TAU completion message including the fifth indication information to the attached satellite network element, the terminal facilitates the network side to promptly obtain information about the terminal's attachment status.

[0141] The above describes the communication process in detail with the terminal, i.e., UE, as the execution subject. The following will describe the communication process designed in this application in detail with the onboard MME as the execution subject.

[0142] See Figure 2 The communication method shown, applied to the onboard MME, includes:

[0143] S210, during the attach or TAU process, a first response message is sent to the terminal; wherein, the first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

[0144] The on-board base station sends (e.g., broadcasts) an SIB message; upon receiving the SIB message, the terminal sends an attach or TAU request to the corresponding on-board MME of the on-board base station; the on-board MME receives the attach or TAU request sent by the terminal; the on-board MME accepts or rejects the attach or TAU request based on its own circumstances and obtains a first response message; the on-board MME sends the first response message to the terminal. For example, the attach or TAU request and / or the first response message may be a NAS message.

[0145] The first response message can be either a rejection message for an attach or TAU request, or an acceptance message for an attach or TAU request. The satellite identifier listening list includes satellite identifiers corresponding to at least one satellite, and the satellites in this list are capable of communicating with the terminal.

[0146] Optionally, the first response message can be an attach rejection message or a TAU rejection message; correspondingly, the first information may include a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process, or the first information may include a satellite identifier listening list for the terminal to re-attach after an attach failure, or to re-TAU after a TAU failure. Alternatively, the first response message can be an attach accept message or a TAU accept message; correspondingly, the first information may include a satellite identifier listening list for the terminal data transmission, TAU, or detach process.

[0147] Optionally, the attach or TAU request may include first indication information; the first indication information is used to indicate that the terminal supports store-and-forward mode. Accordingly, after receiving the attach or TAU request, the on-board MME judges the attach or TAU request; if the first indication information is not present in the attach or TAU request, a first response message indicating rejection is generated, that is, an attach rejection message or a TAU rejection message.

[0148] In one optional embodiment, a satellite identifier listening list can be added to the onboard MME using the default configuration; correspondingly, when the onboard MME generates the first response message, it can directly obtain the satellite identifier listening list configured by default.

[0149] In another optional embodiment, a satellite identifier listening list can be generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS, thereby ensuring the timeliness and accuracy of the satellite identifier listening list.

[0150] Accordingly, after receiving the first response message, the terminal can determine the target satellite for which communication processing will actually be performed based on the satellite identifier listening list; and perform communication processing based on the satellite network elements on the target satellite. It is worth noting that the target satellite can be determined by actively initiating paging or listening to SIB messages; this application does not impose any limitations on this.

[0151] It is worth noting that the communication processing operations corresponding to different satellite identification listening lists are usually at least partially different.

[0152] Optionally, if the first information includes a satellite identifier listening list for the terminal to re-execute or continue a previously incomplete attach or TAU procedure, or a satellite identifier listening list for re-attaching or re-TAU after a failed attach attempt, then the communication processing performed may include re-executing or continuing the attach or TAU procedure. For example, this can be achieved by re-sending attach or TAU requests to satellites in the satellite identifier listening list.

[0153] Alternatively, if the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment procedures, the communication processing performed may include establishing a communication connection with satellites in the satellite identifier listening list and performing data transmission, TAU, or de-attachment procedures.

[0154] Understandably, in order to facilitate subsequent communication processing by the terminal, the terminal may save the first response message, the first information, or the satellite identifier listening list.

[0155] It is worth noting that if the terminal already stores other satellite identifier monitoring lists, the newly received satellite identifier monitoring list can overwrite the original satellite identifier monitoring list, avoiding errors in list usage and improving the rationality and accuracy of satellite resource allocation.

[0156] This application embodiment receives a first response message sent by a satellite network element during the attach or TAU process, and introduces first information including a satellite identifier listening list into the first response message, enabling the terminal to perform communication processing based on the satellite identifier listening list. This allows for load balancing among different satellites when the terminal accesses the network in a multi-satellite scenario, avoiding network congestion or communication waiting, thereby improving the terminal request response efficiency.

[0157] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment. In this optional embodiment, the generation process of the first response message is described in detail for the case where the on-board MME corresponds to the on-board HSS, that is, the case where at least the MME and the HSS are on the network side of the satellite.

[0158] See Figure 3 The steps for generating the first response message shown include:

[0159] S310 authenticates with the terminal.

[0160] For example, if there is no subscription data or security data corresponding to the terminal that sent the attach or TAU request in the current satellite, an authentication failure result is generated; if there is subscription data and security data corresponding to the terminal that sent the first request in the current satellite, an authentication success result is generated.

[0161] Specifically, the onboard MME can obtain the terminal's subscription information from the onboard HSS; if the onboard HSS does not contain the terminal's subscription data, an authentication failure result is generated. The onboard MME can also obtain the terminal's security data from the onboard HSS or other network elements; if the terminal's security data is not found in the onboard HSS or other network elements, an authentication failure result is generated. Furthermore, if the terminal's subscription information exists in the onboard HSS, and the terminal's security data exists in the onboard HSS or other network elements, an authentication success result is generated.

[0162] S320: Based on the authentication result, generate a first response message; the first response message is either an accept message or a reject message for the attach or TAU request.

[0163] Optionally, if authentication fails, a first response message is generated; the first response message is a rejection message for attach or TAU request, i.e., an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for reattaching after the terminal fails to attach, or re-TAU after the TAU fails.

[0164] Alternatively, if authentication is successful, a first response message is generated; the first response message is an acceptance message for the attach or TAU request, i.e., an attach acceptance message or a TAU acceptance message; the first response message includes a satellite identifier listening list for terminal data transmission, TAU, or detach process.

[0165] The satellite identification listening list can be a list configured by default on the onboard MME; or it can be a list generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the onboard HSS.

[0166] It is worth noting that when a satellite identification listening list needs to be generated, the onboard MME can obtain the terminal's subscription information from the onboard HSS.

[0167] In one specific implementation, a first response message is generated if at least one of the following conditions is met during the initial attach process or TAU process: access to the feeder link connection for authentication and security mode procedures is unavailable; and the HSS does not store the terminal's preset authentication vector or preset subscription information.

[0168] Correspondingly, a satellite identifier listening list with the same PLMN information can be generated, allowing the terminal to re-execute the initial attach procedure or TAU procedure. The same PLMN information refers to the PLMN information of the network to which the terminal last attached or underwent TAU.

[0169] This application embodiment, when the on-board MME corresponds to the on-board HSS, introduces the authentication result of the authentication with the terminal to generate the first response message, and distinguishes the generated first response message under different circumstances, thereby improving the accuracy and rationality of the first response message, and thus ensuring the accuracy and effectiveness of the communication services provided to the terminal.

[0170] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment. In this optional embodiment, for the case where the on-board MME corresponds to the ground MME, that is, the satellite network element does not contain HSS and the MME function is separated on the network side of the satellite network element and the ground network element, the generation process of the first response message is described in detail.

[0171] See Figure 4 The steps for generating the first response message shown include:

[0172] S410, Generate a first response message; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process.

[0173] For example, the onboard MME receives an attach or TAU request from a terminal; the onboard MME performs at least one of the following operations: saves the attach or TAU request, the terminal's location information, and the request time of the attach or TAU request; the onboard MME generates a first response message rejecting the attach or TAU request and sends it to the terminal. The first response message includes a satellite identifier listening list for the terminal to re-execute or continue any previously incomplete attach or TAU procedures; the satellite identifier listening list includes the satellite identifiers of at least one satellite.

[0174] For example, the satellite identification listening list can be a list configured by default in the onboard MME; or it can be a list generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the onboard HSS.

[0175] It should be noted that, because the on-board MME needs to work with the ground MME to authenticate the terminal, when the on-board MME receives an attach or TAU request from the terminal, it will initially reject the request. Subsequently, after the ground MME and the terminal have completed authentication, satellite allocation will be performed for the terminal based on its actual status for subsequent communication processing. This improves the rationality of satellite resource allocation in situations where the on-board MME and ground MME are set up separately.

[0176] The generation process of the first response message under different circumstances has been introduced above. The following will describe in detail the message content and response method of the first response message corresponding to the terminal under different access conditions.

[0177] In an optional embodiment, if the first response message is an acceptance message (i.e., an attach acceptance message or a TAU acceptance message), and if the first information includes a satellite identifier listening list for terminal data transmission, TAU, or detachment processes, the first response message may also include a first timer to indicate the waiting time required for terminal data transmission, TAU, or detachment processes.

[0178] If the first timer is not included in the first response message, a communication connection is directly established with the satellite in the satellite identifier listening list, and data transmission, TAU, or de-attachment procedures are performed. The satellite with which the communication connection is established can be the current satellite or the next satellite, and the corresponding satellite's satellite identifier must be present in the satellite identifier listening list.

[0179] If the first response message includes a first timer, the terminal starts the first timer; after the first timer expires, it establishes a communication connection with the satellite in the satellite identifier listening list and performs data transmission, TAU, or deattachment procedures.

[0180] In one optional embodiment, before the first timer expires, the onboard MME synchronizes data with other devices. The synchronized data may include at least one of the following: terminal context information, terminal location, and satellite identifier listening list. The other devices may include at least one of the following: a ground proxy function network element and onboard MMEs of satellites in the satellite identifier listening list. Accordingly, the ground proxy function network element can save the synchronized data for later use.

[0181] It is worth noting that during the first timer period, data synchronization with other devices can lay the foundation for providing network services to terminals for other satellites in the satellite identification monitoring list.

[0182] For example, the terminal does not actively trigger data transmission, TAU, or detachment procedures before the first timer expires. Further, after the first timer expires, the terminal may actively trigger data transmission, TAU, or detachment procedures.

[0183] In one optional embodiment, after the first timer expires, the terminal listens for a first SIB message; wherein the first SIB message includes the satellite identifier of the first satellite; the satellite identifier of the first satellite exists in the satellite identifier listening list; and a communication connection is established with the satellite network element of the first satellite.

[0184] For example, after the first timer expires, the terminal starts listening for SIB messages; it determines whether the satellite identification information in the listened SIB message, i.e., the satellite identification of the first satellite, exists in the satellite identification listening list; if so, it actively triggers a network connection to the satellite's network element and performs data transmission, TAU, or detach process. To distinguish it from the aforementioned SIB messages, the SIB message here can be referred to as the first SIB message.

[0185] In the case where the first response message is a rejection message (i.e., an attach rejection message or a TAU rejection message), in another optional embodiment, if the first information includes a satellite identifier monitoring list for reattaching after a terminal attach failure or re-TAU after a TAU failure, the first response message may also include second indication information, which is used to indicate that the current satellite does not support the terminal attaching or TAU at this moment.

[0186] Optionally, the first response message may also include a second indication message; the second indication message is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0187] If the second timer is not included in the first response message, the terminal can directly resend or continue sending attach or TAU requests to satellites in the satellite identifier listening list. The communicating satellite can be the current satellite or the next satellite, and the corresponding satellite's identifier must be present in the satellite identifier listening list.

[0188] If the first response message includes a second timer, the terminal starts the second timer. After the second timer expires, and if the terminal has not successfully attached to another PLMN network or a satellite network element within the same PLMN network in non-store-and-forward mode, it resends attach or TAU requests to satellites in the satellite identifier listening list. Here, "other PLMN networks" refers to PLMN networks different from the terminal's previous attach or TAU; "same PLMN network" refers to the PLMN network the terminal previously attached to or TAUed with. The advantage of this approach is that by introducing the second timer, terminal power consumption can be saved, and signaling interaction between the terminal and the network can be reduced.

[0189] It is worth noting that before the second timer expires, the terminal will not attempt to initiate an attach or TAU request to the same PLMN network in store-and-forward mode; alternatively, the terminal may attempt to attach to other PLMN networks or to the same PLMN network in non-store-and-forward mode. Here, "other PLMN networks" refers to PLMN networks different from the terminal's last attach or TAU; "same PLMN network" refers to the PLMN network the terminal last attached or TAUed.

[0190] In one alternative embodiment, if the terminal attaches to another PLMN network or the same PLMN network in non-store-forward mode before the second timer expires, the timing of the second timer is stopped. Accordingly, the terminal communicates normally with the successfully attached network.

[0191] In another optional embodiment, after the second timer expires and the terminal fails to attach to the PLMN network or the satellite network element of the same PLMN network in non-store-and-forward mode, the terminal may listen to the second SIB message; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier listening list; and resend attach or TAU requests to the satellite network element of the second satellite.

[0192] In another specific implementation, after the second timer expires, if the terminal fails to attach to another PLMN network or a non-store-and-forward network of the same PLMN, it listens for SIB messages; it checks whether the satellite identifier information in the listened SIB message, i.e., the satellite identifier of the second satellite, exists in the satellite identifier listening list; if so, it attempts to resend or continue to send attach or TAU request messages to the satellite network element of the second satellite; otherwise, it continues to listen for other SIB messages. To distinguish it from the aforementioned SIB messages, the SIB messages here can be referred to as the second SIB messages.

[0193] This application embodiment introduces second indication information into the first response message, enabling the terminal to promptly obtain the response results and reasons from satellite network elements to attach or TAU requests after acquiring the satellite identifier listening list. This avoids communication errors and improves the accuracy of communication services. Optionally, a second timer is introduced into the first response message, allowing the terminal to attempt network attach during the second timer's duration, avoiding prolonged waiting times and improving response efficiency. Furthermore, if attachment is still unsuccessful after the second timer expires, the terminal then sends attach or TAU requests to other satellites in the satellite identifier listening list, preventing communication failures and ensuring the availability of terminal communication services.

[0194] In another optional embodiment, if the first response message is a rejection message (i.e., an attachment rejection message or a TAU rejection message), and if the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previous unfinished attachment or TAU process, the first response message may also include third indication information, which is used to indicate that the current satellite cannot immediately complete the attachment or TAU process.

[0195] Optionally, the first response message may also include a third timer, which indicates the waiting time required for the current or next satellite to re-execute or continue the attachment or TAU process; the satellite identifier of the current or next satellite is present in the satellite identifier listening list.

[0196] If the third timer is not included in the first response message, the terminal can directly resend the attach or TAU request to the current satellite or the next satellite. The communicating satellite can be the current satellite or the next satellite, and the satellite identifier of the corresponding satellite must be present in the satellite identifier listening list.

[0197] If the first response message includes a third timer, the terminal starts the third timer. After the third timer expires, and the terminal has not successfully attached to another PLMN network or a satellite network element within the same PLMN network in non-store-and-forward mode, it resends an attach or TAU request to the current satellite or the next satellite. Here, "other PLMN networks" refers to PLMN networks different from the terminal's previous attach or TAU; "same PLMN network" refers to the PLMN network where the terminal last attached or TAUed; and the satellite identifier of the current or next satellite is present in the satellite identifier listening list. The advantage of this approach is that by introducing the third timer, terminal power consumption can be saved, and signaling interaction between the terminal and the network can be reduced.

[0198] It is worth noting that before the third timer expires, the terminal will not attempt to initiate an attach or TAU request to the same PLMN network in store-and-forward mode; alternatively, the terminal may attempt to attach to other PLMN networks or to the same PLMN network in non-store-and-forward mode. Here, "other PLMN networks" refers to PLMN networks different from the terminal's last attach or TAU; "same PLMN network" refers to the PLMN network where the terminal last attached or TAUed.

[0199] In one alternative embodiment, if the terminal attaches to another PLMN network or the same PLMN network in non-store-forward mode before the third timer expires, the timing of the third timer is stopped. Accordingly, the terminal communicates normally with the successfully attached network.

[0200] In another specific implementation, before the third timer expires, if a paging message is received from the satellite's network element, it is determined whether the satellite identifier exists in the satellite identifier listening list. If it exists, and the PLMN information in the corresponding SIB message is consistent with the PLMN information at the time of the last attachment or TAU, an RRC (Radio Resource Control) connection is established with the satellite's network element, and the unfinished attachment or TAU process is re-executed or continued according to the saved context information of the attachment or TAU process.

[0201] In another optional embodiment, after the third timer expires and the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal can also listen to the third SIB message; wherein the third SIB message includes the satellite identifier of the third satellite; the satellite identifier of the third satellite exists in the satellite identifier listening list; and resend attach or TAU requests to the satellite network element of the third satellite.

[0202] For example, after the third timer expires, if the terminal fails to attach to another PLMN network or a network of the same PLMN in non-store-and-forward mode, it listens for SIB messages; it determines whether the satellite identification information in the listened SIB message, i.e., the satellite identification of the third satellite, exists in the satellite representation listening list; if so, it attempts to resend or continue to send attach or TAU request messages to the satellite network element of the third satellite; otherwise, it continues to listen for other SIB messages. To distinguish it from the aforementioned SIB messages, the SIB messages here can be referred to as the third SIB messages.

[0203] It is worth noting that if the first response message includes a third timer, and the on-board MME is paired with a ground-based MME, the on-board MME cannot authenticate with the terminal. Therefore, before the third timer expires, the on-board MME will send a satellite identifier listening list to the ground-based MME. This allows the ground-based MME to authenticate with the terminal using the satellite that can reach the terminal in the shortest time from the satellite in the listening list. The advantage of this setup is that it facilitates authentication with the terminal, laying the foundation for smooth communication between the terminal and the network side afterwards.

[0204] This application embodiment introduces third indication information into the first response message, enabling the terminal to promptly obtain the response results and reasons from the satellite network element to the attach or TAU request after acquiring the satellite identifier listening list. This avoids communication errors and improves the accuracy of the communication service. Optionally, a third timer is introduced into the first response message, allowing the terminal to attempt network attach during the timer's duration, avoiding long waiting times and improving response efficiency. Furthermore, if attaching is still unsuccessful after the third timer expires, the terminal then sends an attach or TAU request to the current or next satellite, preventing communication failures and ensuring the availability of the terminal's communication service.

[0205] Based on the technical solutions of the above embodiments, further, after the terminal completes the attach or TAU process, it sends an attach or TAU completion message to the attached satellite network element; wherein, the attach or TAU completion message includes fifth indication information; the fifth indication information is used to instruct the terminal to transmit data based on the satellite identifier listening list. Optionally, the attach or TAU completion message can be a NAS message. It is understood that by sending an attach or TAU completion message including the fifth indication information to the attached satellite network element, the terminal facilitates the network side to promptly obtain information about the terminal's attachment status.

[0206] The communication process of this application has been described in detail above, with the onboard MME as the executing entity. It is worth noting that when the satellite network element does not include an onboard HSS, and the MME function is separated between the satellite network element and the ground network element—that is, when the MME includes both onboard and ground MMEs—the ground MME needs to participate in the terminal authentication process and provide differentiated responses to different authentication scenarios. Therefore, the communication process in the above situation will be described in detail below, with the ground MME as the executing entity.

[0207] See Figure 5 The communication method shown is applied to the ground MME corresponding to the onboard MME, including:

[0208] S510, during the attach or TAU process, a first response message is received; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previous unfinished attach or TAU process.

[0209] The onboard base station sends (e.g., broadcasts) an SIB message; upon receiving the SIB message, the terminal sends an attach or TAU request to the onboard MME corresponding to the onboard base station; the onboard MME generates a first response message for the attach or TAU request; the onboard MME sends the first response message to the terminal and forwards the first response message to the ground MME. The first response message includes a satellite identifier listening list for the terminal to re-execute or continue any previously incomplete attach or TAU procedures.

[0210] For example, when the feed link of the satellite to which it belongs is available, the onboard MME forwards the first response message to the ground MME.

[0211] In an alternative embodiment, the attach or TAU request and / or first response message may be a NAS message.

[0212] Since the first response message representing a rejection of attach or a TAU request may have different scenarios, such as not being able to respond immediately or not supporting a response, indication information can be introduced into the first response message to avoid terminal confusion.

[0213] In an optional embodiment, if the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previous unfinished attachment or TAU process, the first response message may also include third indication information, which indicates that the current satellite cannot immediately complete the attachment or TAU process.

[0214] Optionally, the first response message may also include a third timer, which indicates the waiting time required for the current or next satellite to re-execute or continue the attachment or TAU process; the satellite identifier of the current or next satellite is present in the satellite identifier listening list.

[0215] If the third timer is not included in the first response message, the terminal can directly resend the attach or TAU request to the current satellite or the next satellite. The communicating satellite can be the current satellite or the next satellite, and the satellite identifier of the corresponding satellite must be present in the satellite identifier listening list.

[0216] If the first response message includes a third timer, the terminal starts the third timer. After the third timer expires, and the terminal has not successfully attached to another PLMN network or a satellite network element within the same PLMN network in non-store-and-forward mode, it resends an attach or TAU request to the current satellite or the next satellite. Here, "other PLMN networks" refers to PLMN networks different from the terminal's previous attach or TAU; "same PLMN network" refers to the PLMN network where the terminal last attached or TAUed; and the satellite identifier of the current or next satellite is present in the satellite identifier listening list. The advantage of this approach is that by introducing the third timer, terminal power consumption can be saved, and signaling interaction between the terminal and the network can be reduced.

[0217] It is worth noting that before the third timer expires, the terminal will not attempt to initiate an attach or TAU request to the same PLMN network in store-and-forward mode; alternatively, the terminal may attempt to attach to other PLMN networks or to the same PLMN network in non-store-and-forward mode. Here, "other PLMN networks" refers to PLMN networks different from the terminal's last attach or TAU; "same PLMN network" refers to the PLMN network where the terminal last attached or TAUed.

[0218] In one alternative embodiment, if the terminal attaches to another PLMN network or the same PLMN network in non-store-forward mode before the third timer expires, the timing of the third timer is stopped. Accordingly, the terminal communicates normally with the successfully attached network.

[0219] In another specific implementation, before the third timer expires, if a paging message is received from the satellite's network element, it is determined whether the satellite identifier exists in the satellite identifier listening list. If it exists, and the PLMN information in the corresponding SIB message is consistent with the PLMN information at the time of the last attachment or TAU, an RRC (Radio Resource Control) connection is established with the satellite's network element, and the unfinished attachment or TAU process is re-executed or continued according to the saved context information of the attachment or TAU process.

[0220] In another optional embodiment, after the third timer expires and the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal can also listen to the third SIB message; wherein the third SIB message includes the satellite identifier of the third satellite; the satellite identifier of the third satellite exists in the satellite identifier listening list; and resend attach or TAU requests to the satellite network element of the third satellite.

[0221] For example, after the third timer expires, if the terminal fails to attach to another PLMN network or a network of the same PLMN in non-store-and-forward mode, it listens for SIB messages; it determines whether the satellite identification information in the listened SIB message, i.e., the satellite identification of the third satellite, exists in the satellite representation listening list; if so, it attempts to resend or continue to send attach or TAU request messages to the satellite network element of the third satellite; otherwise, it continues to listen for other SIB messages. To distinguish it from the aforementioned SIB messages, the SIB messages here can be referred to as the third SIB messages.

[0222] Understandably, the above scheme, by introducing third indication information into the first response message, facilitates the terminal's timely understanding of the satellite network element's response and reason for the attach or TAU request after obtaining the satellite identifier listening list, thus avoiding communication errors and improving the accuracy of the communication service. Optionally, introducing a third timer into the first response message allows the terminal to attempt network attach during the timer's duration, avoiding prolonged waiting time and improving response efficiency. Furthermore, if attaching is still unsuccessful after the third timer expires, an attach or TAU request is sent to the current or next satellite, preventing communication failures and ensuring the availability of the terminal's communication service.

[0223] The S520 uses the satellite identifier to listen for the fourth satellite in the list that can reach the terminal in the shortest time, and then authenticates with the terminal to obtain an authentication response message.

[0224] For example, the ground-based MME can determine the satellite identifier that can reach the terminal in the shortest time based on the terminal's location. If the satellite identifier exists in the satellite identifier listening list, then the satellite is used as the fourth satellite. The terminal is then authenticated through the fourth satellite to obtain an authentication response message.

[0225] In an optional embodiment, the ground MME can send an authentication vector request to the ground HSS; wherein the authentication vector request includes the request time for an attachment or TAU request; receive the authentication vector sent by the ground HSS if it has not received a location update request from another MME before the request time; authenticate with the terminal by using the fourth satellite in the satellite identifier listening list that is the shortest reachable from the terminal and the authentication vector, and obtain an authentication response message.

[0226] Specifically, the ground MME sends an authentication vector request to the ground HSS, including the request time corresponding to the attach or TAU request; the ground HSS checks whether any other MME has sent a terminal location update request message before the request time of the attach or TAU request; if not, it returns the authentication vector to the ground MME.

[0227] Understandably, by introducing the request time for attach or TAU requests, the return of incorrect authentication vectors is avoided when the terminal location is updated, thus ensuring the accuracy of the returned authentication vectors. This is solely to help improve the accuracy of authentication response messages with the terminal.

[0228] For example, when the satellite feed link of the fourth satellite is available, the ground MME sends a terminal location and / or authentication request message to the fourth satellite; when the fourth satellite determines that the terminal is reachable and the service link is available based on the terminal location, the onboard MME of the fourth satellite sends an authentication request message to the terminal; the terminal sends an authentication response message to the onboard MME of the fourth satellite; when the satellite feed link of the fourth satellite is available, the onboard MME of the fourth satellite forwards the authentication response message to the ground MME.

[0229] In this embodiment, when the ground-based MME receives a first response message corresponding to an attach or TAU request, it determines the fourth satellite that can reach the terminal in the shortest time based on the satellite identifier listening list carried in the first response message, which indicates whether the terminal is re-executing or continuing an incomplete previous attach or TAU process. Then, it authenticates with the terminal through this fourth satellite, obtaining an authentication response message, thereby ensuring the security of providing network services to the terminal. Furthermore, the above authentication process, based on the satellite identifier listening list, schedules authentication tasks on satellites, achieving load balancing for store-and-forward services on different satellites. Simultaneously, authenticating with the terminal using the fourth satellite in the satellite identifier listening list that can reach the terminal in the shortest time saves terminal energy consumption and reduces signaling interaction between the terminal and the network.

[0230] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment, in which the processing procedure of the authentication response message between the ground MME and the terminal is added.

[0231] See Figure 6 The communication method shown includes:

[0232] S610, generate the authentication response verification result based on the expected authentication response value carried in the authentication response message.

[0233] The expected authentication response value can be a value that is saved during the process of the ground MME obtaining the authentication vector from the ground HSS and generating the authentication request message based on the authentication vector. This value can serve as the basis for verifying the authentication response message.

[0234] Optionally, if the authentication response value in the authentication response message is the same as the expected authentication response value, that is, if the authentication response message carries the expected authentication response value, then an authentication response verification result indicating successful authentication response verification is generated.

[0235] Alternatively, if the authentication response value in the authentication response message is different from the expected authentication response value, that is, the authentication response message does not carry the expected authentication response value, then an authentication response verification result indicating authentication response verification failure is generated.

[0236] S620, based on the satellite identification listening list, determines the fifth satellite that can reach the terminal in the shortest time.

[0237] For example, the ground-based MME determines the satellite identifier that can reach the terminal in the shortest time based on the terminal's location; if the satellite identifier exists in the satellite identifier listening list of the first information, then the satellite is used as the fifth satellite for subsequent transmission of the second response message to the terminal.

[0238] S630, based on the authentication response verification result, generate a second response message; the second response message includes second information; the second information includes the first satellite identifier listening list.

[0239] S640 sends a second response message to the terminal via the onboard MME of the fifth satellite.

[0240] It is worth noting that the function of the first satellite identifier listening list included in the second information is the same as or similar to the function of the satellite identifier listening list included in the first information. For ease of distinction, the satellite identifier listening list included in the second information of the second response message is referred to here as the first satellite identifier listening list.

[0241] For example, when the satellite feed link of the fifth satellite is available, the ground MME generates a first satellite identifier listening list; and sends a second response message including the first satellite identifier listening list to the onboard MME of the fifth satellite.

[0242] Optionally, the ground-based MME can directly obtain the default configured first satellite identifier listening list; or, it can generate the first satellite identifier listening list based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0243] Since the second response messages, which represent different meanings, have different functions in carrying the first satellite identifier listening list, and the corresponding communication processing methods also differ, in order to avoid terminal confusion, the second response message can also carry corresponding indication information.

[0244] In an optional embodiment, if the authentication response is successfully verified, a second response message is generated; wherein, the second response message is an acceptance message for the attach or TAU request, that is, an attach acceptance message or a TAU acceptance message; the second response message includes a first satellite identifier listening list for terminal data transmission, TAU, or detach process.

[0245] Optionally, the second response message may also include a fourth timer for indicating the waiting time required for terminal data transmission, TAU, or detach process.

[0246] For example, when the satellite feed link of the fifth satellite is available, the ground MME sends the second response message to the onboard MME of the fifth satellite; the onboard MME of the fifth satellite forwards the second response message obtained from the ground MME to the terminal.

[0247] If the second response message does not include the fourth timer, the terminal directly establishes a communication connection with a satellite in the first satellite identifier listening list and performs data transmission, TAU, or de-attachment procedures. The satellite with which the communication connection is established can be the current satellite or the next satellite, and the corresponding satellite's identifier must exist in the first satellite identifier listening list.

[0248] If the second response message includes a fourth timer, the terminal starts the fourth timer; after the fourth timer expires, it establishes a communication connection with the satellite in the first satellite identifier listening list and performs data transmission, TAU, or deattachment procedures.

[0249] In one optional embodiment, before the fourth timer expires, the ground MME synchronizes data with other devices. The synchronized data includes at least one of the following: terminal context information, terminal location, and a first satellite identifier listening list. The other devices may include at least one of the following: a ground proxy function network element and onboard MMEs of satellites in the first satellite identifier listening list. Accordingly, the ground proxy function network element can save the synchronized data for later use.

[0250] It is worth noting that during the fourth timer period, data synchronization can be performed with satellites in the first satellite identifier listening list, laying the foundation for these satellites to provide network services to the terminal.

[0251] For example, the terminal does not actively trigger data transmission, TAU, or detachment procedures before the fourth timer expires. Further, after the fourth timer expires, the terminal can actively trigger data transmission, TAU, or detachment procedures.

[0252] In an optional embodiment, after the fourth timer expires, the terminal can listen to the fourth SIB message; wherein the fourth SIB message includes the satellite identifier of the sixth satellite; the satellite identifier of the sixth satellite exists in the first satellite identifier listening list; and establish a communication connection with the satellite network element of the sixth satellite.

[0253] For example, after the fourth timer expires, the terminal starts listening for SIB messages; it determines whether the satellite identifier information in the listened SIB message, i.e., the satellite identifier of the sixth satellite, exists in the first satellite identifier listening list; if so, it actively triggers a network connection to the satellite's network element and performs data transmission, TAU, or detach process. To distinguish it from the aforementioned SIB messages, this SIB message can be called the fourth SIB message.

[0254] In an optional embodiment, if the authentication response verification fails, a second response message is generated; wherein, the second response message is an attachment or TAU request rejection message, that is, an attachment rejection message or a TAU rejection message; the second response message includes a first satellite identifier listening list for reattaching after the terminal fails to attach, or re-TAU after the TAU fails.

[0255] Optionally, the second response message may also include a fourth indication message to indicate that the current satellite does not support terminal attachment or TAU at this moment.

[0256] Alternatively, the second response message may also include a fifth timer; the fifth timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0257] For example, the ground-based MME sends at least one of the following to the onboard MME of the fifth satellite: a second response message and the terminal's location. When the fifth satellite determines that the terminal is reachable and the service link is available based on the terminal's location, the onboard MME of the fifth satellite forwards the second response message obtained from the ground-based MME to the terminal.

[0258] If the fifth timer is not included in the second response message, the terminal can directly resend or continue sending attach or TAU requests to satellites in the first satellite identifier listening list. The communicating satellite can be the current satellite or the next satellite, and the corresponding satellite's identifier must exist in the first satellite identifier listening list.

[0259] If the second response message includes a fifth timer, the terminal starts the fifth timer. After the fifth timer expires, and if the terminal has not successfully attached to another PLMN network or a satellite network element within the same PLMN network in non-store-and-forward mode, it resends an attach or TAU request to the current satellite or the next satellite. Here, "other PLMN networks" refers to PLMN networks different from the terminal's previous attach or TAU; "same PLMN network" refers to the PLMN network where the terminal last attached or TAUed; and the satellite identifier of the current or next satellite is present in the first satellite identifier listening list. The advantage of this approach is that by introducing the fifth timer, terminal power consumption can be saved, and signaling interaction between the terminal and the network can be reduced.

[0260] It is worth noting that before the fifth timer expires, the terminal will not attempt to initiate an attach or TAU request to the same PLMN network in store-and-forward mode; alternatively, the terminal may attempt to attach to other PLMN networks or to the same PLMN network in non-store-and-forward mode. Here, "other PLMN networks" refers to PLMN networks different from the terminal's last attach or TAU; "same PLMN network" refers to the PLMN network the terminal last attached or TAUed to.

[0261] In an optional embodiment, if the terminal attaches to another PLMN network or the same PLMN network in non-store-forward mode before the fifth timer expires, the timing of the second timer is stopped. Accordingly, the terminal communicates normally with the successfully attached network.

[0262] In another optional embodiment, after the fifth timer expires and the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal may listen to the fifth SIB message; wherein the fifth SIB message includes the satellite identifier of the seventh satellite; the satellite identifier of the seventh satellite exists in the satellite identifier listening list; and resend attach or TAU requests to the satellite network element of the seventh satellite.

[0263] In another specific implementation, after the fifth timer expires, if the terminal fails to attach to another PLMN network or a network of the same PLMN in non-store-and-forward mode, it listens for SIB messages; it determines whether the satellite identifier information in the listened SIB message, i.e., the satellite identifier of the seventh satellite, exists in the first satellite identifier listening list; if so, it attempts to resend or continue to send attach or TAU request messages to the network element of the seventh satellite; otherwise, it continues to listen for other SIB messages. To distinguish it from the aforementioned SIB messages, the SIB message here can be called the fifth SIB message.

[0264] The above technical solution introduces a fourth indication information into the second response message, enabling the terminal to promptly obtain the response results and reasons of other satellite network elements to attach or TAU requests after acquiring the first satellite identifier listening list. This avoids communication errors and improves the accuracy of communication services. Optionally, a fifth timer is introduced into the second response message, allowing the terminal to attempt network attachment during the fifth timer's duration, avoiding long waiting times and improving response efficiency. Furthermore, if attachment is still unsuccessful after the fifth timer expires, attach or TAU requests are sent to other satellites in the first satellite identifier listening list, preventing communication failures and ensuring the availability of terminal communication services.

[0265] Based on the above technical solutions, furthermore, after the terminal completes the attach or TAU process, it sends an attach or TAU completion message to the attached satellite network element; wherein the attach or TAU completion message includes fifth indication information; the fifth indication information is used to instruct the terminal to transmit data based on the first satellite identifier listening list. Optionally, the attach or TAU completion message can be a NAS message. It is understood that by sending an attach or TAU completion message including the fourth indication information to the attached satellite network element, the terminal facilitates the network side to promptly obtain information about the terminal's attach status.

[0266] This application embodiment authenticates the authentication response message by introducing an expected authentication response value, obtaining different authentication response verification results. Based on the differences in the authentication response verification results, a first satellite identifier listening list in the second response information is generated, enabling the terminal to perform communication processing based on the first satellite identifier listening list. This allows for load balancing among different satellites when the terminal accesses the network in a multi-satellite scenario, thereby improving the response efficiency of terminal requests.

[0267] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment, in which the interaction process between the terminal and the network side including at least the on-board MME and the on-board HSS is described in detail.

[0268] See Figure 7 The communication method shown includes:

[0269] S701, when the service link is available, the terminal receives SIB messages sent by the on-board base station;

[0270] S702, the terminal sends an attach or TAU request message to the onboard MME;

[0271] S703, when the power supply link is unavailable and the service link is available, the onboard MME obtains the terminal's authentication vector from the onboard HSS;

[0272] S704, the onboard MME authenticates with the terminal and obtains the authentication result;

[0273] S705, if authentication fails, the onboard MME generates a satellite identification listening list;

[0274] The satellite identifier monitoring list includes satellite identifiers that support terminal attachment failure or TAU failure followed by TAU.

[0275] The satellite identifier listening list can be pre-configured by default, or based on at least one of the following: terminal location, ephemeris information, and subscription data.

[0276] S706, the onboard MME sends an attach or TAU rejection message to the terminal; the attach or TAU rejection message includes the satellite identifier listening list, indication information and timer;

[0277] The indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; the timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0278] S707: The terminal starts a timer and, after the timer expires, re-executes the attach or TAU process based on the satellite identifier listening list.

[0279] For example, during the timer's execution period, the terminal may attempt to attach to another PLMN's network or a network of the same PLMN in non-store-forward mode. If the attachment is successful, the second timer stops, and the terminal communicates normally with the successfully attached network. After the timer expires, if the terminal has not attached to another PLMN's network or a network of the same PLMN in non-store-forward mode, it listens for SIB messages to determine if the satellite identifier in the SIB message exists in the satellite identifier listening list. If it does, it resends the attach or TAU request message; otherwise, it continues to listen for other SIB messages.

[0280] S708, if authentication is successful, the onboard MME sends a location update request to the onboard HSS;

[0281] S709, the on-board MME receives the location update confirmation message generated by the on-board HSS; the location update confirmation message carries the terminal's subscription data;

[0282] S710, the onboard MME generates a satellite identification listening list;

[0283] The satellite identifier monitoring list includes satellite identifiers of satellites that support terminal data transmission, TAU, or detachment processes.

[0284] The satellite identification listening list can be pre-configured by default, or calculated based on at least one of the terminal location, ephemeris information, and subscription data.

[0285] S711, the onboard MME sends an attach or TAU accept message to the terminal; the attach or TAU accept message includes the satellite identifier listening list and timer;

[0286] S712: The terminal starts a timer, and after the timer expires, it establishes a communication connection with the satellites in the satellite identifier listening list according to the satellite identifier listening list, and performs data transmission, TAU, or de-attachment process.

[0287] For example, before the timer expires, the terminal does not actively trigger data transmission, TAU, or detach process; after the timer expires, the terminal actively triggers data transmission TAU or detach process.

[0288] For example, when the terminal is transmitting data, performing TAU, or detaching, it starts listening for SIB messages and determines whether the satellite ID in the SIB message belongs to the satellite identifier listening list information. If so, it actively triggers the connection to the network and executes the data transmission, TAU, or detaching process; otherwise, it continues to listen for SIB messages.

[0289] The S713 synchronizes data with other devices while the timer is still active and the power supply link is available.

[0290] Other devices may include at least one of the following: a ground proxy network element and an onboard MME corresponding to a satellite in the satellite identifier listening list. The synchronized data may include at least one of the following: a satellite identifier listening list, terminal location, and terminal context information.

[0291] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment, in which the interaction process between the terminal and the MME is separated and the HSS is set on the ground network side is described in detail.

[0292] See Figure 8 The communication method shown includes:

[0293] S801, when the service link is available, the terminal receives the SIB message broadcast by the satellite base station;

[0294] S802, the terminal sends an attach or TAU request message to the onboard MME;

[0295] S803, the onboard MME generates a satellite identification listening list;

[0296] The satellite identifier listening list includes satellite identifiers of satellites that support the terminal in re-executing or continuing an incomplete previous attachment or TAU process.

[0297] S804, the onboard MME sends an attach rejection message to the terminal; the attach rejection message includes the satellite identifier listening list, indication information and timer.

[0298] The indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the timer is used to indicate the waiting time required for the current satellite or the next satellite to re-execute or continue the attachment or TAU process.

[0299] S805, the terminal starts a timer, and after the timer expires, it restarts or continues the previously unfinished attach or TAU request process according to the satellite identifier listening list.

[0300] S806, when the onboard MME is available, it forwards attach or TAU requests to the ground MME;

[0301] S807, the ground MME obtains the terminal's authentication vector from the ground HSS;

[0302] S808, the ground MEM determines the first satellite in the satellite identifier monitoring list that can reach the terminal in the shortest time;

[0303] S809, when the feed link of the first satellite is available, the ground MME sends an authentication request and terminal location to the satellite MME of the first satellite;

[0304] S810, the onboard MME of the first satellite authenticates with the terminal when the service link is available;

[0305] S811, the onboard MME of the first satellite stores the authentication response message;

[0306] S812, when the onboard MME of the first satellite is available, it sends an authentication response message to the ground MME;

[0307] S813, the ground MME verifies the authentication response message based on whether the expected authentication response value exists in the authentication response message;

[0308] S814, the ground-based MME identifies the second satellite in the satellite identification listening list that can reach the terminal in the shortest time;

[0309] S815, if verification fails, the ground MME will regenerate the satellite identifier listening list;

[0310] The satellite identifier monitoring list includes satellite identifiers that support reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0311] S816, when the satellite feed link of the second satellite is available, the ground MME sends an attach or TAU rejection message to the onboard MME of the second satellite; the attach or TAU rejection message includes a satellite identification listening list, indication information and a timer; continue to execute S823;

[0312] The indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; the timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0313] For details on the use of the timer, please refer to the relevant description of the fifth timer mentioned above, which will not be repeated here. S817, if the verification is successful, the ground MME sends a position update request to the ground HSS;

[0314] S818, the ground HSS sends a location update confirmation message to the ground MME; the location update confirmation message carries the terminal's subscription data;

[0315] S819, the ground-based MME regenerates the satellite identification listening list;

[0316] S820, the ground-based MME identifies the second satellite in the satellite identification listening list that can reach the terminal in the shortest time;

[0317] S821, when the satellite feed link of the second satellite is available, the ground MME sends an attach or TAU accept message to the onboard MME of the second satellite; the attach or TAU reject message includes the satellite identification listening list and timer.

[0318] The satellite identifier monitoring category includes satellite identifiers of satellites that support terminal data transmission, TAU, or detachment processes. A timer is used to indicate the waiting time required for terminal data transmission, TAU, or detachment processes. For details on the use of the timer, please refer to the aforementioned description of the fourth timer; it will not be repeated here.

[0319] S822, Ground MME synchronizes data with other equipment; Continue execution of S823;

[0320] S823, when the service link of the second satellite is available, the onboard MME forwards an attach or TAU rejection message to the terminal, or an attach or TAU acceptance message.

[0321] This application embodiment enables load balancing of different satellite store-and-forward services in multi-satellite scenarios while meeting terminal service requirements. Furthermore, the terminal performs attach or TAU, data transmission, detach, and reattach or TAU based on satellite ID monitoring list information and indication information, saving terminal power consumption and reducing signaling interaction between the terminal and the network.

[0322] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0323] Based on the same inventive concept, this application also provides a communication device for implementing the communication method described above. The solution provided by this device is similar to the solution described in the above method; therefore, specific limitations in one or more communication device embodiments provided below can be found in the limitations of the communication method described above, and will not be repeated here.

[0324] In one embodiment, such as Figure 9 As shown, a communication device is provided, configured in a terminal, including: a first receiving module 910 and a first processing module 920. Wherein,

[0325] The first receiving module 910 is used to receive a first response message sent by the satellite network element during the attach or TAU process; wherein the first response message includes first information; the first information includes a satellite identifier listening list;

[0326] The first processing module 920 is used to perform communication processing based on the satellite identifier listening list.

[0327] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0328] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0329] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0330] In one embodiment, the first processing module 920 includes: a first startup unit for starting the first timer; and a first processing unit for establishing a communication connection with satellites in the satellite identifier monitoring list after the first timer expires, and performing data transmission, TAU, or de-attachment processes.

[0331] In one embodiment, when the first processing unit establishes a communication connection with a satellite in the satellite identifier listening list, it is specifically configured to: listen to a first system information block (SIB) message; wherein the first SIB message includes the satellite identifier of the first satellite; the satellite identifier of the first satellite exists in the satellite identifier listening list; and establish a communication connection with the satellite network element of the first satellite.

[0332] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0333] In one embodiment, the attach or TAU request includes first indication information, which allows the satellite network element to generate the first response message based on the first indication information; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0334] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0335] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0336] In one embodiment, if the first response message includes the second timer, then the first processing module 920 includes: a second startup unit for starting the second timer; and a second processing unit for re-sending or continuing to send attach or TAU requests to satellites in the satellite identifier listening list after the second timer expires and the terminal has not successfully attached to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode; wherein, the other PLMN network is a PLMN network different from the terminal's last attach or TAU; and the same PLMN network is the PLMN network of the terminal's last attach or TAU.

[0337] In one embodiment, the second processing unit is further configured to: stop the timing of the second timer if the terminal attaches to another public land mobile network (PLMN) or the same PLMN network in non-store-and-forward mode before the second timer expires.

[0338] In one embodiment, when the second processing unit re-sends the attach or TAU request to the satellite in the satellite identifier listening list, it is specifically configured to: listen to a second SIB message; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier listening list; and re-send the attach or TAU request to the satellite network element of the second satellite.

[0339] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0340] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the current satellite or the next satellite to re-execute or continue the attachment or TAU process; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0341] In one embodiment, if the first response message includes the third timer, then the first processing module 920 includes: a third startup unit for starting the third timer; and a third processing unit for re-sending an attach or TAU request to the current satellite or the next satellite after the third timer expires and the terminal has not successfully attached to another PLMN network or a satellite network element of the same PLMN network in non-store-and-forward mode; wherein, the other PLMN network is a PLMN network different from the terminal's last attach or TAU; and the same PLMN network is the PLMN network of the terminal's last attach or TAU.

[0342] In one embodiment, the third processing unit is further configured to: stop the timing of the third timer if the terminal attaches to another PLMN network or the same PLMN network in non-store-and-forward mode before the third timer expires.

[0343] In one embodiment, when the third processing unit performs the retransmission or continued transmission of the attach or TAU request to the current satellite or the next satellite, it is specifically configured to: listen to a third SIB message; wherein the third SIB message includes the satellite identifier of the third satellite; the satellite identifier of the third satellite exists in the satellite identifier listening list; and retransmit or continue to transmit the attach or TAU request to the satellite network element of the third satellite.

[0344] In another embodiment, such as Figure 10 As shown, a communication device is provided, configured on an onboard MME, including: a first transmitting module 1010. Wherein,

[0345] The first sending module 1010 is used to send a first response message to the terminal during the attach or TAU process;

[0346] The first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

[0347] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0348] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0349] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0350] In one embodiment, the device further includes a second processing module, specifically configured to synchronize data with other devices before the first timer expires; wherein the synchronized data includes at least one of the following: context information of the terminal, terminal location, and satellite identification monitoring list.

[0351] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0352] In one embodiment, the second processing module is further configured to generate the first response message if the first indication information is not present in the attach or TAU request; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0353] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0354] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the second timer is used to indicate the waiting time required for the reattachment or TAU process.

[0355] In one embodiment, the second processing module is further configured to: generate the first response message if at least one of the following conditions is met during the initial attachment process or TAU process: access to the feeder link connection for authentication and security mode process is unavailable; the onboard home subscriber server (HSS) does not store the terminal's preset authentication vector or preset subscription information.

[0356] In one embodiment, the second processing module is further configured to: generate a satellite identifier listening list with the same PLMN information, so that the terminal can re-execute the initial attachment process or TAU process; wherein the same PLMN information is the PLMN information of the network to which the terminal last attached or TAUed.

[0357] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0358] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the terminal to re-execute the attachment or TAU process for the current satellite or the next satellite; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0359] In one embodiment, if the first response message includes the third timer and the on-board MME corresponds to a ground MME, the second processing module is further configured to send the satellite identifier listening list to the ground MME before the third timer expires, so that the ground MME can reach the terminal's satellite in the shortest time through the satellite identifier listening list and authenticate with the terminal.

[0360] In one embodiment, the first sending module 1010 is specifically configured to: generate a first response message if there is a ground-based MME corresponding to the on-board MME; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process; and send the first response message to the terminal.

[0361] In one embodiment, the first sending module 1010 is specifically used to: if the on-board MME corresponds to an on-board HSS, then authenticate with the terminal, and generate the first response message according to the authentication result; and send the first response message to the terminal.

[0362] In one embodiment, the first sending module 1010, when performing the step of generating the first response message based on the authentication result, is specifically configured to: generate the first response message if authentication is successful; the first response message is an attach accept message or a TAU accept message; the first response message includes a satellite identifier listening list for terminal data transmission, TAU, or deattachment processes; generate the first response message if authentication fails; the first response message is an attach reject message or a TAU reject message; the first response message includes a satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0363] In one embodiment, the second processing module is further configured to obtain a default configured satellite identifier listening list; or, generate the satellite identifier listening list based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0364] In yet another embodiment, such as Figure 11 As shown, a communication device is provided, configured on a ground-based MME corresponding to an onboard MME. The device includes: a second receiving module 1110 and a first authentication module 1120. Wherein,

[0365] The second receiving module 1110 is used to receive a first response message during the attachment or TAU process; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previous unfinished attachment or TAU process;

[0366] The first authentication module 1120 is used to authenticate with the terminal by using the fourth satellite in the satellite identifier monitoring list that can reach the terminal in the shortest time to obtain an authentication response message.

[0367] In one embodiment, the device further includes a third processing module, specifically configured to: generate an authentication response verification result based on the expected authentication response value carried in the authentication response message; determine the fifth satellite that can reach the terminal in the shortest time according to the satellite identifier listening list; generate a second response message based on the authentication response verification result; the second response message includes second information; the second information includes a first satellite identifier listening list; and send the second response message to the terminal through the onboard MME of the fifth satellite; wherein the first satellite identifier listening list is used for communication processing by the terminal.

[0368] In one embodiment, when the third processing module generates a second response message based on the authentication response verification result, it is specifically used to: generate the second response message if the authentication response verification is successful; wherein, the second response message is an attach accept message or a TAU accept message; the second response message includes a first satellite identifier listening list for terminal data transmission, TAU, or detach process.

[0369] In one embodiment, the second response message further includes a fourth timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment.

[0370] In one embodiment, the third processing module is further configured to: synchronize data with other devices before the fourth timer expires; wherein the synchronized data includes at least one of the following: the context information of the terminal, the terminal location, and the first satellite identifier listening list.

[0371] In one embodiment, when the third processing module generates a second response message based on the authentication response verification result, it is specifically used to: generate the second response message if the authentication response verification fails; wherein the second response message is an attach rejection message or a TAU rejection message; the second response message includes a first satellite identifier listening list for reattaching after a terminal attach failure or re-TAU after a TAU failure.

[0372] In one embodiment, the second response message further includes a fourth indication message and / or a fifth timer; wherein the fourth indication message is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the fifth timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0373] In one embodiment, the third processing module is further configured to: obtain a first satellite identifier listening list with a default configuration; or, generate the first satellite identifier listening list based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0374] In one embodiment, the first authentication module 1120 is specifically configured to: send an authentication vector request to the ground HSS; wherein the authentication vector request includes a request time for an attachment or TAU request; receive an authentication vector sent by the ground HSS if it has not received a location update request from another MME before the request time; authenticate with the terminal using the fourth satellite in the satellite identifier listening list that is the shortest reachable from the terminal and the authentication vector, and obtain an authentication response message.

[0375] Each module in the aforementioned communication device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the communication device in hardware form or independent of it, or stored in the memory of the communication device in software form, so that the processor can call and execute the operations corresponding to each module.

[0376] In one embodiment, a communication device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 12 As shown, the communication device includes a processor, memory, network interface, and transceiver connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The transceiver, under the control of the processor, performs operations to receive or send data. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores data such as uplink and downlink SMS messages. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a communication method.

[0377] Those skilled in the art will understand that Figure 12 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the communication device to which the present application is applied. Specific communication devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0378] In one embodiment, a communication device is provided, which can serve as a terminal, including a memory and a processor. The memory stores a computer program, and the processor executes the processing logic in the computer program to perform the following steps:

[0379] During the TAU update process in the attachment or tracking area, a first response message is received from the satellite network element; wherein, the first response message includes first information; the first information includes a satellite identifier listening list;

[0380] Communication processing is performed based on the satellite identifier listening list.

[0381] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0382] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0383] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0384] In one embodiment, the first timer is started; after the first timer expires, a communication connection is established with the satellite in the satellite identifier listening list, and data transmission, TAU, or de-attachment process is performed.

[0385] In one embodiment, a first system information block (SIB) message is monitored; wherein the first SIB message includes a satellite identifier of a first satellite; the satellite identifier of the first satellite exists in the satellite identifier monitoring list; and a communication connection is established with the satellite network element of the first satellite.

[0386] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0387] In one embodiment, the attach or TAU request includes first indication information, which allows the satellite network element to generate the first response message based on the first indication information; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0388] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0389] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; and the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0390] In one embodiment, if the first response message includes the second timer, then the communication processing based on the satellite identifier listening list includes: starting the second timer; after the second timer expires, and if the terminal has not successfully attached to another PLMN network or a satellite network element of the same PLMN network in non-store-and-forward mode, re-sending or continuing to send an attach or TAU request to the satellites in the satellite identifier listening list; wherein, the other PLMN network is a PLMN network different from the terminal's last attach or TAU; and the same PLMN network is the PLMN network from which the terminal last attached or TAUed.

[0391] In one embodiment, if the terminal is attached to another Public Land Mobile Network (PLMN) or the same PLMN in non-store-and-forward mode, the timing of the second timer is stopped.

[0392] In one embodiment, a second SIB message is monitored; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier monitoring list; and the attach or TAU request is resent or continued to be sent to the satellite network element of the second satellite.

[0393] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0394] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the current satellite or the next satellite to re-execute or continue the attachment or TAU process; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0395] In one embodiment, the third timer is started; after the third timer expires, and if the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal re-sends an attach or TAU request to the current satellite or the next satellite; wherein, the other PLMN network is a PLMN network different from the terminal's last attach or TAU; and the same PLMN network is the PLMN network of the terminal's last attach or TAU.

[0396] In one embodiment, if the terminal is attached to another PLMN network or the same PLMN network in non-store-forward mode, the timing of the third timer is stopped.

[0397] In one embodiment, a third SIB message is monitored; wherein the third SIB message includes a satellite identifier of a third satellite; the satellite identifier of the third satellite exists in the satellite identifier monitoring list;

[0398] Resend attach or TAU requests to the satellite network element of the third satellite, or continue to do so.

[0399] In one embodiment, another communication device is provided, which can serve as an on-board MME, including a memory and a processor. The memory stores a computer program, and the processor executes the processing logic in the computer program to perform the following steps:

[0400] During the attach or TAU process, a first response message is sent to the terminal;

[0401] The first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

[0402] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0403] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0404] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0405] In one embodiment, data synchronization is performed with other devices; wherein the synchronized data includes at least one of the following: the terminal's context information, the terminal's location, and the satellite identification listening list.

[0406] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0407] In one embodiment, if the first indication information is not present in the attach or TAU request, the first response message is generated; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0408] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0409] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the second timer is used to indicate the waiting time required for the reattachment or TAU process.

[0410] In one embodiment, the first response message is generated if at least one of the following conditions is met during the initial attach process or TAU process: access to the feeder link connection for authentication and security mode procedures is unavailable; or the onboard home subscriber server (HSS) does not store the terminal's preset authentication vector or preset subscription information.

[0411] In one embodiment, a satellite identifier listening list with the same PLMN information is generated so that the terminal can re-execute the initial attachment process or TAU process; wherein, the same PLMN information is the PLMN information of the network to which the terminal last attached or TAUed.

[0412] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0413] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the terminal to re-execute the attachment or TAU process for the current satellite or the next satellite; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0414] In one embodiment, if the first response message includes the third timer and the on-board MME corresponds to a ground MME, then before the third timer expires, the method further includes: sending the satellite identifier listening list to the ground MME so that the ground MME can reach the terminal's satellite in the shortest time through the satellite identifier listening list and authenticate with the terminal.

[0415] In one embodiment, if the on-board MME corresponds to a ground-based MME, a first response message is generated; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process; the first response message is sent to the terminal.

[0416] In one embodiment, if the on-board MME corresponds to an on-board HSS, then the terminal is authenticated, and the first response message is generated based on the authentication result; the first response message is then sent to the terminal.

[0417] In one embodiment, if authentication is successful, a first response message is generated; the first response message is an attach accept message or a TAU accept message; the first response message includes a satellite identifier listening list for terminal data transmission, TAU, or detach process; if authentication fails, a first response message is generated; the first response message is an attach reject message or a TAU reject message; the first response message includes a satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0418] In one embodiment, a default configured satellite identifier listening list is obtained; or, the satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0419] In one embodiment, a communication device is provided, which can serve as a ground-based MME corresponding to an on-board MME, including a memory and a processor. The memory stores a computer program, and the processor executes the processing logic in the computer program to perform the following steps:

[0420] During the attach or TAU process, a first response message is received; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process;

[0421] The terminal is identified by the fourth satellite in the satellite identifier monitoring list that can reach it in the shortest time, and the terminal is authenticated to obtain an authentication response message.

[0422] In one embodiment, an authentication response verification result is generated based on the expected authentication response value carried in the authentication response message; a fifth satellite that can reach the terminal in the shortest time is determined based on the satellite identifier listening list; a second response message is generated based on the authentication response verification result; the second response message includes second information; the second information includes a first satellite identifier listening list; the second response message is sent to the terminal through the onboard MME of the fifth satellite; wherein, the first satellite identifier listening list is used for communication processing by the terminal.

[0423] In one embodiment, if the authentication response is successfully verified, the second response message is generated; wherein the second response message is an attach accept message or a TAU accept message; the second response message includes a first satellite identifier listening list for terminal data transmission, TAU, or detach process.

[0424] In one embodiment, the second response message further includes a fourth timer for indicating the waiting time required for terminal data transmission, TAU, or detachment process.

[0425] In one embodiment, data synchronization is performed with other devices before the fourth timer expires; wherein the synchronized data includes at least one of the following: the terminal's context information, the terminal's location, and the first satellite identifier listening list.

[0426] In one embodiment, if the authentication response verification fails, a second response message is generated; wherein, the second response message is an attach rejection message or a TAU rejection message; the second response message includes a first satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0427] In one embodiment, the second response message further includes a fourth indication information and / or a fifth timer; wherein the fourth indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; and the fifth timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0428] In one embodiment, a first satellite identifier listening list with a default configuration is obtained; or, the first satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0429] In one embodiment, an authentication vector request is sent to the ground HSS; wherein the authentication vector request includes a request time for an attachment or TAU request; the authentication vector sent by the ground HSS if no other MME has sent a location update request before the request time; and the terminal is authenticated by the fourth satellite that is reachable from the terminal in the shortest time according to the satellite identifier listening list and the authentication vector, and an authentication response message is obtained.

[0430] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0431] During the TAU update process in the attachment or tracking area, a first response message is received from the satellite network element; wherein, the first response message includes first information; the first information includes a satellite identifier listening list;

[0432] Communication processing is performed based on the satellite identifier listening list.

[0433] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0434] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0435] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0436] In one embodiment, the first timer is started; after the first timer expires, a communication connection is established with the satellite in the satellite identifier listening list, and data transmission, TAU, or de-attachment process is performed.

[0437] In one embodiment, a first system information block (SIB) message is monitored; wherein the first SIB message includes a satellite identifier of a first satellite; the satellite identifier of the first satellite exists in the satellite identifier monitoring list; and a communication connection is established with the satellite network element of the first satellite.

[0438] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0439] In one embodiment, the attach or TAU request includes first indication information, which allows the satellite network element to generate the first response message based on the first indication information; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0440] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0441] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; and the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0442] In one embodiment, the second timer is started; after the second timer expires, and if the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal re-sends attach or TAU requests to satellites in the satellite identifier listening list; wherein, the other PLMN network is a PLMN network different from the terminal's last attach or TAU; and the same PLMN network is the PLMN network of the terminal's last attach or TAU.

[0443] In one embodiment, if the terminal is attached to another Public Land Mobile Network (PLMN) or the same PLMN in non-store-and-forward mode, the timing of the second timer is stopped.

[0444] In one embodiment, a second SIB message is monitored; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier monitoring list; and the attach or TAU request is resent or continued to be sent to the satellite network element of the second satellite.

[0445] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0446] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the current satellite or the next satellite to re-execute or continue the attachment or TAU process; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0447] In one embodiment, the third timer is started; after the third timer expires, and if the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, it resends or continues to send attach or TAU requests to the current satellite or the next satellite.

[0448] Wherein, the other PLMN network is a PLMN network different from the terminal's last attachment or TAU; the same PLMN network is the PLMN network of the terminal's last attachment or TAU.

[0449] In one embodiment, if the terminal is attached to another PLMN network or the same PLMN network in non-store-forward mode, the timing of the third timer is stopped.

[0450] In one embodiment, a third SIB message is monitored; wherein the third SIB message includes the satellite identifier of a third satellite; the satellite identifier of the third satellite exists in the satellite identifier monitoring list; and an attach or TAU request is resent or continued to be sent to the satellite network element of the third satellite.

[0451] In one embodiment, another computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, performs the following steps: during an attach or TAU process, sending a first response message to a terminal; wherein the first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used for communication processing by the terminal.

[0452] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0453] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0454] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0455] In one embodiment, data synchronization is performed with other devices; wherein the synchronized data includes at least one of the following: the terminal's context information, the terminal's location, and the satellite identification listening list.

[0456] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0457] In one embodiment, if the first indication information is not present in the attachment or TAU request, the first response message is generated;

[0458] The first indication information is used to indicate that the terminal supports store-and-forward mode.

[0459] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0460] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the second timer is used to indicate the waiting time required for the reattachment or TAU process.

[0461] In one embodiment, the first response message is generated if at least one of the following conditions is met during the initial attach process or TAU process: access to the feeder link connection for authentication and security mode procedures is unavailable; or the onboard home subscriber server (HSS) does not store the terminal's preset authentication vector or preset subscription information.

[0462] In one embodiment, a satellite identifier listening list with the same PLMN information is generated so that the terminal can re-execute the initial attachment process or TAU process; wherein, the same PLMN information is the PLMN information of the network to which the terminal last attached or TAUed.

[0463] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0464] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the terminal to re-execute the attachment or TAU process for the current satellite or the next satellite; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0465] In one embodiment, if the first response message includes the third timer and the on-board MME corresponds to a ground MME, then before the third timer expires, the method further includes: sending the satellite identifier listening list to the ground MME so that the ground MME can reach the terminal's satellite in the shortest time through the satellite identifier listening list and authenticate with the terminal.

[0466] In one embodiment, if the on-board MME corresponds to a ground-based MME, a first response message is generated; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process; the first response message is sent to the terminal.

[0467] In one embodiment, if the on-board MME corresponds to an on-board HSS, then the terminal is authenticated, and the first response message is generated based on the authentication result; the first response message is then sent to the terminal.

[0468] In one embodiment, if authentication is successful, a first response message is generated; the first response message is an attach accept message or a TAU accept message; the first response message includes a satellite identifier listening list for terminal data transmission, TAU, or detach process; if authentication fails, a first response message is generated; the first response message is an attach reject message or a TAU reject message; the first response message includes a satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0469] In one embodiment, a default configured satellite identifier listening list is obtained; or, the satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0470] In one embodiment, another computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0471] During the attach or TAU process, a first response message is received; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process;

[0472] The terminal is identified by the fourth satellite in the satellite identifier monitoring list that can reach it in the shortest time, and the terminal is authenticated to obtain an authentication response message.

[0473] In one embodiment, an authentication response verification result is generated based on the expected authentication response value carried in the authentication response message; a fifth satellite that can reach the terminal in the shortest time is determined based on the satellite identifier listening list; a second response message is generated based on the authentication response verification result; the second response message includes second information; the second information includes a first satellite identifier listening list; the second response message is sent to the terminal through the onboard MME of the fifth satellite; wherein, the first satellite identifier listening list is used for communication processing by the terminal.

[0474] In one embodiment, if the authentication response is successfully verified, the second response message is generated; wherein the second response message is an attach accept message or a TAU accept message; the second response message includes a first satellite identifier listening list for terminal data transmission, TAU, or detach process.

[0475] In one embodiment, the second response message further includes a fourth timer for indicating the waiting time required for terminal data transmission, TAU, or detachment process.

[0476] In one embodiment, data synchronization is performed with other devices before the fourth timer expires; wherein the synchronized data includes at least one of the following: the terminal's context information, the terminal's location, and the first satellite identifier listening list.

[0477] In one embodiment, if the authentication response verification fails, a second response message is generated; wherein, the second response message is an attach rejection message or a TAU rejection message; the second response message includes a first satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0478] In one embodiment, the second response message further includes a fourth indication information and / or a fifth timer; wherein the fourth indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; and the fifth timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0479] In one embodiment, a first satellite identifier listening list with a default configuration is obtained; or, the first satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0480] In one embodiment, an authentication vector request is sent to the ground HSS; wherein the authentication vector request includes a request time for an attachment or TAU request; the authentication vector sent by the ground HSS if no other MME has sent a location update request before the request time; and the terminal is authenticated by the fourth satellite that is reachable from the terminal in the shortest time according to the satellite identifier listening list and the authentication vector, and an authentication response message is obtained.

[0481] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0482] During the TAU update process in the attachment or tracking area, a first response message is received from the satellite network element; wherein, the first response message includes first information; the first information includes a satellite identifier listening list;

[0483] Communication processing is performed based on the satellite identifier listening list.

[0484] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0485] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0486] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0487] In one embodiment, the first timer is started; after the first timer expires, a communication connection is established with the satellite in the satellite identifier listening list, and data transmission, TAU, or de-attachment process is performed.

[0488] In one embodiment, a first system information block (SIB) message is monitored; wherein the first SIB message includes a satellite identifier of a first satellite; the satellite identifier of the first satellite exists in the satellite identifier monitoring list; and a communication connection is established with the satellite network element of the first satellite.

[0489] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0490] In one embodiment, the attach or TAU request includes first indication information, which allows the satellite network element to generate the first response message based on the first indication information; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0491] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0492] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; and the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0493] In one embodiment, the second timer is started; after the second timer expires, and if the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal re-sends attach or TAU requests to satellites in the satellite identifier listening list; wherein, the other PLMN network is a PLMN network different from the terminal's last attach or TAU; and the same PLMN network is the PLMN network of the terminal's last attach or TAU.

[0494] In one embodiment, if the terminal is attached to another Public Land Mobile Network (PLMN) or the same PLMN in non-store-and-forward mode, the timing of the second timer is stopped.

[0495] In one embodiment, a second SIB message is monitored; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier monitoring list; and the attach or TAU request is resent or continued to be sent to the satellite network element of the second satellite.

[0496] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0497] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the current satellite or the next satellite to re-execute or continue the attachment or TAU process; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0498] In one embodiment, the third timer is started; after the third timer expires, and if the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode, the terminal re-sends an attach or TAU request to the current satellite or the next satellite; wherein, the other PLMN network is a PLMN network different from the terminal's last attach or TAU; and the same PLMN network is the PLMN network of the terminal's last attach or TAU.

[0499] In one embodiment, if the terminal is attached to another PLMN network or the same PLMN network in non-store-forward mode, the timing of the third timer is stopped.

[0500] In one embodiment, a third SIB message is monitored; wherein the third SIB message includes the satellite identifier of a third satellite; the satellite identifier of the third satellite exists in the satellite identifier monitoring list; and an attach or TAU request is resent or continued to be sent to the satellite network element of the third satellite.

[0501] In one embodiment, another computer program product is provided, including a computer program that, when executed by a processor, performs the following steps: during attachment or TAU, sending a first response message to a terminal;

[0502] The first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

[0503] In one embodiment, the first response message is an attach accept message or a TAU accept message.

[0504] In one embodiment, the first information includes a satellite identifier listening list for terminal data transmission, TAU, or de-attachment processes.

[0505] In one embodiment, the first response message further includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or deattachment process.

[0506] In one embodiment, data synchronization is performed with other devices; wherein the synchronized data includes at least one of the following: the terminal's context information, the terminal's location, and the satellite identification listening list.

[0507] In one embodiment, the first response message is an attach rejection message or a TAU rejection message.

[0508] In one embodiment, if the first indication information is not present in the attach or TAU request, the first response message is generated; wherein the first indication information is used to indicate that the terminal supports store-and-forward mode.

[0509] In one embodiment, the first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

[0510] In one embodiment, the first response message further includes second indication information and / or a second timer; wherein the second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; and the second timer is used to indicate the waiting time required for the reattachment or TAU process.

[0511] In one embodiment, the first response message is generated if at least one of the following conditions is met during the initial attach process or TAU process: access to the feeder link connection for authentication and security mode procedures is unavailable; or the onboard home subscriber server (HSS) does not store the terminal's preset authentication vector or preset subscription information.

[0512] In one embodiment, a satellite identifier listening list with the same PLMN information is generated so that the terminal can re-execute the initial attachment process or TAU process; wherein, the same PLMN information is the PLMN information of the network to which the terminal last attached or TAUed.

[0513] In one embodiment, the first information includes a satellite identification listening list for the terminal to re-execute or continue a previously incomplete attachment or TAU process.

[0514] In one embodiment, the first response message further includes third indication information and / or a third timer; wherein the third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the terminal to re-execute the attachment or TAU process for the current satellite or the next satellite; and the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

[0515] In one embodiment, the satellite identifier listening list is sent to the ground MME so that the ground MME can authenticate the terminal by using the satellite in the shortest time that can reach the terminal through the satellite identifier listening list.

[0516] In one embodiment, if the on-board MME corresponds to a ground-based MME, a first response message is generated; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process; the first response message is sent to the terminal.

[0517] In one embodiment, if the on-board MME corresponds to an on-board HSS, then the terminal is authenticated, and the first response message is generated based on the authentication result; the first response message is then sent to the terminal.

[0518] In one embodiment, if authentication is successful, a first response message is generated; the first response message is an attach accept message or a TAU accept message; the first response message includes a satellite identifier listening list for terminal data transmission, TAU, or detach process; if authentication fails, a first response message is generated; the first response message is an attach reject message or a TAU reject message; the first response message includes a satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0519] In one embodiment, a default configured satellite identifier listening list is obtained; or, the satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0520] In one embodiment, another computer program product is provided, comprising a computer program that, when executed by a processor, performs the following steps:

[0521] During the attach or TAU process, a first response message is received; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process;

[0522] The terminal is identified by the fourth satellite in the satellite identifier monitoring list that can reach it in the shortest time, and the terminal is authenticated to obtain an authentication response message.

[0523] In one embodiment, an authentication response verification result is generated based on the expected authentication response value carried in the authentication response message; a fifth satellite that can reach the terminal in the shortest time is determined based on the satellite identifier listening list; a second response message is generated based on the authentication response verification result; the second response message includes second information; the second information includes a first satellite identifier listening list; the second response message is sent to the terminal through the onboard MME of the fifth satellite; wherein, the first satellite identifier listening list is used for communication processing by the terminal.

[0524] In one embodiment, if the authentication response is successfully verified, the second response message is generated; wherein the second response message is an attach accept message or a TAU accept message; the second response message includes a first satellite identifier listening list for terminal data transmission, TAU, or detach process.

[0525] In one embodiment, the second response message further includes a fourth timer for indicating the waiting time required for terminal data transmission, TAU, or detachment process.

[0526] In one embodiment, data synchronization is performed with other devices before the fourth timer expires; wherein the synchronized data includes at least one of the following: the terminal's context information, the terminal's location, and the first satellite identifier listening list.

[0527] In one embodiment, if the authentication response verification fails, a second response message is generated; wherein, the second response message is an attach rejection message or a TAU rejection message; the second response message includes a first satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

[0528] In one embodiment, the second response message further includes a fourth indication information and / or a fifth timer; wherein the fourth indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; and the fifth timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

[0529] In one embodiment, a first satellite identifier listening list with a default configuration is obtained; or, the first satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

[0530] In one embodiment, an authentication vector request is sent to the ground HSS; wherein the authentication vector request includes a request time for an attachment or TAU request; the authentication vector sent by the ground HSS if no other MME has sent a location update request before the request time; and the terminal is authenticated by the fourth satellite that is reachable from the terminal in the shortest time according to the satellite identifier listening list and the authentication vector, and an authentication response message is obtained.

[0531] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0532] 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. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0533] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0534] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A communication method, characterized in that, Applied to a terminal, the method includes: During the TAU update process in the attachment or tracking area, a first response message is received from the satellite network element; wherein, the first response message includes first information; the first information includes a satellite identifier listening list; Communication processing is performed based on the satellite identifier listening list.

2. The method according to claim 1, characterized in that, The first response message is an attach accept message or a TAU accept message.

3. The method according to claim 2, characterized in that, The first information includes a satellite identifier listening list used for terminal data transmission, TAU, or de-attachment processes.

4. The method according to claim 3, characterized in that, The first response message also includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or detach process.

5. The method according to claim 4, characterized in that, The communication processing based on the satellite identifier listening list includes: Start the first timer; After the first timer expires, a communication connection is established with the satellite in the satellite identifier monitoring list, and data transmission, TAU, or deattachment process is performed.

6. The method according to claim 5, characterized in that, Establishing a communication connection with satellites in the satellite identifier monitoring list includes: Listen to the first system information block (SIB) message; wherein the first SIB message includes the satellite identifier of the first satellite; the satellite identifier of the first satellite exists in the satellite identifier listening list; Establish a communication connection with the satellite's network element.

7. The method according to claim 1, characterized in that, The first response message is an attach rejection message or a TAU rejection message.

8. The method according to claim 7, characterized in that, The first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

9. The method according to claim 8, characterized in that, The first response message also includes second indication information and / or a second timer; The second indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; the second timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

10. The method according to claim 9, characterized in that, If the first response message includes the second timer, then the communication processing based on the satellite identifier listening list includes: Start the second timer; If the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode after the second timer expires, it shall resend or continue to send attach or TAU requests to the satellites in the satellite identifier listening list. Wherein, the other PLMN network is a PLMN network different from the terminal's last attachment or TAU; the same PLMN network is the PLMN network of the terminal's last attachment or TAU.

11. The method according to claim 10, characterized in that, Before the second timer expires, the method further includes: If the terminal is attached to another Public Land Mobile Network (PLMN) or the same PLMN in non-store-and-forward mode, the timing of the second timer is stopped.

12. The method according to claim 10, characterized in that, The resending or continuing to send attach or TAU requests to satellites in the satellite identifier listening list includes: Listen to the second SIB message; wherein the second SIB message includes the satellite identifier of the second satellite; the satellite identifier of the second satellite exists in the satellite identifier listening list; Resend the attach or TAU request to the satellite network element of the second satellite, or continue to do so.

13. The method according to claim 7, characterized in that, The first information includes a satellite identification listening list for the terminal to re-execute or continue any previously incomplete attachment or TAU procedures.

14. The method according to claim 13, characterized in that, The first response message also includes third indication information and / or a third timer; The third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the current satellite or the next satellite to re-execute or continue the attachment or TAU process; the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

15. The method according to claim 14, characterized in that, If the first response message includes the third timer, then the communication processing based on the satellite identifier listening list includes: Start the third timer; If the terminal fails to attach to other PLMN networks or satellite network elements of the same PLMN network in non-store-and-forward mode after the third timer expires, it shall resend or continue to send attach or TAU requests to the current satellite or the next satellite. Wherein, the other PLMN network is a PLMN network different from the terminal's last attachment or TAU; the same PLMN network is the PLMN network of the terminal's last attachment or TAU.

16. The method according to claim 15, characterized in that, Before the third timer expires, the method further includes: If the terminal attaches to another PLMN network or the same PLMN network in non-store-and-forward mode, the timing of the third timer is stopped.

17. The method according to claim 15, characterized in that, The retransmission or continuation of the attach or TAU request to the current or next satellite includes: Listen to the third SIB message; wherein the third SIB message includes the satellite identifier of the third satellite; the satellite identifier of the third satellite exists in the satellite identifier listening list; Resend attach or TAU requests to the satellite network element of the third satellite, or continue to do so.

18. A communication method, characterized in that, The method, applied to an on-board mobility management entity (MME), includes: During the attach or TAU process, a first response message is sent to the terminal; The first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

19. The method according to claim 18, characterized in that, The first response message is an attach accept message or a TAU accept message.

20. The method according to claim 19, characterized in that, The first information includes a satellite identifier listening list used for terminal data transmission, TAU, or de-attachment processes.

21. The method according to claim 20, characterized in that, The first response message also includes a first timer for indicating the waiting time required for terminal data transmission, TAU, or detach process.

22. The method according to claim 21, characterized in that, Before the first timer expires, the method further includes: Synchronize data with other devices; The synchronized data includes at least one of the following: the context information of the terminal, the terminal location, and the satellite identification monitoring list.

23. The method according to claim 18, characterized in that, The first response message is an attach rejection message or a TAU rejection message.

24. The method according to claim 23, characterized in that, The first information includes a satellite identifier monitoring list for reattaching after a terminal attachment failure or re-TAU after a TAU failure.

25. The method according to claim 24, characterized in that, The first response message also includes second indication information and / or a second timer; The second indication information is used to indicate that the current satellite does not support the terminal's attachment or TAU at this moment; the second timer is used to indicate the waiting time required for the reattachment or TAU process.

26. The method according to claim 24, characterized in that, The method further includes: The first response message is generated if at least one of the following conditions is met during the initial attachment process or the TAU process: Access to the feeder link connection for authentication and secure mode procedures is unavailable; The onboard home subscriber server (HSS) does not store the terminal's preset authentication vector or preset subscription information.

27. The method according to claim 26, characterized in that, The method further includes: Generate a satellite identifier listening list with the same PLMN information so that the terminal can re-execute the initial attachment process or TAU process; The same PLMN information refers to the PLMN information of the network to which the terminal last attached or TAU last used.

28. The method according to claim 23, characterized in that, The first information includes a satellite identification listening list for the terminal to re-execute or continue any previously incomplete attachment or TAU procedures.

29. The method according to claim 28, characterized in that, The first response message also includes third indication information and / or a third timer; The third indication information is used to indicate that the current satellite cannot immediately complete the attachment or TAU process; the third timer is used to indicate the waiting time required for the terminal to re-execute the attachment or TAU process for the current satellite or the next satellite; the satellite identifier of the current satellite or the next satellite exists in the satellite identifier listening list.

30. The method according to claim 29, characterized in that, If the first response message includes the third timer, and the on-board MME corresponds to a ground-based MME, then before the third timer expires, the method further includes: The satellite identifier listening list is sent to the ground MME so that the ground MME can reach the terminal via the satellite in the shortest time through the satellite identifier listening list and authenticate with the terminal.

31. The method according to claim 18, characterized in that, Sending the first response message to the terminal includes: If the on-board MME corresponds to a ground-based MME, a first response message is generated; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process; The first response message is sent to the terminal.

32. The method according to claim 18, characterized in that, Sending the first response message to the terminal includes: If the on-board MME corresponds to the on-board HSS, then it authenticates with the terminal and generates the first response message based on the authentication result; The first response message is sent to the terminal.

33. The method according to claim 32, characterized in that, The step of generating the first response message based on the authentication result includes: If authentication is successful, a first response message is generated; the first response message is an attach accept message or a TAU accept message; the first response message includes a satellite identifier listening list for terminal data transmission, TAU, or detach process; If authentication fails, a first response message is generated; the first response message is an attach rejection message or a TAU rejection message; the first response message includes a satellite identifier monitoring list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

34. The method according to any one of claims 18-33, characterized in that, The method further includes: Retrieve the default configuration list of satellite identifiers to monitor; or, The satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

35. A communication method, characterized in that, The method, applied to a ground-based MME corresponding to an onboard MME, includes: During the attach or TAU process, a first response message is received; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previously incomplete attach or TAU process; The terminal is identified by the fourth satellite in the satellite identifier monitoring list that can reach it in the shortest time, and the terminal is authenticated to obtain an authentication response message.

36. The method according to claim 35, characterized in that, The method further includes: Based on the expected authentication response value carried in the authentication response message, an authentication response verification result is generated; Based on the satellite identifier monitoring list, determine the fifth satellite that can reach the terminal in the shortest time; Based on the authentication response verification result, a second response message is generated; the second response message includes second information; the second information includes a first satellite identifier listening list; The second response message is sent to the terminal via the onboard MME of the fifth satellite; The first satellite identifier listening list is used by the terminal for communication processing.

37. The method according to claim 36, characterized in that, The step of generating a second response message based on the authentication response verification result includes: If the authentication response is successfully verified, the second response message is generated; wherein, the second response message is an attach accept message or a TAU accept message; the second response message includes a first satellite identifier listening list for terminal data transmission, TAU, or detach process.

38. The method according to claim 37, characterized in that, The second response message also includes a fourth timer for indicating the waiting time required for terminal data transmission, TAU, or detach process.

39. The method according to claim 38, characterized in that, The method further includes: Before the fourth timer expires, data synchronization is performed with other devices; The synchronized data includes at least one of the following: the context information of the terminal, the terminal location, and the first satellite identifier listening list.

40. The method according to claim 36, characterized in that, The step of generating a second response message based on the authentication response verification result includes: If the authentication response verification fails, a second response message is generated; wherein, the second response message is an attach rejection message or a TAU rejection message; the second response message includes a first satellite identifier listening list for reattaching after a terminal attach failure, or re-TAU after a TAU failure.

41. The method according to claim 40, characterized in that, The second response message also includes a fourth indication message and / or a fifth timer; The fourth indication information is used to indicate that the current satellite does not support the attachment or TAU of the terminal at this moment; the fifth timer is used to indicate the waiting time required to re-execute or continue the attachment or TAU process.

42. The method according to claim 36, characterized in that, The method further includes: Retrieve the first satellite identifier listening list with the default configuration; or, The first satellite identifier listening list is generated based on at least one of the terminal location, ephemeris information, and the terminal's subscription information on the HSS.

43. The method according to claim 35, characterized in that, The fourth satellite in the satellite identifier monitoring list that can reach the terminal in the shortest time is used to authenticate with the terminal and obtain an authentication response message, including: Send an authentication vector request to the ground HSS; wherein the authentication vector request includes the request time for an attachment or TAU request; Receive the authentication vector sent by the ground HSS if it has not received a location update request from another MME before the requested time; The terminal is authenticated by the fourth satellite in the satellite identifier listening list that can reach the terminal in the shortest time and the authentication vector, and an authentication response message is obtained.

44. A communication device, characterized in that, Configured in a terminal, the device includes: The first receiving module is configured to receive a first response message sent by the satellite network element during the attach or TAU process; wherein the first response message includes first information; the first information includes a satellite identifier listening list; The first processing module is used to perform communication processing based on the satellite identifier listening list.

45. A communication device, characterized in that, Configured on the onboard MME, the device includes: The first sending module is used to send a first response message to the terminal during the attach or TAU process; The first response message includes first information; the first information includes a satellite identifier listening list; the satellite identifier listening list is used by the terminal for communication processing.

46. ​​A communication device, characterized in that, The device, configured on the ground-based MME corresponding to the on-board MME, includes: The second receiving module is used to receive a first response message during the attachment or TAU process; wherein the first response message includes first information; the first information includes a satellite identifier listening list for the terminal to re-execute or continue the previous unfinished attachment or TAU process; The first authentication module is used to authenticate with the terminal by listening to the fourth satellite in the satellite identifier monitoring list that can reach the terminal in the shortest time and obtain an authentication response message.

47. A communication device comprising a memory, a transceiver, and a processor, wherein the memory stores a computer program, characterized in that, The transceiver is used to receive or send data under the control of the processor, which, when executing the computer program, implements the steps of the method according to any one of claims 1-43.

48. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-43.

49. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-43.

Images