Access satellite selection method and device, terminal and satellite network

Abstract

The invention provides an access satellite selection method and device, a terminal and a satellite network. The method is applied to a terminal supporting a store-and-forward function, and comprises: receiving a first message sent by a satellite network, the first message comprising any one of the following items: a first satellite identifier list, the first satellite identifier list comprising at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite; a second satellite identifier list and list valid time, wherein the second satellite identifier list comprises at least one satellite to which the terminal preferably accesses; the second satellite identifier list, the third satellite identifier list and the list valid time are received, and the third satellite identifier list comprises at least one satellite which stores subscription information or context information of the terminal; a third satellite identifier list and list valid time corresponding to the third satellite identifier list; and selecting an access satellite according to the first message. According to the scheme, the terminal can be assisted to efficiently select a proper satellite for network access.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to methods, apparatus, terminals and satellite networks for selecting access satellites. Background Technology

[0002] In modern communication networks, the stability and efficiency of the connection between the terminal and the network are crucial, especially in scenarios involving satellite communication. A satellite operating in normal mode can only provide services to the UE if both the service link between the terminal and the satellite and the feeder link between the satellite and the ground are simultaneously available. However, in reality, the feeder link may not always be available depending on the satellite's operational status; for example, the satellite may lose connection with the ground gateway station when it reaches a certain location. To provide services to the terminal in situations where the feeder link is temporarily unavailable, a store-and-forward mode is defined for the satellite. When a satellite operates in store-and-forward mode, the onboard base station includes an indication in its broadcast message. Upon receiving this indication, if the terminal also supports store-and-forward, it will indicate its store-and-forward capability to the network during the Attach and Tracking Area Update (TAU) processes.

[0003] To support store-and-forward capabilities, two network architectures are defined: the Split MME architecture and the Evolved Packet Core (EPC) star architecture, which integrates the Mobility Management Entity (MME) and the FullCN onboard architecture.

[0004] In related technologies, whether using a separate MME architecture or an EPC-based overall satellite architecture, the network can indicate a list of preferred satellite identifiers to the terminal to assist the UE in selecting a serving satellite for subsequent access. However, in practical applications, due to the mobility of satellites, the terminal cannot accurately and efficiently select a suitable satellite, which can easily lead to failures in attach access or tracking area updates. Summary of the Invention

[0005] The purpose of this application is to provide a method, apparatus, terminal, and satellite network for selecting access satellites, in order to solve the technical problem that due to the mobility of satellites, the terminal cannot accurately and efficiently select a suitable satellite, which easily leads to the failure of attachment access or tracking area updates.

[0006] In a first aspect, embodiments of this application provide a method for selecting access satellites, applied to a terminal, the terminal supporting store-and-forward functionality, including:

[0007] Receive a first message sent by the satellite network, wherein the first message includes any one of the following:

[0008] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0009] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0010] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0011] The third satellite identifier list and the corresponding list validity period D3;

[0012] Based on the first message, select the satellite to access.

[0013] In some embodiments, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0014] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0015] In some embodiments, the first satellite identifier list includes at least one of the following:

[0016] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0017] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0018] In some embodiments, the first message may further include at least one of the following:

[0019] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0020] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0021] In some embodiments, the first satellite identifier sublist and the second satellite identifier sublist further include at least one of the following:

[0022] The waiting time for each satellite;

[0023] Each satellite has a corresponding Public Land Mobile Network (PLMN) identifier.

[0024] In some embodiments, selecting an access satellite based on the first message includes:

[0025] During the effective period of the list, a second attachment request or a second tracking area update request is sent to the satellites in the list.

[0026] In some embodiments, when the second attach request is sent to a satellite in the first satellite identifier sublist, the second attach request does not include a Packet Data Network (PDN) connection.

[0027] In some embodiments, sending a second attachment request or a second tracking area update request to the satellites in the list during the effective time of the list includes:

[0028] If the first message includes both the second satellite identifier list and the third satellite identifier list, then within the validity period D3 corresponding to the third satellite identifier list, a satellite in the third satellite identifier list is selected for network access; if the validity period D3 of the third satellite identifier list has expired, then within the validity period D2 of the second satellite identifier list, a satellite in the second satellite identifier list is selected for network access; wherein, the validity period D3 of the third satellite identifier list is less than the validity period D2 of the second satellite identifier list.

[0029] In some embodiments, the second satellite identifier list and the three-satellite identifier list further include at least one of the following:

[0030] The waiting time for each satellite;

[0031] Each satellite has a corresponding PLMN identifier.

[0032] In some embodiments, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0033] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0034] Secondly, embodiments of this application provide a method for selecting access satellites, applied to a satellite network, wherein the satellite network supports store-and-forward functionality, including:

[0035] The receiving terminal sends a first attachment request or a first tracking area update request;

[0036] Send a first message to the terminal, the first message being either a rejection message or an acceptance message, wherein the first message includes any one of the following:

[0037] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0038] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0039] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0040] The third satellite identifier list and the corresponding list validity period D3.

[0041] In some embodiments, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0042] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0043] In some embodiments, the first satellite identifier list includes at least one of the following:

[0044] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0045] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0046] In some embodiments, the first message may further include at least one of the following:

[0047] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0048] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0049] In some embodiments, the first satellite identifier sublist and the second satellite identifier sublist further include at least one of the following:

[0050] The waiting time for each satellite;

[0051] Each satellite has a corresponding PLMN identifier.

[0052] In some embodiments, the second satellite identifier list and the three-satellite identifier list further include at least one of the following:

[0053] The waiting time for each satellite;

[0054] Each satellite has a corresponding PLMN identifier.

[0055] In some embodiments, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0056] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0057] Thirdly, embodiments of this application provide a terminal, including: a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor; the terminal supports store-and-forward functionality, and the processor is used to read the program from the memory and execute the following processes:

[0058] Receive a first message sent by the satellite network, wherein the first message includes any one of the following:

[0059] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0060] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0061] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0062] The third satellite identifier list and the corresponding list validity period D3;

[0063] Based on the first message, select the satellite to access.

[0064] In some embodiments, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0065] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0066] In some embodiments, the first satellite identifier list includes at least one of the following:

[0067] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0068] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0069] In some embodiments, the first message may further include at least one of the following:

[0070] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0071] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0072] In some embodiments, the first satellite identifier sublist and the second satellite identifier sublist further include at least one of the following:

[0073] The waiting time for each satellite;

[0074] Each satellite has a corresponding PLMN identifier.

[0075] In some embodiments, the processor is specifically configured to read a program from memory and execute the following processes:

[0076] During the effective period of the list, a second attachment request or a second tracking area update request is sent to the satellites in the list.

[0077] In some embodiments, when the second attach request is sent to a satellite in the first satellite identifier sublist, the second attach request does not include a Packet Data Network (PDN) connection.

[0078] In some embodiments, the processor is specifically configured to read a program from memory and execute the following processes:

[0079] If the first message includes both the second satellite identifier list and the third satellite identifier list, then within the validity period D3 corresponding to the third satellite identifier list, a satellite in the third satellite identifier list is selected for network access; if the validity period D3 of the third satellite identifier list has expired, then within the validity period D2 of the second satellite identifier list, a satellite in the second satellite identifier list is selected for network access; wherein, the validity period D3 of the third satellite identifier list is less than the validity period D2 of the second satellite identifier list.

[0080] In some embodiments, the second satellite identifier list and the three-satellite identifier list further include at least one of the following:

[0081] The waiting time for each satellite;

[0082] Each satellite has a corresponding PLMN identifier.

[0083] In some embodiments, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0084] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0085] Fourthly, embodiments of this application provide a satellite network, including: a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor; the satellite network supports store-and-forward functionality, and the processor is used to read the program from the memory and execute the following processes:

[0086] The receiving terminal sends a first attachment request or a first tracking area update request;

[0087] Send a first message to the terminal, the first message being either a rejection message or an acceptance message, wherein the first message includes any one of the following:

[0088] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0089] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0090] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0091] The third satellite identifier list and the corresponding list validity period D3.

[0092] In some embodiments, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0093] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0094] In some embodiments, the first satellite identifier list includes at least one of the following:

[0095] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0096] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0097] In some embodiments, the first message may further include at least one of the following:

[0098] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0099] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0100] In some embodiments, the first satellite identifier sublist and the second satellite identifier sublist further include at least one of the following:

[0101] The waiting time for each satellite;

[0102] Each satellite has a corresponding PLMN identifier.

[0103] In some embodiments, the second satellite identifier list and the three-satellite identifier list further include at least one of the following:

[0104] The waiting time for each satellite;

[0105] Each satellite has a corresponding PLMN identifier.

[0106] In some embodiments, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0107] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0108] Fifthly, embodiments of this application provide a satellite access selection device applied to a terminal, the terminal supporting store-and-forward functionality, including:

[0109] The first transmitting module is used to send a first attachment request or a first tracking area update request to the satellite network;

[0110] A first receiving module is configured to receive a first message sent by the satellite network, wherein the first message is a rejection message or an acceptance message, and the first message includes any one of the following:

[0111] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0112] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0113] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0114] The third satellite identifier list and the corresponding list validity period D3;

[0115] The satellite selection module is used to select an access satellite based on the first message.

[0116] Sixthly, embodiments of this application provide a satellite access selection device applied to a satellite network, wherein the satellite network supports store-and-forward functionality, including:

[0117] The second receiving module is used to receive the first attachment request or the first tracking area update request sent by the terminal.

[0118] The second sending module is configured to send a first message to the terminal, wherein the first message is a rejection message or an acceptance message, and the first message includes any one of the following:

[0119] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0120] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0121] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0122] The third satellite identifier list and the corresponding list validity period D3.

[0123] In a seventh aspect, embodiments of this application provide a processor-readable storage medium storing a computer program for causing the processor to perform the satellite access selection method as described in the first or second aspect.

[0124] The beneficial effects of the above technical solution in this application are as follows:

[0125] In the above scheme, after sending a first attach request or a first tracking area update request to the satellite network, the terminal receives a first message from the satellite network, which is either a rejection message or an acceptance message. When the first message includes a first satellite identifier list, since the first satellite identifier list includes at least one satellite and its corresponding network store-and-forward architecture, the terminal can select the satellite that provides the best quality of service based on the satellite's network store-and-forward architecture, thereby optimizing resource utilization and reducing the probability of access failure. When the first message includes a second satellite identifier list, or includes a second satellite identifier list and / or a third satellite identifier list, since the lists include a list validity period, the terminal can determine the availability time of satellites in the second satellite identifier list based on the list validity period, preventing the terminal from attempting access on expired satellite lists and reducing unnecessary attach failures and signaling overhead. Furthermore, by informing the terminal of the validity period, the terminal does not need to frequently request updated satellite lists from the network, thereby reducing the frequency of signaling interactions. Attached Figure Description

[0126] Figure 1 This is one of the flowcharts for the satellite selection method in this application embodiment;

[0127] Figure 2This is a second flowchart of the satellite selection method according to an embodiment of this application;

[0128] Figure 3 This is the third flowchart of the satellite selection method according to an embodiment of this application;

[0129] Figure 4 This is the fourth flowchart of the satellite selection method according to an embodiment of this application;

[0130] Figure 5 This is one of the structural block diagrams of the satellite access selection device according to an embodiment of this application;

[0131] Figure 6 This is a second structural block diagram of the satellite access selection device according to an embodiment of this application;

[0132] Figure 7 This is a schematic diagram of the hardware structure of the terminal according to an embodiment of this application;

[0133] Figure 8 This is a schematic diagram of the hardware structure of a satellite network according to an embodiment of this application. Detailed Implementation

[0134] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0135] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0136] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0137] The following section will first introduce the content related to the solutions provided in the embodiments of this application.

[0138] I. Satellite Store-and-Forward Operations

[0139] In normal operation, a satellite can only provide services to a terminal if both the service link between the satellite and the terminal and the feeder link between the satellite and the ground station are simultaneously available. However, in reality, the feeder link may not always be available depending on the satellite's operational status; for example, the satellite may lose connection with the ground gateway station when it reaches a specific location. In cases where the feeder link is temporarily unavailable, a store-and-forward mode is defined for the satellite to still provide services to the terminal.

[0140] For example, when the satellite is at position L1, the terminal is within the satellite's coverage area, and the service link between the satellite and the terminal is available, but the connection between the satellite and the ground network is unavailable. At this time, the satellite temporarily stores the uplink data received from the terminal and forwards the stored downlink data to the terminal. When the satellite moves to position L2, the feeder link returns to normal, and the satellite forwards the stored uplink data to the ground network and receives downlink data from the ground network.

[0141] For satellites operating in store-and-forward mode, the onboard base station includes an indication in the broadcast message. Upon receiving this indication, if the UE also supports store-and-forward, it will indicate its store-and-forward capability to the network during the Attach and Tracking Area Update (TAU) processes. Store-and-forward operations are suitable for latency-insensitive services, such as cellular IoT and short message services.

[0142] II. Store-and-forward network architecture

[0143] To support store-and-forward, two network architectures were defined: Split MME architecture and Full CN onboard architecture.

[0144] 1. Separate MME architecture

[0145] In this architecture, base stations and some MME functions (onboard MMEs) are deployed on satellites, while other MME functions (terrestrial MMEs) and other 4G core network elements are located on the ground. The onboard MME is responsible for the S1 interface interaction with the base station and the NAS signaling processing interaction with the UE, while the terrestrial MME is responsible for interface interaction with other core network elements. The onboard and terrestrial MMEs together form a complete MME entity, and one terrestrial MME can be associated with multiple onboard MMEs.

[0146] When a UE initiates a call and needs to interact with the terrestrial network, the onboard MME stores the call session information and synchronizes the data to the terrestrial MME when the power supply link is available. The terrestrial MME performs interactions with other core network elements and synchronizes the UE's context and data to the onboard MME.

[0147] When the MME is operating in store-and-forward mode, if the MME is currently unable to complete the NAS procedure (e.g., during attach, the MME fails to obtain the security context or subscription data from the terrestrial network), and the UE also supports store-and-forward mode, the MME should reject the UE's signaling request, carrying the relevant reason value. After receiving the rejection message, the UE can re-initiate the NAS request after a certain period of time. This NAS request can be a retry of the previously rejected request, or it can be a continuation of the previous NAS procedure.

[0148] 2. Overall Satellite Architecture of Core Network

[0149] In this architecture, base stations and all EPC network elements (including MME, SGW, PGW, HSS, and SMSC) are deployed on satellites. Additionally, each satellite has a proxy function that simulates a remote endpoint (such as an application server) for UE communication, used to store and forward UE communication data.

[0150] Data sent by the UE is stored in the proxy function. After the power supply link is restored, the on-board proxy function sends the data to the ground proxy function and the ground network. The ground proxy function can also receive and store the called party's downlink data, select the on-board proxy function that will serve the UE, and then have the on-board proxy function send the data to the UE. When the base station and core network are deployed on the satellite and the service link is available, the UE can complete processes such as attaching, tracking area update, and data reception and transmission.

[0151] In related technologies, whether using a separate MME architecture or an EPC-based overall satellite architecture, the network can indicate a list of preferred satellite identifiers to the terminal to assist the UE in selecting a serving satellite for subsequent access. However, due to the mobility of satellites, this approach is not feasible in practical applications, as the terminal cannot efficiently select a suitable satellite, which can easily lead to failures in attach access or tracking area updates.

[0152] Based on the above, this application provides a method, apparatus, terminal, and satellite network for selecting access satellites, in order to solve the technical problem that due to the mobility of satellites, the terminal cannot accurately and efficiently select a suitable satellite, which easily leads to the failure of attachment access or tracking area update.

[0153] See Figure 1 This application provides a method for selecting access satellites, applied to a terminal that supports store-and-forward functionality, including:

[0154] Step 101: Receive a first message sent by the satellite network, the first message including one of the following:

[0155] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0156] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0157] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0158] The third satellite identifier list and the corresponding list validity period D3.

[0159] It should be noted that the above-mentioned list validity period is used to characterize the availability of the satellite identifier list. In other words, the list validity period is used by the terminal to determine the available time range of the satellite identifier list. After the list validity period expires, the satellite identifier list becomes unavailable.

[0160] Understandably, in order to facilitate the terminal in determining the available time range of the satellite identifier list, the satellite network can also send the list validity period corresponding to the satellite identifier list to the terminal; if the terminal receives the satellite identifier list and the list validity period corresponding to the satellite identifier list at the first moment, then the time range from the first moment to the second moment is determined as the available time range of the satellite identifier list; where the second moment = the first moment + the list validity period.

[0161] In some application examples, the first message is an attach rejection message or an attach acceptance message sent by the satellite network in response to the first attach request; or, the first message is a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to the tracking area update request. That is, the terminal sends a first attach request or a first tracking area update request to the satellite network; further, the satellite network sends an attach rejection message or an attach acceptance message to the terminal in response to the first attach request; or the satellite network sends a tracking area update rejection message or a tracking area update acceptance message to the terminal in response to the first tracking area update request.

[0162] It should be noted that in application scenarios where the service link between the terminal and the satellite is available, but the power supply link between the satellite and the ground is unavailable, the terminal can access the satellite. After the terminal initiates an Attach Request or Tracking Area Update Request (TAU Request), for a separate MME architecture, since the power supply link is unavailable at this time, the onboard MME does not have the UE's context information and cannot interact with core network elements in the ground network (such as the ground MME and HSS), so the onboard MME rejects the Attach Request or Tracking Area Update Request sent by the terminal. For a core network-as-a-satellite architecture, if the current satellite cannot provide services to the terminal (e.g., the UE is not subscribed in the onboard HSS), the MME rejects the Attach Request or Tracking Area Update Request sent by the terminal.

[0163] Optionally, the attached rejection message and the tracking area update rejection message carry a rejection reason value to indicate that the network rejected the request due to the store-and-forward operation.

[0164] In other application examples, the first message is a registration rejection message or registration acceptance message sent by the satellite network based on the registration request. That is, the terminal sends a registration request to the satellite network; the satellite network sends a registration rejection message or registration acceptance message to the terminal based on the registration request; wherein, the registration request is an initial registration request or a registration update request.

[0165] In practice, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris; the third satellite identifier list is configured in the onboard MME, or in the user subscription data of the onboard HSS, or is synchronized from the ground MME to the onboard MME.

[0166] Step 102: Select the access satellite based on the first message.

[0167] For example, if the first message includes a first satellite identifier list, an attach request or tracking area update request is initiated again for a satellite in the first satellite identifier list; for example, if the first message includes a first satellite identifier list and a corresponding list validity period D1, an attach request or tracking area update request is initiated again for a satellite in the first satellite identifier list within the list validity period D1; for example, if the first message includes a second satellite identifier list and a corresponding list validity period D2, an attach request or tracking area update request is initiated again for a satellite in the second satellite identifier list within the list validity period D2. Tracking area update request; for example, if the first message includes a third satellite identifier list and the corresponding list validity period D3, within the corresponding list validity period D3, select one satellite in the third satellite identifier list to re-initiate an attach request or tracking area update request; for example, if the first message includes a second satellite identifier list, the corresponding list validity period D2, a third satellite identifier list, and the corresponding list validity period D3, preferentially select one satellite in the third satellite identifier list to re-initiate an attach request or tracking area update request within the corresponding list validity period D3.

[0168] In the above embodiments, when the first message includes a first satellite identifier list, since the first satellite identifier list includes at least one satellite and its corresponding network store-and-forward architecture information, the terminal can select the satellite that provides the best quality of service based on the satellite's network store-and-forward architecture, thereby optimizing resource utilization and reducing the probability of access failure. When the first message includes a second satellite identifier list, or includes a second satellite identifier list and / or a third satellite identifier list, since the first message also includes the list's validity period, the terminal can determine the availability time of satellites in the second satellite identifier list based on the list's validity period, preventing the terminal from attempting access on expired satellite lists and reducing unnecessary attach failures and signaling overhead. Furthermore, by informing the terminal of the validity period, the terminal does not need to frequently request updated satellite lists from the network, thereby reducing the frequency of signaling interactions, alleviating network burden, and improving overall network efficiency.

[0169] In some embodiments, the first satellite identifier list includes at least one of the following:

[0170] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0171] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0172] For example, the first satellite identifier list is shown in Table 1 below:

[0173]

[0174]

[0175] Table 1

[0176] As shown in Table 1 above, the first satellite identifier list includes the first satellite identifier sublist under the separate architecture, and / or the second satellite identifier sublist under the overall core network satellite architecture.

[0177] In some embodiments, the first message also includes at least one of the following:

[0178] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0179] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0180] In specific implementation, the list validity period T1 corresponding to the first satellite identifier sublist is used to characterize the availability and timeliness of the first satellite identifier sublist, that is, the available time range of the first satellite identifier sublist. Within the list validity period T1, the terminal can subsequently select satellites in the first satellite identifier sublist for network access. For example, within the list validity period T1, a second attach request or a second tracking area update request can be sent to a satellite in the list; where, within the list validity period can be understood as within the valid time range characterized by the list validity period.

[0181] In specific implementation, the list validity period T2 corresponding to the second satellite identifier sublist is used to characterize the availability and timeliness of the second satellite identifier sublist, that is, the available time range of the second satellite identifier sublist. Within the list validity period T2, the terminal can subsequently select satellites in the second satellite identifier sublist for network access. For example, within the list validity period T2, a second attach request or a second tracking area update request can be sent to a satellite in the list; where, within the list validity period can be understood as within the valid time range characterized by the list validity period. It should be noted that the list validity periods in the first satellite identifier sublist and the second satellite identifier sublist can be the same or different.

[0182] The first satellite identifier sublist also includes at least one of the following:

[0183] The waiting time for each satellite;

[0184] Each satellite has a corresponding PLMN identifier.

[0185] For example, the first satellite identifier sublist is shown in Table 2 below:

[0186]

[0187] Table 2

[0188] As shown in Table 2 above, the first satellite identifier sublist includes not only the satellite identifier, but also the PLMN identifier corresponding to each satellite, the waiting time, and the list validity period T1.

[0189] In practice, the waiting time is used to characterize how long the satellite will wait before it can improve signal coverage for the area where the terminal is currently located. For example, satellite x2 in the first satellite identifier sublist under the MME architecture, belonging to PLMN1, will provide signal coverage for the area where the terminal is currently located after a waiting time 'a'.

[0190] In some embodiments, the second satellite identifier sublist also includes at least one of the following:

[0191] The waiting time for each satellite;

[0192] Each satellite has a corresponding PLMN identifier.

[0193] For example, the second satellite identifier sublist is shown in Table 3 below:

[0194]

[0195] Table 3

[0196] As shown in Table 3 above, the second satellite identifier sublist includes not only the satellite identifier, but also the PLMN identifier corresponding to each satellite, the waiting time, and the list validity period T2.

[0197] In practice, the waiting time is used to characterize how long a satellite will need to wait before it can improve signal coverage for the area where the terminal is currently located. For example, satellite y2 in the second satellite identifier sublist, belonging to PLMN1, will provide signal coverage for the area where the terminal is currently located after a waiting time of 2.

[0198] In some embodiments, when the second attach request is sent to a satellite in the first satellite identifier sublist, the second attach request does not include a Packet Data Network (PDN) connection.

[0199] In this embodiment, when the second attach request is sent to a satellite in the second satellite identifier list under the separate MME architecture, by restricting the terminal to only initiating attach requests that do not include a PDN connection, it is possible to avoid failure to establish a data connection under the current conditions. The terminal can send data through control plane signaling messages.

[0200] In some embodiments, sending a second attachment request or a second tracking area update request to the satellites in the list during the effective time of the list includes:

[0201] If the first message includes both the second satellite identifier list and the third satellite identifier list, then within the validity period D3 corresponding to the third satellite identifier list, a satellite in the third satellite identifier list is selected for network access; if the validity period D3 of the third satellite identifier list has expired, then within the validity period D2 of the second satellite identifier list, a satellite in the second satellite identifier list is selected for network access; wherein, the validity period D3 of the third satellite identifier list is less than the validity period D2 of the second satellite identifier list.

[0202] In this embodiment, the third satellite identifier list is a subset of the second satellite identifier list, and the validity period of the third satellite identifier list is shorter than that of the second satellite identifier list. If the terminal obtains both the second and third satellite identifier lists simultaneously, it will prioritize connecting to satellites in the third satellite identifier list during the validity period of the third satellite identifier list. After the validity period of the third satellite identifier list expires, it will then attempt to connect to satellites in the second satellite identifier list. This ensures that the terminal can prioritize connecting to more timely satellites within the validity period.

[0203] It should be noted that if the terminal only obtains the third satellite identifier list, then within the list validity period D3 of the third satellite identifier list, the terminal will only attempt to access the satellites in the third satellite identifier list; if the third satellite identifier list is not obtained, or the list validity period D3 has expired, then within the list validity period D2 of the second satellite identifier list, the terminal will only attempt to access the satellites in the second satellite identifier list.

[0204] In some embodiments, the second satellite identifier list and the three-satellite identifier list further include at least one of the following:

[0205] The waiting time for each satellite;

[0206] Each satellite has a corresponding PLMN identifier.

[0207] For example, the list of second satellite identifiers is shown in Table 4 below:

[0208]

[0209] Table 4

[0210] For example, the list of third satellite identifiers is shown in Table 5 below:

[0211]

[0212] Table 5

[0213] In practice, the waiting time is used to characterize how long the satellite will wait before it can improve signal coverage for the area where the terminal is currently located. For example, satellite 12 in the second satellite identifier list, belonging to PLMN1, will provide signal coverage for the area where the terminal is currently located after a waiting time of b2.

[0214] In practice, the list validity period is used to characterize the availability of the list. Within the list validity period, the terminal can subsequently select satellites in the list for network access. For example, within the list validity period, a second attach request or a second tracking area update request can be sent to a satellite in the list. It should be noted that the list validity periods in the second satellite identifier list and the third satellite identifier list can be the same or different.

[0215] See Figure 2 This application provides a method for selecting access satellites, applied to a satellite network, wherein the satellite network supports store-and-forward functionality, including:

[0216] Step 201: Send a first message to the terminal, the first message including one of the following:

[0217] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0218] The second satellite identifier list and the corresponding list validity period, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0219] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0220] The third satellite identifier list and the corresponding list validity period D3.

[0221] In practice, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0222] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0223] In the above embodiments, when the first message includes a first satellite identifier list, since the first satellite identifier list includes at least one satellite and its corresponding network store-and-forward architecture information, the terminal can select the satellite that provides the best quality of service based on the satellite's network store-and-forward architecture, thereby optimizing resource utilization and reducing the probability of access failure. When the first message includes a second satellite identifier list, or includes a second satellite identifier list and / or a third satellite identifier list, since the first message includes the list's validity period, the terminal can determine the available time range of satellites in the second satellite identifier list based on the list's validity period. This prevents the terminal from attempting access on expired satellite lists, reducing unnecessary attach failures and signaling overhead. Furthermore, by informing the terminal of the validity period, the terminal does not need to frequently request updated satellite lists from the network, thereby reducing the frequency of signaling interactions, alleviating network burden, and improving overall network efficiency.

[0224] In some embodiments, the first satellite identifier list includes at least one of the following:

[0225] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0226] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0227] In some embodiments, the first message may further include at least one of the following:

[0228] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0229] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0230] In some embodiments, the first satellite identifier sublist and the second satellite identifier sublist further include at least one of the following:

[0231] The waiting time for each satellite;

[0232] Each satellite has a corresponding PLMN identifier.

[0233] In some embodiments, the second satellite identifier list and the three-satellite identifier list further include at least one of the following:

[0234] The waiting time for each satellite;

[0235] Each satellite has a corresponding PLMN identifier.

[0236] The following is in conjunction with the appendix Figure 3 and 4 This application provides an exemplary method for selecting access satellites.

[0237] like Figure 3 As shown, the method for selecting access satellites may include the following steps:

[0238] Step 1: Determine that the service link between the UE and the satellite is available, and the power supply link between the satellite and the ground is unavailable. The UE can then access the satellite.

[0239] Step 2: The UE initiates an Attach Request or a Tracking Area Update Request (TAU Request).

[0240] Step 3: The satellite network sends an Attach Reject message or a Tracking Area Update Reject message to the UE. The Attach Reject message or Tracking Area Update Reject message carries the reason for rejection, which is used to indicate that the network rejects this request due to the store-and-forward operation.

[0241] Among them, the attach rejection message or tracking area update rejection message also includes:

[0242] A first satellite identifier list, comprising a first satellite identifier sublist and / or a second satellite identifier sublist, wherein the first satellite identifier sublist indicates at least one satellite under the separate MME architecture, and the second satellite identifier sublist indicates at least one satellite under the overall core network satellite architecture; or...

[0243] The second satellite identifier list and its corresponding validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; or...

[0244] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information.

[0245] In this step, for a separate MME architecture, since the power supply link is unavailable at this time, the onboard MME does not have the UE's context information and cannot interact with the core network elements in the ground network. Therefore, the onboard MME rejects the attachment or tracking area update request. For a core network-wide onboard architecture, if the current satellite cannot provide services to the UE (e.g., the UE is not subscribed in the onboard HSS), the MME rejects the attachment or tracking area update request.

[0246] Step 4: For the separate MME architecture, the power supply link is restored, and the on-board MME interacts with the ground MME and HSS and other network elements to obtain the UE's subscription and authentication data.

[0247] Step 5: The service link between the UE and the satellite is available, and the UE can access the satellite.

[0248] It should be noted that the satellite in step 5 may be different from the satellite in step 1.

[0249] Step 6: The UE re-initiates the attach request or tracking area update request.

[0250] In this step, if the UE receives the first satellite identifier sublist in step 3, the UE can only initiate an attach request that does not include a PDN connection within the list's validity period. If the UE receives the second satellite identifier sublist in step 3, the UE can re-initiate an attach request or tracking area update request to a satellite in the second satellite identifier sublist within the list's validity period. If the UE receives both the first and second satellite identifier sublists in step 3, the UE can attempt to re-initiate an attach request or tracking area update request to satellites in both the first and second satellite identifier sublists within the list's validity period. If the UE receives the second satellite identifier list in step 3, the UE can re-initiate an attach request or tracking area update request to a satellite in the second satellite identifier list within the list's validity period. If the UE receives both the second and third satellite identifier lists in step 3, the UE can only re-initiate an attach request or tracking area update request to a satellite in the third satellite identifier list within the list's validity period.

[0251] Step 7, NAS process including UE and network authentication.

[0252] Step 8: The network sends an Attach Accept request or a Tracking Area Update Accept request to the UE. The Attach Accept or Tracking Area Update Accept message includes:

[0253] A first satellite identifier list, comprising a first satellite identifier sublist and / or a second satellite identifier sublist, wherein the first satellite identifier sublist indicates at least one satellite under the separate MME architecture, and the second satellite identifier sublist indicates at least one satellite under the overall core network satellite architecture; or...

[0254] The second satellite identifier list and its corresponding validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; or...

[0255] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information.

[0256] It should be noted that the satellites involved in the satellite lists in step 8 and the satellite lists in step 3 may be different.

[0257] Step 9: The UE proceeds with subsequent signaling or data transmission and reception. Due to satellite movement, the UE can select different satellites to access and use store-and-forward services based on the satellite identifier list received in Step 8.

[0258] like Figure 4 As shown, the method for selecting access satellites may include the following steps:

[0259] Step 1: Determine that the service link between the UE and the satellite is available, and the power supply link between the satellite and the ground is unavailable. The UE can then access the satellite.

[0260] Step 2: The UE initiates an Attach Request or a Tracking Area Update Request (TAU Request).

[0261] Step 3: If the satellite network is a core network-wide onboard architecture, and the onboard HSS contains the UE's subscription, the satellite network sends an Attach Accept request or a Tracking Area Update Accept request (TAU Accept) to the UE. The Attach Accept or Tracking Area Update Accept message includes:

[0262] A first satellite identifier list, comprising a first satellite identifier sublist and / or a second satellite identifier sublist, wherein the first satellite identifier sublist indicates at least one satellite under the separate MME architecture, and the second satellite identifier sublist indicates at least one satellite under the overall core network satellite architecture; or...

[0263] The second satellite identifier list and its corresponding validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; or...

[0264] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information.

[0265] Step 4: The UE sends an Attach Complete or Tracking Area Update Complete message.

[0266] Step 5: Subsequent signaling or data transmission and reception process for the UE. Due to the movement of satellites, the UE can select different satellites for access based on the satellite identifier list received in Step 3.

[0267] It should be noted that although the above example uses the 4G process for description, its technical features are also applicable to 5G or subsequent network architectures.

[0268] See Figure 5 This application provides a satellite access selection device 500, applied to a terminal, which supports store-and-forward functionality, including:

[0269] The first receiving module 501 is configured to receive a first message sent by the satellite network, the first message including one of the following:

[0270] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0271] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0272] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0273] The third satellite identifier list and the corresponding list validity period D3;

[0274] The satellite selection module 502 is used to select an access satellite based on the first message.

[0275] Optionally, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0276] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0277] Optionally, the first satellite identifier list includes at least one of the following:

[0278] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0279] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0280] Optionally, the first message may also include at least one of the following:

[0281] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0282] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0283] Optionally, the first satellite identifier sublist and the second satellite identifier sublist may further include at least one of the following:

[0284] The waiting time for each satellite;

[0285] Each satellite has a corresponding PLMN identifier.

[0286] Optionally, the satellite selection module 503 includes:

[0287] The first processing submodule is used to send a second attachment request or a second tracking area update request to the satellites in the list within the effective time of the list.

[0288] Optionally, when sending the second attach request to a satellite in the first satellite identifier sublist, the second attach request does not include a Packet Data Network (PDN) connection.

[0289] Optionally, the first processing submodule is specifically configured to, when the first message includes the second satellite identifier list and the third satellite identifier list, select a satellite in the third satellite identifier list for network access within the list validity period D3 corresponding to the third satellite identifier list; if the list validity period D3 corresponding to the third satellite identifier list has expired, select a satellite in the second satellite identifier list for network access within the list validity period D2 corresponding to the second satellite identifier list; wherein, the list validity period D3 corresponding to the third satellite identifier list is less than the list validity period D2 corresponding to the second satellite identifier list.

[0290] Optionally, the second satellite identifier list and the three satellite identifier list shall each include at least one of the following:

[0291] The waiting time for each satellite;

[0292] Each satellite has a corresponding PLMN identifier.

[0293] Optionally, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0294] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0295] It should be noted that the device 500 provided in this application embodiment can implement all the method steps implemented in the above terminal-side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0296] See Figure 6 This application provides a satellite access selection device 600, applied to a satellite network, the satellite network supporting store-and-forward functionality, including:

[0297] The first sending module 601 is configured to send a first message to the terminal, the first message including one of the following:

[0298] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0299] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0300] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0301] The third satellite identifier list and the corresponding list validity period D3.

[0302] Optionally, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0303] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0304] Optionally, the first satellite identifier list includes at least one of the following:

[0305] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0306] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0307] Optionally, the first message may also include at least one of the following:

[0308] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0309] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0310] Optionally, the first satellite identifier sublist and the second satellite identifier sublist may further include at least one of the following:

[0311] The waiting time for each satellite;

[0312] Each satellite has a corresponding PLMN identifier.

[0313] Optionally, the second satellite identifier list and the three satellite identifier list shall each include at least one of the following:

[0314] The waiting time for each satellite;

[0315] Each satellite has a corresponding PLMN identifier.

[0316] Optionally, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0317] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0318] It should be noted that the device 600 provided in this application embodiment can implement all the method steps implemented in the above-mentioned satellite network side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0319] See Figure 7 This application provides a terminal that supports store-and-forward functionality, including: a processor 700; and a memory 720 connected to the processor 700 via a bus interface. The memory 720 is used to store programs and data used by the processor 700 during operation, and the processor 700 calls and executes the programs and data stored in the memory 720.

[0320] The transceiver 710 is connected to a bus interface and is used to receive and send data under the control of the processor 700; the processor 700 reads the program from the memory 720 to implement the following steps:

[0321] Receive a first message sent by the satellite network, the first message including one of the following:

[0322] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0323] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0324] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0325] The third satellite identifier list and the corresponding list validity period D3;

[0326] Based on the first message, select the satellite to access.

[0327] Optionally, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0328] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0329] Optionally, the first satellite identifier list includes at least one of the following:

[0330] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0331] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0332] Optionally, the first message may also include at least one of the following pieces of information:

[0333] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0334] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0335] Optionally, the first satellite identifier sublist and the second satellite identifier sublist may further include at least one of the following:

[0336] The waiting time for each satellite;

[0337] Each satellite has a corresponding PLMN identifier.

[0338] Optionally, the processor 700 is further configured to read the program from the memory 720 and execute the following processes:

[0339] During the effective period of the list, a second attachment request or a second tracking area update request is sent to the satellites in the list.

[0340] Optionally, when sending the second attach request to a satellite in the first satellite identifier sublist, the second attach request does not include a Packet Data Network (PDN) connection.

[0341] Optionally, the processor 700 is specifically used to read the program in the memory 720 and execute the following processes:

[0342] If the first message includes both the second satellite identifier list and the third satellite identifier list, then within the validity period D3 corresponding to the third satellite identifier list, a satellite in the third satellite identifier list is selected for network access; if the validity period D3 of the third satellite identifier list has expired, then within the validity period D2 of the second satellite identifier list, a satellite in the second satellite identifier list is selected for network access; wherein, the validity period D3 of the third satellite identifier list is less than the validity period D2 of the second satellite identifier list.

[0343] Optionally, the second satellite identifier list and the three satellite identifier list shall each include at least one of the following:

[0344] The waiting time for each satellite;

[0345] Each satellite has a corresponding PLMN identifier.

[0346] Optionally, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0347] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0348] Among them, Figure 7 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 700) and memory (memory 720). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 710 can be multiple elements, including transmitters and transceivers, providing a unit for communicating with various other devices over a transmission medium. For different terminals, the user interface 730 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 can store data used by the processor 700 during operation.

[0349] The processor 700 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0350] See Figure 8 This application provides a satellite network that supports store-and-forward functionality, including: a processor 800; and a memory 820 connected to the processor 800 via a bus interface. The memory 820 is used to store programs and data used by the processor 800 during operation, and the processor 800 calls and executes the programs and data stored in the memory 820.

[0351] The transceiver 810 is connected to the bus interface and is used to receive and send data under the control of the processor 800; the processor 800 is used to read the program in the memory 820 to implement the following steps:

[0352] Send a first message to the terminal, the first message including one of the following:

[0353] A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite;

[0354] The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses;

[0355] The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information;

[0356] The third satellite identifier list and the corresponding list validity period D3.

[0357] Optionally, the first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request;

[0358] Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

[0359] Optionally, the first satellite identifier list includes at least one of the following:

[0360] A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture;

[0361] The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

[0362] Optionally, the first message may also include at least one of the following pieces of information:

[0363] The effective time T1 of the list corresponding to the first satellite identifier sublist;

[0364] The validity period of the list corresponding to the second satellite identifier sublist is T2.

[0365] Optionally, the first satellite identifier sublist and the second satellite identifier sublist may further include at least one of the following:

[0366] The waiting time for each satellite;

[0367] Each satellite has a corresponding PLMN identifier.

[0368] Optionally, the second satellite identifier list and the three satellite identifier list shall each include at least one of the following:

[0369] The waiting time for each satellite;

[0370] Each satellite has a corresponding PLMN identifier.

[0371] Optionally, the second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris.

[0372] The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

[0373] Among them, Figure 8In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 800) and memory (memory 820). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 810 can be multiple elements, including transmitters and transceivers, providing a unit for communicating with various other devices over a transmission medium. The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 can store data used by the processor 800 during operation.

[0374] The processor 800 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0375] This application also provides a processor-readable storage medium storing a computer program for causing the processor to perform methods such as those on the terminal side or the satellite network side.

[0376] This application also provides a computer program product, including computer instructions. When these computer instructions are executed by a processor, they implement the various processes of the above method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0377] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0378] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

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

[0380] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0381] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0382] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0383] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for selecting access satellites, characterized in that, Applied to a terminal, the terminal supports store-and-forward functionality, including: Receive a first message sent by the satellite network, wherein the first message includes any one of the following: A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite; The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information; The third satellite identifier list and the corresponding list validity period D3; Based on the first message, select the satellite to access.

2. The method for selecting access satellites according to claim 1, characterized in that, The first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request; Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

3. The method for selecting access satellites according to claim 1, characterized in that, The first satellite identifier list includes at least one of the following: A first satellite identifier sublist, which is used to indicate at least one satellite under the separate mobility management entity (MME) architecture; The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

4. The method for selecting access satellites according to claim 3, characterized in that, The first message also includes at least one of the following: The effective time T1 of the list corresponding to the first satellite identifier sublist; The validity period of the list corresponding to the second satellite identifier sublist is T2.

5. The method for selecting access satellites according to claim 3, characterized in that, The first satellite identifier sublist and the second satellite identifier sublist each include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

6. The method for selecting access satellites according to any one of claims 2 to 4, characterized in that, The step of selecting a satellite to access based on the first message includes: During the effective period of the list, a second attachment request or a second tracking area update request is sent to the satellites in the list.

7. The method for selecting access satellites according to claim 6, characterized in that, When the second attach request is sent to a satellite in the first satellite identifier sublist, the second attach request does not include a Packet Data Network (PDN) connection.

8. The method for selecting access satellites according to claim 6, characterized in that, Sending a second attachment request or a second tracking area update request to the satellites in the list within the effective time of the list includes: If the first message includes both the second satellite identifier list and the third satellite identifier list, then within the validity period D3 corresponding to the third satellite identifier list, a satellite in the third satellite identifier list is selected for network access; if the validity period D3 of the third satellite identifier list has expired, then within the validity period D2 of the second satellite identifier list, a satellite in the second satellite identifier list is selected for network access; wherein, the validity period D3 of the third satellite identifier list is less than the validity period D2 of the second satellite identifier list.

9. The method for selecting access satellites according to claim 1, characterized in that, The second satellite identifier list and the three satellite identifier list also each include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

10. The method for selecting access satellites according to claim 1, characterized in that, The second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris; The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

11. A method for selecting access satellites, characterized in that, Applied to satellite networks that support store-and-forward functionality, including: Send a first message to the terminal, the first message including any one of the following: A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite; The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information; The third satellite identifier list and the corresponding list validity period D3.

12. The method for selecting access satellites according to claim 11, characterized in that, The first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request; Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

13. The method for selecting access satellites according to claim 11, characterized in that, The first satellite identifier list includes at least one of the following: A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture; The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

14. The method for selecting access satellites according to claim 13, characterized in that, The first message also includes at least one of the following: The effective time T1 of the list corresponding to the first satellite identifier sublist; The validity period of the list corresponding to the second satellite identifier sublist is T2.

15. The method for selecting access satellites according to claim 13, characterized in that, The first satellite identifier sublist and the second satellite identifier sublist also include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

16. The method for selecting access satellites according to claim 11, characterized in that, The second satellite identifier list and the three satellite identifier list also each include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

17. The method for selecting access satellites according to claim 11, characterized in that, The second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris; The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

18. A terminal, comprising: A transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor; characterized in that the terminal supports store-and-forward functionality, and the processor is used to read the program from the memory and execute the following processes: Receive a first message sent by the satellite network, wherein the first message includes any one of the following: A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite; The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information; The third satellite identifier list and the corresponding list validity period D3; Based on the first message, select the satellite to access.

19. The terminal according to claim 18, characterized in that, The first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request; Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

20. The terminal according to claim 18, characterized in that, The first satellite identifier list includes at least one of the following: A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture; The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

21. The terminal according to claim 20, characterized in that, The first message also includes at least one of the following: The effective time T1 of the list corresponding to the first satellite identifier sublist; The validity period of the list corresponding to the second satellite identifier sublist is T2.

22. The terminal according to claim 20, characterized in that, The first satellite identifier sublist and the second satellite identifier sublist each include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

23. The terminal according to any one of claims 19 to 21, characterized in that, The processor is specifically used to read the program from the memory and execute the following processes: During the effective period of the list, a second attachment request or a second tracking area update request is sent to the satellites in the list.

24. The terminal according to claim 23, characterized in that, When the second attach request is sent to a satellite in the first satellite identifier sublist, the second attach request does not include a Packet Data Network (PDN) connection.

25. The terminal according to claim 23, characterized in that, The processor is specifically used to read the program from the memory and execute the following processes: If the first message includes the second satellite identifier list and the third satellite identifier list, then within the list validity period D3 corresponding to the third satellite identifier list, a satellite in the third satellite identifier list is selected for network access. If the validity period of the third satellite identifier list is exceeded, then within the validity period D2 of the second satellite identifier list, a satellite in the second satellite identifier list is selected for network access; wherein, the validity period D3 of the third satellite identifier list is less than the validity period D2 of the second satellite identifier list.

26. The terminal according to claim 19, characterized in that, The second satellite identifier list and the three satellite identifier list also each include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

27. The terminal according to claim 19, characterized in that, The second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris; The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

28. A satellite network, comprising: A transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor; characterized in that the satellite network supports store-and-forward functionality, and the processor is used to read the program from the memory and execute the following processes: Send a first message to the terminal, the first message including any one of the following: A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite; The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information; The third satellite identifier list and the corresponding list validity period D3.

29. The satellite network according to claim 28, characterized in that, The first message is an attach rejection message or an attach accept message sent by the satellite network in response to the first attach request; Alternatively, the first message may be a tracking area update rejection message or a tracking area update acceptance message sent by the satellite network in response to a first tracking area update request.

30. The satellite network according to claim 28, characterized in that, The first satellite identifier list includes at least one of the following: A first satellite identifier sublist, which is used to indicate at least one satellite under the separate MME architecture; The second satellite identifier sublist is used to indicate at least one satellite in the overall core network satellite architecture.

31. The satellite network according to claim 29, characterized in that, The first message also includes at least one of the following: The effective time T1 of the list corresponding to the first satellite identifier sublist; The validity period of the list corresponding to the second satellite identifier sublist is T2.

32. The satellite network according to claim 28, characterized in that, The first satellite identifier sublist and the second satellite identifier sublist also include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

33. The satellite network according to claim 28, characterized in that, The second satellite identifier list and the three satellite identifier list also each include at least one of the following: The waiting time for each satellite; Each satellite has a corresponding PLMN identifier.

34. The satellite network according to claim 28, characterized in that, The second satellite identifier list is configured in the onboard MME, or is inferred by the onboard MME based on ephemeris; The third satellite identifier list is configured in the on-board MME, or in the user subscription data of the on-board HSS, or is synchronized from the ground MME to the on-board MME.

35. A satellite access selection device, characterized in that, Applied to a terminal, the terminal supports store-and-forward functionality, including: The first receiving module is configured to receive a first message sent by the satellite network, wherein the first message includes any one of the following: A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite; The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; The second satellite identifier list, and the corresponding list validity period D2. The third satellite identifier list and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information; The third satellite identifier list and the corresponding list validity period D2; The satellite selection module is used to select an access satellite based on the first message.

36. A satellite access selection device, characterized in that, Applied to satellite networks that support store-and-forward functionality, including: The first sending module is configured to send a first message to the terminal, wherein the first message includes any one of the following: A first satellite identifier list, which includes at least one satellite and network store-and-forward architecture information corresponding to the at least one satellite; The second satellite identifier list and the corresponding list validity period D2, wherein the second satellite identifier list includes at least one satellite that the terminal preferably accesses; The second satellite identifier list, the list validity period D2 corresponding to the second satellite identifier list, the third satellite identifier list, and the list validity period D3 corresponding to the third satellite identifier list, wherein the third satellite identifier list includes at least one satellite storing the terminal's subscription information or context information; The third satellite identifier list and the corresponding list validity period D3.

37. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program for causing the processor to perform the access satellite selection method as described in any one of claims 1 to 10, or the access satellite selection method as described in any one of claims 11 to 17.

Images