Ephemeris data processing method, communication device, storage medium and product

Abstract

The embodiment of the invention provides an ephemeris data processing method, communication equipment, a storage medium and a product, and the method comprises the steps: obtaining ephemeris data according to communication association information, and storing the ephemeris data to an ephemeris database; and according to an ephemeris data acquisition request, acquiring target ephemeris data corresponding to the ephemeris data acquisition request from the ephemeris database, and sending the target ephemeris data to a target function network element corresponding to the ephemeris data acquisition request. By setting network element equipment for storing ephemeris data, the ephemeris data is stored in a local ephemeris database of the network element equipment, and target function network elements needing to use the ephemeris data all acquire required target ephemeris data from the network element equipment for storing the ephemeris data. When the ephemeris data needs to be updated or managed and maintained, only the network element equipment storing the ephemeris data needs to be operated, so that centralized management of the ephemeris data is realized, maintenance is convenient, and convenience of ephemeris data management is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method for processing ephemeris data, a communication device, a storage medium, and a product. Background Technology

[0002] With the further development of mobile communications, satellite communications are becoming increasingly mature. Satellite communications have various networking modes, such as the regenerative mode that deploys base stations and user plane functions (UPFs) on satellites.

[0003] In related technologies, ephemeris data is crucial for mobile networks. Typically, Operation Administration and Maintenance (OAM) statically configures ephemeris data directly on the functional network elements that require it. This requires configuring ephemeris data for every functional network element that needs it, making ephemeris data management and maintenance extremely cumbersome. Improving the ease of ephemeris data management is a pressing issue that needs to be discussed and resolved. Summary of the Invention

[0004] This application provides an ephemeris data processing method, communication device, storage medium, and product, aiming to centrally manage ephemeris data and improve the convenience of ephemeris data management.

[0005] In a first aspect, embodiments of this application provide an ephemeris data processing method applied to a network element device. The method includes: acquiring ephemeris data based on communication association information and storing the ephemeris data in an ephemeris database; acquiring target ephemeris data corresponding to the ephemeris data acquisition request from the ephemeris database according to the ephemeris data acquisition request, and sending the target ephemeris data to the target functional network element corresponding to the ephemeris data acquisition request.

[0006] Secondly, embodiments of this application provide an ephemeris data processing method applied to a functional network element. The method includes: receiving target ephemeris data sent by the network element device, wherein the target ephemeris data is obtained by the network element device from an ephemeris database according to an ephemeris data acquisition request; and determining the communication resources that the satellite corresponding to the target ephemeris data can provide based on the target ephemeris data.

[0007] Thirdly, embodiments of this application provide a communication device, including: at least one processor; at least one memory for storing at least one program; and when at least one of the programs is executed by at least one of the processors, implementing the ephemeris data processing method as described in the first or second aspect.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions for performing the ephemeris data processing method as described in the first or second aspect.

[0009] Fifthly, embodiments of this application provide a machine program product, including a computer program or computer instructions, characterized in that the computer program or computer instructions are stored in a computer-readable storage medium, a processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, causing the computer device to perform the ephemeris data processing method as described in the first aspect.

[0010] This application establishes a network element device for storing ephemeris data. Based on communication association information, it retrieves ephemeris data for relevant satellites and stores it in a local ephemeris database. Target functional network elements requiring ephemeris data obtain the necessary data from this storage device, eliminating the need for manual configuration of ephemeris information for each individual target functional network element. When ephemeris data updates or maintenance are required, only the storage device needs to be operated, achieving centralized management of ephemeris data, facilitating maintenance, and improving the convenience of ephemeris data management. Attached Figure Description

[0011] Figure 1 This is a schematic diagram of a satellite communication ground system provided in an embodiment of this application;

[0012] Figure 2 This is a schematic diagram illustrating ephemeris data management as an example provided in this application;

[0013] Figure 3 A flowchart illustrating a method for processing ephemeris data according to an embodiment of this application;

[0014] Figure 4 This is an example of an interaction diagram provided in this application to synchronize ephemeris data from the AMF to the ephemeris management network element;

[0015] Figure 5 This is an example of an interaction diagram provided in this application, illustrating the function registration, update, and release of an ephemeris management network element to the NRF.

[0016] Figure 6 This is a schematic diagram illustrating the interaction between the AMF and the ephemeris management network element to obtain and subscribe to ephemeris data, as provided in an example of this application.

[0017] Figure 7 This application provides an example of an interactive diagram illustrating the process of updating ephemeris data after subscribing to it via AMF.

[0018] Figure 8 This is an example of the interaction diagram provided in this application, illustrating the process of subscribing to ephemeris data using AMF.

[0019] Figure 9 A flowchart of an ephemeris data processing method provided in another embodiment of this application;

[0020] Figure 10 This is a schematic diagram illustrating the interaction between AMF-synchronized ephemeris data and the RAN, as provided in this application.

[0021] Figure 11 This is a schematic diagram illustrating the interaction between the AMF synchronized ephemeris data and the UE, as provided in this application.

[0022] Figure 12 This is an example of the interaction between PCF and UE for synchronizing ephemeris data;

[0023] Figure 13 This is a schematic diagram of the structure of an NF that manages ephemeris data, as provided in an example of this application.

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

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

[0026] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0027] In the description of the embodiments of this application, unless otherwise expressly limited, terms such as setting, installing, and connecting should be interpreted broadly, and those skilled in the art can reasonably determine the specific meaning of the above terms in the embodiments of this application in combination with the specific content of the technical solution.

[0028] In this application, the terms "furthermore," "exemplarily," or "optionally" are used as examples, illustrations, or descriptions and should not be construed as being more preferred or advantageous than other embodiments or designs. The use of terms such as "furthermore," "exemplarily," or "optionally" is intended to present the relevant concepts in a specific manner.

[0029] The technical solutions of this application can be applied to various communication systems, such as: Wideband Code Division Multiple Access (WCDMA) mobile communication system, Evolved Universal Terrestrial Radio Access Network (EUTRAN) system, Next Generation Radio Access Network (NGRAN) system, Long Term Evolution (LTE) system, Worldwide Interoperability For Microwave Access (WiMAX) communication system, 5th Generation (5G) system, such as New Radio Access Technology (NR), and future communication systems, such as 6G system, etc.

[0030] Among related technologies, satellite communication is becoming increasingly mature as mobile communication continues to develop. Satellite communication has various networking modes, such as the regenerative mode that deploys base stations and user plane functions (UPFs) on satellites.

[0031] In satellite communications, because communication satellites operate in Earth orbit, their connection to the ground system is only partial due to their motion. Satellite ephemeris data can be used by User Equipment (UE) and multiple Network Functions (NFs). For the UE, ephemeris data helps calculate the available service time from the satellite. For the Access and Mobility Management (AMF) function, in scenarios with discontinuous coverage, ephemeris data helps calculate the available service time for the UE and notifies the UE of this available service time. The Session Management (SMF) function can use ephemeris data to assist in managing or selecting User Plane Functions (UPFs). For radio, conditional handover can be initiated based on ephemeris data. Other NFs can use ephemeris data to predict traffic changes and adopt appropriate scaling-out strategies. Therefore, satellite ephemeris data is crucial for mobile networks.

[0032] In related technologies, Operation Administration and Maintenance (OAM) is typically used to statically configure ephemeris data directly on the functional network elements that require it. This requires configuring ephemeris data for every functional network element that needs it, making ephemeris data management and maintenance very cumbersome. Improving the convenience of ephemeris data management is a problem that urgently needs to be discussed and solved.

[0033] Based on this, embodiments of this application provide an ephemeris data processing method, communication device, storage medium, and product. By setting up a network element device for storing ephemeris data, the ephemeris data of relevant satellites is obtained according to communication association information and stored in a local ephemeris database. Target functional network elements that need to use ephemeris data obtain the required target ephemeris data from the network element device storing the ephemeris data, eliminating the need for manual configuration through OAM. When it is necessary to update or manage and maintain the ephemeris data, only the network element device storing the ephemeris data needs to be operated, realizing centralized management of ephemeris data, facilitating maintenance, and improving the convenience of ephemeris data management.

[0034] The embodiments of this application will be further described below with reference to the accompanying drawings.

[0035] Figure 1 This is a schematic diagram of a satellite communication ground system provided in one embodiment of this application. For example... Figure 1As shown, the satellite-ground system refers to a communication system that includes a satellite subsystem and a ground subsystem 120. The satellite subsystem consists of multiple satellites 110, and the ground subsystem consists of multiple network functional elements 120.

[0036] Satellite 110 is a microwave communication device deployed in the space segment, capable of providing long-distance voice, data, image, and video transmission. When Satellite 110 reaches its designated location, it establishes a wireless communication connection with Terminal 140 and / or Gateway Station 130 for data exchange. Satellite 110 also deploys a Radio Access Network (RAN) and a User Plane Function (UPF). The RAN is responsible for scheduling air interface resources for terminal access and managing air interface connections; the UPF is the core network user plane functional entity, responsible for forwarding user data packets and also performing statistical analysis of user data packets for billing and other functions.

[0037] Ground subsystem 120 refers to a system composed of various network functional elements deployed on the ground. Ground system 120 includes AUSF, UDM, PCF, AMF, SMF, and other functional network elements.

[0038] Authentication Server Function (AUSF): A core network control plane entity primarily responsible for authenticating and authorizing users to ensure that they are legitimate users.

[0039] Unified Data Management (UDM): A core network control plane entity, belonging to the user server, permanently storing user subscription data.

[0040] Policy Control Functionality (PCF): A core network control plane entity responsible for access and mobility management policies, UE policies, session management policies, and charging rules. This entity primarily generates access and mobility management policies, UE routing policies, Quality of Service (QoS) rules for user data transmission, and charging rules based on service information, user subscription information, and operator configuration information.

[0041] Access and Mobility Management Function (AMF): A core network control plane entity primarily responsible for user mobility management, including registration and temporary identifier allocation; maintaining idle and connected states and state transitions; handover in the connected state; and triggering paging functions in the user's idle state.

[0042] Session Management Function (AMF): A core network control plane entity primarily responsible for maintaining Protocol Data Unit sessions, allocating user IP addresses, and providing QoS control and accounting functions; it also buffers downlink data packets received by users in IDLE state and notifies the AMF to page users, among other functions.

[0043] Gateway station 130 is deployed on the ground and carries out the data exchange function of the satellite communication space-to-ground system, responsible for the collection and distribution of satellite communication service data. Satellite 110 and ground subsystem 120 exchange data through gateway station 130.

[0044] Terminal 140 exchanges data with satellite 110 via wireless communication. Terminal 140 primarily accesses the satellite-to-ground system network and obtains services through the air interface. Terminal 140 interacts with the base station via the air interface and through Non-Access Stratum (NAS) and AMF (Active Information Function). Terminal 140 can take various forms, including desktop computers, laptops, PDAs (Personal Digital Assistants), mobile phones, vehicle-mounted terminals, home theater terminals, and dedicated terminals. Furthermore, it can be a single device or a collection of multiple devices. For example, multiple devices can be connected via a local area network, sharing a single display device to work collaboratively, forming a single terminal.

[0045] The network element used to execute the ephemeris data processing method provided in this application can be an independent network element deployed separately in the ground subsystem 120, or the ephemeris data processing method provided in this application can be deployed in an existing network function network element.

[0046] Figure 2 This is a schematic diagram illustrating ephemeris data management as an example provided in this application. (Refer to...) Figure 2 There exists one NF that manages ephemeris data and multiple NFs that need to use ephemeris data. The multiple NFs that need to use ephemeris data establish communication connections with the NF that manages the ephemeris data.

[0047] The Network Element (NF) that manages ephemeris data is a newly established independent functional network element. This NF is responsible for acquiring, storing, and analyzing ephemeris data. NFs that need to use ephemeris data refer to the functional network elements in the core network that require ephemeris data, such as the AMF, PCF, and SMF.

[0048] The NF that manages ephemeris data receives ephemeris data reported from the radio access network and stores this ephemeris data in a local database. NFs that need to use ephemeris data, if they do not have complete ephemeris data locally, send a request to the NF that manages the ephemeris data to obtain the required ephemeris data. NFs that need to use ephemeris data can also subscribe to ephemeris data from the NF that manages the ephemeris data to achieve synchronized updates and obtain the latest ephemeris data.

[0049] This example demonstrates how to centrally acquire and manage ephemeris data by configuring a Function (NF) to manage ephemeris data. It retrieves ephemeris data for relevant satellites based on communication association information and stores it in a local ephemeris database. NFs that need to use ephemeris data uniformly request the required data from the managing NF, eliminating the need for manual configuration via OAM. When updates or maintenance of ephemeris data are required, only the managing NF needs to be operated on, achieving centralized management of ephemeris data, facilitating maintenance, and improving the convenience of ephemeris data management.

[0050] Figure 3 This is a flowchart illustrating an embodiment of an ephemeris data processing method provided in this application. This ephemeris data processing method can be, but is not limited to, applied to network element devices, such as… Figure 1 Any network element in the ground subsystem 120 shown, such as Figure 2 The NF shown represents the management of ephemeris data. (For example...) Figure 3 As shown, this ephemeris data processing method includes, but is not limited to:

[0051] Step 310: Obtain ephemeris data based on communication association information and store the ephemeris data in the ephemeris database;

[0052] Step 320: Based on the ephemeris data acquisition request, retrieve the target ephemeris data corresponding to the ephemeris data acquisition request from the ephemeris database, and send the target ephemeris data to the target functional network element corresponding to the ephemeris data acquisition request.

[0053] In step 310, communication association information refers to information used to indicate satellites associated with satellite communication. Through communication association information, the satellite equipment participating in the current network can be identified, and the ephemeris data corresponding to these satellite equipment can be obtained. Ephemeris data refers to information used to describe the satellite's flight trajectory, such as the satellite's position and velocity in its orbit. Ephemeris data includes multiple parameters, such as time parameters, Keplerian orbit parameters, and orbital perturbation parameters.

[0054] An ephemeris database refers to a database used locally by a network element device to store ephemeris data. A network element device refers to a network element used to execute the ephemeris data processing methods provided in the embodiments of this application. It can be an independently configured network element or an existing functional network element in the core network. The network element device is responsible for collecting, storing, and analyzing ephemeris data to manage the ephemeris data. For ease of understanding, the network element device will be referred to as the ephemeris management network element below.

[0055] In step 320, the ephemeris data acquisition request is a request to obtain ephemeris data from the ephemeris management network element. This request can be a request sent by a functional network element that needs to use ephemeris data to the ephemeris management network element, or it can be a request generated internally by the ephemeris management network element to trigger the ephemeris management network element to send the corresponding target ephemeris data to the target functional network element.

[0056] Target ephemeris data refers to the ephemeris data in the ephemeris database corresponding to the ephemeris data retrieval request. Target functional network element refers to a network element that needs to use ephemeris data for service processing, communication management, etc. For example, AMF, SMF, PCF, UPF, UDM, or other network elements in 4G or 6G communication networks that need to use ephemeris data are examples, without specific limitations here.

[0057] In steps 310 and 320 above, a network element device is configured to store ephemeris data. Based on communication association information, the ephemeris data of relevant satellites is obtained and stored in a local ephemeris database. Target function network elements that need to use ephemeris data obtain the required target ephemeris data from this storage device, eliminating the need for manual configuration via OAM. When ephemeris data updates or maintenance are required, only the storage device needs to be operated, achieving centralized management of ephemeris data, facilitating maintenance, and improving the convenience of ephemeris data management.

[0058] The above is a general description of steps 310 and 320. The following is a detailed description of the specific implementation process of steps 310 and 320.

[0059] In one embodiment, step 310 includes at least one of the following:

[0060] Obtain static configuration data and extract ephemeris data from the static configuration data;

[0061] Obtain ephemeris data of at least one satellite corresponding to the communication association information from the satellite data server;

[0062] The first functional network element obtains the ephemeris data reported by each access network node to the first functional network element, wherein the first functional network element includes network elements that directly interact with the radio access network.

[0063] In this embodiment, static configuration data refers to the data configured to the ephemeris management network element via OAM. In this embodiment, it is only necessary to write static configuration data carrying ephemeris data to the ephemeris management network element, which then distributes the ephemeris data to other functional network elements. This eliminates the need to configure ephemeris data for each functional network element separately, thus improving the convenience of ephemeris data configuration.

[0064] A satellite data server is a third-party server that stores satellite ephemeris data, such as the server of a company that operates communication satellites. By obtaining the required satellite ephemeris data from a satellite data server, it is possible to supplement ephemeris data obtained through static configuration or dynamic learning, thereby improving the completeness of the ephemeris data.

[0065] The first functional network element refers to a network element that interacts directly with the radio access network, such as the AMF or PCF. Access network nodes refer to the various nodes in the RAN that provide radio interfaces to enable user equipment (such as mobile phones, computers, etc.) to connect wirelessly to the core network. For example, an access network node can be a base station. Since the RAN requires ephemeris data for resource management, especially for RANs deployed on satellites, it typically carries ephemeris data. Therefore, the ephemeris management network element can obtain ephemeris data from the RAN through functional network elements directly connected to the RAN, enabling dynamic learning of the ephemeris data.

[0066] In one embodiment, obtaining ephemeris data reported by each access network node to the first functional network element through the first functional network element includes:

[0067] Receive ephemeris data reporting requests from the first functional network element, wherein the ephemeris data reporting requests are obtained based on the ephemeris data carried in the NG establishment requests of each access network node, and the access network nodes include access network nodes deployed on satellites and access network nodes deployed on the ground.

[0068] Obtain ephemeris data based on the ephemeris data reporting request, and update the ephemeris data in the ephemeris database.

[0069] In this embodiment, an ephemeris data reporting request refers to information carrying ephemeris data corresponding to the access network node to which the first functional network element is connected, obtained by the first functional network element itself. Upon receiving the ephemeris data reporting request, the ephemeris management network element can extract the ephemeris data and return an ephemeris data reporting response to inform the first functional network element that the reported ephemeris data has been received.

[0070] An NG establishment request is a request sent by an access network node (RAN node) to establish an NG interface with a first functional network element for communication. The NG interface refers to the interface between the radio access network and the core network. The access network node carries ephemeris data in the NG establishment request, uploading its stored ephemeris data to the first functional network element. This allows the first functional network element to obtain ephemeris data from each access network node with which it has a communication connection. The first functional network element then uploads the obtained ephemeris data to the ephemeris management network element, which stores it in its local ephemeris database.

[0071] For example, Figure 4 This is a schematic diagram illustrating the interaction between the AMF and the ephemeris management network element to synchronize ephemeris data, as provided in this application. Figure 4 As shown in this example, the first functional network element is assumed to be the AMF, and the ephemeris management network element is a network element that independently stores and manages ephemeris data. The process by which the ephemeris management network element automatically and dynamically updates ephemeris data through the AMF is as follows:

[0072] In step 401, when the RAN sends an NG establishment request message to the AMF, it carries ephemeris data.

[0073] Step 402: The AMF returns an NG establishment response message to the RAN. Specifically, the AMF establishes an NG interface to communicate with the RAN based on the NG establishment request and generates the NG establishment response message. The AMF also extracts and stores the ephemeris data carried in the NG establishment request.

[0074] Step 403: The AMF sends an ephemeris data reporting request message to the ephemeris management network element. This message carries the ephemeris data extracted by the AMF from the NG establishment request. For example, the AMF periodically generates ephemeris data reporting request messages and sends them to the ephemeris management network element; alternatively, the AMF generates an ephemeris data reporting request to upload the ephemeris data to the ephemeris data network element every time it extracts ephemeris data from a message sent by the RAN or receives ephemeris data reported by the RAN.

[0075] Step 404: The ephemeris management network element returns an ephemeris data reporting response message to the AMF. After extracting the ephemeris data from the ephemeris data reporting request, the ephemeris management network element generates an ephemeris data reporting response message and returns it to the AMF to inform the AMF that the ephemeris data reception is complete.

[0076] Step 405: The ephemeris management network element stores the ephemeris data of the RAN obtained through the AMF report.

[0077] Step 406: RAN detects changes in ephemeris data.

[0078] Step 407: The RAN sends a configuration update request message to the AMF, which carries new ephemeris data.

[0079] Step 408: The AMF returns a configuration update response message to the RAN. Specifically, the AMF updates the RAN's configuration information based on the configuration update request message and generates the configuration update response message. The AMF also extracts new ephemeris data from the configuration update request message.

[0080] Step 409: The AMF sends an ephemeris data reporting request message to the ephemeris management network element. The ephemeris data reporting request message carries the new ephemeris data reported by the RAN.

[0081] Step 410: The ephemeris management network element returns an ephemeris data reporting response message to the AMF. After extracting the ephemeris data from the ephemeris data reporting request, the ephemeris management network element generates an ephemeris data reporting response message and returns it to the AMF to inform the AMF that the ephemeris data reception is complete.

[0082] Step 411: The ephemeris management network element updates the ephemeris database with the new ephemeris data reported by the AMF.

[0083] In the above embodiments, the first functional network element collects ephemeris data from each access network node connected to it and reports it to the ephemeris management network element. This enables the ephemeris management network element to automatically and dynamically learn ephemeris data, simplifying the maintenance of ephemeris data.

[0084] In one embodiment, the ephemeris data processing method further includes:

[0085] Register functional information with the network element in the network function library. The functional information includes a first identifier for indicating the network element device and a second identifier for indicating that the network element device has the ability to store ephemeris data.

[0086] Based on functional information, the target functional network element receives a communication association request from the target functional network element. The target functional network element determines that the network element device has ephemeris data storage capability based on the second identifier and determines the first identifier based on the functional information corresponding to the second identifier. The communication association request is used for communication management of the ephemeris data corresponding to the target functional network element.

[0087] In this embodiment, the Network Function Repository Function (NRF) is a core network control plane entity responsible for the dynamic registration of network function service capabilities and network function discovery. After the Ephemeris Management Function (NRF) registers its own NF information with the NRF, it generates corresponding function information. The function information includes at least the identifier of the Ephemeris Management Function and the functions supported by the Ephemeris Management Function, such as the storage or retrieval of ephemeris data and ephemeris data analysis.

[0088] For example, Figure 5 This is a schematic diagram illustrating the interaction between an ephemeris management network element and the NRF for function registration, updating, and release, as provided in an example of this application. Figure 5 In this context, the ephemeris management network element is a network element with the independent function of storing and managing ephemeris data.

[0089] like Figure 5 As shown, the interaction flow between the ephemeris management network element and the NRF is as follows:

[0090] Step 501: The ephemeris management network element sends a network function registration request message to the NRF to register network function information with the NRF; wherein, the network function registration request message includes the identification information of the ephemeris management network element, as well as the capabilities of the ephemeris management network element, such as storage or retrieval of ephemeris data, ephemeris data analysis, etc.

[0091] Step 502: The NRF returns a network function registration response message. The NRF receives the network function registration request message, obtains the identifier of the ephemeris management element and the capabilities it possesses, generates and stores the corresponding function information, and completes the capability registration. After completing the capability registration, the NRF generates a network function registration response message and returns it to the ephemeris management element to inform it that the capability registration is complete.

[0092] Step 503: If the ephemeris management network element has updated its network function configuration data, send a network function update request message to the NRF to update the network function information to the NRF.

[0093] Step 504: The NRF returns a network function update response message. Based on the network function update request message, the NRF updates the capability information of the ephemeris management network element stored in its own memory, generates a network function update response message, and returns it to the ephemeris management network element to inform it that the capability update is complete.

[0094] Step 505: If the ephemeris management network element no longer provides services, send a network function release request message to the NRF so that the NRF releases the network function information.

[0095] Step 506: The NRF returns a network function release response message. Based on the network function release request message, the NRF releases the capability information of the ephemeris management element, generates a network function release response message, and returns it to the ephemeris management element to inform it that the capability release is complete.

[0096] In one embodiment, step 320 includes:

[0097] In response to the ephemeris acquisition request of the target functional network element, the ephemeris data of at least one satellite corresponding to the ephemeris acquisition request is extracted from the ephemeris database as the target ephemeris data. The ephemeris acquisition request is generated by the target functional network element according to the business function corresponding to the target functional network element.

[0098] Send the target ephemeris data to the target functional network element.

[0099] In this embodiment, an ephemeris acquisition request refers to a request generated by the service function corresponding to the target functional network element, used to obtain ephemeris data from the ephemeris management network element. The ephemeris acquisition request includes at least one satellite identifier, enabling the ephemeris management network element to extract ephemeris data from the corresponding satellite in the ephemeris database based on the satellite identifier.

[0100] For example, if the target functional network element is AMF, the corresponding service function includes: in the case of discontinuous satellite coverage, AMF needs ephemeris data to calculate the available satellite time period and notifies the UE of this information. For example, if the target functional network element is SMF, the corresponding service function includes: SMF needs ephemeris data to calculate the available satellite time period, thereby selecting and managing UPF.

[0101] In one embodiment, the method further includes:

[0102] In response to the ephemeris data subscription request from the target functional network element, a subscription relationship for ephemeris data is established with the target functional network element. The ephemeris data subscription request is generated by the target functional network element according to the business function corresponding to the target functional network element.

[0103] When the ephemeris database is updated, the updated ephemeris data corresponding to the business function in the ephemeris database is sent to the functional network elements with which the subscription relationship exists.

[0104] In this embodiment, an ephemeris data subscription request refers to a request generated by a target functional network element based on the ephemeris data required for its supported service functions, used to subscribe to the ephemeris data of the corresponding satellite from the ephemeris management network element. The ephemeris subscription request includes at least one satellite identifier, enabling the ephemeris management network element to send new ephemeris data to the subscribing target functional network element based on the satellite identifier when the ephemeris data of the corresponding satellite is updated.

[0105] In other embodiments of this application, the target functional network element can directly subscribe to all ephemeris data from the ephemeris management network element. In this case, the ephemeris data subscription request may not carry satellite identifiers. After the target functional network element establishes a subscription relationship with the ephemeris management network element, when the ephemeris data in the ephemeris management network element is updated, the ephemeris management network element sends the updated ephemeris data to the target functional network element. The ephemeris management network element may send all ephemeris data or only the updated portion of the ephemeris data.

[0106] For example, Figure 6 This is a schematic diagram illustrating the interaction between the AMF and the ephemeris management network element to obtain and subscribe to ephemeris data, as provided in an example of this application. Figure 6As shown in this example, the target functional network element is assumed to be AMF, and the ephemeris management network element is a network element that independently stores and manages ephemeris data. The process by which AMF obtains and subscribes to ephemeris data from the ephemeris management network element is as follows:

[0107] Step 601: When the AMF needs to discover an ephemeris management network element, it sends an NF discovery request to the NRF. The target NF type corresponding to the NF discovery request is the NF that stores ephemeris data, i.e., the ephemeris management network element.

[0108] Step 602: The NRF returns an NF discovery response, which carries the target NF list information. The AMF can determine, based on the target NF list information, at least that the ephemeris management network element is a network element with the function of storing ephemeris data.

[0109] Step 603: The AMF sends an ephemeris data acquisition request to the ephemeris management network element. This request may include satellite identifiers, indicating that ephemeris data for one or more specific satellites is required; alternatively, it may omit satellite identifiers, indicating that ephemeris data for all satellites is needed. The AMF's ephemeris data acquisition request may also include an identifier indicating that analytical data based on the ephemeris data is required.

[0110] Step 604: The ephemeris management network element returns an ephemeris data acquisition response message, which carries ephemeris data. If the ephemeris data acquisition request carries an identifier indicating the acquisition of analysis data based on the ephemeris data, and the ephemeris management network element also supports generating analysis data based on the ephemeris data, then the ephemeris data acquisition response message carries the analysis data based on the ephemeris data. If the ephemeris data acquisition request carries a satellite identifier, then the ephemeris data acquisition response message carries the ephemeris data of one or more corresponding satellites. If the ephemeris data acquisition request does not carry an identifier, then the ephemeris data acquisition response message carries the ephemeris data of all satellites.

[0111] Step 605: AMF sends a subscription request to the ephemeris management network element to subscribe to ephemeris data change notifications.

[0112] Step 606: The ephemeris management element returns a subscription response message. The subscription relationship is now established.

[0113] Step 607: Based on the received ephemeris data, the AMF calculates the time during which the UE can be served and notifies the UE.

[0114] For example, Figure 7 This is an example illustration of the interaction between AMF subscribing to ephemeris data and updating the ephemeris data. Figure 7As shown in this example, the target functional network element is assumed to be the AMF, and the ephemeris management network element is a network element that independently stores and manages ephemeris data. The process by which the AMF subscribes to ephemeris data from the ephemeris management network element and updates the ephemeris data based on the subscription relationship is as follows:

[0115] Step 701: When the AMF needs to discover an ephemeris management network element, it sends an NF discovery request to the NRF. The target NF type corresponding to the NF discovery request is the NF storing ephemeris data, i.e., the ephemeris management network element.

[0116] In step 702, the NRF returns an NF discovery response, which carries the target NF list information. Based on the target NF list information, the AMF can at least determine that the ephemeris management network element is a network element with the function of storing ephemeris data.

[0117] Step 703: The AMF sends an ephemeris data acquisition request to the ephemeris management network element. This request may carry satellite identifiers, indicating that ephemeris data for one or more specific satellites needs to be acquired, or it may not carry satellite identifiers, indicating that ephemeris data for all satellites needs to be acquired. The ephemeris data acquisition request sent by the AMF may also carry an identifier indicating that analytical data based on the ephemeris data needs to be acquired.

[0118] Step 704: The ephemeris management network element returns an ephemeris data acquisition response message, which carries ephemeris data. If the ephemeris data acquisition request carries an identifier indicating the acquisition of analysis data based on ephemeris data, and the ephemeris management network element also supports generating analysis data based on ephemeris data, then the ephemeris data acquisition response message carries the analysis data based on ephemeris data. If the ephemeris data acquisition request carries a satellite identifier, then the ephemeris data acquisition response message carries the ephemeris data of one or more corresponding satellites. If the ephemeris data acquisition request does not carry an identifier, then the ephemeris data acquisition response message carries the ephemeris data of all satellites.

[0119] Step 705: AMF sends a subscription request to the ephemeris management network element to subscribe to ephemeris data change notifications.

[0120] Step 706: The ephemeris management element returns a subscription response message. The subscription relationship is now established.

[0121] Step 707: The ephemeris management network element detects a change in the ephemeris data (ephemeris data update).

[0122] Step 708: The ephemeris management network element sends a subscription notification request message to the AMF, which carries new ephemeris data.

[0123] Step 709: AMF returns a subscription notification response message to the ephemeris management network element.

[0124] For example, Figure 8 This is an example of an interaction diagram provided in this application, illustrating the process of subscribing to ephemeris data via AMF. For instance... Figure 8 As shown in this example, the target functional network element is assumed to be AMF, and the ephemeris management network element is a network element that independently stores and manages ephemeris data. The process of AMF subscribing to ephemeris data from the ephemeris management network element and then subscribing again is as follows:

[0125] Step 801: When the AMF needs to discover an ephemeris management network element, it sends an NF discovery request to the NRF. The target NF type corresponding to the NF discovery request is the NF that stores ephemeris data, i.e., the ephemeris management network element.

[0126] In step 802, the NRF returns an NF discovery response, which carries the target NF list information. Based on the target NF list information, the AMF can at least determine that the ephemeris management network element is a network element with the function of storing ephemeris data.

[0127] Step 803: The AMF sends an ephemeris data acquisition request to the ephemeris management network element. This request may carry satellite identifiers, indicating that ephemeris data for one or more specific satellites needs to be acquired, or it may not carry satellite identifiers, indicating that ephemeris data for all satellites needs to be acquired. The ephemeris data acquisition request sent by the AMF may also carry an identifier indicating that analytical data based on the ephemeris data needs to be acquired.

[0128] Step 804: The ephemeris management network element returns an ephemeris data acquisition response message, which carries ephemeris data. If the ephemeris data acquisition request carries an identifier indicating the acquisition of analysis data based on the ephemeris data, and the ephemeris management network element also supports generating analysis data based on the ephemeris data, then the ephemeris data acquisition response message carries the analysis data based on the ephemeris data. If the ephemeris data acquisition request carries a satellite identifier, then the ephemeris data acquisition response message carries the ephemeris data of one or more corresponding satellites. If the ephemeris data acquisition request does not carry an identifier, then the ephemeris data acquisition response message carries the ephemeris data of all satellites.

[0129] Step 805: AMF sends a subscription request to the ephemeris management network element to subscribe to ephemeris data change notifications.

[0130] Step 806: The ephemeris management network element returns a subscription response message. The subscription relationship is now established.

[0131] In step 807, the AMF determined that it was no longer necessary to obtain updates to the ephemeris data.

[0132] Step 808: AMF sends a subscription request to the ephemeris management network element.

[0133] Step 809: The ephemeris management network element returns a subscription response to the AMF.

[0134] In one embodiment, the method further includes:

[0135] Obtain the ephemeris data corresponding to each target functional network element;

[0136] Based on the ephemeris data and regional feature data corresponding to each target functional network element, analysis data on satellite availability is generated for each target functional network element. The analysis data includes satellite orbit time and the time period during which the satellite provides services to the target area.

[0137] The analyzed data is sent to the corresponding target functional network element.

[0138] In this embodiment, the regional feature data corresponding to the target functional network element refers to the regional information corresponding to the target functional network element, such as latitude and longitude information, communication scheduling strategy information corresponding to the region, etc.

[0139] The time period during which a satellite provides services to a target area includes the start time and duration of the service. The target area can be a tracking area (TA), a tracking area list, a public land mobile network (PLMN), or any other defined area; no specific limitations are specified here.

[0140] The above embodiments directly analyze ephemeris data through the ephemeris management network element and send the analyzed data to the target functional network element. This eliminates the need for the target functional network element to perform additional ephemeris data analysis, reducing resource consumption and improving communication efficiency.

[0141] Figure 9 A flowchart illustrating a star data processing method provided in another embodiment of this application. This star data processing method can be, but is not limited to, applied to functional network elements, such as… Figure 1 The functional network elements in the ground subsystem 120 that require ephemeris data, such as... Figure 2 The example shown is an NF that requires ephemeris data. Figure 9 As shown, this ephemeris data processing method includes, but is not limited to:

[0142] Step 910: Receive target ephemeris data sent by the network element device, wherein the target ephemeris data is obtained by the network element device from the ephemeris database according to the ephemeris data acquisition request;

[0143] Step 920: Based on the target ephemeris data, determine the communication resources that the satellite corresponding to the target ephemeris data can provide.

[0144] In step 910, the network element device refers to a network element with the function of storing and managing ephemeris data. It can be an independently set network element or an existing functional network element in the core network. The network element device is responsible for collecting, storing, and analyzing ephemeris data in order to manage the ephemeris data. For easier understanding, the network element device will be referred to as the ephemeris management network element.

[0145] An ephemeris database refers to a database used locally by a network element to store ephemeris data. Target ephemeris data refers to the ephemeris data required by the functional network element, such as the ephemeris data of one or more related satellites.

[0146] In step 920, the communication resources that the satellite can provide include at least: the satellite's available service time period, the satellite's available service area, and the satellite's corresponding bandwidth.

[0147] In steps 910 and 920 above, by setting up a network element device for storing ephemeris data, the satellite ephemeris data is stored in the local ephemeris database of the network element device for unified management. Functional network elements that need to use ephemeris data obtain the required target ephemeris data from this network element device, eliminating the need for manual configuration via OAM. When ephemeris data updates or maintenance are required, only the network element device storing the ephemeris data needs to be operated, achieving centralized management of ephemeris data, facilitating maintenance, and improving the convenience of ephemeris data management.

[0148] It should be noted that the embodiments corresponding to steps 910 and 920, as well as the embodiments related to the functional network element side, are all corresponding to the above-described method for processing ephemeris data applied to the network element device side. The specific implementation details and beneficial effects involved can be determined in the above embodiments, and will not be repeated here.

[0149] In one embodiment, the ephemeris data processing method further includes:

[0150] Send an ephemeris data subscription request to the network element device to establish a subscription relationship for ephemeris data with the network element device. The ephemeris data subscription request is generated by the functional network element according to the corresponding business function of the functional network element.

[0151] When the ephemeris database of the receiving network element is updated, the received network element sends the updated ephemeris data.

[0152] By subscribing to ephemeris data from network element devices (ephemeris management network elements) and establishing a subscription relationship, the latest ephemeris data can be obtained in a timely manner.

[0153] In one embodiment, after receiving the updated ephemeris data sent by the network element device, the ephemeris data processing method further includes:

[0154] Upon receiving updated ephemeris data from a network element, determine the access network node corresponding to the updated ephemeris data;

[0155] Send updated ephemeris data to the access network nodes.

[0156] For example, the access network node corresponding to the updated ephemeris data refers to the satellite to which the updated ephemeris data belongs and the access network node that are associated.

[0157] For example, Figure 10 This is a schematic diagram illustrating the interaction between AMF-synchronized ephemeris data and the RAN, as provided in an example of this application. Figure 10 As shown in this example, the functional network element is assumed to be the AMF. The specific process of the AMF sending ephemeris data to the RAN (corresponding access network node) is as follows:

[0158] Step 1001: The RAN sends an NG establishment request message to the AMF, and the NG establishment request message does not carry ephemeris data.

[0159] Step 1002: The AMF returns an NG establishment response message to the RAN. If the AMF finds that the NG establishment request message sent by the RAN does not carry ephemeris data, and the AMF determines, based on its local policy, that ephemeris data needs to be delivered to the RAN, then the AMF includes the ephemeris data in the NG establishment response message.

[0160] Step 1003: AMF detects that the ephemeris data has been updated, and that the RAN had previously synchronized the ephemeris data.

[0161] Step 1004: AMF sends a configuration update request message to RAN, which carries the updated ephemeris data.

[0162] Step 1005: The RAN returns a configuration update response message to the AMF.

[0163] In one embodiment, the ephemeris data processing method further includes:

[0164] Receive registration requests sent by the terminal;

[0165] If the registration request includes an identifier that supports synchronized ephemeris data, a registration acceptance response carrying ephemeris data is sent to the terminal.

[0166] Upon receiving updated ephemeris data from a network element, the updated ephemeris data is sent to the terminal.

[0167] In this embodiment, a registration request refers to a request from the terminal to register its own information. A "support for synchronized ephemeris data" identifier is an identifier used to indicate that the terminal can support ephemeris data synchronization, or that the terminal needs to synchronize ephemeris data.

[0168] If the terminal's registration request does not include a flag indicating support for synchronized ephemeris data, or if the flag indicates no support (not supported), the registration acceptance response sent by the functional network element to the terminal will also not include ephemeris data. Subsequently, when the functional network element updates its own ephemeris data, it will not synchronize the new ephemeris data to the terminal.

[0169] In one example, Figure 11 This is a schematic diagram illustrating the interaction between the AMF synchronized ephemeris data and the UE, as provided in this application. Figure 11 As shown in this example, the functional network element is assumed to be the AMF. The specific process of the AMF synchronizing ephemeris data with the UE (terminal) is as follows:

[0170] Step 1101: The UE sends a registration request message to the AMF, which carries a support for synchronous ephemeris data identifier and sets the status indicated by the identifier to support.

[0171] Step 1102: The AMF processes the registration process and sends a registration acceptance message to the UE. If the UE supports synchronizing ephemeris data and the AMF also supports synchronizing ephemeris data to the UE, the registration acceptance message will carry the ephemeris data.

[0172] Step 1103: The AMF detects that the ephemeris data has been updated. Alternatively, the AMF receives updated ephemeris data from the ephemeris management network element.

[0173] Step 1104: If the AMF has previously synchronized ephemeris data with the UE, the AMF sends a UE configuration update command to the UE, which carries the updated ephemeris data.

[0174] Step 1105: The UE returns a UE configuration update complete message to the AMF.

[0175] In another example, Figure 12 This is a schematic diagram illustrating the interaction between the PCF and the UE, as provided in this application, to synchronize ephemeris data. Figure 12 As shown in this example, it is assumed that functional network elements AMF and PCF exist. The specific process of PCF synchronizing ephemeris data with UE (terminal) is as follows:

[0176] Step 1201: The UE sends a registration request message to the AMF, which carries a support for synchronous ephemeris data identifier and sets the status indicated by the identifier to support.

[0177] Step 1202: The AMF processes the registration procedure and sends a registration acceptance message to the UE.

[0178] Step 1203: The AMF sends a UE policy establishment request message to the PCF. The message carries a support for synchronous ephemeris data identifier and also sets it to support.

[0179] Step 1204: PCF returns a UE policy establishment response message to AMF.

[0180] Step 1205: If the UE supports synchronizing ephemeris data and the PCF also supports synchronizing ephemeris data to the UE, then the PCF sends an N1N2 message delivery request carrying ephemeris data to the AMF.

[0181] Step 1206: AMF returns an N1N2 message delivery response to PCF.

[0182] Step 1207: The AMF sends a UE configuration update command carrying ephemeris data to the UE.

[0183] Step 1208: The UE returns a UE configuration update complete message to the AMF.

[0184] Step 1209: PCF detects that the ephemeris data has been updated.

[0185] Step 1210: If ephemeris data has been synchronized to the UE before, the PCF sends an N1N2 message delivery request carrying the updated ephemeris data to the AMF.

[0186] Step 1211: AMF returns an N1N2 message delivery response to PCF.

[0187] Step 1212: The AMF sends a UE configuration update command carrying the updated ephemeris data to the UE.

[0188] Step 1213: The UE returns a UE configuration update complete message to the AMF.

[0189] In one embodiment, after receiving the target ephemeris data sent by the network element device, the method further includes:

[0190] Based on the target ephemeris data, determine the service area and service time of the user plane function network elements deployed on the satellites corresponding to the target ephemeris data;

[0191] Send the available service area and available service time to the terminal.

[0192] In this embodiment, the core network user plane NF is satellite-mounted, meaning the RAN and UPF in the core network are deployed on satellites. The core network control plane NF can obtain ephemeris data from the ephemeris management network element, calculate the service area and time available to the core network user plane NF, and optimize the management of the core network user plane NF. For example, the functional network element that uses ephemeris data to optimize the user plane NF can be an SMF, the control plane of a Serving Gateway (SGW), the control plane of a Packet Data Network Gateway (PDNGateway, PGW), or the control plane of a Session Border Controller (SBC).

[0193] In one embodiment, after receiving the target ephemeris data sent by the network element device, the ephemeris data processing method further includes:

[0194] Obtain the location and time information of the terminal's historical access;

[0195] The target satellite is determined based on historical location and time information and target ephemeris data;

[0196] Send a paging command to the target satellite so that the target satellite can page the terminal.

[0197] In this embodiment, the core network functional element can obtain ephemeris data from the ephemeris management element, calculate the satellites currently available to serve the user's previously accessed location based on the user's previous access location and time, select appropriate satellites to paging the user, and optimize paging for the user. For example, the core network functional element that uses ephemeris data to optimize paging can be an AMF, a Mobility Management Entity (MME), a 6G connection management NF, or a connection management NF in other systems.

[0198] The following examples provide a comprehensive and detailed description of the ephemeris data processing method of this application. It is understood that the following embodiments are merely illustrative examples to better illustrate the ephemeris data processing method of this application and are not intended to limit its scope.

[0199] Figure 13 This is a schematic diagram of the structure of the NF for managing ephemeris data provided in an example of this application. For example... Figure 13 As shown, the NF that manages ephemeris data includes an ephemeris data analysis unit, an ephemeris data provision unit, an ephemeris data storage unit, and an ephemeris data acquisition unit.

[0200] The ephemeris data acquisition unit is used to acquire ephemeris data. For example, ephemeris data can be statically configured into the ephemeris data acquisition unit through OAM, or the ephemeris data acquisition unit can obtain ephemeris data of the target satellite from a third-party server, or the ephemeris data acquisition unit can dynamically learn ephemeris data from the RAN.

[0201] The ephemeris data storage unit is used to store the ephemeris data obtained by the ephemeris data acquisition unit into the ephemeris database.

[0202] The ephemeris data analysis unit is used to extract ephemeris data from the ephemeris data storage unit, analyze and process it to obtain analysis data, and then return the analysis data to the ephemeris data storage unit for storage.

[0203] The ephemeris data providing unit is used to extract ephemeris data or analyze data from the ephemeris data storage unit and send it to the NF that uses the ephemeris data.

[0204] This example demonstrates how to centrally acquire and manage ephemeris data by configuring a Function (NF) to manage ephemeris data. It retrieves ephemeris data for relevant satellites based on communication association information and stores it in a local ephemeris database. NFs that need to use ephemeris data uniformly request the required data from the managing NF, eliminating the need for manual configuration via OAM. When updates or maintenance of ephemeris data are required, only the managing NF needs to be operated on, achieving centralized management of ephemeris data, facilitating maintenance, and improving the convenience of ephemeris data management.

[0205] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 14 As shown, the communication device 2000 includes a memory and a processor. The number of memories and processors can be one or more. Figure 14 Taking a memory 2101 and a processor 2201 as an example; the memory 2101 and processor 2201 in the network device can be connected via a bus or other means. Figure 14 Taking the example of a connection between China and Israel via a bus.

[0206] The memory 2101, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the methods provided in any embodiment of this application. The processor 2201 implements the ephemeris data processing method provided in any of the above embodiments by running the software programs, instructions, and modules stored in the memory 2101.

[0207] Memory 2101 may primarily include a program storage area and a data storage area, wherein the program storage area may store the operating system and application programs required for at least one function. Furthermore, memory 2101 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, memory 2101 further includes memory remotely located relative to processor 2201, and this remote memory can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0208] One embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions for performing the ephemeris data processing method provided in any embodiment of this application.

[0209] An embodiment of this application also provides a computer program product, including a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform the ephemeris data processing method provided in any embodiment of this application.

[0210] The system architecture and application scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will understand that as system architectures evolve and new application scenarios emerge, the technical solutions provided in this application are also applicable to similar technical problems.

[0211] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0212] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0213] The terms “component,” “module,” “system,” etc., used in this specification are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process or execution thread, and components may be located on a single computer or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

[0214] The above description, with reference to the accompanying drawings, illustrates some embodiments of this application, but does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this application shall be within the scope of this application.

Claims

1. A method for processing ephemeris data, characterized in that, Applied to network element devices, the method includes: Obtain ephemeris data based on communication association information, and store the ephemeris data in an ephemeris database; Based on the ephemeris data acquisition request, the target ephemeris data corresponding to the ephemeris data acquisition request is obtained from the ephemeris database, and the target ephemeris data is sent to the target functional network element corresponding to the ephemeris data acquisition request.

2. The ephemeris data processing method according to claim 1, characterized in that, The step of obtaining the target ephemeris data corresponding to the ephemeris data acquisition request from the ephemeris database and sending the target ephemeris data to the target functional network element corresponding to the ephemeris data acquisition request includes: In response to the ephemeris acquisition request of the target functional network element, ephemeris data of at least one satellite corresponding to the ephemeris acquisition request is extracted from the ephemeris database as the target ephemeris data, wherein the ephemeris acquisition request is generated by the target functional network element according to the service function corresponding to the target functional network element; The target ephemeris data is sent to the target functional network element.

3. The ephemeris data processing method according to claim 1 or 2, characterized in that, The method further includes: In response to the ephemeris data subscription request of the target functional network element, a subscription relationship for the ephemeris data is established with the target functional network element. The ephemeris data subscription request is generated by the target functional network element according to the business function corresponding to the target functional network element. When the ephemeris database is updated, the updated ephemeris data corresponding to the service function in the ephemeris database is sent to the functional network element with the subscription relationship.

4. The ephemeris data processing method according to claim 1, characterized in that, The acquisition of ephemeris data based on communication association information includes at least one of the following: Obtain static configuration data, and extract the ephemeris data from the static configuration data; Obtain the ephemeris data of at least one satellite corresponding to the communication association information from the satellite data server; The first functional network element obtains the ephemeris data reported by each access network node to the first functional network element, wherein the first functional network element includes network elements that directly interact with the radio access network.

5. The ephemeris data processing method according to claim 4, characterized in that, The step of obtaining the ephemeris data reported by each access network node to the first functional network element through the first functional network element includes: Receive the ephemeris data reporting request from the first functional network element, wherein the ephemeris data reporting request is obtained based on the ephemeris data carried in the NG establishment request of each access network node, and the access network node includes access network nodes deployed on satellites and access network nodes deployed on the ground. The ephemeris data is obtained according to the ephemeris data reporting request, and the ephemeris data is updated in the ephemeris database.

6. The ephemeris data processing method according to claim 1, characterized in that, The method further includes: Register functional information with the network element in the network function library, wherein the functional information includes a first identifier for indicating the network element device and a second identifier for indicating that the network element device has ephemeris data storage capability; Based on the functional information, the target functional network element receives a communication association request from the target functional network element, wherein the target functional network element is used to determine that the network element device has ephemeris data storage capability according to the second identifier, and to determine the first identifier according to the functional information corresponding to the second identifier, and the communication association request is used for communication management of the ephemeris data corresponding to the target functional network element.

7. The ephemeris data processing method according to claim 1, characterized in that, The method further includes: Obtain the ephemeris data corresponding to each of the target functional network elements; Based on the ephemeris data and regional feature data corresponding to each target functional network element, analysis data on satellite availability is generated for each target functional network element. The analysis data includes satellite orbit time and the time period during which the satellite provides services to the target area. The analyzed data is sent to the corresponding target functional network element.

8. A method for processing ephemeris data, characterized in that, Applied to functional network elements, the method includes: Receive target ephemeris data sent by a network element device, wherein the target ephemeris data is obtained by the network element device from an ephemeris database according to an ephemeris data acquisition request; Based on the target ephemeris data, determine the communication resources that the satellite corresponding to the target ephemeris data can provide.

9. The ephemeris data processing method according to claim 8, characterized in that, The method further includes: Send an ephemeris data subscription request to the network element device and establish a subscription relationship for the ephemeris data with the network element device, wherein the ephemeris data subscription request is generated by the functional network element according to the service function corresponding to the functional network element; If the ephemeris database of the network element device is updated, the updated ephemeris data sent by the network element device shall be received.

10. The ephemeris data processing method according to claim 9, characterized in that, After receiving the updated ephemeris data sent by the network element device, the method further includes: Upon receiving the updated ephemeris data sent by the network element device, determine the access network node corresponding to the updated ephemeris data; The updated ephemeris data is sent to the access network node.

11. The ephemeris data processing method according to claim 9, characterized in that, The method further includes: Receive the registration request sent by the terminal; If the registration request carries an identifier that supports synchronized ephemeris data, a registration acceptance response carrying the ephemeris data is sent to the terminal; Upon receiving the updated ephemeris data sent by the network element device, the updated ephemeris data is sent to the terminal.

12. The ephemeris data processing method according to claim 8, characterized in that, After receiving the target ephemeris data sent by the network element device, the method further includes: Based on the target ephemeris data, determine the service area and service time of the user plane function network elements deployed on the satellite corresponding to the target ephemeris data; The serviceable area and the serviceable time are sent to the terminal.

13. A communication device, characterized in that, include: At least one processor; At least one memory for storing at least one program; The method as described in any one of claims 1 to 12 is implemented when at least one of the programs is executed by at least one of the processors.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for performing the method as described in any one of claims 1 to 12.

15. A computer program product, comprising a computer program or computer instructions, characterized in that, The computer program or the computer instructions are stored in a computer-readable storage medium, and the processor of the computer device reads the computer program or the computer instructions from the computer-readable storage medium. The processor executes the computer program or the computer instructions, causing the computer device to perform the method as described in any one of claims 1 to 12.

Images