Method and apparatus for assigning location identity of a satellite user plane function network element

Abstract

The application discloses a satellite-borne user plane function network element position identification allocation method and device, and belongs to the technical field of satellite mobile communication. A satellite ephemeris pre-allocates a temporary position identification for a satellite-borne user plane function network element based on a satellite-ground core network, and sets state bits for the temporary position identification to represent active and idle states respectively; when the satellite-borne user plane function network element enters a position management area of a high-orbit core network satellite, a position identification state update request is sent to a corresponding high-orbit core network satellite, the state bits of the position identification in a high-orbit identification mapping table are updated, and communication reachability of the satellite-borne user plane function network element is realized. The application realizes pre-allocation and state management of the position identification of the satellite-borne user plane function network element, and improves the mobility management capability and communication reliability of the satellite-ground integrated core 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 allocating location identifiers for satellite user plane functional network elements. Background Technology

[0002] As mobile communication technology evolves towards full coverage and ubiquitous connectivity, space-ground converged networks have become a key infrastructure for expanding the boundaries of terrestrial network services. In this architecture, the collaborative networking of high-orbit and low-orbit satellites provides crucial support for achieving wide-area, continuous, and reliable communication services. Simultaneously, deploying some terrestrial network functions on satellites, particularly access network and core network user plane functions, has become an important research and practical direction for academia and industry in promoting space-ground integration, and related technical solutions are gradually entering the international standardization process.

[0003] However, while satellite-based network functions bring coverage advantages, they also introduce significant challenges. Unlike the relatively stable topology of traditional terrestrial networks, spaceborne platforms such as low-Earth orbit satellites exhibit high-speed movement, resulting in high dynamism for the core network user plane function (S-UPF) network elements carried by them. This high dynamism places unprecedented demands on existing network management systems based on terrestrial static or quasi-static assumptions, especially in areas such as identifier management, location tracking, and control plane coordination. Existing mechanisms struggle to effectively adapt in terms of real-time performance, signaling overhead, and resource efficiency.

[0004] Specifically, in the field of identifier management, existing terrestrial mobile communication networks typically employ a multi-level decoupled identifier mapping system, separating the fixed identity identifier (ID) of a network element from its variable location identifier (Locator). While this scheme achieves a certain degree of logical decoupling between identity and location, its initial design did not fully consider the complex characteristics of multi-layered satellite control architecture, dynamic changes in inter-satellite links, and frequent cross-domain movements of onboard network elements in space-ground converged networks. Under the traditional mechanism, the temporary location identifier of a spaceborne user plane function (S-UPF) network element is usually assigned by its current location management area (such as a terrestrial core network or a high-orbit core network satellite). Whenever a network element switches to a new location management area, a complete temporary location identifier allocation process must be executed, involving multiple satellite-ground or inter-satellite signaling interactions. This process is frequently triggered in highly dynamic scenarios, leading to heavy network signaling load, increased location update latency, and ineffective reservation and fragmentation of identifier resources. This severely restricts the efficient utilization of limited communication and computing resources in space-ground converged networks, becoming one of the key bottlenecks restricting their large-scale deployment and efficient operation.

[0005] Therefore, there is an urgent need for an efficient method for the allocation and management of identifiers for satellite-borne user plane functional network elements in the satellite-ground converged core network, in order to address the shortcomings of existing technologies in terms of dynamism, resource efficiency, and signaling overhead. 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 issue, this invention proposes a method for allocating location identifiers for spaceborne user plane functional network elements. Through collaboration between the ground core network and the high-orbit core network, temporary location identifiers are pre-assigned to each spaceborne user plane functional network element in each high-orbit location management area, and status bits are set. A global mapping table is used to synchronize identifier information and maintain status. When a network element enters the management area, it quickly completes status activation and registration based on the pre-assigned identifier. This optimizes the identifier allocation process in highly dynamic scenarios, effectively reducing signaling overhead and resource consumption.

[0008] Another objective of this invention is to provide a location identifier allocation device for spaceborne user plane functional network elements.

[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 method for allocating location identifiers for spaceborne user plane functional network elements, comprising: S1, the ground core network assigns a unique and fixed identity to the spaceborne user plane functional network element, and stores the identity and the low-orbit satellite number to which the spaceborne user plane functional network element belongs in the global user plane functional network element identity mapping table of the space-ground fusion core network; S2, based on the ephemeris characteristics of low-orbit satellites, the high-orbit core network pre-allocates temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite, and sets a status bit corresponding to the pre-allocated temporary location identifier in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the onboard user plane functional network element in the corresponding high-orbit core network satellite location management area. S3, the high-orbit core network sends the pre-allocated temporary location identifier to the ground core network, and the ground core network stores the mapping relationship between the temporary location identifier and the identity identifier in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network; S4. When a satellite-borne user plane function network element moves into the high-orbit core network position management area along with a low-orbit satellite, it sends a position identifier status update request to the high-orbit core network of the corresponding high-orbit core network satellite position management area. The corresponding request message carries the identity identifier corresponding to the satellite-borne user plane function network element. The high-orbit core network queries the satellite-borne user plane function network element identifier mapping table in the high-orbit core network satellite position management area based on the satellite-borne user plane function network element identity identifier, returns the corresponding pre-allocated temporary position identifier to the satellite-borne user plane function network element, and updates the status bit of the pre-allocated temporary position identifier.

[0012] The location identifier allocation method for spaceborne user plane functional network elements in this embodiment of the 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 spaceborne user plane function network element, and stores the identity identifier in a global user plane function network element identifier mapping table of the space-ground fusion core network, associating the identity identifier with the low-Earth orbit satellite number to which the spaceborne user plane function network element belongs. S11. User plane function 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 user plane functional 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 user plane functional network elements and ground user plane functional network elements. Among them, the ground user plane functional network elements are managed by the ground core network based on the existing identifier management mechanism.

[0013] In one embodiment of the present invention, the high-orbit core network, based on the ephemeris characteristics of low-orbit satellites, pre-allocates temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite, and sets a status bit corresponding to the pre-allocated temporary location identifier in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. The status bit is used to characterize the activation and idle states of the onboard user plane functional network element in the corresponding high-orbit core network satellite location management area, including: S21. Temporary location identifiers pre-allocated by spaceborne user plane function network elements can be allocated in the form of IP addresses, but are not limited to the form of IP addresses. S22, the status bits of the pre-allocated temporary location identifier are non-binary attributes. Specifically, the status bits include: 00 indicates that the onboard user plane function network element is in an idle state, and 11 indicates that the onboard user plane function network element is in an active state.

[0014] In one embodiment of the present invention, the high-orbit core network sends pre-allocated temporary location identifiers to the ground core network. The ground core network stores the mapping relationship between the temporary location identifiers and identity identifiers in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network, including: S31, the global user plane function network element identifier mapping table of the space-ground integrated core network contains multiple high-orbit core network satellite position management area position identifier fields. Each field corresponds to a temporary position identifier pre-assigned by the high-orbit core network satellite position management area for the onboard user plane function network element.

[0015] In one embodiment of the present invention, when a satellite-borne user plane function network element moves into the high-orbit core network location management area along with a low-orbit satellite, a location identifier status update request is sent to the high-orbit core network of the corresponding high-orbit core network satellite location management area. The corresponding request message carries the identity identifier corresponding to the satellite-borne user plane function network element. The high-orbit core network queries the satellite-borne user plane function network element identifier mapping table in the high-orbit core network satellite location management area based on the satellite-borne user plane function network element identity identifier, returns the corresponding pre-allocated temporary location identifier to the satellite-borne user plane function network element, and updates the status bit of the pre-allocated temporary location identifier, including: S41. After receiving the request to update the status of the location identifier of the satellite user plane function network element, the high-orbit core network queries whether the temporary location identifier status bit of the corresponding satellite user plane function network element identity identifier in the satellite location management area of ​​the high-orbit core network is idle. If it is idle, the status bit of the temporary location identifier is updated to active.

[0016] In one embodiment of the present invention, it further includes: S5, the high-orbit core network periodically sends heartbeat monitoring messages to the active satellite user plane function network elements within the current high-orbit core network satellite position management area. If no heartbeat monitoring response is received from the satellite user plane function network element within the heartbeat monitoring period, the status bit of the temporary position identifier of the corresponding satellite user plane function network element in the satellite user plane function network element identifier mapping table of the high-orbit core network satellite position management area is updated, indicating that the satellite user plane function network element is currently in an idle state.

[0017] To achieve the above objectives, another aspect of the present invention proposes a location identifier allocation device for spaceborne user plane functional network elements, comprising: The identity allocation and associated storage module is used by the ground core network to allocate unique and fixed identity identifiers to the satellite user plane functional network elements, and to associate the identity identifiers with the low-orbit satellite numbers to which the satellite user plane functional network elements belong and store them in the global user plane functional network element identifier mapping table of the space-ground fusion core network. The temporary location identifier pre-allocation and status bit setting module is used by the high-orbit core network to pre-allocate temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite based on the ephemeris characteristics of low-orbit satellites, and to set the status bit corresponding to the pre-allocated temporary location identifier in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the onboard user plane functional network element in the corresponding high-orbit core network satellite location management area. The temporary location identifier transmission and mapping update module is used for the high-orbit core network to send the pre-allocated temporary location identifiers to the ground core network, and the ground core network to store the mapping relationship between the temporary location identifiers and identity identifiers in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network; The temporary location identifier status update module is used to send a location identifier status update request to the corresponding high-orbit core network satellite location management area when the onboard user plane function network element moves into the high-orbit core network location management area with the low-orbit satellite. The corresponding request message carries the identity identifier of the onboard user plane function network element. The high-orbit core network queries the onboard user plane function network element identifier mapping table in the high-orbit core network satellite location management area according to the identity identifier of the onboard user plane function network element, returns the corresponding pre-allocated temporary location identifier to the onboard user plane function network element, and updates the status bit of the pre-allocated temporary location identifier.

[0018] In one embodiment of the present invention, it further includes: The heartbeat monitoring module is used to periodically send heartbeat monitoring messages to the active satellite user plane function network elements within the current satellite position management area of ​​the high-orbit core network. If no heartbeat monitoring response is received from the satellite user plane function network element within the heartbeat monitoring period, the module updates the status bit of the temporary position identifier of the corresponding satellite user plane function network element in the satellite user plane function network element identifier mapping table of the high-orbit core network satellite position management area, indicating that the satellite user plane function network element is currently in an idle state.

[0019] The location identifier allocation method and apparatus for spaceborne user plane functional network elements in this invention achieves pre-configuration and unified state-based management of location identifiers for spaceborne user plane functional network elements by coordinating the pre-allocation of fixed temporary identifiers and maintaining a global mapping between the ground and high-orbit core networks. This significantly reduces the signaling interaction overhead and allocation latency caused by frequent switching in highly dynamic scenarios, and enables rapid location identifier updates for spaceborne user plane functional network elements across the satellite location management area of ​​the high-orbit core network. Simultaneously, the heartbeat monitoring and synchronization mechanism based on status bits ensures the real-time nature of network topology awareness and the refined management of identifier resources, thereby effectively improving the communication reliability, resource utilization efficiency, and overall operation and maintenance efficiency of the space-ground integrated core network.

[0020] 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 location identifier allocation method for spaceborne user plane function network elements as described in the first aspect embodiment.

[0021] To achieve the above objectives, a fourth aspect of this application provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the location identifier allocation method for spaceborne user plane functional network elements as described in the first aspect embodiment.

[0022] 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

[0023] 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 for allocating location identifiers for spaceborne user plane functional network elements according to an embodiment of the present invention; Figure 2 This is a diagram of the satellite-ground fusion core network architecture of another method for allocating location identifiers of satellite user plane functional network elements according to an embodiment of the present invention. Figure 3 This is a flowchart of the location identifier allocation process for a spaceborne user plane functional network element according to another method for allocating location identifiers according to an embodiment of the present invention. Figure 4 This is a schematic diagram of the location identifier allocation process of a spaceborne user plane functional network element according to another method for allocating location identifiers of spaceborne user plane functional network elements according to an embodiment of the present invention. Figure 5 This is a flowchart of the location identifier activation process of a spaceborne user plane functional network element according to another method for allocating location identifiers of spaceborne user plane functional network elements according to an embodiment of the present invention. Figure 6 This is a schematic diagram of the activation process of the location identifier of a spaceborne user plane functional network element according to another method for allocating location identifiers of spaceborne user plane functional network elements according to an embodiment of the present invention. Figure 7 This is an example diagram of the location identifier allocation process of a spaceborne user plane functional network element in an application scenario of another location identifier allocation method according to an embodiment of the present invention. Figure 8This is an example diagram illustrating network initialization and identifier pre-allocation in an application scenario of another location identifier allocation method for spaceborne user plane functional network elements according to an embodiment of the present invention. Figure 9 This is a schematic diagram of the location identifier allocation device for spaceborne user plane functional network elements 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

[0024] 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.

[0025] 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.

[0026] The following description, with reference to the accompanying drawings, outlines a method, apparatus, device, and storage medium for allocating location identifiers for spaceborne user plane functional network elements according to embodiments of the present invention.

[0027] This invention relates to a method for allocating location identifiers for spaceborne user plane functional network elements. A unique and fixed identifier is assigned to each spaceborne user plane functional network element by the ground core network, and this identifier is associated with the assigned low-Earth orbit (LEO) satellite number and stored in a global user plane functional network element identifier mapping table of the space-ground fusion core network. Based on the ephemeris characteristics of LEO satellites, the high-Earth orbit (HEO) core network pre-allocates a temporary location identifier for each spaceborne user plane functional network element within the location management area of ​​each HEO core network satellite. A status bit is set in the spaceborne user plane functional network element identifier mapping table of the HEO core network satellite location management area to indicate the active or idle state of the temporary location identifier. The HEO core network synchronizes the pre-allocated temporary location identifiers to the ground core network, which then stores this mapping relationship in the corresponding HEO core network satellite location management area location identifier field of the global user plane functional network element identifier mapping table of the space-ground fusion core network, thereby completing the coordination of the two-level mapping information. When a satellite-borne user plane function network element moves with the satellite into a new high-orbit core network location management area, it sends a location identifier update request carrying its identity identifier to that management area. The high-orbit core network then queries the satellite-borne user plane function network element identifier mapping table in the high-orbit core network satellite location management area based on this identity identifier, returns the corresponding pre-allocated temporary location identifier to the network element for routing and data transmission, and updates the status bit of this temporary identifier to the active state. This method achieves unified management and efficient activation of dynamic satellite-borne user plane function network element location identifiers, ensuring the mobility management capabilities and communication reliability of the space-ground integrated network.

[0028] Example 1 To achieve the above invention, embodiments of the present invention provide a method for allocating location identifiers for spaceborne user plane functional network elements, such as... Figure 1 As shown, it includes: S1, the ground core network assigns a unique and fixed identity to the spaceborne user plane function network element, and stores the identity and the low-orbit satellite number to which the spaceborne user plane function network element belongs in the global user plane function network element identity mapping table of the space-ground fusion core network.

[0029] Specifically, this step is a key component of the identifier management mechanism in the space-ground converged core network. Its technical implementation is based on the design concept of decoupling identity identifiers and location identifiers, aiming to improve the identifier allocation efficiency and topology stability of spaceborne user plane functional network elements in a highly dynamic satellite network environment.

[0030] Specifically, after the deployment of the spaceborne user plane function network element, the ground core network issues a unique and fixed identity identifier (EID) to it through the control plane signaling interface. This identifier can be in the form of, but is not limited to, IP addresses, ensuring global uniqueness throughout the entire space-ground converged network. Simultaneously, the ground core network also needs to obtain the low-Earth orbit satellite number (e.g., LEO-0101) deployed by the spaceborne user plane function network element and write it, along with the identity identifier, into the global user plane function network element identifier mapping table of the space-ground converged core network. This mapping table contains multiple fields, such as the user plane function network element name, user plane function network element identity identifier, the assigned low-Earth orbit satellite number, the name of the current location management area, and the location identifier fields corresponding to multiple high-Earth orbit core network satellite location management areas, to support subsequent dynamic location identifier management and status updates.

[0031] Specifically, this step is mainly applied to the initialization phase of spaceborne user plane functional network elements in the space-ground integrated core network. When a new S-UPF instance is deployed on a low-Earth orbit satellite, the ground core network needs to complete the allocation of its identity identifier and the initialization of the global user plane functional network element identifier mapping table. This mechanism is suitable for scenarios where multiple high-Earth orbit satellites collaboratively manage multiple low-Earth orbit satellite user plane network elements. Especially in large-scale constellation deployments, it can significantly reduce the signaling overhead and network latency of identifier allocation.

[0032] Specifically, by binding the identity identifier to the assigned low-Earth orbit satellite number during the initialization phase, basic data support is provided for the subsequent dynamic identifier activation and status update of the high-Earth orbit core network within the location management area. This mechanism effectively reduces the frequent signaling interactions in the traditional identifier allocation process, improves the efficiency and reliability of identifier management in the space-ground integrated network, and lays the foundation for achieving efficient mobility management of spaceborne user plane functional network elements.

[0033] Furthermore, S1 includes: S11. User plane function network element identity identifiers can be assigned in the form of IP addresses, but are not limited to the form of IP addresses.

[0034] Specifically, the identity identifiers of user plane function network elements are preferably assigned in the form of IP addresses. This is because of their high compatibility with existing Internet and mobile communication network protocol stacks, and they can achieve efficient resolution based on mature routing and addressing mechanisms. However, the identity identifier system of this solution is not limited to the specific form of IP addresses. Other globally unique identifiers can also be used, such as Uniform Resource Identifiers (URIs) above the network layer, structured identifiers customized based on operator policies, etc., thus providing sufficient flexibility and scalability in technical implementation.

[0035] Furthermore, the diversity of identity identifiers allows this solution to adapt to different network deployment environments and protocol evolution stages. For example, in a space-ground converged network based on pure IP transmission, directly using IP addresses as identity identifiers simplifies the encapsulation and processing flow; while in a service-oriented network architecture, using higher-level identifiers such as URIs facilitates complete decoupling of identity and location, supporting more flexible service discovery and access.

[0036] Specifically, regardless of the form of identity used, its core parameters must meet the requirements of global uniqueness, persistence (fixed throughout the network element's lifecycle), and efficient mapping and querying by the controllable plane. The length, format, and parsing efficiency of the identifier are important technical indicators for evaluating specific implementation schemes.

[0037] Specifically, this design makes the present invention applicable not only to IP-based satellite-ground converged mobile communication networks, but also to other networks or systems using non-IP identification systems, enhancing the universality and future applicability of the solution.

[0038] Specifically, this design, which is not bound to a specific identifier format, significantly improves the versatility and scalability of the identifier management system, avoids overly binding the solution to the underlying addressing technology, helps protect the core invention concept, and supports its application in a wider range of network evolution scenarios.

[0039] S12, the global user plane functional 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 user plane functional network elements and ground user plane functional network elements. Among them, the ground user plane functional network elements are managed by the ground core network based on the existing identifier management mechanism.

[0040] Specifically, the global user plane functional network element identifier mapping table of the space-ground integrated core network, by extending its table structure and field definitions, has the ability to uniformly manage the identifiers and mapping information of two types of entities: spaceborne user plane functional network elements and ground user plane functional network elements. This table adds identifier fields (such as "network element type" or "deployment location") to distinguish network element types based on common fields (such as network element name and identity identifier), and associates different management attribute fields according to type differences (such as associating "belonging low-Earth orbit satellite number" and "high-Earth orbit management area location identifier" for spaceborne network elements, and "ground area identifier" for ground network elements), thereby achieving integrated storage and collaborative management of heterogeneous network element identifier information in a single logical view.

[0041] Furthermore, incorporating both types of network elements into a unified global mapping table for management greatly simplifies the query and management logic of the control plane in the space-ground converged core network. Control plane nodes no longer need to maintain two independent mapping systems for spaceborne and ground network elements; they only need to query this unified mapping table based on the network element's identity identifier in the request to obtain its currently valid location identifier and management domain. This achieves the standardization of management interfaces and processes, reducing system complexity and operation and maintenance costs.

[0042] Furthermore, the management capabilities of this global mapping table are reflected in its supported concurrent query throughput, total record size, and update and response latency under a mixed load of dynamic records from spaceborne network elements and relatively static records from ground network elements. These metrics collectively ensure its performance and reliability as an authoritative mapping service in large-scale space-ground integrated networks.

[0043] Specifically, this design enables the identifier management system constructed by the present invention to seamlessly cover the entire user plane from ground fixed infrastructure to onboard dynamic nodes, and is particularly suitable for converged networking scenarios where user services seamlessly switch between satellite and ground networks or where offloading services are jointly provided by satellite and ground user plane network elements.

[0044] Specifically, this unified management mechanism not only enhances the overall control efficiency and consistency of the integrated network, but also protects existing investments by being compatible with and reusing existing ground identification management mechanisms, enabling a smooth evolution of the ground network into a space-ground converged network, demonstrating the backward compatibility and forward-looking nature of the solution design.

[0045] S2. Based on the ephemeris characteristics of low-orbit satellites, the high-orbit core network pre-allocates temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite. It also sets a status bit corresponding to the pre-allocated temporary location identifier in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the onboard user plane functional network element in the corresponding high-orbit core network satellite location management area.

[0046] Specifically, based on the known ephemeris characteristics of low-Earth orbit satellites, including their orbital parameters, coverage areas, and time windows, the high-orbit core network pre-assigns fixed temporary location identifiers to each potential onboard user plane functional network element within the location management area of ​​its corresponding high-orbit core network satellite. This pre-assignment is completed during system initialization or network element registration and is fully recorded in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. This table sets corresponding status bits for each pre-assigned temporary location identifier. These status bits employ a multi-bit coding design, not only representing the most basic "active" and "idle" states of the network element within the current management area, but also further indicating states such as "migration in progress" or "node unresponsive," thereby achieving fine-grained status tracking and control.

[0047] Furthermore, this mechanism, based on pre-allocation and status bit management, simplifies the core operation of network element mobility management from complex dynamic allocation and reclamation of identifiers to atomic updates of status bits in memory. When a spaceborne network element enters or leaves a high-orbit management area with a low-orbit satellite, the high-orbit control plane only needs to update the status bit value of the corresponding entry in the mapping table to complete the logical access and departure registration of the network element, greatly reducing the signaling interaction and processing latency required for allocating temporary identifiers.

[0048] Specifically, the key performance characteristics of this mechanism are reflected in the processing latency of state bit updates, the space utilization efficiency of pre-allocated identifiers, and the system's ability to maintain state consistency when a large number of low-Earth orbit satellites are simultaneously performing inter-regional handovers. These indicators are directly related to the network's response speed and resource management efficiency under dynamic topology.

[0049] Specifically, this design is particularly suitable for "static-dynamic" space-ground integrated networks where high-orbit satellites provide wide-area coverage and control, while low-orbit satellites provide high-speed access and transmission. It effectively solves the problems of identifier allocation storms and network oscillations caused by the frequent switching of management areas by network elements carried by low-orbit satellites due to their high-speed movement.

[0050] Specifically, by combining pre-allocation with status bit management, this invention significantly reduces the signaling overhead and handover latency of mobility management while ensuring the global uniqueness of identifiers and location reachability. It also improves the stability of network topology and the predictability of resource management, providing an efficient and reliable identifier management solution for highly dynamic satellite-ground converged networks.

[0051] Furthermore, S2 includes: S21. Temporary location identifiers pre-allocated by spaceborne user plane function network elements can be allocated in the form of IP addresses, but are not limited to the form of IP addresses.

[0052] Specifically, the temporary location identifiers pre-allocated for spaceborne user plane function network elements are preferably allocated in the form of IP addresses. This is mainly due to the inherent compatibility of the IP address system with current mainstream network protocol stacks and routing infrastructure, enabling efficient addressing and delivery of data packets within the space-ground converged network based on existing routing and forwarding mechanisms. However, the form of the temporary location identifier described in this invention is not limited to IP addresses; its technical essence lies in a logical address that can uniquely identify the network element within a specific management domain and be used for routing within that domain. Therefore, other network layer or custom addressing identifiers can also be used, such as structured addresses based on geographical or topological coordinates, segment IDs, or operator-defined domain-unique codes.

[0053] Specifically, this design provides a high degree of flexibility in network deployment. In scenarios where global interconnection is achieved based on the IP protocol stack, directly using IP addresses as temporary location identifiers can simplify protocol processing to the greatest extent and achieve seamless integration with the terrestrial internet. In some proprietary satellite networks designed for specific services or employing new network architectures, using more streamlined or customized identifiers helps optimize signaling overhead and resource utilization, meeting differentiated performance and cost requirements.

[0054] Furthermore, regardless of the specific form of the temporary location identifier used, its core evaluation criteria lie in the local uniqueness of the identifier within the current high-orbit satellite location management area, and its processing efficiency in control plane mapping queries and user plane data forwarding. The identifier's length, encoding complexity, and parsing latency are key parameters affecting the overall system performance.

[0055] Specifically, by not fixing temporary location identifiers into IP addresses, the identifier pre-allocation and management mechanism of this invention can go beyond the scope of traditional TCP / IP networks and is applicable to heterogeneous converged networks using different network layer protocols, new space information networks for the future, and even proprietary satellite communication systems that have undergone specific optimization.

[0056] Specifically, this open design ensures the versatility of the core inventive concept—"pre-allocation + state management." It avoids over-coupling a high-level management method innovation with the underlying specific addressing technology implementation, thereby enhancing the forward-looking nature of the patent solution and its inclusiveness to different technical routes, ensuring its long-term applicability in the process of technological evolution.

[0057] S22, the status bits of the pre-allocated temporary location identifier are non-binary attributes. Specifically, the status bits include: 00 indicates that the onboard user plane function network element is in an idle state, and 11 indicates that the onboard user plane function network element is in an active state.

[0058] Furthermore, the status bits corresponding to the pre-allocated temporary location identifier are designed as non-binary attributes, specifically using multi-bit binary encoding to represent the rich states of network elements within the management area. For example, "00" indicates that the onboard user plane function network element has completed initialization but is currently in an "idle" state; "11" indicates that the network element is in an "active" state, meaning it has successfully registered and is located within this management area, and can normally carry out service operations. In addition, this encoding space reserves other status values ​​(such as "01" and "10") to indicate states such as "migration in progress" or "node unresponsive," thereby achieving a fine-grained characterization of the network element's lifecycle.

[0059] Furthermore, the design of the status bits requires a trade-off between the granularity of the status indication and the storage and lookup overhead. Two-bit encoding provides four basic states while maintaining extremely low space consumption and fast bit operation efficiency. The latency and consistency of status bit updates are key performance indicators for evaluating the effectiveness of this mechanism in dynamic network environments.

[0060] Furthermore, the non-binary state bit mechanism is particularly well-suited to the highly dynamic and predictable mobility characteristics of low-Earth orbit satellite network nodes. It enables the network to distinguish between "planned departures" (such as switching to another region based on ephemeris) and "abnormal failures" of network elements, thereby supporting more intelligent fault detection, resource pre-scheduling, and mobility management strategies.

[0061] Specifically, this design significantly enhances the expressiveness and flexibility of the identification management system. Through the extended state space, the system can more gracefully handle the smooth transition of network element states and the coordination of management areas, reducing signaling storms or service interruptions caused by state misjudgments, and improving the robustness and management efficiency of the entire space-ground converged network.

[0062] S3, the high-orbit core network sends the pre-allocated temporary location identifiers to the ground core network. The ground core network stores the mapping relationship between the temporary location identifiers and the identity identifiers in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network.

[0063] Furthermore, the high-orbit core network, through a pre-defined satellite-to-ground signaling interface, sends the temporary location identifiers pre-assigned to all satellite-borne user plane functional network elements within its location management area, along with the corresponding network element identity identifiers, to the ground core network in a structured data format. Upon receiving this mapping data, the ground core network persistently stores it in the global user plane functional network element identifier mapping table of the satellite-to-ground fusion core network. Specifically, this table has a dedicated location identifier field for each high-orbit core network satellite location management area (e.g., "High-orbit core network satellite location management area 1 location identifier"). The ground core network accurately fills the received temporary location identifiers into the corresponding fields recorded in the corresponding network element, thereby establishing a complete mapping set from the network-wide unique identity identifier to the pre-assigned location identifiers for each high-orbit management area.

[0064] Furthermore, this step completes the construction of a global network perspective. The terrestrial core network, acting as the global coordinator and authoritative information repository of the network, obtains a complete view of all potential "logical locations" of spaceborne network elements across the entire network by aggregating pre-allocated information from all high-orbit management areas. This enables the terrestrial core network to respond to queries from any network entity regarding the logical location of any spaceborne network element within all high-orbit management areas, providing core data support for cross-domain routing decisions, mobility anchor selection, and global load balancing.

[0065] Specifically, efficiency and reliability are crucial in this process. Key performance indicators (KPIs) include the synchronization latency of mapping information from high-orbit to ground, the integrity of data transmission (such as packet loss retransmission mechanisms), and the storage and indexing efficiency of the massive mapping relationship records in the ground core network. These KPIs collectively ensure the real-time performance, accuracy, and high availability of the global mapping table data.

[0066] Specifically, this design fully adapts to the hierarchical management architecture of space-ground integrated networks. It allows the high-orbit core network to perform efficient pre-allocation and status management (distributed operation) based on local ephemeris information, while ensuring logical unity and coordination of the entire network control plane (centralized view) by synchronizing mapping relationships to the ground core network. It is particularly suitable for complex scenarios that require mobility management or global resource scheduling across multiple high-orbit core network satellite position management areas.

[0067] Specifically, by aggregating and maintaining globally pre-allocated mapping relationships through the ground core network, an organic unity of "distributed" and "centralized" network management is achieved. This not only reduces the burden on the high-orbit core network when handling cross-regional queries, but also avoids the potential state inconsistency problems that may occur in fully distributed mapping management, significantly improving the reliability, scalability, and management efficiency of the entire identifier mapping system.

[0068] Furthermore, S3 includes: S31, the global user plane function network element identifier mapping table of the space-ground integrated core network contains multiple high-orbit core network satellite position management area position identifier fields. Each field corresponds to a temporary position identifier pre-assigned by the high-orbit core network satellite position management area for the onboard user plane function network element.

[0069] Furthermore, the global user plane functional network element identifier mapping table of the space-ground integrated core network establishes a corresponding dedicated location identifier field in its data structure for each independent location management area governed by each high-orbit core network satellite within the network. For example, following the naming rule of "High-orbit core network satellite location management area N location identifier" (where N is the sequence number), a field is assigned to each management area. The value of each field is used to store the fixed temporary location identifiers pre-assigned by the specific high-orbit core network satellite location management area for all onboard user plane functional network elements within its jurisdiction. This design is reflected at the database level as a wide table structure, where each row represents a network element and each column represents the logical address of that network element in a specific high-orbit management area, thus clearly constructing a multi-dimensional mapping relationship of "network element-management area-pre-assigned identifier" in the relational data model.

[0070] Specifically, this table structure, which places pre-assigned identifiers for different management areas in different fields of the same record, enables the ground core network to perform efficient full-network status queries and maintenance for any network element. When it is necessary to determine the logical location of a satellite-borne network element in a specific high-orbit management area (such as GEO-2 area), the control plane can directly query the field named "High-orbit Core Network Satellite Position Management Area 2 Location Identifier" in the network element record, without performing complex association queries or traversals, greatly improving the efficiency of identifier resolution and routing queries.

[0071] Specifically, the key parameters of this table structure include the total number of high-level management zones it can support (i.e., the number of fields), the total length of a single record, and the response time for conditional queries based on identity identifiers or management zone fields under a massive number of network element records. These metrics directly determine the network scale and performance that the global mapping system can support.

[0072] Specifically, this flat design of "one record per network element, one field per management area" perfectly matches the topological characteristics of high-orbit satellite position management areas in space-ground integrated networks, which are characterized by a relatively fixed number of areas, clear boundaries, and long-term stability. It is suitable for scenarios that require centralized and atomic management of all onboard network elements across multiple high-orbit management areas, providing an ideal data foundation for global route calculation, mobility policy formulation, and panoramic visualization of network resources.

[0073] Furthermore, by aggregating the pre-allocated information scattered across various high-orbit nodes into a unified view of the ground core network in the form of structured fields, this invention not only achieves centralized and authoritative storage of mapping information, but also reduces the complexity of data maintenance and query latency through optimized data structures, ensuring that the space-ground fusion core network can still maintain efficient and reliable global identifier mapping and addressing capabilities in dynamic environments.

[0074] S4. When a satellite-borne user plane function network element moves into the high-orbit core network position management area along with a low-orbit satellite, it sends a position identifier status update request to the high-orbit core network of the corresponding high-orbit core network satellite position management area. The corresponding request message carries the identity identifier corresponding to the satellite-borne user plane function network element. The high-orbit core network queries the satellite-borne user plane function network element identifier mapping table in the high-orbit core network satellite position management area based on the satellite-borne user plane function network element identity identifier, returns the corresponding pre-allocated temporary position identifier to the satellite-borne user plane function network element, and updates the status bit of the pre-allocated temporary position identifier.

[0075] Furthermore, when a satellite-borne user plane function network element moves with its low-Earth orbit satellite into the coverage area of ​​a high-Earth orbit core network location management area, the element initiates a location identifier status update request to the high-Earth orbit core network control plane node of that management area via inter-satellite or satellite-to-ground signaling links. The request message encapsulates its unique identifier across the entire network. Upon receiving the request, the high-Earth orbit core network control plane node uses the identifier as the key to query its locally maintained "High-Earth Orbit Core Network Satellite Location Management Area Satellite-borne User Plane Function Network Element Identifier Mapping Table," quickly retrieving the fixed temporary location identifier pre-assigned to the element within this management area. Subsequently, the control plane node returns a response message containing this pre-assigned temporary location identifier to the requesting element and simultaneously updates the status bit of the corresponding entry in the mapping table to "active" (e.g., "11"), thus completing the logical registration and activation of the network element within this management area.

[0076] Specifically, this process simplifies the lengthy traditional mobility management workflow of "entering a new area - applying for a new address - configuring a new address" into a highly efficient workflow of "entering a new area - declaring identity - obtaining a pre-configured address - activating status." Network elements no longer need to undergo complex identifier application and negotiation, and the high-orbit core network no longer needs to perform dynamic address allocation and conflict detection, greatly simplifying the handover signaling process and shortening the time required for network elements to access a new management area and resume service carrying.

[0077] Specifically, the core performance indicators of this process include: end-to-end latency for processing state update requests, mapping table lookup hit rate and response time, and atomicity and consistency guarantees for state bit updates. These indicators directly determine the smoothness of network element handover across management areas and the duration of service interruption.

[0078] Furthermore, this design precisely addresses the highly dynamic characteristics of low-Earth orbit satellite networks, making it suitable for scenarios where onboard network elements regularly and predictably switch between fixed beams or fixed management areas of high-Earth orbit satellites. It enables mobility management to be pre-synchronized with satellite ephemeris, achieving near-seamless session continuity.

[0079] Specifically, by employing a mechanism of "identity identifier querying pre-assigned identifiers and triggering state updates," this invention successfully transforms the core action of mobility management from resource allocation to state transition. This significantly reduces control plane signaling load and processing overhead, improves network response speed and overall stability in high-speed dynamic environments, and provides an efficient, reliable, and lightweight mobility management solution for space-ground converged networks. Furthermore, S4 includes: S41. After receiving the request to update the status of the location identifier of the satellite user plane function network element, the high-orbit core network queries whether the temporary location identifier status bit of the corresponding satellite user plane function network element identity identifier in the satellite location management area of ​​the high-orbit core network is idle. If it is idle, the status bit of the temporary location identifier is updated to active.

[0080] Furthermore, upon receiving a location identifier status update request from an onboard user plane function network element, the control plane node of the high-orbit core network first parses the network element identity identifier carried in the request message. Then, using this identifier as an index key, it retrieves the onboard user plane function network element identifier mapping table maintained locally in the high-orbit core network satellite position management area, locates the corresponding record, and reads the current value of its "location identifier status bit identifier" field. The node executes a status determination logic: if the status bit currently represents an "idle state" (e.g., encoded "00"), it determines that the temporary location identifier of the user plane function network element has not yet been activated, and immediately updates it to an "activated state" (e.g., encoded "11") in an atomic transaction. This process ensures the accuracy and consistency of state transitions.

[0081] Furthermore, this state determination and update mechanism is crucial for ensuring correct resource allocation and preventing state conflicts. While allowing network elements to activate normally and enter new management areas, it effectively avoids the risk that the same pre-allocated identifier might be erroneously activated simultaneously in multiple management areas due to signaling anomalies or duplicate requests, thereby maintaining the uniqueness of the identifier mapping relationship and the logical correctness of the network topology.

[0082] Specifically, the core performance of this process is reflected in the processing latency of status query and discrimination, the atomicity guarantee of status bit reading and writing, and the processing capacity and success rate of massive concurrent status update requests during peak switching periods. These indicators are directly related to the reliability and real-time performance of the mobility management process.

[0083] Specifically, this state-verification-based activation mechanism is particularly suitable for complex scenarios in networks where element movement and state updates are not fully synchronized due to ephemeris prediction errors, signaling delays, or fault recovery. It provides the necessary fault tolerance and consistency verification capabilities for resource management in highly dynamic environments.

[0084] Specifically, by adding an "idle state" verification step before state updates, this invention significantly enhances the robustness of the system while maintaining process simplicity. It not only ensures the orderly and secure allocation of pre-allocated identifier resources but also reduces the probability of routing errors or service interruptions caused by inconsistent states, thereby improving the overall reliability of mobility management in space-ground converged networks.

[0085] S5, the high-orbit core network periodically sends heartbeat monitoring messages to the active satellite user plane function network elements within the current high-orbit core network satellite position management area. If no heartbeat monitoring response is received from the satellite user plane function network element within the heartbeat monitoring period, the status bit of the temporary position identifier of the corresponding satellite user plane function network element in the satellite user plane function network element identifier mapping table of the high-orbit core network satellite position management area is updated, indicating that the satellite user plane function network element is currently in an idle state.

[0086] Furthermore, the heartbeat monitoring mechanism, through the high-orbit core network control plane nodes, proactively sends lightweight heartbeat monitoring request messages at preset intervals to all onboard user plane functional network elements with the status bit set to "active" within its location management area. This message is used to detect the reachability and operational status of the network elements. The high-orbit core network maintains a monitoring timer for each network element. If no heartbeat response is received from the corresponding network element within the specified monitoring period, a timeout judgment logic is triggered. Subsequently, in an atomic operation, the control plane nodes access the onboard user plane functional network element identifier mapping table within the high-orbit core network's satellite location management area, updating the status bit of the corresponding network element entry from "active" (e.g., "11") to "idle" (e.g., "00"), thereby completing the logical reclamation and status reset of the network element resources.

[0087] Specifically, this heartbeat monitoring and status recovery mechanism is key to achieving fault detection and automatic resource management. It can effectively identify "silent failures" caused by low-orbit satellite malfunctions, inter-satellite link interruptions, or network element anomalies, preventing unreachable network elements from occupying logical identifiers and network resources for extended periods. This ensures the consistency between the status information in the mapping table and the actual network topology, providing an accurate basis for routing calculations and resource scheduling.

[0088] Furthermore, the core configurable parameters of this mechanism include the heartbeat sending cycle, timeout threshold, and upper limit on the number of network elements monitored concurrently. These parameters need to strike a balance between network signaling load, fault detection sensitivity, and timely resource release. The success rate of monitoring, the latency of status updates, and the performance stability under high load are important indicators for measuring its effectiveness.

[0089] Specifically, this design is particularly suitable for satellite-ground convergence scenarios with complex network environments and relatively low node reliability. It not only handles the normal state migration of network elements due to movement away from the management area, but also effectively responds to abnormal sudden failures, enhancing the system's self-recovery and continuous service capabilities in the event of partial node failures or channel degradation.

[0090] Specifically, by introducing periodic heartbeat monitoring and automatic state recovery, this invention significantly improves the robustness and autonomy of the identification management system. It reduces reliance on manual intervention, enables real-time and precise control of network resources, and effectively prevents addressing errors or resource waste caused by outdated state information, thereby ensuring the long-term efficiency and reliability of the space-ground converged network.

[0091] The location identifier allocation method for spaceborne user plane functional network elements in this invention effectively solves the technical challenges of frequent identifier allocation, high signaling overhead, and network topology oscillation caused by high-speed node movement in space-ground converged networks by decoupling identity and location identifiers, using ephemeris-based identifier pre-allocation, and a state bit collaborative management mechanism. This method achieves automated management and control throughout the entire lifecycle, from global identifier pre-configuration and dynamic state activation to abnormal resource reclamation, significantly improving the stability and addressing efficiency of identifier mapping in highly dynamic environments, reducing control plane load, and providing key technical support for building an efficient and reliable integrated space-ground converged core network.

[0092] Example 2 To achieve the above invention, embodiments of the present invention also provide another method for allocating location identifiers for spaceborne user plane functional network elements, including: This invention proposes another method for allocating location identifiers for spaceborne user plane functional network elements. The network architecture of the research scenario is as follows: Figure 2 As shown, the space-ground integrated core network consists of three parts: a ground core network, an EOR core network, and a LOR 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 EOR core network (containing no fewer than three EOR satellites) acts as an onboard control node, with each EOR satellite independently deploying complete control plane functions, storing the status of onboard user plane function network elements deployed on LOR satellites, and dynamically managing the onboard user plane function network elements within the current location management area. The LOR core network only deploys onboard user plane function network elements and is responsible for carrying user plane service data. The ground core network control plane network elements and the EOR core network network elements together form the space-ground integrated core network control plane, collaboratively completing the initialization registration, identifier allocation, mapping management, and mobility control of the LOR onboard user plane function network elements.

[0093] This invention employs an identifier mapping system that separates identity identifiers and location identifiers in the space-ground integrated core network, enabling dynamic management of the identity identifiers and location identifiers of low-Earth orbit satellite-borne user plane functional network elements. The hierarchical identifier mapping relationship mainly includes: The high-orbit core network maintains the mapping relationship between the identity identifiers and temporary location identifiers of onboard user plane functional network elements within the satellite position management area through the onboard user plane functional identifier mapping table (example shown in Table 1). The mapping table consists of fields such as onboard user plane functional network element name, onboard user plane functional network element identity identifier, onboard user plane functional network element location identifier, and location identifier status bit. The onboard user plane functional network element name, identity identifier, and location identifier fields remain unchanged after the onboard user plane functional 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 and idle status of the onboard user plane functional network element within the current high-orbit satellite's corresponding position management area. The value of the onboard user plane functional network element location identifier field is pre-assigned by the high-orbit control plane nodes and is only effective within the satellite position management area corresponding to the high-orbit core network satellite.

[0094] Table 1. Mapping Table of Functional Identifiers for X-Shipborne User Plane in High-Orbit Core Network Satellite Position Management Area - Fields

[0095] Table 1 Field Descriptions: Spaceborne User Plane Function (S-UPF) Network Element Name: The instance ID corresponding to the Spaceborne User Plane Function (S-UPF) network element, used to distinguish each S-UPF network element instance; Spaceborne User Plane Function (S-UPF) Network Element Identity Identifier: The ground core network assigns a unique and fixed identity identifier to the S-UPF network element. The identity identifier can be, but is not limited to, an IP address; Spaceborne User Plane Function (S-UPF) Network Element Location Identifier: A temporary location identifier assigned to the S-UPF network element by each high-orbit core network satellite during the initialization of the S-UPF network element. The location identifier can be, but is not limited to, an IP address; Location Identifier Status Bit: Used to indicate the identification status of the S-UPF 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 onboard user plane function network element is in an idle state within the current high-orbit satellite position management area. A value of 11 indicates that the onboard user plane function network element is in an active state within the current high-orbit satellite position management area. Other values ​​can be reserved for the high-orbit core network to manage the status of the onboard user plane function network element position identifier.

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

[0097] Table 2. Mapping Table of Global User Plane Functional Network Element Identifiers for Satellite-Ground Convergence Core Network - Fields

[0098] Table 2 Field Descriptions: User Plane Function Network Element Name: The instance ID corresponding to the user plane function network element, used to distinguish each satellite-borne user plane function network element instance; User Plane Function Network Element Identifier: The ground core network assigns a unique and fixed identifier to the user plane function 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 user plane function 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 user plane function network element moves with the low-Earth orbit satellite at the current moment. If it is prefixed with GEO, it indicates that the user plane function 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 user plane function (S-UPF) network element is configured with a fixed 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.

[0099] This invention addresses a scenario 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 user plane network elements of the low-orbit core network. For example... Figure 3 As shown, the communication process for identifier allocation in the satellite-ground integrated core network of this invention mainly includes: Furthermore, the process of allocating location identifiers for spaceborne user plane function (S-UPF) network elements. This process involves a scenario where, during the initialization of S-UPF network elements, the space-ground converged core network control plane assigns identifiers to the S-UPF network elements.

[0100] Furthermore, the activation process of location identifiers for spaceborne user plane function (S-UPF) network elements. This process involves a scenario where the S-UPF network elements complete the activation of their location identifier status within the location management area corresponding to the high-orbit core network satellite.

[0101] Specifically, the location identifier allocation process for spaceborne user plane functional network elements proposed in this invention is as follows: Figure 3 , 4 As shown.

[0102] The following is the detailed process for allocating location identifiers for onboard user plane function network elements: During the allocation of location identifiers for onboard user plane function network elements, the ground core network assigns a unique and fixed network element identity identifier to each onboard user plane function network element. The ground core network broadcasts the initialized onboard user plane function network element information, including the network element name and identity identifier, to the high-orbit core network. Each high-orbit core network, based on the ephemeris characteristics of low-orbit satellites, pre-allocates temporary location identifiers for all onboard user plane function network elements and configures the location identifier status bits, completing the initialization of the onboard user plane function network element in the onboard user plane function identifier mapping table within the high-orbit core network's satellite position management area. The high-orbit core network then sends the pre-allocated temporary location identifiers within the corresponding satellite position management area of ​​the high-orbit core network to the ground core network. The ground core network stores the location identifiers allocated to each high-orbit core network satellite position management area, completing the initialization of the onboard user plane function network element in the global user plane function network element identifier mapping table of the space-ground fusion core network.

[0103] Specifically, the activation process for the location identifier of the spaceborne user plane functional network element proposed in this invention is as follows: Figure 5 , 6 As shown.

[0104] The following is the detailed process for activating the location identifier of the onboard user plane function network element: When a satellite-borne user plane function network element starts operating, it sends a location identifier status update request to the control plane network element of the high-orbit core network in its current location management area. This request carries the identity information of the current satellite-borne user plane function network element. Upon receiving the request, the high-orbit core network looks up the corresponding location identifier in the satellite-borne user plane function network element identifier mapping table within its satellite location management area, based on the network element's identity identifier. It then updates the status bit of the location identifier in the table to "active," indicating that the satellite-borne user plane function network element is active within its current satellite location management area. The high-orbit core network then returns a location identifier status update response to the satellite-borne user plane function network element. This response carries the network element's identity identifier and a temporary location identifier, which the satellite-borne user plane function network element uses to complete communication and data transmission.

[0105] Specifically, to prevent the management of location identifiers for onboard user plane functional network elements from failing due to abnormal operation of low-Earth orbit satellites, the high-Earth orbit core network employs a heartbeat mechanism. This mechanism effectively monitors the activation status of location identifiers for onboard user plane functional network elements by sending heartbeat monitoring messages between these elements within the high-Earth orbit core network's location management area. If the high-Earth orbit core network does not receive a heartbeat response from an onboard user plane functional network element for an extended period, it automatically executes the deactivation process for the corresponding status bit of that element's location identifier, updating the corresponding location identifier status bit value in the onboard user plane functional network element identifier mapping table within the high-Earth orbit core network's satellite location management area to an idle state.

[0106] Another location identifier allocation method for spaceborne user plane function network elements in this invention effectively solves the problem of frequent allocation of temporary location identifiers and signaling overload caused by the high dynamism of spaceborne user plane function network elements in space-ground converged networks. This method, based on the decoupling of identity and location identifiers, realizes the pre-configuration, stateful updating, and globally unified management of identifiers, significantly reducing the latency and control plane overhead of spaceborne network elements switching across management areas. Combined with heartbeat monitoring and automatic state synchronization mechanisms, it improves the real-time performance of network topology awareness and the level of management refinement, thereby comprehensively enhancing the communication reliability and mobility management capabilities of the space-ground converged core network.

[0107] Example 3 To achieve the above invention, embodiments of the present invention also provide an application scenario for a method for allocating location identifiers for spaceborne user plane functional network elements, including: This embodiment includes the process of allocating location identifiers for spaceborne user plane function network elements in the space-ground converged core network, and the activation and identifier acquisition process for the spaceborne user plane function network element S-UPF-1. In this embodiment, both the identity identifier and location identifier of the spaceborne user plane function network element are in the form of IP addresses. In specific application scenarios, the identifiers can be in the form of, but are not limited to, IP addresses.

[0108] Specifically, the process of allocating location identifiers for onboard user plane functional network elements is as follows: During this process, the space-ground fusion core network assigns identity and location identifiers to onboard user plane functional network elements deployed on low-Earth orbit satellites, completing the initialization of entries for onboard user plane functional network elements within the global user plane functional network element identifier mapping table of the space-ground fusion core network and the onboard user plane functional network element identifier mapping table of the satellite location management area of ​​the high-Earth orbit core network. The specific process is as follows: Figure 7 As shown.

[0109] Furthermore, the space-ground integrated core network completes the deployment of spaceborne user plane function network elements S-UPF-1 and S-UPF-2. The ground core network assigns unique and fixed network element identifiers to the spaceborne user plane function network elements for initialization, completes the initialization of the corresponding entries in the global user plane function network element identifier mapping table of the space-ground integrated core network, and completes the configuration of the user plane function network element name, user plane function network element identifier, and affiliated low-Earth orbit satellite number field values.

[0110] Furthermore, the ground core network distributes the names and identifiers of the spaceborne user plane function network elements to the three high-orbit core network nodes.

[0111] Furthermore, based on the ephemeris characteristics of low-Earth orbit satellites, the high-orbit core network pre-allocates temporary location identifiers for onboard user plane functional network elements, setting the location identifier status bit field value to idle. The high-orbit core network then completes the initialization of the onboard user plane functional network elements in the onboard user plane functional network element identifier mapping table within the high-orbit core network satellite position management area.

[0112] Furthermore, the three high-orbit core networks send temporary location identifiers assigned to the onboard user plane function network elements by their respective high-orbit core network satellite position management areas to the ground core network. The ground core network records the location identifiers corresponding to the onboard user plane function network elements in the high-orbit core network satellite position management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network.

[0113] Specifically, the global user plane functional network element identifier mapping table of the space-ground fusion core network after initialization of the spaceborne user plane functional network elements is shown in Table 3, and the spaceborne user plane functional network element identifier mapping tables of satellite position management areas 1 / 2 / 3 of the high-orbit core network are shown in Tables 4 / 5 / 6 respectively.

[0114] Table 3. Mapping Table of Global User Plane Functional Network Element Identifiers for Space-Ground Convergence Core Network

[0115] Table 4. Mapping Table of Satellite Position Management Area 1 Satellite User Plane Functional Network Element Identifiers for High-Orbit Core Network

[0116] Table 5. Mapping Table of Satellite Position Management Area 2 Satellite User Plane Functional Network Elements Identifiers for High-Orbit Core Network

[0117] Table 6. Mapping Table of Functional Network Elements Identifiers for 3 Satellite-borne User Planes in the High-Orbit Core Network Satellite Position Management Area

[0118] Activation process of spaceborne user plane function network element: The spaceborne user plane function network element S-UPF-1 completes the network element location identifier status update process in the space-ground converged core network scenario. The specific process is as follows: Figure 8 As shown.

[0119] Furthermore, the onboard user plane function network element S-UPF-1 carried by the low-orbit satellite 0101 starts operation in the high-orbit location area corresponding to the high-orbit core network 1 and initiates a position identifier status update process to the control plane of the high-orbit core network. The request signaling contains the identity identifier of the onboard user plane function network element S-UPF-1.

[0120] Furthermore, upon receiving the location identifier status update request, the high-orbit core network 1 queries the satellite user plane function element identifier mapping table in the high-orbit core network satellite location management area 1 to obtain the location identifier 172.12.0.11 corresponding to the identity identifier, and updates the location identifier status bit of the satellite user plane function element to 11. Subsequently, the high-orbit core network 1 synchronizes the location identifier status update information to other control plane nodes.

[0121] Furthermore, the high-orbit core network 1 returns a location identifier status update response to the onboard user plane function network element S-UPF-1, which includes the current identity identifier and location identifier of the onboard user plane function network element. The onboard user plane function network element S-UPF-1 updates its temporary location identifier to 172.12.0.11 for subsequent communication and data transmission.

[0122] Specifically, the mapping table of satellite-borne user plane functional network element identifiers for satellite position management area 1 of the high-orbit core network is shown in Table 7, and the mapping table of satellite-borne user plane functional network element identifiers for satellite position management area 2 of the high-orbit core network is shown in Table 8.

[0123] Table 7. Mapping Table of Satellite Position Management Area 1 Satellite User Plane Functional Network Element Identifiers for High-Orbit Core Network

[0124] Table 8. Mapping Table of Satellite Position Management Area 2 Satellite User Plane Functional Network Elements Identifiers for High-Orbit Core Network

[0125] This invention discloses an application scenario for a location identifier allocation method for spaceborne user plane function network elements. The application scenario verifies that the identifier management method, based on identity and location identifier decoupling and pre-allocation mechanisms, effectively solves the problems of identifier allocation signaling overload and registration latency caused by frequent handovers in highly dynamic satellite networks. It achieves end-to-end optimization from identifier pre-configuration and global synchronization to state activation, significantly improving the efficiency of cross-management area handovers and the stability of network topology. Simultaneously, by combining status bit management and heartbeat monitoring mechanisms, it enhances the system's real-time perception and automated management capabilities of the spaceborne network element's operating status, thereby comprehensively improving the communication reliability and mobility management capabilities of the space-ground converged core network.

[0126] Example 4 To achieve the above invention, such as Figure 9 As shown, this embodiment also provides a location identifier allocation device 10 for spaceborne user plane function network elements, the device 10 comprising: The identity allocation and associated storage module 100 is used by the ground core network to allocate unique and fixed identity identifiers to the satellite user plane function network elements, and to associate the identity identifiers with the low-orbit satellite numbers to which the satellite user plane function network elements belong and store them in the global user plane function network element identifier mapping table of the space-ground fusion core network.

[0127] The temporary location identifier pre-allocation and status bit setting module 200 is used by the high-orbit core network to pre-allocate temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite based on the ephemeris characteristics of low-orbit satellites, and to set the status bit corresponding to the pre-allocated temporary location identifier in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the onboard user plane functional network element in the corresponding high-orbit core network satellite location management area.

[0128] The temporary location identifier transmission and mapping update module 300 is used for the high-orbit core network to send the pre-allocated temporary location identifiers to the ground core network, and the ground core network to store the mapping relationship between the temporary location identifiers and identity identifiers in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the satellite-ground fusion core network.

[0129] The temporary location identifier status update module 400 is used to send a location identifier status update request to the high-orbit core network of the corresponding high-orbit core network satellite location management area when the onboard user plane function network element moves into the high-orbit core network location management area with the low-orbit satellite. The corresponding request message carries the identity identifier of the onboard user plane function network element. The high-orbit core network queries the onboard user plane function network element identifier mapping table of the high-orbit core network satellite location management area according to the identity identifier of the onboard user plane function network element, returns the corresponding pre-allocated temporary location identifier to the onboard user plane function network element, and updates the status bit of the pre-allocated temporary location identifier.

[0130] In one embodiment of the present invention, it further includes: a heartbeat monitoring module, used to periodically send heartbeat monitoring messages to the active satellite user plane function network elements within the current high-orbit core network satellite position management area, and when no heartbeat monitoring response is received from the satellite user plane function network elements within the heartbeat monitoring period, update the status bit of the temporary position identifier of the satellite user plane function network element corresponding to the satellite user plane function network element identifier mapping table in the high-orbit core network satellite position management area, indicating that the satellite user plane function network element is currently in an idle state.

[0131] This invention discloses a location identifier allocation device for spaceborne user plane function network elements. Through a modular collaborative mechanism, it effectively solves the problem of repeated allocation of temporary location identifiers and redundant signaling interaction caused by highly dynamic handover of spaceborne user plane function network elements in traditional space-ground converged networks. This device achieves closed-loop management of the entire process from identity identifier allocation, location identifier pre-configuration, global mapping synchronization to state activation update, significantly reducing control plane signaling overhead and registration latency when spaceborne network elements move across management areas. Simultaneously, relying on integrated heartbeat monitoring and state synchronization functions, it enhances the network's real-time perception and automated operation and maintenance capabilities of the spaceborne network element topology location, thereby comprehensively strengthening the mobility management capabilities and communication reliability of the space-ground converged core network.

[0132] 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 above-described method for managing the location identifier of a satellite user plane in a satellite-ground integrated core network.

[0133] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a satellite-ground fusion core network spaceborne user plane location identifier management method as described in the foregoing embodiments.

[0134] 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.

[0135] 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 allocating location identifiers for spaceborne user plane functional network elements, characterized in that, include: S1, the ground core network assigns a unique and fixed identity to the spaceborne user plane functional network element, and stores the identity and the low-orbit satellite number to which the spaceborne user plane functional network element belongs in the global user plane functional network element identity mapping table of the space-ground fusion core network; S2, based on the ephemeris characteristics of low-orbit satellites, the high-orbit core network pre-allocates temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite, and sets a status bit corresponding to the pre-allocated temporary location identifier in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the onboard user plane functional network element in the corresponding high-orbit core network satellite location management area. S3, the high-orbit core network sends the pre-allocated temporary location identifier to the ground core network, and the ground core network stores the mapping relationship between the temporary location identifier and the identity identifier in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network; S4. When a satellite-borne user plane function network element moves into the high-orbit core network position management area along with a low-orbit satellite, it sends a position identifier status update request to the high-orbit core network of the corresponding high-orbit core network satellite position management area. The corresponding request message carries the identity identifier corresponding to the satellite-borne user plane function network element. The high-orbit core network queries the satellite-borne user plane function network element identifier mapping table in the high-orbit core network satellite position management area based on the satellite-borne user plane function network element identity identifier, returns the corresponding pre-allocated temporary position identifier to the satellite-borne user plane function network element, and updates the status bit of the pre-allocated temporary position identifier.

2. The method as described in claim 1, characterized in that, The ground core network assigns unique and fixed identifiers to the spaceborne user plane function network elements, and stores these identifiers in a global user plane function network element identifier mapping table of the space-ground fusion core network, associating them with the low-Earth orbit satellite numbers to which the spaceborne user plane function network elements belong. This includes: S11. User plane function 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 user plane functional 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 user plane functional network elements and ground user plane functional network elements. Among them, the ground user plane functional network elements are managed by the ground core network based on the existing identifier management mechanism.

3. The method as described in claim 1, characterized in that, Based on the ephemeris characteristics of low-Earth orbit satellites, the high-orbit core network pre-assigns temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite. A status bit corresponding to the pre-assigned temporary location identifier is set in the onboard user plane functional network element identifier mapping table within the high-orbit core network satellite location management area. This status bit characterizes the activation and idle status of the onboard user plane functional network element within the corresponding high-orbit core network satellite location management area, including: S21. Temporary location identifiers pre-allocated by spaceborne user plane function network elements can be allocated in the form of IP addresses, but are not limited to the form of IP addresses. S22, the status bits of the pre-allocated temporary location identifier are non-binary attributes. Specifically, the status bits include: 00 indicates that the onboard user plane function network element is in an idle state, and 11 indicates that the onboard user plane function network element is in an active state.

4. The method as described in claim 1, characterized in that, The high-orbit core network sends pre-allocated temporary location identifiers to the ground core network. The ground core network stores the mapping relationship between temporary location identifiers and identity identifiers in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network, including: S31, the global user plane function network element identifier mapping table of the space-ground integrated core network contains multiple high-orbit core network satellite position management area position identifier fields. Each field corresponds to a temporary position identifier pre-assigned by the high-orbit core network satellite position management area for the onboard user plane function network element.

5. The method as described in claim 1, characterized in that, When a satellite-borne user plane function network element moves with a low-Earth orbit satellite into the high-Earth orbit core network's location management area, it sends a location identifier status update request to the corresponding high-Earth orbit core network satellite location management area. The request message carries the identity identifier corresponding to the satellite-borne user plane function network element. The high-Earth orbit core network queries the satellite-borne user plane function network element identifier mapping table in the high-Earth orbit core network satellite location management area based on the satellite-borne user plane function network element's identity identifier, returns the corresponding pre-allocated temporary location identifier to the satellite-borne user plane function network element, and updates the status bits of the pre-allocated temporary location identifier, including: S41. After receiving the request to update the status of the location identifier of the satellite user plane function network element, the high-orbit core network queries whether the temporary location identifier status bit of the corresponding satellite user plane function network element identity identifier in the satellite location management area of ​​the high-orbit core network is idle. If it is idle, the status bit of the temporary location identifier is updated to active.

6. The method as described in claim 1, characterized in that, Also includes: S5, the high-orbit core network periodically sends heartbeat monitoring messages to the active satellite user plane function network elements within the current high-orbit core network satellite position management area. If no heartbeat monitoring response is received from the satellite user plane function network element within the heartbeat monitoring period, the status bit of the temporary position identifier of the corresponding satellite user plane function network element in the satellite user plane function network element identifier mapping table of the high-orbit core network satellite position management area is updated, indicating that the satellite user plane function network element is currently in an idle state.

7. A location identifier allocation device for spaceborne user plane functional network elements, characterized in that, include: The identity allocation and associated storage module is used by the ground core network to allocate unique and fixed identity identifiers to the satellite user plane functional network elements, and to associate the identity identifiers with the low-orbit satellite numbers to which the satellite user plane functional network elements belong and store them in the global user plane functional network element identifier mapping table of the space-ground fusion core network. The temporary location identifier pre-allocation and status bit setting module is used by the high-orbit core network to pre-allocate temporary location identifiers for each onboard user plane functional network element within the location management area of ​​each high-orbit core network satellite based on the ephemeris characteristics of low-orbit satellites, and to set the status bit corresponding to the pre-allocated temporary location identifier in the onboard user plane functional network element identifier mapping table of the high-orbit core network satellite location management area. The status bit is used to characterize the activation and idle status of the onboard user plane functional network element in the corresponding high-orbit core network satellite location management area. The temporary location identifier transmission and mapping update module is used for the high-orbit core network to send the pre-allocated temporary location identifiers to the ground core network, and the ground core network to store the mapping relationship between the temporary location identifiers and identity identifiers in the corresponding high-orbit core network satellite location management area location identifier field of the global user plane function network element identifier mapping table of the space-ground fusion core network; The temporary location identifier status update module is used to send a location identifier status update request to the corresponding high-orbit core network satellite location management area when the onboard user plane function network element moves into the high-orbit core network location management area with the low-orbit satellite. The corresponding request message carries the identity identifier of the onboard user plane function network element. The high-orbit core network queries the onboard user plane function network element identifier mapping table in the high-orbit core network satellite location management area according to the identity identifier of the onboard user plane function network element, returns the corresponding pre-allocated temporary location identifier to the onboard user plane function network element, and updates the status bit of the pre-allocated temporary location identifier.

8. The apparatus as claimed in claim 7, characterized in that, Also includes: The heartbeat monitoring module is used to periodically send heartbeat monitoring messages to the active satellite user plane function network elements within the current satellite position management area of ​​the high-orbit core network. If no heartbeat monitoring response is received from the satellite user plane function network element within the heartbeat monitoring period, the module updates the status bit of the temporary position identifier of the corresponding satellite user plane function network element in the satellite user plane function network element identifier mapping table of the high-orbit core network satellite position management area, indicating that the satellite user plane function network element is currently in an idle state.

9. An electronic device, comprising: processor; The memory stores executable instructions; when the processor executes the instructions, it implements the location identifier allocation method for spaceborne user plane functional network elements as described in any one of claims 1-6.

10. A computer-readable storage medium storing a computer program, which, when executed by a processor, implements the location identifier allocation method for spaceborne user plane functional network elements as described in any one of claims 1-6.

Images