Mapping query and update method for spaceborne network element identification in satellite-ground network

Abstract

The application discloses a mapping query and updating method and device for satellite-borne network element identification in a satellite-ground network, and belongs to the technical field of satellite mobile communication. A satellite-ground core network pre-allocates a temporary position identification based on a satellite ephemeris of a satellite-borne network element, and sets state bits for the temporary position identification to represent active and idle states respectively; when the satellite-borne network element initiates data transmission, the satellite-borne network element queries a high-orbit core network currently belonging to the satellite-borne network element to obtain a pre-allocated temporary position identification corresponding to a target satellite-borne network element identity and state bits, so as to realize mapping query of the satellite-borne network element identification; when the satellite-borne network element moves across a satellite position management area of the high-orbit core network, the state bits of the pre-allocated temporary position identification corresponding to the satellite-borne network element in a high-orbit mapping table are updated, so as to realize mapping updating of the satellite-borne network element position identification. The application realizes efficient query and dynamic updating of the satellite-borne network element identification mapping, and improves the mobility management capability and communication continuity of the satellite-ground integrated network.

Description

Technical Field

[0001] This invention relates to the field of satellite mobile communication technology, and in particular to a method, apparatus, device, and storage medium for mapping, querying, and updating satellite network element identifiers in a satellite-to-ground network. Background Technology

[0002] With the deep integration of satellite communication technology and terrestrial mobile networks, building a converged satellite-terrestrial network has become an important evolution direction for sixth-generation mobile communication systems. In this process, deploying base stations and core network elements on satellite platforms, i.e., regenerative mode, has become a key technical path to achieve seamless global coverage and support high-speed mobility services, and has received widespread attention and promotion in international standardization organizations.

[0003] However, compared to the relatively fixed topology and limited mobility of traditional terrestrial networks, space-ground integrated networks exhibit significant differences: on the one hand, low-Earth orbit satellites move at high speeds relative to the ground, resulting in continuous, large-scale, cross-regional mobility of their onboard network elements; on the other hand, unique channel conditions exist between space and ground, such as long propagation delays and intermittent connections. These characteristics pose a severe challenge to existing network management mechanisms designed based on static or quasi-static assumptions, especially identifier management systems.

[0004] Currently, terrestrial mobile communication networks generally adopt a mapping architecture that decouples identity identifiers from location identifiers. Under this architecture, each network element is assigned a unique fixed identity identifier and a temporary location identifier associated with its actual access location, and addressing is achieved through a two-level mapping relationship. When this mechanism is directly applied to satellite-terrestrial convergence scenarios, its inherent limitations become apparent: First, the query for the location information of the peer network element at the time of transmission initiation relies entirely on the terrestrial core network, and the inherent latency of the satellite-terrestrial link directly affects query efficiency and increases transmission establishment latency; second, each handover of a satellite network element across satellite location management areas requires the release and reallocation of the temporary location identifier, which, in the context of frequent handovers due to high-speed satellite movement, will trigger a large amount of signaling interaction and processing overhead; third, the centralized identifier management on the ground is difficult to adapt to the dynamic distribution of satellite nodes and the autonomy requirements of the network portion. These factors collectively restrict the overall performance improvement of satellite-terrestrial convergence networks, particularly affecting the continuity of services and quality of service in large-scale, highly dynamic scenarios.

[0005] Therefore, there is an urgent need to design an efficient identifier mapping management method suitable for satellite-to-ground networks, which can reduce satellite-to-ground signaling overhead and transmission latency while supporting the high mobility of satellite network elements and improving the overall network performance. Summary of the Invention

[0006] The present invention aims to at least partially solve one of the technical problems in the related art.

[0007] To address this, this invention proposes a method for mapping, querying, and updating satellite-borne network element identifiers in a space-to-ground network. This method pre-assigns fixed temporary location identifiers to all satellite-borne network elements within the high-orbit core network's satellite management area, and performs localized queries and dynamic home status updates based on the identifier status bits. When satellite-borne network elements switch between regions, only the status bits need to be updated, and the changed information is synchronized to the ground core network. This achieves efficient maintenance of identifier mapping relationships and significantly reduces space-to-ground signaling overhead and transmission latency.

[0008] Another objective of this invention is to provide a mapping query and update device for satellite network element identifiers in a satellite-to-ground network.

[0009] The third objective of this invention is to provide a computer device.

[0010] A fourth objective of this invention is to provide a non-transitory computer-readable storage medium.

[0011] To achieve the above objectives, this invention proposes a mapping method for spaceborne network element identifiers in a space-ground integrated network, comprising: S1, the ground core network assigns a unique and fixed identity to each satellite network element, and stores the identity as associated with the low-Earth orbit satellite number to which the satellite network element belongs in the global network element identity mapping table of the satellite-ground fusion core network. Based on the ephemeris characteristics of low-Earth orbit satellites, the high-Earth orbit core network pre-assigns a temporary location identifier for each satellite network element in the location management area of ​​each high-Earth orbit core network satellite, and sets a status bit corresponding to the pre-assigned temporary location identifier in the satellite network element identity mapping table of the high-Earth orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the satellite network element in the corresponding high-Earth orbit core network satellite location management area. S2, when a satellite-borne network element initiates data transmission to other satellite-borne network elements, it sends a position identifier mapping query request to the satellite of the high-orbit core network in the current high-orbit core network satellite position management area. The request message contains the identity identifier of the target satellite-borne network element. The high-orbit core network queries the pre-allocated temporary position identifier and status bit in the satellite-borne network element identifier mapping table in the current high-orbit core network satellite position management area according to the identity identifier of the target satellite-borne network element, and completes the satellite-borne network element identifier mapping query. S3. When the onboard network element moves across the high-orbit core network satellite position management area with the low-orbit satellite, the corresponding high-orbit core network before and after the high-orbit core network satellite position management area switch updates the temporary position identifier status bit of the onboard network element in the onboard network element identifier mapping table in the corresponding high-orbit core network satellite position management area, thus completing the update of the position identifier status of the onboard network element in the two high-orbit core network satellite position management areas.

[0012] The mapping query and update method for satellite-borne network element identifiers in a satellite-to-ground network according to an embodiment of the present invention may also have the following additional technical features: In one embodiment of the present invention, the ground core network assigns a unique and fixed identity identifier to each satellite-borne network element, and stores the identity identifier in a global network element identifier mapping table of the satellite-ground fusion core network, associating the identifier with the low-Earth orbit (LEO) satellite number to which the satellite-borne network element belongs. Based on the ephemeris characteristics of LEO satellites, the high-Earth orbit (HEO) core network pre-assigns a temporary location identifier to each satellite-borne network element within the location management area of ​​each HEO core network satellite, and sets a status bit corresponding to the pre-assigned temporary location identifier in the satellite-borne network element identifier mapping table of the HEO core network satellite location management area. The status bit is used to characterize the activation and idle states of the satellite-borne network element within the corresponding HEO core network satellite location management area, including: S11. Network element identity identifiers can be assigned in the form of IP addresses, but are not limited to the form of IP addresses; S12, the global network element identifier mapping table of the space-ground converged core network can manage and maintain the identifiers and mapping information of two types of functional network elements: spaceborne network elements and ground network elements; among them, ground network elements are managed by the ground core network based on the existing identifier management mechanism; S13. Temporary location identifiers pre-allocated by spaceborne network elements can be allocated in the form of IP addresses, but are not limited to the form of IP addresses; S14, the status bit of the pre-allocated temporary location identifier is a non-binary attribute. The specific status bits include: 00 indicates that the satellite network element is in an idle state, and 11 indicates that the satellite network element is in an active state.

[0013] In one embodiment of the present invention, when the onboard network element moves with a low-Earth orbit satellite across a high-Earth orbit core network satellite position management area, the corresponding high-Earth orbit core networks before and after the high-Earth orbit core network satellite position management area switch update the temporary position identifier status bit of the onboard network element in the corresponding high-Earth orbit core network satellite position management area's onboard network element identifier mapping table, completing the update of the onboard network element's position identifier status in the two high-Earth orbit core network satellite position management areas, including: S31, the high-orbit core network corresponding to the satellite position management area of ​​the high-orbit core network before the switchover will update the status bit corresponding to the temporary position identifier of the satellite network element in the satellite network element identifier mapping table of the high-orbit core network satellite position management area to the deactivated state, indicating that the satellite network element has left the high-orbit core network satellite position management area; S32, the high-orbit core network corresponding to the satellite position management area of ​​the high-orbit core network after the switch will update the status bit corresponding to the temporary position identifier of the satellite network element in the satellite network element identifier mapping table of the high-orbit core network satellite position management area to the active state, indicating that the satellite network element has been managed by the high-orbit core network satellite position management area.

[0014] To achieve the above objectives, another aspect of the present invention proposes a mapping query and update device for satellite-borne network element identifiers in a satellite-to-ground network, comprising: The identifier pre-allocation and status bit setting module is used by the ground core network to assign a unique and fixed identity identifier to the satellite network element, and to associate the identity identifier with the low-Earth orbit satellite number to which the satellite network element belongs and store it in the global network element identifier mapping table of the space-ground fusion core network. Based on the ephemeris characteristics of low-Earth orbit satellites, the high-Earth orbit core network pre-allocates a temporary location identifier for each satellite network element in the location management area of ​​each high-Earth orbit core network satellite, and sets a status bit corresponding to the pre-allocated temporary location identifier in the satellite network element identifier mapping table of the high-Earth orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the satellite network element in the corresponding high-Earth orbit core network satellite location management area. The identifier mapping query module is used to send a location identifier mapping query request to the high-orbit core network satellite in the current high-orbit core network satellite position management area when a satellite-borne network element initiates data transmission to other satellite-borne network elements. The request message contains the identity identifier of the target satellite-borne network element. The high-orbit core network queries the pre-allocated temporary location identifier and status bit in the satellite-borne network element identifier mapping table in the current high-orbit core network satellite position management area based on the identity identifier of the target satellite-borne network element, and completes the satellite-borne network element identifier mapping query. The identifier mapping update module is used to update the temporary position identifier status bit of the satellite network element in the satellite network element identifier mapping table in the corresponding high-orbit core network before and after the high-orbit core network satellite position management area is switched when the satellite network element moves with the low-orbit satellite across the high-orbit core network satellite position management area. This completes the update of the position identifier status of the satellite network element in the two high-orbit core network satellite position management areas.

[0015] The mapping method and apparatus for spaceborne network element identifiers in a space-ground integrated network according to embodiments of the present invention effectively solves the addressing and management challenges caused by frequent movement of network elements in a dynamic space-ground network environment. Through the collaborative mapping of globally fixed identifiers and pre-allocated temporary location identifiers, along with status bit management, efficient and accurate addressing and seamless status updates of spaceborne network elements across high-orbit satellite position management areas are achieved. This significantly improves the efficiency of communication connection establishment and management reliability in the space-ground integrated network, enhances the system's adaptability to dynamic changes in ephemeris data, and provides stable and scalable identifier management support for large-scale, highly mobile spaceborne network elements.

[0016] To achieve the above objectives, a third aspect of this application provides a computer device, including a processor and a memory; wherein the processor reads executable program code stored in the memory to run a program corresponding to the executable program code, for implementing the mapping query and update method for satellite network element identifiers in a satellite-to-ground network as described in the first aspect embodiment.

[0017] To achieve the above objectives, the fourth aspect of this application proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the mapping query and update method for satellite network element identifiers in a satellite-to-ground network as described in the first aspect embodiment.

[0018] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0019] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart of a method and apparatus for mapping, querying and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention. Figure 2 This is a diagram showing the network architecture and identifier mapping of the space-ground fusion core network of the method and apparatus for mapping, querying and updating the identifiers of spaceborne network elements in a space-ground network according to an embodiment of the present invention. Figure 3 This is a flowchart of the network element location identifier mapping query process of the method and apparatus for mapping query and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the network element location identifier mapping query process of the method and apparatus for mapping query and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention. Figure 5 This is a schematic diagram of the network element location identifier mapping and updating process of the method and apparatus for mapping querying and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention. Figure 6 This is a schematic diagram of the network element location identifier mapping and updating process of the method and apparatus for mapping querying and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention. Figure 7 This is an example diagram illustrating the application scenario of the method and apparatus for mapping and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention; Figure 8 This is an example diagram illustrating the location identifier status update process in an application scenario of the method and apparatus for mapping, querying and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention. Figure 9 This is a schematic diagram of the method and apparatus for mapping, querying and updating satellite network element identifiers in a satellite-to-ground network according to an embodiment of the present invention. Figure 10 It is a computer device according to an embodiment of the present invention. Detailed Implementation

[0020] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0021] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0022] The following description, with reference to the accompanying drawings, describes the method, apparatus, device, and storage medium for mapping, querying, and updating satellite network element identifiers in a satellite-to-ground network according to embodiments of the present invention.

[0023] This invention, using a Spaceborne User Plane Function (S-UPF) network element as an example, addresses the management challenges posed by the highly dynamic movement of spaceborne nodes in a space-ground integrated network by designing a satellite identifier mapping management mechanism based on pre-allocation and status bit coordination. First, based on the network topology, fixed temporary location identifiers are pre-allocated to all spaceborne user plane function network elements within each high-orbit satellite position management area, and multi-dimensional status bits are established to accurately represent their current affiliation. Based on this pre-allocation system, when a spaceborne network element initiates data transmission, its affiliated high-orbit satellite can directly perform a localized query based on the status bits to quickly obtain the valid location identifier of the peer network element. When a spaceborne network element switches between management areas, only the status bits of the corresponding identifiers need to be atomically updated on the satellites in the original and new areas to complete the smooth transfer and dynamic update of the mapping relationship. All status bit changes are synchronized to the ground core network to maintain the consistency of the global mapping table. This significantly reduces the overhead of satellite-to-ground signaling interaction and resource allocation caused by frequent switching and querying, while ensuring the overall network control capability, thus significantly improving the operational efficiency and service continuity of the satellite-to-ground converged network.

[0024] Example 1 To achieve the above invention, embodiments of the present invention provide a method for mapping, querying, and updating satellite-borne network element identifiers in a satellite-to-ground network, such as... Figure 1 As shown, it includes: S1, the ground core network assigns a unique and fixed identity to each satellite-borne network element, and stores the identity associating it with the low-Earth orbit satellite number to which the satellite-borne network element belongs in the global network element identity mapping table of the satellite-ground fusion core network. Based on the ephemeris characteristics of low-Earth orbit satellites, the high-Earth orbit core network pre-assigns a temporary location identifier for each satellite-borne network element in the location management area of ​​each high-Earth orbit core network satellite, and sets a status bit corresponding to the pre-assigned temporary location identifier in the satellite-borne network element identity mapping table of the high-Earth orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the satellite-borne network element in the corresponding high-Earth orbit core network satellite location management area.

[0025] Specifically, the ground-based core network first assigns a globally unique and permanently fixed identity to each satellite-borne network element, and associates this identity with the serial number of the low-Earth orbit satellite it carries, recording them together in a global network element identity mapping table maintained by the space-ground fusion core network. This forms the basis for a unified identity addressing across the entire network. Simultaneously, the high-Earth orbit core network, based on the pre-known ephemeris operational characteristics of the low-Earth orbit satellites, pre-assigns a dedicated temporary location identifier to all satellite-borne network elements that may enter its designated location management area. This pre-assigned identifier and its corresponding status bit are recorded in a separate network element identity mapping table for that location management area. The status bit is a non-binary management field used to accurately characterize the real-time management status of the corresponding satellite-borne network element within the current high-Earth orbit satellite location management area, such as "active" or "idle."

[0026] Furthermore, this pre-allocation mechanism moves the allocation of identifier resources to the system initialization or planning stage, avoiding the signaling interaction and latency caused by real-time dynamic allocation during the high-speed movement of satellite network elements. Network operators or the system can pre-plan and construct identifier resource mapping tables for all potential location management areas based on known satellite orbit parameters, thereby minimizing runtime management overhead.

[0027] Specifically, both the identity identifier and the temporary location identifier can be implemented using IP address format, but are not limited to this and can also be adapted to other network addressing schemes. Status bits can use multi-bit encoding (such as two binary codes "00", "01", "11") to represent various fine-grained states, thereby supporting more complex mobility management strategies. The key fields of the mapping table include at least the network element instance name, identity identifier, pre-allocated temporary location identifier, and status bits. Its design ensures the consistency of the mapping relationship, query efficiency, and atomicity of updates.

[0028] Specifically, the core application scenario for this method is a space-ground integrated network system composed of terrestrial mobile networks, high-orbit satellite networks, and low-orbit satellite networks. Particularly for dynamic environments where the high-speed movement of low-orbit satellites causes their network elements to frequently cross different high-orbit satellite location management areas, this method provides an efficient identification management framework.

[0029] Specifically, through a combined mechanism of "pre-allocation + status bit management," the temporary location identifier reassignment process, which is inevitably triggered during cross-region handover in traditional methods, is transformed into a lightweight update process that only updates the status bits of pre-existing identifiers. Simultaneously, the large-scale identifier lookup across satellite and ground that may be required when initiating data transmission is transformed into a mapping lookup that is prioritized and completed within the local high-orbit location management area. These two transformations significantly reduce control plane signaling overhead, decrease service establishment latency, and improve the management efficiency and scalability of the entire satellite-ground converged network in dynamic environments.

[0030] Furthermore, S1 includes: S11. Network element identity identifiers can be assigned in the form of IP addresses, but are not limited to the form of IP addresses.

[0031] Specifically, IP addresses are preferred. This is primarily because IP addresses are widely used and mature addressing and routing identifiers in the Internet and mobile communication networks. Their format is clearly defined, their allocation and management mechanisms are well-established, and they can be naturally integrated into the existing terrestrial network protocol stack, facilitating unified management and seamless interaction between space-to-ground networks at the addressing layer. Using IP addresses allows spaceborne network elements to be logically considered as standard nodes within the network, simplifying routing calculations, packet encapsulation, and forwarding processes.

[0032] Furthermore, the stipulation that it is "not limited to IP address format" reflects the openness and forward-looking nature of the technical solution. As network architecture evolves and new addressing technologies develop, such as content-based identifiers, distributed hash identifiers, or identifiers specific to future network protocols, the identity identification concepts defined in this method can be compatible and adapted. This design ensures that the core identifier management mechanism will not become obsolete due to changes in the specific form of the underlying identifiers, thus extending the solution's lifespan and applicability.

[0033] Furthermore, as key metadata, the core parameters of identity identifiers are global uniqueness, long-term stability, and manageability. Regardless of the specific form adopted, the identifier must be unique throughout the entire space-ground converged network and remain stable throughout the network element's lifecycle, serving as its unchangeable logical identity. The management layer needs to support efficient identifier allocation, mapping queries, and secure authentication.

[0034] Specifically, this design addresses application scenarios ranging from converged space-ground networks built on existing IP Internet technology to next-generation space information networks employing entirely new network architectures and protocols. It ensures that the identifier management framework meets the urgent needs for technological compatibility and practicality in current engineering practices, while also reserving sufficient flexibility for future technological upgrades and transformations.

[0035] Specifically, by decoupling the specific form of the identity identifier from the core mapping management mechanism, the mature ecosystem of existing IP technologies is utilized to reduce deployment complexity and cost. At the same time, the invention core is protected through abstract design, enabling the identifier management method to adapt to long-term technological development and avoiding the technical limitations that may result from being bound to a single identifier format. This enhances the technical resilience and long-term competitiveness of the overall solution.

[0036] S12, the global network element identifier mapping table of the space-ground converged core network can manage and maintain the identifiers and mapping information of two types of functional network elements: spaceborne network elements and ground network elements; among them, ground network elements are managed by the ground core network based on the existing identifier management mechanism.

[0037] Specifically, for satellite-borne network elements, this table records their fixed identity identifier, their associated low-Earth orbit satellite number, and the set of temporary location identifiers pre-assigned in each high-Earth orbit location management area, achieving an authoritative mapping between their global movement trajectory and logical location. For terrestrial network elements, their identification information (such as fixed IP addresses or device identifiers) is also managed in this global table, but their specific management logic—including identifier allocation, updates, and lifecycle maintenance—fully follows and integrates existing mature terrestrial core network identifier management mechanisms, such as existing processes based on DHCP, PCRF, or network management systems.

[0038] Furthermore, this "unified management, categorized policy implementation" design model provides network operators with a panoramic view of network element identification. Maintenance personnel can query and monitor the logical identity and location mapping status of all core network functional elements through a single management interface or system, without frequently switching between two independent management systems (satellite and ground). This greatly simplifies the operational complexity in hybrid network environments.

[0039] Furthermore, the key fields of this global mapping table need to possess sufficient versatility and scalability. For all network elements, their identity identifier and type identifier (spaceborne / terrestrial) are basic fields. For spaceborne network elements, it also needs to include exclusive fields such as the satellite number and pre-assigned location identifier set; while for terrestrial network elements, it may be associated with terrestrial network-specific attributes such as their geographical region and access point identifier. This structure ensures the completeness and efficiency of the data model.

[0040] Specifically, this method targets the core network control plane where deep integration of space and ground and collaborative operation of heterogeneous network elements are essential. Whether it is a spaceborne user plane network element needing to communicate with a ground data gateway, or a ground control plane network element needing to address spaceborne functions, the valid identifier of the peer can be obtained by querying this unified global mapping table, thereby achieving seamless end-to-end service establishment and data routing.

[0041] Specifically, firstly, it achieves logical unification of identifier management in heterogeneous space-ground networks, breaking down management silos and laying the foundation for the implementation of unified control strategies. Secondly, by utilizing existing mature mechanisms for ground network elements, it maximizes the protection of existing investments, reduces technology migration risks and deployment costs, ensures the smooth implementation and backward compatibility of the solution, and thus accelerates the commercial deployment process of space-ground converged networks.

[0042] S13. Temporary location identifiers pre-allocated by satellite network elements can be allocated in the form of IP addresses, but are not limited to the form of IP addresses.

[0043] Specifically, using IP addresses as temporary location identifiers enables onboard network elements to be seamlessly treated as a standard network access point within the high-orbit satellite location management area where they are located. This allows them to directly utilize existing mature IP routing protocol stacks to complete intra-domain and cross-domain data forwarding, greatly reducing the complexity and cost of introducing special routing mechanisms at the satellite link level.

[0044] Furthermore, explicitly defining the limitation as "not limited to IP address format" reserves future adaptability for this technical solution. With the development of new network architectures and aerospace information network technologies, dedicated location identification systems more suitable for highly dynamic, high-latency spatial network environments may emerge. The abstract design of this solution allows the specific representation of temporary location identifiers to be flexibly replaced or expanded into other types of network locators or topology identifiers in the future, without altering the core mechanism of "pre-allocation + state management."

[0045] Specifically, the temporary location identifier, as a key operational parameter, is primarily measured by its local validity, dynamic updability, and strong mapping to the identity identifier. It only has routing significance within its specific high-orbit satellite location management area, and its "active" or "idle" status is precisely indicated by the corresponding status bit, and it is strictly bound to the network element's globally fixed identity identifier in the mapping table.

[0046] Furthermore, this method is directly applied to each location management area under the jurisdiction of the high-orbit core network satellite. Within this relatively stable space coverage area, temporary location identifiers serve as the direct routing basis for onboard network elements to conduct local communication and data forwarding.

[0047] Specifically, on the one hand, by adopting a widely supported IP address format, this solution ensures plug-and-play compatibility with existing terrestrial network infrastructure and protocols, significantly reducing the integration difficulty and deployment cost of the space-ground converged network at the user plane data routing layer, and achieving a smooth technological transition. On the other hand, by maintaining the openness of the identifier format, it ensures that this core mechanism will not become obsolete due to the evolution of underlying network technologies, enhancing the overall architecture's forward-looking nature and technological vitality, and providing the necessary flexibility to cope with future network changes.

[0048] S14, the status bit of the pre-allocated temporary location identifier is a non-binary attribute. The specific status bits include: 00 indicates that the satellite network element is in an idle state, and 11 indicates that the satellite network element is in an active state.

[0049] Specifically, in the method described in this invention, the status bit configured for the pre-allocated temporary location identifier is designed to have a non-binary attribute at the technical implementation level. This means that the status bit is not a simple "valid / invalid" binary switch, but rather uses multi-bit encoding (e.g., two binary codes) to represent a set of ordered and well-defined management states. For example, state "00" is defined as the onboard network element being in an idle state, indicating that its pre-allocated temporary location identifier resources have been reserved but are not currently being used by the network element for data transmission; state "11" is defined as the onboard network element being in an active state, indicating that the network element is currently located within the current high-orbit satellite location management area, and its pre-allocated temporary location identifier is in an active and available state, which can be used for local routing and data forwarding. This multi-bit status encoding provides a foundation for achieving refined mobility management.

[0050] Furthermore, the non-binary state bits enable the high-orbit core network to perform more accurate state tracking and management of onboard network elements. Based on the prediction of low-orbit satellite ephemeris, the network can proactively and in advance update state bits, thereby achieving smooth and predictive handover management and avoiding service interruptions or signaling storms caused by sudden state changes.

[0051] Furthermore, as a critical control field, the status bit itself must be designed to meet the requirements of clear encoding, easy parsing, and efficient updating. Its value set (such as {00, 11} and reserved values) must be uniformly defined within the system. Status bit update operations must possess atomicity and consistency to ensure that, in a highly dynamic network environment, the status information obtained at any query time accurately reflects the real-time management affiliation of the network element.

[0052] Specifically, the core application scenarios of this method span the cross-regional movement of spaceborne network elements and the identifier query process when initiating services. During the movement, the dynamic change of status bits is the core indicator of the transfer of network element management rights; during the query process, status bits are the key basis for determining whether the counterpart's location identifier can be directly resolved in the local high-orbit location management area.

[0053] Specifically, firstly, the non-binary state bit mechanism elevates mobility management from a coarse "location identifier allocation / reclamation" to a refined "state machine-driven" approach, significantly reducing control plane signaling overhead and processing latency caused by frequent handovers. Secondly, it enhances the predictability and controllability of the system, supporting state-based optimization strategies (such as resource pre-scheduling), thereby improving the overall operational efficiency, reliability, and resource utilization of the space-ground converged network when facing highly dynamic spaceborne nodes.

[0054] S2, when a satellite-borne network element initiates data transmission to other satellite-borne network elements, it sends a position identifier mapping query request to the satellite of the high-orbit core network in the current high-orbit core network satellite position management area. The request message contains the identity identifier of the target satellite-borne network element. The high-orbit core network queries the pre-allocated temporary position identifier and status bit in the satellite-borne network element identifier mapping table in the current high-orbit core network satellite position management area based on the identity identifier of the target satellite-borne network element, and completes the satellite-borne network element identifier mapping query.

[0055] Specifically, an efficient addressing process is defined when a satellite-borne network element (source network element) needs to initiate data transmission to another satellite-borne network element (target network element). The source network element first initiates a position identifier mapping query request to the control entity corresponding to its current high-orbit core network satellite position management area—that is, the high-orbit core network satellite. This request message must carry the globally unique identifier of the target network element as the query key. Upon receiving the request, the high-orbit core network then searches its locally maintained "High-orbit Core Network Satellite Position Management Area Satellite-borne Network Element Identifier Mapping Table" using this identifier as the index.

[0056] Furthermore, the retrieval objective is to obtain two key pieces of information: first, the temporary location identifier pre-assigned to the target network element within its local location management area; and second, the current status bit corresponding to this identifier. The query is considered complete upon successfully obtaining both pieces of information. In particular, the status bit plays a decisive role in this process: if it indicates "active" (e.g., "11"), it means the target network element is currently managed by the same location management area, and the retrieved temporary location identifier can be directly used to establish a data path; if it indicates other statuses (e.g., "00" or others), it may trigger further collaborative query procedures.

[0057] Specifically, this design transforms traditional global queries, which may require direct access to the ground core network, into a localized or regionalized query operation. This aligns with the optimization principle of minimizing the number of signaling interactions between satellite and ground, given the long latency characteristics of satellite network links. The source network element only needs to interact with the high-orbit control node currently serving it, simplifying the protocol processing logic of the end network element.

[0058] Specifically, the performance of this query process critically depends on the query efficiency of the local mapping table and the real-time nature of status bit determination. Query request and response messages need to be designed with a lightweight format, including not only the necessary identity and location fields, but also control information such as transaction identifiers and result codes to ensure the reliability and traceability of the query.

[0059] Specifically, the core application scenario of this process is the initial stage of establishing a data connection between any two spaceborne network elements within a space-ground integrated network. Whether it is a data tunnel needing to be established between spaceborne user plane network elements, or a control plane network element needing to address a user plane network element, this process must first be used to resolve the valid operating address of the peer under the current network topology.

[0060] S3. When the onboard network element moves across the high-orbit core network satellite position management area with the low-orbit satellite, the corresponding high-orbit core network before and after the high-orbit core network satellite position management area switch updates the temporary position identifier status bit of the onboard network element in the onboard network element identifier mapping table in the corresponding high-orbit core network satellite position management area, thus completing the update of the position identifier status of the onboard network element in the two high-orbit core network satellite position management areas.

[0061] Furthermore, when a satellite-borne network element moves across management areas, the global update is not performed by a single entity. Instead, the high-orbit core network of the source management area and the high-orbit core network of the target management area operate their respective local mapping tables in an orderly manner. By sequentially updating the status bits of the same satellite-borne network element in their respective tables (updating to idle status in the source area and active status in the target area), the two jointly complete a seamless transfer of management authority and status refresh in spatial logic.

[0062] Specifically, this collaborative update process can be driven by predictable ephemeris data from low-Earth orbit satellites. The network control plane can pre-calculate the handover timeline, thereby coordinating the two high-Earth orbit core network nodes to perform status bit update operations in a near-synchronous or minimally timed manner. This achieves tight coupling between network management state and physical location changes, making the transfer of management authority smooth and predictable for ongoing data services, and minimizing the control plane impact of the handover.

[0063] Specifically, the successful execution of this process depends on several key metrics: the transmission latency and reliability of state update commands between the two high-orbit core networks, the atomicity and completion time of their respective local update operations, and the consistency of global state synchronization with the ground core network after the update is completed. These metrics collectively determine the latency, success rate, and final network state consistency level of the entire handover process.

[0064] Furthermore, this process is specifically designed to address the frequent cross-high-orbit location management area handover events that inevitably occur for satellite network elements in highly dynamic satellite networks. It is one of the core control processes for mobility management in space-ground converged networks, ensuring that network elements maintain their network reachability and manageability amidst constantly changing network topologies.

[0065] Furthermore, S3 includes: S31, the high-orbit core network corresponding to the satellite position management area of ​​the high-orbit core network before the switchover will update the status bit corresponding to the temporary position identifier of the satellite network element in the satellite network element identifier mapping table of the high-orbit core network satellite position management area to the deactivated state, indicating that the satellite network element has left the high-orbit core network satellite position management area.

[0066] Specifically, when a low-Earth orbit (LEO) satellite-borne network element is about to leave or begins to leave the location management area of ​​a high-Earth orbit (HEO) core network satellite to which it currently belongs, the corresponding HEO core network control entity is responsible for performing a proactive identifier status update. The core operation involves accessing and modifying its locally maintained "High-Earth Orbit Core Network Satellite Location Management Area Onboard Network Element Identifier Mapping Table," updating the status bit of the pre-allocated temporary location identifier corresponding to the departing network element from a "active" state (e.g., "11") to a "idle" state (e.g., "00"). This change in status bit formally declares the termination of the HEO core network satellite's real-time management responsibility for the network element at the data level.

[0067] Furthermore, this update is often predictive. Based on known precise ephemeris data from low-Earth orbit satellites, the high-orbit core network can pre-calculate and determine the departure time window of onboard network elements at the network level. This allows for the deactivation and updating of status bits in advance or in real-time, before or during the physical handover. This achieves a "soft release" of management authority, avoiding query errors or resource suspensions caused by the sudden disappearance of network elements, and creating an orderly context for subsequent handover procedures.

[0068] Specifically, this step focuses on the atomic update of a specific field: the state bit. The triggering conditions for the update (such as prediction-based triggering based on ephemeris or measurement report triggering), the specific target state value to be updated (such as from "11" to "00"), and the timing relationship between the update operation and the synchronization of the state with the ground core network all require precisely defined protocol behaviors and performance indicators to ensure the consistency of the state across the entire network.

[0069] Furthermore, this step occurs in a specific application scenario: the initial moment when the onboard network element, moving with the low-Earth orbit satellite, triggers a handover of the high-Earth orbit position management area. It is the first critical network-side action in the handover control signaling process, marking the formal commencement of the mobility management event in the control plane.

[0070] Specifically, firstly, it replaces the complex "temporary location identifier recycling and context deletion" process that may be required in traditional mechanisms with lightweight local state bit flipping, greatly simplifying the operational complexity and processing latency of departure processing. Secondly, timely and accurate state bit deactivation updates prevent other network elements from subsequently initiating invalid queries to the location management area for the departed network element, reducing erroneous signaling, optimizing the management efficiency of network resources, and laying the foundation for seamless handover.

[0071] S32, the high-orbit core network corresponding to the satellite position management area of ​​the high-orbit core network after the switch will update the status bit corresponding to the temporary position identifier of the satellite network element in the satellite network element identifier mapping table of the high-orbit core network satellite position management area to the active state, indicating that the satellite network element has been managed by the high-orbit core network satellite position management area.

[0072] Furthermore, when a satellite-borne network element enters a new high-orbit core network satellite position management area along with a low-orbit satellite, the high-orbit core network control entity corresponding to that target area performs a crucial identifier status takeover. Its core operation involves accessing its locally maintained mapping table and updating the status bit corresponding to the temporary location identifier pre-assigned to the satellite-borne network element within this area to a state indicating "activation" (e.g., "11"). This update operation formally establishes the high-orbit core network satellite's real-time management rights over the entering network element at the protocol and data levels, signifying the completion of the handover.

[0073] Specifically, this activation operation is also predictive and proactive. The target high-orbit core network can predict the arrival of network elements based on ephemeris data, prepare the context in advance, and activate the status bits immediately or in advance after confirming that the network element has entered its management scope. This ensures that the moment the network element completes the switchover at the physical layer, its management at the network logic layer is also ready, achieving a "seamless takeover" of management rights and creating conditions for the rapid recovery of service flows.

[0074] Specifically, the key to the successful execution of this step lies in the orderly coordination with the release of the previous management area state, and the timeliness and reliability of state synchronization with the ground core network after the update. The activation operation itself must be atomic, ensuring that the network's perception of the management rights of the network element is unique and clear at any given time.

[0075] Specifically, this step occurs in a particular application scenario: the decisive moment when the onboard network element completes its movement across high-orbit position management areas and is officially taken over by the new area. It marks the successful conclusion of a complete handover event in the control plane.

[0076] Specifically, by transforming the traditional reconfiguration process of "applying for and allocating a new temporary location identifier in a new area" into a one-time activation of the status bits of a pre-existing identifier, the signaling interaction and waiting latency during the handover process are completely eliminated. This enables onboard network elements to restore addressability and service transmission capabilities in the new area almost instantaneously after handover, greatly improving the efficiency of mobility management and ensuring the continuity of upper-layer services and user experience.

[0077] Specifically, it completely transforms the essential and costly "temporary location identifier reassignment" process in traditional mobility management into two extremely lightweight, local "pre-assigned identifier status bit flipping" operations. This transformation fundamentally eliminates the identifier allocation signaling interaction, resource negotiation, and configuration latency during the handover process, significantly reducing control plane signaling overhead and processing load. This enables ultra-high-speed mobile spaceborne network elements to achieve near-instantaneous handover of management rights and maintenance of service continuity, thereby significantly improving the robustness, efficiency, and scalability of the entire space-ground converged network in extreme dynamic environments.

[0078] The mapping query and update method for spaceborne user plane network element identifiers in the space-ground converged network of this invention transforms the traditional dynamic identifier allocation and remote query process into local state update and efficient query by pre-allocating temporary location identifiers and a collaborative management mechanism for status bits. This effectively solves the core problems of high addressing signaling overhead, prolonged handover time, and low management efficiency caused by the high dynamic movement of spaceborne network elements in existing technologies. This method achieves end-to-end optimization from identifier pre-allocation, status tracking, localized addressing to seamless handover, significantly reducing control plane load and service establishment latency. While improving network resource utilization efficiency, it ensures service continuity and enhances the overall management efficiency and scalability of the space-ground converged network in wide-area coverage and high-dynamic scenarios.

[0079] Example 2 To achieve the above invention, embodiments of the present invention also provide another method for mapping, querying, and updating satellite-borne network element identifiers in a satellite-to-ground network, including: The embodiments of this invention take the Spaceborne User Plane Function (S-UPF) network element as an example, and propose another method for mapping, querying, and updating the identifier of spaceborne network elements in a space-to-ground network. The network architecture of the research scenario is as follows: Figure 2As shown, the space-ground integrated core network consists of three parts: a ground core network, a high-orbit core network, and a low-orbit core network. The ground core network acts as a ground control node, deploying complete core network functions and storing global onboard user plane function network element information. The high-orbit core network (containing no fewer than three high-orbit satellites) acts as an onboard control node, with each high-orbit satellite independently deploying complete control plane functions, storing the status of onboard user plane network element functions deployed on low-orbit satellites, and dynamically managing the onboard user plane network element functions within the current location management area. The low-orbit core network deploys onboard user plane network element functions and is responsible for carrying user plane service data. The ground core network control plane network element functions and the high-orbit core network network element functions together form the space-ground integrated core network control plane, collaboratively completing the initialization registration, identifier allocation, mapping management, and mobility control of the low-orbit onboard user plane network element functions.

[0080] In embodiments of the present invention, an identifier mapping system that separates identity identifiers and location identifiers is adopted in the space-ground integrated core network to realize dynamic management of identity identifiers and location identifiers of low-Earth orbit satellite-borne user plane network elements. The hierarchical identifier mapping relationship mainly includes: Specifically, the high-orbit core network maintains the mapping relationship between the identity identifiers and temporary location identifiers of onboard network elements within the satellite location management area through the onboard network element identifier mapping table (example shown in Table 1). The onboard network element identifier mapping table consists of fields such as onboard network element name, onboard network element identity identifier, onboard network element location identifier, and location identifier status bit. The onboard network element name, onboard network element identity identifier, and onboard network element location identifier fields remain unchanged after the onboard network element is initialized. The location identifier status bit is dynamically updated as the low-orbit satellite moves. The location identifier status bit field indicates the active or idle status of the onboard network element within the current high-orbit satellite's corresponding location management area. The onboard network element location identifier field value is pre-assigned by the high-orbit control plane nodes and is only effective within the location management area corresponding to the high-orbit core network satellite.

[0081] Table 1. Mapping Table of Satellite Position Management Area X-Shipborne Network Element Identifiers for High-Orbit Core Network - Fields

[0082] Further, the fields in Table 1 are explained as follows: **Satellite Network Element Name:** The instance ID corresponding to the satellite network element, used to distinguish each satellite network element instance; **Satellite Network Element Identity:** A unique and fixed identity assigned to each satellite network element by the ground core network. This identity can be, but is not limited to, an IP address; **Satellite Network Element Location Identifier:** A temporary location identifier assigned to each satellite network element by the high-orbit core network satellite during initialization. This location identifier can be, but is not limited to, an IP address; **Location Identifier Status Bit:** This indicates the identification status of the satellite network element within the corresponding location management area of ​​the high-orbit core network satellite. This status bit has a non-binary attribute: a value of 00 indicates that the satellite network element is in an idle state, a value of 11 indicates that the satellite network element is in an active state, and other values ​​can be reserved for the high-orbit core network to manage the status of the satellite network element's location identifier.

[0083] Specifically, the ground core network maintains the mapping relationship between the identity identifiers and location identifiers of satellite-borne network elements globally through a global network element identifier mapping table (example shown in Table 2). The global network element identifier mapping table consists of fields such as network element name, network element identity identifier, affiliated low-Earth orbit satellite number, current satellite location management area name, location identifier for high-Earth orbit core network satellite location management area 1, location identifier for high-Earth orbit core network satellite location management area 2, and location identifier for high-Earth orbit core network satellite location management area 3. The network element name, network element identity identifier, and affiliated low-Earth orbit satellite number fields are written during the allocation of satellite-borne network element location identifiers. The network element identity identifier is a unique and fixed identifier uniformly assigned by the ground core network. During the allocation of satellite-borne network element identifiers, the satellite location management area corresponding to the high-Earth orbit core network pre-assigns temporary location identifiers to all satellite-borne network elements, and each satellite-borne network element is pre-assigned a fixed temporary location identifier in the location management area of ​​each high-Earth orbit core network satellite. The Current Location Area Name field is used to maintain the current location management area to which the satellite network element belongs and to indicate the location identifier used by the current satellite network element.

[0084] Table 2 Global Network Element Identifier Mapping Table for Satellite-Ground Convergence Core Network - Fields

[0085] Further, the fields in Table 2 are explained as follows: Network Element Name: The instance ID corresponding to the network element, used to distinguish each network element instance; Network Element Identifier: The ground core network assigns a unique and fixed identifier to the satellite-borne network element. The identifier can be, but is not limited to, an IP address; Belonging Low-Earth Orbit Satellite Number: The low-Earth orbit satellite number to which the satellite-borne network element's running instance belongs; Current Satellite Position Management Area Name: The name of the position management area corresponding to the position management area to which the satellite-borne network element moves with the low-Earth orbit satellite at the current moment. If it is prefixed with GEO, it indicates that the satellite-borne network element is managed by the corresponding high-Earth orbit core network satellite position management area. If it is empty, it indicates that it is currently managed by the ground position management area. High-Earth orbit core network satellite position management area 1 position identifier / High-Earth orbit core network satellite position management area 2 position identifier / High-Earth orbit core network satellite position management area 3 position identifier: Each satellite-borne network element is configured with a temporary position identifier in the position management area of ​​each high-Earth orbit core network satellite. The position identifier can be, but is not limited to, an IP address.

[0086] The embodiments of this invention are geared towards scenarios in a space-ground integrated core network where the ground core network control plane and the high-orbit core network control plane collaboratively manage the low-orbit core network user plane network elements. For example... Figure 3 As shown, the core network mapping query and update communication process in this invention mainly includes: Specifically, the network element location identifier mapping query process involves a scenario where, before initiating data forwarding between Spaceborne User Plane Function (S-UPF) network elements and other S-UPF network elements, a location identifier mapping query is performed through the high-orbit location management area. The network element location identifier mapping update process involves a scenario where, within the high-orbit location management area, S-UPF network elements update their location identifier status.

[0087] The network element location identifier mapping query process proposed in this embodiment of the invention is as follows: Figure 3 , 4 As shown.

[0088] Furthermore, the following is the specific process for querying the network element location identifier mapping: 1. Before the onboard user plane network element S-UPF-1 and onboard user plane network element S-UPF-2 forward data, if the onboard user plane network element S-UPF-1 and onboard user plane network element S-UPF-2 establish a connection for the first time and there is no temporary satellite position identifier for the current onboard user plane network element, then the onboard user plane network element S-UPF-1 carries the identity identifier of the onboard user plane network element S-UPF-2 and sends a position identifier mapping query to the high-orbit core network to which it belongs.

[0089] 2. Based on the identity identifier of the onboard user plane network element S-UPF-2 carried in the location identifier query request, the high-orbit core network performs a location identifier mapping query in the onboard network element identifier mapping table of the high-orbit location management area to find the location identifier corresponding to the identity identifier. If the status bit identifier field value of the corresponding onboard network element location identifier in the table is 11, it indicates that the onboard user plane network element S-UPF-2 and the onboard user plane network element S-UPF-1 are in the same high-orbit location management area, and then proceed directly to step 4; otherwise, proceed to step 3.

[0090] 3. The high-orbit core network forwards the location identifier query request to the ground core network. The ground core network uses the identity identifier of the spaceborne user plane network element S-UPF-2 to query the global network element identifier mapping table of the space-ground fusion core network, determines the current location identifier used by the spaceborne user plane network element S-UPF-2 based on the current location management area name field, and returns the query result to the high-orbit core network.

[0091] 4. The high-orbit core network returns a location identifier mapping query response to the onboard user plane network element S-UPF-1. The response signaling includes the identity identifier and location identifier of the onboard user plane network element S-UPF-2.

[0092] 5. The complete session data stream is transmitted using the identity identifiers of the onboard user plane network elements at both ends, and the network layer uses the location identifiers of the onboard user plane network elements S-UPF-1 and S-UPF-2 for data forwarding. This invention introduces a caching mechanism during the query process, allowing the onboard user plane network element sender to locally cache part of the mapping results, reducing subsequent query overhead.

[0093] The network element location identifier mapping update process proposed in this embodiment of the invention is as follows: Figure 5 , 6 As shown.

[0094] Furthermore, the specific process for updating location identifiers is as follows: When a user plane network element on a low-Earth orbit (LEO) satellite moves across a high-Earth orbit (HEO) location management area, such as from the location management area corresponding to HEO core network 1 satellite to the location management area corresponding to HEO core network 2 satellite, HEO core network 1 first predicts the departure of the user plane network element based on the ephemeris characteristics of the LEO satellite. It then updates the identifier status bit of the network element in the HEO location management area 1 network element mapping table to 00, indicating that the network element is idle within the HEO core network 1 satellite location management area. HEO core network 1 then synchronously updates the identifier status bit of the network element in the HEO location management area 1 network element identifier mapping table to the ground core network. HEO core network 2, based on the LEO satellite ephemeris characteristics, predicts that the user plane network element is entering the location management area corresponding to its own core network satellite. HEO core network 2 then updates the identifier status bit of the network element in the HEO location management area 2 network element mapping table to 11, indicating that the network element is active within the HEO core network 2 satellite location management area. At the same time, the high-orbit core network 2 distributes the temporary location identifiers pre-allocated by the corresponding location management area of ​​the satellite to the onboard network element; the high-orbit core network 2 also updates the status of the onboard network element location identifiers in the high-orbit location management area 2 onboard network element identifier mapping table to the ground core network.

[0095] This invention proposes another method for mapping, querying, and updating satellite-borne network element identifiers in a space-to-ground network. By constructing a hierarchical identifier mapping system that coordinates the terrestrial core network and the high-orbit core network, it effectively solves the core challenges of complex location management and high signaling overhead for satellite-borne network elements in highly dynamic scenarios. Based on an identity and location identifier separation architecture, and utilizing a pre-allocated identifier and status bit mechanism, it achieves lightweight status updates for onboard local queries and cross-regional handovers, thereby significantly improving the location management efficiency, service response speed, and resource utilization efficiency of the entire network. This provides key technical support for building an efficient and reliable space-to-ground converged core network.

[0096] Example 3 To achieve the above invention, embodiments of the present invention also provide application scenarios for the mapping query and update method and apparatus for satellite-borne network element identifiers in satellite-to-ground networks, including: This invention relates to specific embodiments of the method and apparatus designed for use in a space-ground converged core network scenario. Taking a Spaceborne User Plane Function (S-UPF) network element as an example, this embodiment includes a network element location identifier mapping query process before S-UPF-1 sends data to S-UPF-2, and a network element location identifier mapping update process when S-UPF-1 moves across GEO location management areas. In this embodiment, both the identity identifier and location identifier of the spaceborne user plane network element are in the form of IP addresses. In specific application scenarios, the identifier can be, but is not limited to, IP addresses.

[0097] Before the start of this embodiment's process, the space-ground converged core network has completed the identifier allocation and activation processes for the spaceborne user plane network elements. The space-ground converged core network has also completed the initialization of the global network element identifier mapping table and the high-orbit position management area 1 / 2 / 3 spaceborne network element identifier mapping tables. This embodiment mainly involves the global network element identifier mapping table and the high-orbit position management area 1 / 2 spaceborne network element identifier mapping tables, as shown in Tables 3 / 4 / 5 respectively.

[0098] Table 3 Global Network Element Identifier Mapping Table for Satellite-Ground Convergence Core Network

[0099] Table 4. Mapping Table of Satellite Position Management Area 1 Satellite-borne Network Element Identifiers for High-Orbit Core Network

[0100] Table 5. Mapping Table of Satellite Position Management Area 2 Satellite-borne Network Element Identifiers for High-Orbit Core Network

[0101] Furthermore, the network element location identifier mapping query process: The location identifier mapping query process is completed before the onboard user plane network element S-UPF-1 initiates data interaction with the onboard user plane network element S-UPF-2. The specific process is as follows: Figure 7 As shown.

[0102] Step 1: The onboard user plane network element S-UPF-1 first initiates a location identifier mapping query request to the high-orbit core network 2 to query the current location identifier corresponding to the identity identifier 10.112.0.2 of the onboard user plane network element S-UPF-2.

[0103] Step 2: The high-orbit core network 2 queries the satellite-borne network element identifier mapping table of the high-orbit location management area 2 to find the location identifier corresponding to the satellite-borne user plane network element S-UPF-2 identity identifier 10.112.0.2. The status bit identifier is 11, which means that the current satellite-borne user plane network element S-UPF-2 is also in the location management area corresponding to the high-orbit core network 2. The corresponding location identifier in the current table is returned as the query response.

[0104] Step 3: The high-orbit core network 2 sends the location identifier field value 172.12.0.15 corresponding to the spaceborne user plane network element S-UPF-2 to the spaceborne user plane network element S-UPF-1.

[0105] Step 4: The onboard user plane network element S-UPF-1 establishes a data path with the onboard user plane network element S-UPF-2 using a temporary location identifier.

[0106] Further, the network element location identifier mapping update process: When the onboard user plane network element S-UPF-1 moves with the low-Earth orbit satellite 01 from high-Earth orbit location management area 1 to high-Earth orbit location management area 2, the location identifier status update process is triggered. Note: In this invention, the user plane network element does not involve the update process of the user plane session during the movement across location areas. The specific process is as follows: Figure 8 As shown.

[0107] Step 1: Based on the ephemeris characteristics of low-orbit satellites, the high-orbit core network 1 updates the identifier status bit of the onboard user plane network element S-UPF-1 that is about to leave the location management area, and updates the value of the identifier field of the location identifier status bit in the high-orbit location management area 1 onboard network element identifier mapping table from 11 to 00.

[0108] Step 2: The high-orbit core network 1 synchronizes the updated status bit identifier information to the ground core network.

[0109] Step 3: Based on the ephemeris characteristics of low-Earth orbit satellites, the high-orbit core network 2 updates the location identifier status of the onboard user plane network element S-UPF-1 entering the location management area. The high-orbit core network 2 updates the pre-allocated temporary location identifier corresponding to the onboard user plane network element S-UPF-1 in the high-orbit location management area 2 onboard network element identifier mapping table to the onboard user plane network element S-UPF-1, and simultaneously updates the location identifier status bit identifier field value of the onboard user plane network element S-UPF-1 in the high-orbit location management area 2 onboard user plane network element identifier mapping table to 11.

[0110] Step 4: The high-orbit core network 2 will synchronize the updated status bit identification information to the ground core network.

[0111] After the S-UPF-1 identifier of the satellite user plane network element is updated, the global network element identifier mapping table of the satellite-ground converged core network is shown in Table 6, the satellite network element identifier mapping table of high orbit position management area 1 is shown in Table 7, and the satellite network element identifier mapping table of high orbit position management area 2 is shown in Table 8.

[0112] Table 6 Global Network Element Identifier Mapping Table for Satellite-Ground Convergence Core Network

[0113] Table 7 Mapping Table of Satellite-borne Network Element Identifiers for High-Orbit Position Management Area 1

[0114] Table 8. Mapping Table of Satellite-borne Network Element Identifiers for High-Orbit Position Management Area 2

[0115] The application scenarios of the method and apparatus for mapping and updating satellite network element identifiers in a space-to-ground network according to embodiments of the present invention fully demonstrate the workflow and final results of the proposed identifier mapping method in a real environment. Based on pre-allocated fixed identifiers and a collaborative state management mechanism, this method completely solves the problems of high signaling overhead and long service latency caused by frequent space-to-ground queries and identifier reassignment in traditional solutions. Through localized queries and lightweight state updates, it achieves a significant leap in network element location management efficiency. While ensuring global consistency, it greatly optimizes network resource utilization and service response speed, providing solid technical verification and practical basis for building an efficient, reliable, and scalable space-to-ground converged core network.

[0116] Example 4 To achieve the above invention, such as Figure 9 As shown, this embodiment takes the Spaceborne User Plane Function (S-UPF) network element as an example and provides a mapping query and update device 10 for the identifier of a spaceborne network element in a space-to-ground network. The device 10 includes: The identifier pre-allocation and status bit setting module 100 is used by the ground core network to assign unique and fixed identity identifiers to satellite-borne network elements, and to associate the identity identifiers with the low-Earth orbit satellite numbers to which the satellite-borne network elements belong, storing them in the global network element identifier mapping table of the space-ground fusion core network. Based on the ephemeris characteristics of low-Earth orbit satellites, the high-Earth orbit core network pre-allocates temporary location identifiers for each satellite-borne network element within the location management area of ​​each high-Earth orbit core network satellite, and sets a status bit corresponding to the pre-allocated temporary location identifier in the satellite-borne network element identifier mapping table of the high-Earth orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the satellite-borne network element in the corresponding high-Earth orbit core network satellite location management area.

[0117] The identifier mapping query module 200 is used to send a position identifier mapping query request to the high-orbit core network satellite in the current high-orbit core network satellite position management area when the satellite-borne network element initiates data transmission to other satellite-borne network elements. The request message contains the identity identifier of the target satellite-borne network element. The high-orbit core network queries the pre-allocated temporary position identifier and status bit in the satellite-borne network element identifier mapping table in the current high-orbit core network satellite position management area according to the identity identifier of the target satellite-borne network element, and completes the satellite-borne network element identifier mapping query.

[0118] The identifier mapping update module 300 is used to update the temporary position identifier status bit of the satellite network element in the satellite network element identifier mapping table in the high-orbit core network before and after the high-orbit core network satellite position management area is switched when the satellite network element moves with the low-orbit satellite across the high-orbit core network satellite position management area, thereby completing the update of the position identifier status of the satellite network element in the two high-orbit core network satellite position management areas.

[0119] This invention discloses a mapping device for the location identifiers of spaceborne user plane network elements in a space-ground converged network. Through modular design, it achieves efficient collaborative management of these location identifiers. Based on a core mechanism of pre-allocation and status bit coordination, the device organically integrates functions such as identifier allocation, status query, cross-regional handover updates, and space-ground synchronization, effectively solving the core problems of frequent signaling interactions and delayed location management in traditional space-ground networks. Its integrated architecture significantly reduces the complexity of system implementation and the burden of operation and maintenance. While improving the real-time performance of location identifier queries and updates, it ensures the consistency and reliability of the global mapping status, thus providing a directly deployable device-level solution for building a high-performance, highly reliable space-ground converged core network.

[0120] To implement the methods of the above embodiments, the present invention also provides a computer device, such as... Figure 10 As shown, the computer device 600 includes a memory 601 and a processor 602; wherein, the processor 602 reads the executable program code stored in the memory 601 to run a program corresponding to the executable program code, so as to implement the various steps of the mapping method for the location identifier of the spaceborne user plane network element in the space-ground fusion network described above.

[0121] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon. When the program is executed by a processor, it implements the mapping query and update method and apparatus for satellite network element identifiers in the satellite-to-ground network as described in the foregoing embodiments.

[0122] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0123] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

Claims

1. A method for mapping, querying, and updating satellite-borne network element identifiers in a satellite-to-ground network, characterized in that, include: S1, the ground core network assigns a unique and fixed identity to each satellite network element, and stores the identity as associated with the low-Earth orbit satellite number to which the satellite network element belongs in the global network element identity mapping table of the satellite-ground fusion core network. Based on the ephemeris characteristics of low-Earth orbit satellites, the high-Earth orbit core network pre-assigns a temporary location identifier for each satellite network element in the location management area of ​​each high-Earth orbit core network satellite, and sets a status bit corresponding to the pre-assigned temporary location identifier in the satellite network element identity mapping table of the high-Earth orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the satellite network element in the corresponding high-Earth orbit core network satellite location management area. S2, when a satellite-borne network element initiates data transmission to other satellite-borne network elements, it sends a position identifier mapping query request to the satellite of the high-orbit core network in the current high-orbit core network satellite position management area. The request message contains the identity identifier of the target satellite-borne network element. The high-orbit core network queries the pre-allocated temporary position identifier and status bit in the satellite-borne network element identifier mapping table in the current high-orbit core network satellite position management area according to the identity identifier of the target satellite-borne network element, and completes the satellite-borne network element identifier mapping query. S3. When the onboard network element moves across the high-orbit core network satellite position management area with the low-orbit satellite, the corresponding high-orbit core network before and after the high-orbit core network satellite position management area switch updates the temporary position identifier status bit of the onboard network element in the onboard network element identifier mapping table in the corresponding high-orbit core network satellite position management area, thus completing the update of the position identifier status of the onboard network element in the two high-orbit core network satellite position management areas.

2. The method as described in claim 1, characterized in that, The ground core network assigns unique and fixed identifiers to each satellite-borne network element, and stores these identifiers in a global network element identifier mapping table of the satellite-ground fusion core network, associating them with the low-Earth orbit (LEO) satellite number to which the satellite-borne network element belongs. Based on the ephemeris characteristics of LEO satellites, the high-Earth orbit (HEO) core network pre-assigns temporary location identifiers to each satellite-borne network element within the location management area of ​​each HEO core network satellite. A status bit corresponding to the pre-assigned temporary location identifier is set in the satellite-borne network element identifier mapping table of the HEO core network satellite location management area. This status bit characterizes the activation and idle status of the satellite-borne network element within the corresponding HEO core network satellite location management area, including: S11. Network element identity identifiers can be assigned in the form of IP addresses, but are not limited to the form of IP addresses; S12, the global network element identifier mapping table of the space-ground converged core network can manage and maintain the identifiers and mapping information of two types of functional network elements: spaceborne network elements and ground network elements; among them, ground network elements are managed by the ground core network based on the existing identifier management mechanism; S13. Temporary location identifiers pre-allocated by spaceborne network elements can be allocated in the form of IP addresses, but are not limited to the form of IP addresses; S14, the status bit of the pre-allocated temporary location identifier is a non-binary attribute. The specific status bits include: 00 indicates that the satellite network element is in an idle state, and 11 indicates that the satellite network element is in an active state.

3. The method as described in claim 1, characterized in that, When a satellite-borne network element moves across a high-orbit core network satellite position management area with a low-orbit satellite, the corresponding high-orbit core networks before and after the high-orbit core network satellite position management area switch update the temporary position identifier status bit of the satellite-borne network element in the corresponding high-orbit core network satellite position management area's satellite-borne network element identifier mapping table, completing the update of the satellite-borne network element's position identifier status in the two high-orbit core network satellite position management areas, including: S31, the high-orbit core network corresponding to the satellite position management area of ​​the high-orbit core network before the switchover will update the status bit corresponding to the temporary position identifier of the satellite network element in the satellite network element identifier mapping table of the high-orbit core network satellite position management area to the deactivated state, indicating that the satellite network element has left the high-orbit core network satellite position management area; S32, the high-orbit core network corresponding to the satellite position management area of ​​the high-orbit core network after the switch will update the status bit corresponding to the temporary position identifier of the satellite network element in the satellite network element identifier mapping table of the high-orbit core network satellite position management area to the active state, indicating that the satellite network element has been managed by the high-orbit core network satellite position management area.

4. A device for mapping, querying, and updating satellite-borne network element identifiers in a satellite-to-ground network, characterized in that, include: The identifier pre-allocation and status bit setting module is used by the ground core network to assign a unique and fixed identity identifier to the satellite network element, and to associate the identity identifier with the low-Earth orbit satellite number to which the satellite network element belongs and store it in the global network element identifier mapping table of the space-ground fusion core network. Based on the ephemeris characteristics of low-Earth orbit satellites, the high-Earth orbit core network pre-allocates a temporary location identifier for each satellite network element in the location management area of ​​each high-Earth orbit core network satellite, and sets a status bit corresponding to the pre-allocated temporary location identifier in the satellite network element identifier mapping table of the high-Earth orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the satellite network element in the corresponding high-Earth orbit core network satellite location management area. The identifier mapping query module is used to send a location identifier mapping query request to the high-orbit core network satellite in the current high-orbit core network satellite position management area when a satellite-borne network element initiates data transmission to other satellite-borne network elements. The request message contains the identity identifier of the target satellite-borne network element. The high-orbit core network queries the pre-allocated temporary location identifier and status bit in the satellite-borne network element identifier mapping table in the current high-orbit core network satellite position management area based on the identity identifier of the target satellite-borne network element, and completes the satellite-borne network element identifier mapping query. The identifier mapping update module is used to update the temporary position identifier status bit of the satellite network element in the satellite network element identifier mapping table in the corresponding high-orbit core network before and after the high-orbit core network satellite position management area is switched when the satellite network element moves with the low-orbit satellite across the high-orbit core network satellite position management area. This completes the update of the position identifier status of the satellite network element in the two high-orbit core network satellite position management areas.

5. An electronic device, comprising: processor; The memory stores executable instructions; when the processor executes the instructions, it implements the mapping query and update method for satellite network element identifiers in a satellite-to-ground network as described in any one of claims 1-3.

6. A computer-readable storage medium storing a computer program, which, when executed by a processor, implements the mapping query and update method for satellite network element identifiers in a satellite-to-ground network as described in any one of claims 1-3.

Images