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

Abstract

Provided in the embodiments of the present application are ephemeris data processing methods, a communication device, a storage medium and a product. A method comprises: acquiring ephemeris data on the basis of communication association information, and storing the ephemeris data in an ephemeris database (310); and on the basis of an ephemeris data acquisition request, acquiring, from the ephemeris database, target ephemeris data corresponding to the ephemeris data acquisition request, and sending the target ephemeris data to a target functional network element corresponding to the ephemeris data acquisition request (320).

Description

Method for processing ephemeris data, communication device, storage medium and product

[0001] Cross-reference to related applications

[0002] The present application is based on the Chinese patent application No. 2024111204294, filed on August 14, 2024, and claims priority to the Chinese patent application, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] Embodiments of the present application relate to the field of communication technology, in particular to a method for processing ephemeris data, a communication device, a storage medium and a product. BACKGROUND

[0004] With the further development of mobile communication, satellite communication is becoming more and more mature. There are various networking modes for satellite communication, such as a regenerative mode in which base stations and user plane functions (UPF, User plane function) are deployed on satellites.

[0005] In related technologies, ephemeris data is very important to mobile networks. Ephemeris data is usually statically configured by operation administration and maintenance (OAM) directly on functional network elements that need to use ephemeris data. All functional network elements that need to use ephemeris data need to be configured with ephemeris data, and the management and maintenance of ephemeris data is very troublesome. How to improve the convenience of ephemeris data management is a problem that needs to be discussed and solved. SUMMARY

[0006] Embodiments of the present application provide a method for processing ephemeris data, a communication device, a storage medium and a product.

[0007] In a first aspect, embodiments of the present application provide a method for processing ephemeris data, applied to a network element device, the method comprising: obtaining ephemeris data according to communication association information, and storing the ephemeris data to an ephemeris database; obtaining target ephemeris data corresponding to an ephemeris data obtaining request from the ephemeris database according to the ephemeris data obtaining request, and sending the target ephemeris data to a target functional network element corresponding to the ephemeris data obtaining request.

[0008] In a second aspect, embodiments of the present application provide a method for processing ephemeris data, applied to a functional network element, the method comprising: receiving 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 obtaining request; determining communication resources that can be provided by a satellite corresponding to the target ephemeris data according to the target ephemeris data.

[0009] In a third aspect, an embodiment of the present application provides a communication device, comprising: at least one processor; at least one memory configured to store at least one program; and the at least one processor is configured to implement the ephemeris data processing method according to the first aspect or the second aspect when executing the at least one program.

[0010] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, which stores computer executable instructions, and the computer executable instructions are used to execute the ephemeris data processing method according to the first aspect or the second aspect.

[0011] In a fifth aspect, an embodiment of the present application provides a computer program product, which comprises a computer program or computer instructions, and the computer program or the computer instructions are stored in a computer readable storage medium, and a processor of a computer device reads the computer program or the computer instructions from the computer readable storage medium, and the processor executes the computer program or the computer instructions, so that the computer device executes the ephemeris data processing method according to the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0012] FIG. 1 is a networking schematic diagram of a satellite communication satellite-ground system according to an embodiment of the present application;

[0013] FIG. 2 is a schematic diagram of ephemeris data management according to an embodiment of the present application;

[0014] FIG. 3 is a flowchart of an ephemeris data processing method according to an embodiment of the present application;

[0015] FIG. 4 is an interaction schematic diagram of AMF synchronizing ephemeris data to an ephemeris management network element according to an embodiment of the present application;

[0016] FIG. 5 is an interaction schematic diagram of an ephemeris management network element registering, updating and releasing functions to an NRF according to an embodiment of the present application;

[0017] FIG. 6 is an interaction schematic diagram of AMF acquiring and subscribing ephemeris data from an ephemeris management network element according to an embodiment of the present application;

[0018] FIG. 7 is an interaction schematic diagram of AMF updating ephemeris data after subscribing ephemeris data according to an embodiment of the present application;

[0019] FIG. 8 is an interaction schematic diagram of AMF unsubscribing ephemeris data after subscribing ephemeris data according to an embodiment of the present application;

[0020] FIG. 9 is a flowchart of an ephemeris data processing method according to another embodiment of the present application;

[0021] FIG. 10 is an interaction diagram of synchronizing AMF with ephemeris data to RAN according to an example of the present application;

[0022] FIG. 11 is an interaction diagram of synchronizing AMF with ephemeris data to UE according to an example of the present application;

[0023] FIG. 12 is an interaction diagram of synchronizing PCF with ephemeris data to UE according to an example of the present application;

[0024] FIG. 13 is a structure diagram of NF managing ephemeris data according to an example of the present application;

[0025] FIG. 14 is a structure diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and should not be used to limit the present application.

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

[0028] In the description of the embodiments of the present application, unless otherwise explicitly limited, the words such as setting, installing, connecting, etc. should be understood in a broad sense, and the person skilled in the art can reasonably determine the specific meaning of the above words in the embodiments of the present application according to the specific content of the technical solutions.

[0029] In the embodiments of the present application, the words "further", "exemplarily" or "optionally" are used to represent as an example, illustration or description, and should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. The words "further", "exemplarily" or "optionally" are used to present the related concept in a specific way.

[0030] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a wideband code division multiple access (WCDMA) mobile communication system, an evolved universal terrestrial radio access network (EUTRAN) system, a next generation radio access network (NG RAN) system, a long term evolution (LTE) system, a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) system such as new radio access technology (NR), and a future communication system such as a 6G system.

[0031] In the related art, with the further development of mobile communication, satellite communication is becoming more and more mature. There are various networking modes for satellite communication, for example, a regenerative mode in which a base station and a user plane function (UPF) are deployed on a satellite.

[0032] In satellite communication, since a communication satellite operates in an earth orbit, only part of the time is connected with a ground system due to the movement of the satellite. Ephemeris data of the satellite can be used by a user equipment (UE) and multiple network functions (NFs). For the UE, the ephemeris data can assist in calculating the time when the satellite can serve the UE. For an access and mobility management function (AMF), in a non-continuous coverage scenario, the ephemeris data can assist in calculating the time when the UE can be served by the satellite, and the time information when the UE can be served by the satellite is notified to the UE. A session management function (SMF) can assist in managing or selecting a user plane function (UPF) based on the ephemeris data. For the radio, a conditional handover can be initiated based on the ephemeris data. Other NFs can estimate traffic changes based on the ephemeris data and take appropriate scaling strategies. Therefore, the ephemeris data of the satellite is very important for the mobile network.

[0033] In the related art, operation administration and maintenance (OAM) is usually used to directly configure ephemeris data on a functional network element that needs to use the ephemeris data. All functional network elements that need to use the ephemeris data need to be configured with the ephemeris data, and the management and maintenance of the ephemeris data is very troublesome. How to improve the convenience of ephemeris data management is a problem that needs to be discussed and solved at present.

[0034] Based on this, the embodiment of the application provides an ephemeris data processing method, a communication device, a storage medium and a product. By setting 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. The target functional network element that needs to use the ephemeris data obtains the target ephemeris data required by the network element device for storing ephemeris data, without manual configuration by OAM. When the ephemeris data needs to be updated or managed and maintained, only the network element device for storing ephemeris data needs to be operated, the centralized management of the ephemeris data is realized, the maintenance is facilitated, and the convenience of ephemeris data management is improved.

[0035] The embodiment of the application will be further described below with reference to the drawings.

[0036] FIG. 1 is a networking schematic diagram of a satellite-ground system of satellite communication provided by an embodiment of the application. As shown in FIG. 1, the satellite-ground system refers to a communication system including a satellite subsystem and a ground subsystem 120, wherein the satellite subsystem is composed of multiple satellites 110, and the ground subsystem 120 is composed of multiple network functional network elements.

[0037] The satellite 110 is a microwave communication device deployed in a space segment and capable of providing functions such as long-distance voice, data, image and video transmission. When the satellite 110 runs to a corresponding position, it establishes a wireless communication connection with the terminal 140 and / or the gateway station 130 to perform data inter-transmission. The satellite 110 also has a RAN and a UPF deployed therein. The radio access network (RAN) is responsible for air interface resource scheduling and air interface connection management of terminal access to the network; and the UPF is a core network user plane function entity, responsible for forwarding user data packets and performing statistics on user data packets for functions such as charging.

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

[0039] Authentication Server Function (AUSF): a core network control plane entity, mainly responsible for the authentication and authorization of users to ensure that the user is a legitimate user.

[0040] Unified Data Management (UDM): a core network control plane entity, a home user server, permanently storing user subscription data.

[0041] Policy Control Functionality (PCF): a core network control plane entity, responsible for access and mobility management policy, UE policy, session management policy and charging rules function entity. This function entity mainly generates access and mobility management policy, UE routing selection policy, quality of service (QoS) rules for user data transmission and charging rules according to service information, user subscription information and operator configuration information.

[0042] Access and Mobility Management Function (AMF): a core network control plane entity, mainly responsible for user mobility management, including registration and temporary identifier allocation; maintaining IDLE and CONNECT states and state migration; handover in CONNECT state; paging in IDLE state, etc.

[0043] Session Management Function (AMF): a core network control plane entity, mainly responsible for maintaining protocol data unit sessions, responsible for allocating user IP addresses, with QoS control and charging functions; receiving downlink data packets in IDLE state and notifying AMF to page the user, etc.

[0044] The gateway station 130 is deployed on the ground and carries out the data exchange function of the satellite communication satellite-ground system, and is responsible for collecting and distributing satellite communication business data. The satellite 110 and the ground subsystem 120 exchange data through the gateway station 130.

[0045] The terminal 140 exchanges data with the satellite 110 through a wireless communication connection. The terminal 140 mainly accesses the satellite-ground system network through a wireless air interface and obtains services. The terminal 140 exchanges information with a base station through the air interface and exchanges information with an AMF through non-access stratum (NAS) signaling. The terminal 140 includes various forms such as a desktop computer, a laptop computer, a PDA (personal digital assistant), a mobile phone, a vehicle-mounted terminal, a home theater terminal, and a dedicated terminal. In addition, the terminal 140 can be a single device or a collection of multiple devices. For example, multiple devices are connected through a local area network, share a display device for collaborative work, and collectively constitute a terminal.

[0046] The network element for performing the method for processing ephemeris data provided in the present application can be an independent network element separately deployed in the ground subsystem 120. The method for processing ephemeris data provided in the present application can also be deployed in an existing network function network element.

[0047] FIG. 2 is a schematic diagram of managing ephemeris data according to an example of the present application. Referring to FIG. 2, there is an NF that manages ephemeris data and multiple NFs that need to use ephemeris data. The multiple NFs that need to use ephemeris data respectively establish a communication connection with the NF that manages ephemeris data.

[0048] The NF that manages ephemeris data is a newly set independent function network element. The NF that manages ephemeris data is responsible for obtaining ephemeris data and storing and analyzing the ephemeris data. The NF that needs to use ephemeris data refers to each function network element in the core network that needs ephemeris data, such as an AMF, a PCF, and an SMF.

[0049] The NF that manages ephemeris data receives ephemeris data reported by a radio access network and stores these ephemeris data in a local database. Each NF that needs to use ephemeris data sends an acquisition request to the NF that manages ephemeris data to obtain the required ephemeris data in the case that the local NF does not have complete ephemeris data. The NF that needs to use ephemeris data can also subscribe to ephemeris data from the NF that manages ephemeris data to achieve synchronized updating of ephemeris data and obtain the latest ephemeris data.

[0050] This example sets the NF that manages ephemeris data to uniformly obtain and manage ephemeris data. The ephemeris data of relevant satellites is obtained according to communication association information and is stored in a local ephemeris database. The NF that needs to use ephemeris data uniformly obtains the required ephemeris data from the NF that manages ephemeris data without manual configuration by OAM. When ephemeris data needs to be updated or managed and maintained, only the NF that manages ephemeris data needs to be operated. This achieves centralized management of ephemeris data, facilitates maintenance, and improves the convenience of ephemeris data management.

[0051] FIG. 3 is a flowchart of a method for processing ephemeris data according to an embodiment of the present application. The method for processing ephemeris data can be applied to a network element device, any network element in the ground subsystem 120 shown in FIG. 1, or an NF for managing ephemeris data shown in FIG. 2, but is not limited thereto. As shown in FIG. 3, the method for processing ephemeris data includes at least the following steps, but is not limited thereto:

[0052] In step 310, ephemeris data is obtained according to the communication association information, and the ephemeris data is stored in an ephemeris database.

[0053] In step 320, target ephemeris data corresponding to the ephemeris data acquisition request is obtained from the ephemeris database according to the ephemeris data acquisition request, and the target ephemeris data is sent to a target functional network element corresponding to the ephemeris data acquisition request.

[0054] In step 310, the communication association information refers to information indicating a satellite associated with satellite communication. Through the communication association information, satellite devices participating in the current networking can be determined, and ephemeris data corresponding to the satellite devices can be obtained. The ephemeris data refers to information for describing the flight trajectory of a satellite, such as the position and speed of the satellite on the orbit, etc. The ephemeris data includes multiple parameters, such as time parameters, Kepler orbit parameters, and orbit perturbation force parameters, etc.

[0055] The ephemeris database refers to a database locally used by a network element device to store ephemeris data. The network element device refers to a network element for executing the method for processing ephemeris data provided by the embodiments of the present application, which 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, analyzing, etc. the ephemeris data, for managing the ephemeris data. For easier understanding, the network element device will be referred to as an ephemeris management network element hereinafter.

[0056] In step 320, the ephemeris data acquisition request is a request for obtaining ephemeris data from the ephemeris management network element. The request can be sent by a functional network element needing to use ephemeris data to the ephemeris management network element, or can be a request generated internally by the ephemeris management network element to trigger the ephemeris management network element to send corresponding target ephemeris data to a target functional network element.

[0057] The target ephemeris data refers to ephemeris data in the ephemeris database corresponding to the ephemeris data acquisition request. The target functional network element refers to a network element needing to use ephemeris data for business processing, communication management, etc. For example, the AMF, SMF, PCF, UPF, UDM, or other 4G or 6G communication network needing to use ephemeris data, which is not limited herein.

[0058] In steps 310 and 320, the ephemeris data of the satellites is obtained according to the communication association information and stored in the local ephemeris database by setting the network element device for storing the ephemeris data. The target function network elements that need to use the ephemeris data obtain the target ephemeris data required from the network element device for storing the ephemeris data, without the need for manual configuration by the OAM one by one. When the ephemeris data needs to be updated or managed and maintained, only the network element device for storing the ephemeris data needs to be operated, the centralized management of the ephemeris data is realized, the maintenance is facilitated, and the convenience of the ephemeris data management is improved.

[0059] The above is the general description of steps 310 and 320, and the specific implementation process of steps 310 and 320 is described in detail below.

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

[0061] Obtaining static configuration data, and extracting the ephemeris data from the static configuration data;

[0062] Obtaining the ephemeris data of at least one satellite corresponding to the communication association information from a satellite data server;

[0063] Obtaining the ephemeris data reported by each access network node to the first function network element through the first function network element, wherein the first function network element includes a network element directly interacting with the wireless access network.

[0064] In this embodiment, the static configuration data refers to the data configured to the ephemeris management network element by the OAM. In the embodiment of the present application, only the static configuration data carrying the ephemeris data needs to be written to the ephemeris management network element, and the ephemeris data is distributed to other function network elements by the ephemeris management network element, without the need for configuring the ephemeris data to each function network element respectively, thereby improving the convenience of the ephemeris data configuration.

[0065] The satellite data server refers to a third-party server storing the ephemeris data of the satellites, for example, a server of an enterprise responsible for operating the communication satellite. By obtaining the ephemeris data of the satellites required from the satellite data server, the ephemeris data obtained by static configuration or dynamic learning can be supplemented, and the integrity of the ephemeris data is improved.

[0066] The first function network element refers to a network element directly interacting with the wireless access network, such as AMF or PCF. The access network node refers to various nodes of the RAN providing a wireless interface for user equipment (such as mobile phones, computers, etc.) to connect to the core network through wireless connection. Exemplarily, the access network node can be a base station. Since the RAN needs ephemeris data for resource management, especially the RAN deployed on satellites. Therefore, the RAN usually carries ephemeris data. Therefore, the ephemeris management network element can obtain the ephemeris data in the RAN through the function network element connected with the RAN directly, and realize dynamic learning of the ephemeris data.

[0067] In an embodiment, the ephemeris data reported by each access network node to the first function network element is obtained through the first function network element, including:

[0068] The ephemeris data reporting request of the first function network element is received, wherein the ephemeris data reporting request is obtained according to the ephemeris data carried in the NG establishment request of each access network node, and the access network node includes the access network node deployed on the satellite and the access network node deployed on the ground;

[0069] The ephemeris data is obtained according to the ephemeris data reporting request, and the ephemeris data is updated to the ephemeris database.

[0070] In this embodiment, the ephemeris data reporting request refers to the information carrying the ephemeris data corresponding to the access network node connected with the first function network element based on the first function network element. The ephemeris management network element receives the ephemeris data reporting request to extract the ephemeris data, and returns the ephemeris data reporting response to inform the first function network element that the reported ephemeris data has been received.

[0071] The NG establishment request refers to the request sent by the access network node (RAN node) to establish the NG interface with the first function network element for communication connection. The NG interface refers to the interface between the wireless access network and the core network. The access network node carries the ephemeris data through the NG establishment request to upload the ephemeris data stored by itself to the first function network element. Therefore, the first function network element can obtain the ephemeris data of each access network node connected with it. The first function network element uploads the obtained ephemeris data to the ephemeris management network element, and the ephemeris management network element stores the ephemeris data to the local ephemeris database.

[0072] Exemplarily, FIG. 4 is an interaction schematic diagram of the AMF synchronizing the ephemeris data to the ephemeris management network element provided by an example of the present application. As shown in FIG. 4, in this example, the first function network element is assumed to be the AMF, and the ephemeris management network element is a network element independently storing and managing the ephemeris data. The ephemeris management network element automatically and dynamically updates the ephemeris data through the AMF as follows:

[0073] In step 401, when the RAN sends the NG establishment request message to the AMF, the ephemeris data is carried.

[0074] At step 402, the AMF returns an NG setup response message to the RAN. The AMF establishes the NG interface to communicate with the RAN according to the NG setup request, and generates the NG setup response message. The AMF also extracts the ephemeris data carried in the NG setup request and stores it.

[0075] At step 403, the AMF sends an ephemeris data reporting request message to the ephemeris management network element, where the ephemeris data reporting request message carries the ephemeris data extracted by the AMF from the NG setup request. Illustratively, the AMF generates the ephemeris data reporting request message periodically and sends it to the ephemeris management network element; or alternatively, the AMF generates the ephemeris data reporting request to upload the ephemeris data to the ephemeris data network element each time it extracts the ephemeris data from the message sent by the RAN or receives the ephemeris data reported by the RAN.

[0076] At 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 the ephemeris data reporting response message and returns it to the AMF to inform the AMF that the ephemeris data has been received.

[0077] At step 405, the ephemeris management network element stores the ephemeris data of the RAN reported through the AMF.

[0078] At step 406, the RAN discovers that the ephemeris data has changed.

[0079] At step 407, the RAN sends a configuration update request message to the AMF, where the configuration update request message carries the new ephemeris data.

[0080] At step 408, the AMF returns a configuration update response message to the RAN. The AMF updates the configuration information of the RAN according to the configuration update request message, and generates the configuration update response message. The AMF also extracts the new ephemeris data from the configuration update request message.

[0081] At step 409, the AMF sends an ephemeris data reporting request message to the ephemeris management network element, where the ephemeris data reporting request message carries the new ephemeris data reported by the RAN.

[0082] At 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 the ephemeris data reporting response message and returns it to the AMF to inform the AMF that the ephemeris data has been received.

[0083] At step 411, the ephemeris management network element updates the new ephemeris data reported through the AMF to the ephemeris database.

[0084] In the above embodiments, the first function network element collects ephemeris data of each access network node connected thereto and reports the ephemeris data to the ephemeris management network element. Thus, the ephemeris management network element can automatically and dynamically learn the ephemeris data, and the maintenance of the ephemeris data is simplified.

[0085] In an embodiment, the ephemeris data processing method further includes:

[0086] registering function information to a network function library function network element, wherein the function 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;

[0087] receiving a communication association request of a target function network element based on the function information, wherein the target function network element is used to determine that the network element device has ephemeris data storage capability according to the second identifier, and determine the first identifier according to the function information corresponding to the second identifier, and the communication association request is used for communication management of the target function network element corresponding to the ephemeris data.

[0088] In the present embodiment, the network function library function network element, i.e. NRF, is a core network control plane entity, responsible for dynamic registration of service capabilities of network functions and discovery of network functions. After the ephemeris management network element registers its NF information to the NRF, corresponding function information is generated. The function information at least includes the identifier of the ephemeris management network element, and functions supported by the ephemeris management network element, such as storage or extraction of ephemeris data, ephemeris data analysis, etc.

[0089] Exemplarily, FIG. 5 is an interaction schematic diagram of function registration, update and release of the ephemeris management network element to the NRF provided by an example of the present application. In FIG. 5, the ephemeris management network element is a network element having the function of independently storing and managing ephemeris data.

[0090] As shown in FIG. 5, the interaction process between the ephemeris management network element and the NRF is as follows:

[0091] Step 501, the ephemeris management network element sends a network function registration request message to the NRF to register network function information to the NRF; wherein the network function registration request message includes the identifier information of the ephemeris management network element and the capabilities of the ephemeris management network element, such as storage or extraction of ephemeris data, ephemeris data analysis, etc.

[0092] 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 network element and the capabilities of the ephemeris management network element therein, generates corresponding function information for storage, 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 network element to inform it that the capability registration is completed.

[0093] Step 503, if the ephemeris management network element has network function configuration data update, a network function update request message is sent to the NRF, and the network function information is updated to the NRF.

[0094] Step 504, the NRF returns a network function update response message. The NRF updates the capability information of the ephemeris management network element stored by itself based on the network function update request message, generates a network function update response message, and returns it to the ephemeris management network element to inform it of the completion of the capability update.

[0095] Step 505, if the ephemeris management network element no longer provides services, a network function release request message is sent to the NRF to make the NRF release the network function information.

[0096] Step 506, the NRF returns a network function release response message. The NRF releases the capability information of the ephemeris management network element according to the network function release request message, generates a network function release response message, and returns it to the ephemeris management network element to inform it of the completion of the capability release.

[0097] In an embodiment, step 320 comprises:

[0098] extracting ephemeris data of at least one satellite corresponding to the ephemeris acquisition request from the ephemeris database as target ephemeris data in response to the ephemeris acquisition request generated by the target function network element according to the service function corresponding to the target function network element;

[0099] sending the target ephemeris data to the target function network element.

[0100] In this embodiment, the ephemeris acquisition request is generated by the demand of the service function corresponding to the target function network element, and is a request for acquiring ephemeris data from the ephemeris management network element. The ephemeris acquisition request includes at least one satellite identifier, so that the ephemeris management network element can extract ephemeris data of the corresponding satellite from the ephemeris database based on the satellite identifier.

[0101] For example, the target function network element is an AMF, and correspondingly, the service function includes that the AMF needs ephemeris data to calculate the satellite available time period in the case of satellite discontinuous coverage, and informs the UE of the information. For example, the target function network element is an SMF, and correspondingly, the service function includes that the SMF needs ephemeris data to calculate the satellite available time period, so as to select and manage the UPF.

[0102] In an embodiment, the method further comprises:

[0103] In response to the ephemeris data subscription request of the target function network element, a subscription relationship for ephemeris data is established with the target function network element, and the ephemeris data subscription request is generated by the target function network element according to the service function corresponding to the target function network element;

[0104] In the case of updating the ephemeris database, the function network element with the subscription relationship is sent the ephemeris data corresponding to the service function in the updated ephemeris database.

[0105] In this embodiment, the ephemeris data subscription request is generated by the target function network element according to the ephemeris data required by the service function supported by the target function network element, and is 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, so that the ephemeris management network element can send new ephemeris data to the subscribed target function network element based on the satellite identifier in the case of updating the ephemeris data of the corresponding satellite.

[0106] In other embodiments of the present application, the target function network element can directly subscribe to all ephemeris data from the ephemeris management network element, and at this time the ephemeris data subscription request can not carry the satellite identifier. After the target function 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 function network element. The ephemeris management network element can send all ephemeris data or only the updated part of ephemeris data.

[0107] Exemplarily, FIG. 6 is an interaction diagram of AMF obtaining and subscribing ephemeris data from the ephemeris management network element according to an example of the present application. As shown in FIG. 6, in this example, it is assumed that the target function network element is AMF, and the ephemeris management network element is a network element that independently stores and manages ephemeris data. The process of AMF obtaining and subscribing ephemeris data from the ephemeris management network element is as follows:

[0108] In step 601, when the AMF needs to discover the 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.

[0109] In step 602, the NRF returns an NF discovery response, which carries target NF list information. The AMF can determine at least that the ephemeris management network element is a network element with the function of storing ephemeris data according to the target NF list information.

[0110] In step 603, the AMF sends an ephemeris data obtaining request to the ephemeris management network element. The ephemeris data obtaining request can carry a satellite identifier, indicating that the ephemeris data of a specific satellite or satellites is needed, or can not carry a satellite identifier, indicating that the ephemeris data of all satellites is needed. The ephemeris data obtaining request sent by the AMF can also carry an identifier indicating that analysis data based on ephemeris data is needed.

[0111] At 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 that analysis data based on ephemeris data is to be acquired, and the ephemeris management network element also supports generating analysis data based on ephemeris data, the ephemeris data acquisition response message carries analysis data based on ephemeris data. If the ephemeris data acquisition request carries a satellite identifier, the ephemeris data acquisition response message carries ephemeris data of a certain satellite or certain satellites corresponding to the identifier. If the ephemeris data acquisition identifier does not carry an identifier, the ephemeris data acquisition response message carries ephemeris data of all satellites.

[0112] At step 605, the AMF sends a subscription request to the ephemeris management network element to subscribe to ephemeris data change notifications.

[0113] At step 606, the ephemeris management network element returns a subscription response message. The subscription relationship establishment is completed.

[0114] At step 607, the AMF calculates the time during which the UE can be served based on the received ephemeris data, and notifies the UE.

[0115] Exemplarily, FIG. 7 is an interaction diagram of updating ephemeris data after an AMF subscribes to ephemeris data according to an example of the present application. As shown in FIG. 7, in this example, it is assumed that the target function network element is an AMF, and the ephemeris management network element is a network element that independently stores and manages ephemeris data. The AMF subscribes to ephemeris data from the ephemeris management network element, and the process of updating ephemeris data based on the subscription relationship is as follows:

[0116] At step 701, when the AMF needs to discover the ephemeris management network element, the AMF sends an NF discovery request to the NRF. The target NF type corresponding to the NF discovery request is an NF that stores ephemeris data, i.e., the ephemeris management network element.

[0117] At step 702, the NRF returns an NF discovery response, which carries target NF list information. The AMF can determine at least that the ephemeris management network element is a network element having a function of storing ephemeris data according to the target NF list information.

[0118] At step 703, the AMF sends an ephemeris data acquisition request to the ephemeris management network element. The ephemeris data acquisition request can carry a satellite identifier, indicating that ephemeris data of a certain satellite or certain satellites is to be acquired, or can not carry a satellite identifier, indicating that ephemeris data of all satellites is to be acquired. The ephemeris data acquisition request sent by the AMF can also carry an identifier indicating that analysis data based on ephemeris data is to be acquired.

[0119] At 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 that analysis data based on ephemeris data is to be acquired, and the ephemeris management network element also supports generating analysis data based on ephemeris data, the ephemeris data acquisition response message carries analysis data based on ephemeris data. If the ephemeris data acquisition request carries a satellite identifier, the ephemeris data acquisition response message carries ephemeris data of a certain satellite or certain satellites. If the ephemeris data acquisition identifier does not carry an identifier, the ephemeris data acquisition response message carries ephemeris data of all satellites.

[0120] At step 705, the AMF sends a subscription request to the ephemeris management network element to subscribe to ephemeris data change notifications.

[0121] At step 706, the ephemeris management network element returns a subscription response message. The subscription relationship establishment is completed.

[0122] At step 707, the ephemeris management network element discovers that ephemeris data has changed (ephemeris data is updated).

[0123] At step 708, the ephemeris management network element sends a subscription notification request message to the AMF, which carries new ephemeris data.

[0124] At step 709, the AMF returns a subscription notification response message to the ephemeris management network element.

[0125] Exemplarily, FIG. 8 is an interaction diagram of AMF subscribing to ephemeris data and then unsubscribing to ephemeris data according to an example of the present application. As shown in FIG. 8, in this example, it is assumed that the target function network element is an AMF, and the ephemeris management network element is a network element that independently stores and manages ephemeris data. The process of the AMF subscribing to ephemeris data and then unsubscribing to ephemeris data from the ephemeris management network element is as follows:

[0126] At step 801, when the AMF needs to discover the ephemeris management network element, the AMF sends an NF discovery request to the NRF. The target NF type corresponding to the NF discovery request is an NF that stores ephemeris data, i.e., the ephemeris management network element.

[0127] At step 802, the NRF returns an NF discovery response, which carries target NF list information. The AMF can determine at least that the ephemeris management network element is a network element having a function of storing ephemeris data according to the target NF list information.

[0128] At step 803, the AMF sends an ephemeris data acquisition request to the ephemeris management network element. The ephemeris data acquisition request can carry a satellite identifier, indicating that ephemeris data of a certain satellite or certain satellites is to be acquired, or can not carry a satellite identifier, indicating that ephemeris data of all satellites is to be acquired. The ephemeris data acquisition request sent by the AMF can also carry an identifier indicating that analysis data based on ephemeris data is to be acquired.

[0129] At step 804, the ephemeris management network element returns an ephemeris data acquisition response message, and the ephemeris data acquisition response message carries ephemeris data. If the ephemeris data acquisition request carries an identifier indicating acquisition of analysis data based on ephemeris data, and the ephemeris management network element also supports generation of analysis data based on ephemeris data, the ephemeris data acquisition response message carries analysis data based on ephemeris data. If the ephemeris data acquisition request carries a satellite identifier, the ephemeris data acquisition response message carries ephemeris data of a certain satellite or certain satellites corresponding to the identifier. If the ephemeris data acquisition identifier does not carry an identifier, the ephemeris data acquisition response message carries ephemeris data of all satellites.

[0130] At step 805, the AMF sends a subscription request to the ephemeris management network element to subscribe to ephemeris data change notifications.

[0131] At step 806, the ephemeris management network element returns a subscription response message to complete establishment of a subscription relationship.

[0132] At step 807, the AMF discovers that it no longer needs to acquire updates of ephemeris data.

[0133] At step 808, the AMF sends an unsubscription request to the ephemeris management network element.

[0134] At step 809, the ephemeris management network element returns an unsubscription response to the AMF.

[0135] In an embodiment, the method further includes:

[0136] acquiring ephemeris data corresponding to each target function network element;

[0137] generating analysis data corresponding to each target function network element for satellite availability based on ephemeris data corresponding to each target function network element and regional characteristic data corresponding to each target function network element, wherein the analysis data includes satellite time around the earth and a time period in which a satellite provides services to a target region;

[0138] sending the analysis data to the corresponding target function network element.

[0139] In this embodiment, the regional characteristic data corresponding to the target function network element refers to regional information corresponding to the target function network element, such as latitude and longitude information, communication scheduling strategy information corresponding to a region, and the like.

[0140] The time period in which the satellite provides services to the target area includes a start time and a time length in which the satellite provides services. The target area can be a tracking area (TA), a tracking area list (TA List), a public land mobile network (PLMN), or other certain area range, which is not limited herein.

[0141] The above embodiment analyzes the ephemeris data directly by the ephemeris management network element, and sends the analysis data to the target function network element. Thus, the target function network element does not need to analyze the ephemeris data additionally, the resource occupation of the target function network element is reduced, and the communication efficiency is improved.

[0142] FIG. 9 is a flowchart of an ephemeris data processing method according to another embodiment of the present application. The ephemeris data processing method can be applied to a function network element, a function network element requiring ephemeris data in the ground subsystem 120 shown in FIG. 1, or an NF requiring ephemeris data shown in FIG. 2, but is not limited thereto. As shown in FIG. 9, the ephemeris data processing method includes at least the following steps, but is not limited thereto:

[0143] In step 910, the target ephemeris data is obtained from the ephemeris database by the network element device according to the ephemeris data acquisition request.

[0144] In step 920, the communication resources that can be provided by the satellite corresponding to the target ephemeris data are determined according to the target ephemeris data.

[0145] In step 910, the network element device refers to a network element having the functions of storing and managing ephemeris data, which can be an independently set network element or an existing function 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 better understanding, the network element device is referred to as an ephemeris management network element hereinafter.

[0146] The ephemeris database refers to a database locally used by the network element device to store ephemeris data. The target ephemeris data refers to the ephemeris data required by the function network element, such as the ephemeris data of a certain satellite or certain satellites.

[0147] In step 920, the communication resources that can be provided by the satellite include at least the serviceable time period of the satellite, the serviceable area of the satellite, the bandwidth corresponding to the satellite, and the like.

[0148] In steps 910 and 920, the ephemeris data of the satellites are stored in the ephemeris database of the network element device locally, and are uniformly managed by setting the network element device for storing the ephemeris data. The functional network elements that need to use the ephemeris data obtain the target ephemeris data required from the network element device for storing the ephemeris data, without manual configuration by the OAM one by one. When the ephemeris data needs to be updated or managed and maintained, the network element device for storing the ephemeris data is only needed to be operated, the centralized management of the ephemeris data is realized, the maintenance is facilitated, and the convenience of the ephemeris data management is improved.

[0149] It should be noted that steps 910 and 920 correspond to each embodiment of the functional network element side and each embodiment related to the functional network element side, and the specific implementation details and beneficial effects involved in the above ephemeris data processing method applied to the network element device side can be determined in each embodiment, which will not be described here.

[0150] In an embodiment, the ephemeris data processing method further comprises:

[0151] sending an ephemeris data subscription request to the network element device, and establishing 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;

[0152] receiving the updated ephemeris data sent by the network element device when the ephemeris database of the network element device is updated.

[0153] By subscribing to the ephemeris data of the network element device (the ephemeris management network element), a subscription relationship is established, and the latest ephemeris data can be obtained in time.

[0154] In an embodiment, after receiving the updated ephemeris data sent by the network element device, the ephemeris data processing method further comprises:

[0155] In the case of receiving the updated ephemeris data sent by the network element device, determining the access network node corresponding to the updated ephemeris data;

[0156] sending the updated ephemeris data to the access network node.

[0157] Exemplarily, the access network node corresponding to the updated ephemeris data refers to the association relationship between the satellite to which the updated ephemeris data belongs and the access network node.

[0158] Exemplarily, FIG. 10 is an interaction diagram of the AMF synchronizing the ephemeris data to the RAN provided by an example of the present application. As shown in FIG. 10, in the present example, it is assumed that the functional network element is the AMF. The specific process of the AMF sending the ephemeris data to the RAN (corresponding to the access network node) is as follows:

[0159] Step 1001, the RAN sends an NG setup request message to the AMF, and the NG setup request message does not carry ephemeris data.

[0160] Step 1002, the AMF returns an NG setup response message to the RAN. If the AMF finds that the NG setup request message sent by the RAN does not carry ephemeris data, and the AMF determines according to a local policy that it needs to deliver ephemeris data to the RAN, the AMF carries ephemeris data in the NG setup response message.

[0161] Step 1003, the AMF finds that ephemeris data has been updated, and the RAN has previously synchronized the ephemeris data.

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

[0163] Step 1005, the RAN returns a configuration update response message to the AMF.

[0164] In an embodiment, the ephemeris data processing method further includes:

[0165] receiving a registration request sent by a terminal;

[0166] in a case where the registration request carries a support synchronization ephemeris data identifier, sending a registration acceptance response carrying ephemeris data to the terminal;

[0167] in a case where updated ephemeris data sent by a network element device is received, sending the updated ephemeris data to the terminal.

[0168] In an embodiment, the registration request is a request used by the terminal to register its own information. The support synchronization ephemeris data identifier is an identifier used to indicate that the terminal can support synchronization of ephemeris data, or that the terminal needs to perform synchronization of ephemeris data.

[0169] If the registration request of the terminal does not carry the support synchronization ephemeris data identifier, or the support synchronization ephemeris data identifier is no (not supported), the registration acceptance response sent by the functional network element to the terminal also does not carry ephemeris data. When the functional network element itself updates its own ephemeris data, it also does not synchronize the new ephemeris data to the terminal.

[0170] In an example, FIG. 11 is an interaction diagram of synchronization of ephemeris data by an AMF to a UE according to an example of the present application. As shown in FIG. 11, in this example, it is assumed that the functional network element is an AMF. The process of synchronization of ephemeris data by the AMF to the UE (terminal) is as follows:

[0171] Step 1101, the UE sends a registration request message to the AMF, and the message carries a support synchronization ephemeris data identifier, and the state indicated by the identifier is set to support.

[0172] Step 1102, the AMF processes the registration procedure, and sends a registration accept message to the UE. If the UE supports synchronization ephemeris data and the AMF also supports synchronization ephemeris data to the UE, the registration accept message carries ephemeris data.

[0173] Step 1103, the AMF discovers that ephemeris data is updated. Or the AMF receives updated ephemeris data from the ephemeris management network element.

[0174] Step 1104, if the AMF has synchronized ephemeris data to the UE before, the AMF sends a UE configuration update command to the UE, which carries updated ephemeris data.

[0175] Step 1105, the UE returns a UE configuration update complete message to the AMF.

[0176] In another example, FIG. 12 is an interaction diagram of the PCF synchronizing ephemeris data to the UE according to an example of the present application. As shown in FIG. 12, in this example, it is assumed that there are functional network elements AMF and PCF. The process of the PCF synchronizing ephemeris data to the UE is as follows:

[0177] Step 1201, the UE sends a registration request message to the AMF, which carries a synchronization ephemeris data support identifier, and sets the state indicated by the identifier to support.

[0178] Step 1202, the AMF processes the registration procedure, and sends a registration accept message to the UE.

[0179] Step 1203, the AMF sends a UE policy establishment request message to the PCF, which carries a synchronization ephemeris data support identifier, and also sets the state to support.

[0180] Step 1204, the PCF returns a UE policy establishment response message to the AMF.

[0181] Step 1205, if the UE supports synchronization ephemeris data and the PCF also supports synchronization ephemeris data to the UE, the PCF sends an N1N2 message delivery request carrying ephemeris data to the AMF.

[0182] Step 1206, the AMF returns an N1N2 message delivery response to the PCF.

[0183] Step 1207, the AMF sends a UE configuration update command carrying ephemeris data to the UE.

[0184] Step 1208, the UE returns a UE configuration update complete message to the AMF.

[0185] Step 1209, the PCF discovers that ephemeris data is updated.

[0186] Step 1210, if the UE is previously synchronized with ephemeris data, the PCF sends an N1N2 message delivery request carrying the updated ephemeris data to the AMF.

[0187] Step 1211, the AMF returns an N1N2 message delivery response to the PCF.

[0188] Step 1212, the AMF sends a UE configuration update command carrying the updated ephemeris data to the UE.

[0189] Step 1213, the UE returns a UE configuration update completion message to the AMF.

[0190] In an embodiment, after receiving the target ephemeris data sent by the network element device, the method further comprises:

[0191] According to the target ephemeris data, determining the serviceable area and serviceable time of the user plane function network element deployed on the satellite corresponding to the target ephemeris data;

[0192] Sending the serviceable area and serviceable time to the terminal.

[0193] In this embodiment, the core network user plane NF is on the satellite, that is, the RAN and UPF in the core network are deployed on the satellite. After the core network control plane NF obtains the ephemeris data from the ephemeris management network element, it can calculate the area and time that the core network user plane NF can serve, and optimize the management of the core network user plane NF. Exemplarily, the function network element that uses the ephemeris data to optimize the user plane NF can be the SMF, the control plane of the Serving Gateway (SGW), the control plane of the Packet Data Network Gateway (PGW), or the control plane of the Session Border Controller (SBC).

[0194] In an embodiment, after receiving the target ephemeris data sent by the network element device, the ephemeris data processing method further comprises:

[0195] Obtaining the location information and time information of the historical access of the terminal;

[0196] According to the historical access location information and time information and the target ephemeris data, determining the target satellite;

[0197] Sending a paging instruction to the target satellite to make the target satellite page the terminal.

[0198] In this embodiment, after the core network function network element obtains the ephemeris data from the ephemeris management network element, based on the location and time of the previous access of the user, the core network function network element calculates the satellites currently serving the location previously accessed by the user, selects a suitable satellite to page the user, and optimizes the paging of the user. Exemplarily, the core network function network element that uses the ephemeris data to optimize paging can be an AMF, can be a Mobility Management Entity (MME), can be a 6G NF responsible for connection management, or can be a NF responsible for connection management in other systems.

[0199] The ephemeris data processing method of the present application will be specifically described below by way of examples. It can be understood that the following embodiments are only used to better illustrate the ephemeris data processing method of the present application and are not limited in specific.

[0200] FIG. 13 is a structural schematic diagram of a NF for managing ephemeris data according to an example of the present application. As shown in FIG. 13, the NF for managing ephemeris data includes an ephemeris data analysis unit, an ephemeris data providing unit, an ephemeris data storage unit, and an ephemeris data obtaining unit.

[0201] The ephemeris data obtaining unit is configured to obtain ephemeris data. For example, the ephemeris data is statically configured into the ephemeris data obtaining unit by an OAM, or the ephemeris data obtaining unit obtains the ephemeris data of the target satellite from a third-party server, or the ephemeris data obtaining unit dynamically learns the ephemeris data from a RAN.

[0202] The ephemeris data storage unit is configured to store the ephemeris data obtained by the ephemeris data obtaining unit into an ephemeris database.

[0203] The ephemeris data analysis unit is configured to extract the ephemeris data from the ephemeris data storage unit and perform analysis and processing to obtain analysis data, and return the analysis data to the ephemeris data storage unit for storage.

[0204] The ephemeris data providing unit is configured to extract the ephemeris data or analysis data from the ephemeris data storage unit and send it to the NF using the ephemeris data.

[0205] The present example sets the NF for managing ephemeris data to uniformly obtain and manage ephemeris data, and obtains the ephemeris data of the relevant satellites according to the communication association information and stores it in the local ephemeris database. The NF that needs to use the ephemeris data uniformly obtains the required ephemeris data from the NF for managing ephemeris data, without the need for manual configuration by the OAM one by one. When it is necessary to update or manage and maintain the ephemeris data, only the NF for managing ephemeris data needs to be operated, which realizes the centralized management of ephemeris data, is convenient for maintenance, and improves the convenience of ephemeris data management.

[0206] FIG. 14 is a structural schematic diagram of a communication device according to an embodiment of the present application. As shown in FIG. 14, the communication device 2000 includes a memory and a processor. The number of memories and processors can be one or more, and one memory 2101 and one processor 2201 are taken as an example in FIG. 14. The memory 2101 and the processor 2201 in the network device can be connected through a bus or other means, and connection through a bus is taken as an example in FIG. 14.

[0207] The memory 2101 is a computer readable storage medium, which can be used to store software programs, computer executable programs and modules, such as program instructions / modules of the method provided in any embodiment of the present application. The processor 2201 realizes the ephemeris data processing method provided in any embodiment of the present application by running the software programs, instructions and modules stored in the memory 2101.

[0208] The memory 2101 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system and application programs required by at least one function. In addition, the memory 2101 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device or other non-volatile solid-state memory device. In some examples, the memory 2101 further includes a memory remotely arranged with respect to the processor 2201, and these remote memories can be connected to the device through a network. Examples of the above network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network and a combination thereof.

[0209] An embodiment of the present application further provides a computer readable storage medium, which stores computer executable instructions, and the computer executable instructions are used to execute the ephemeris data processing method provided in any embodiment of the present application.

[0210] An embodiment of the present application further provides a computer program product, which includes a computer program or computer instructions, and the computer program or computer instructions are stored in a computer readable storage medium. The 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, so that the computer device executes the ephemeris data processing method provided in any embodiment of the present application.

[0211] The application sets a network element device for storing ephemeris data, acquires ephemeris data of relevant satellites according to communication association information and stores the ephemeris data in a local ephemeris database. Target function network elements requiring ephemeris data acquire target ephemeris data required by the network element device for storing ephemeris data, without manually configuring ephemeris information for each target function network element. When ephemeris data needs to be updated or managed and maintained, the network element device for storing ephemeris data is only operated, the centralized management of ephemeris data is realized, maintenance is facilitated, and the convenience of ephemeris data management is improved.

[0212] The system architecture and application scenarios described in the embodiments of the application are used to more clearly illustrate the technical solutions of the embodiments of the application, and do not constitute a limitation on the technical solutions provided by the embodiments of the application. It can be understood by those skilled in the art that, as the system architecture evolves and new application scenarios appear, the technical solutions provided by the embodiments of the application are also applicable to similar technical problems.

[0213] It can be understood by those skilled in the art that all or some steps in the methods disclosed above, and the function modules / units in the systems and devices can be implemented as software, firmware, hardware and appropriate combinations thereof.

[0214] In a hardware implementation, the division between the function modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component can have multiple functions, or one function or step can be performed by several physical components in cooperation. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software can be distributed on a computer readable medium, which can include computer storage media (or non-transitory media) and communication media (or transitory media). As is well 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 storage of 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 technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media typically includes computer readable instructions, data structures, program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and can include any information delivery medium.

[0215] As used in this description, the terms "component," "module," "system" and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process or thread of execution and a component can be localized, partially or wholly, in one computer or distributed between two or more computers. Also, these components can execute from various computer-readable media having various data structures stored thereon. The components can communicate by way of local or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, or across a network such as the Internet with other systems via the signal).

[0216] The above description is intended to explain and describe aspects of the present application that are believed to be of economic importance. Those skilled in the art will readily recognize from this description that alternative embodiments of the application can be practiced that are not specifically described. For example, while methods associated with the present application have been described, it is to be understood that the present application is not limited to the methods described, but is intended to cover any and all methods consistent with the scope of the claims, and their equivalents. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific embodiments described herein. It is therefore to be understood that any alterations and modifications to the specific embodiments described herein are fully intended to be encompassed by the present application. The preceding description is exemplary rather than limiting in nature and, thus, is not intended to indicate any single feature or combination of features is necessary for a system, apparatus, or method to fall within the scope of the present application. Numerous modifications and variations are possible in light of the above teachings. It is, therefore, to be understood that within the scope of the claims, the application can be practiced otherwise than as specifically described. While the present application has been described with reference to one or more particular embodiments thereof, the same should not be construed as limiting the application but rather as illustrating it. Other embodiments and aspects thereof will occur to those skilled in the art upon consideration of the description and figures and are intended to be included within the scope of the claims. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the spirit and scope of the present application. Accordingly, it is intended that all such modifications and variations come within the scope of the claims.

Claims

1. A method for processing ephemeris data, applied to a network element device, the method comprising: obtaining ephemeris data according to communication association information, and storing the ephemeris data into an ephemeris database; obtaining target ephemeris data corresponding to an ephemeris data obtaining request from the ephemeris database according to the ephemeris data obtaining request, and sending the target ephemeris data to a target functional network element corresponding to the ephemeris data obtaining request.

2. The method of processing almanac data according to claim 1, wherein, The obtaining of the target ephemeris data corresponding to the ephemeris data obtaining request from the ephemeris database and the sending of the target ephemeris data to the target functional network element corresponding to the ephemeris data obtaining request comprise: extracting ephemeris data of at least one satellite corresponding to an ephemeris obtaining request of the target functional network element from the ephemeris database as the target ephemeris data in response to the ephemeris obtaining request, wherein the ephemeris obtaining request is generated by the target functional network element according to a service function corresponding to the target functional network element; sending the target ephemeris data to the target functional network element.

3. The method of claim 1 or 2, further comprising: establishing a subscription relationship for the ephemeris data with the target functional network element in response to an ephemeris data subscription request of the target functional network element, wherein the ephemeris data subscription request is generated by the target functional network element according to a service function corresponding to the target functional network element; sending ephemeris data corresponding to the service function in the updated ephemeris database to the functional network element having the subscription relationship in case of an update of the ephemeris database.

4. The method of Claim 1, wherein, The obtaining of the ephemeris data according to the communication association information comprises at least one of: obtaining static configuration data, and extracting the ephemeris data from the static configuration data; obtaining the ephemeris data of at least one satellite corresponding to the communication association information from a satellite data server; obtaining the ephemeris data reported by each access network node to a first functional network element through the first functional network element, wherein the first functional network element comprises a network element directly interacting with a radio access network.

5. The method of claim 4, wherein, The obtaining of the ephemeris data reported by each access network node to the first functional network element through the first functional network element comprises: receiving an ephemeris data reporting request of the first functional network element, wherein the ephemeris data reporting request is obtained according to ephemeris data carried in an NG establishment request of each access network node, and the access network node comprises an access network node deployed on a satellite and an access network node deployed on the ground; obtaining the ephemeris data according to the ephemeris data reporting request, and updating the ephemeris data into the ephemeris database.

6. The method of claim 1, further comprising: registering function information to a network function repository functional network element, wherein the function information comprises a first identifier indicating the network element device and a second identifier indicating that the network element device has ephemeris data storage capability. receive a communication association request of the target function network element based on the function information, wherein the target function network element is configured to determine that the network element device has the ephemeris data storage capability according to the second identifier, and determine the first identifier according to the function information corresponding to the second identifier, and the communication association request is used for the communication management of the target function network element corresponding ephemeris data.

7. The ephemeris data processing method of claim 1, further comprising: obtaining the ephemeris data corresponding to each of the target function network elements; generating analysis data corresponding to each of the target function network elements for the availability of satellites respectively according to the ephemeris data corresponding to each of the target function network elements and the regional characteristic data corresponding to each of the target function network elements, wherein the analysis data comprises satellite time around the earth and time period in which a satellite provides services to a target region; sending the analysis data to the corresponding target function network element.

8. An ephemeris data processing method applied to a function network element, comprising: receiving 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 obtaining request; determining communication resources that can be provided by a satellite corresponding to the target ephemeris data according to the target ephemeris data.

9. The ephemeris data processing method of claim 8, further comprising: sending an ephemeris data subscription request to the network element device to establish a subscription relationship for the ephemeris data with the network element device, wherein the ephemeris data subscription request is generated by the function network element according to a service function corresponding to the function network element; receiving updated ephemeris data sent by the network element device when the ephemeris database of the network element device is updated.

10. The method of processing almanac data according to claim 9, wherein, After receiving the updated ephemeris data sent by the network element device, the method further comprises: determining an access network node corresponding to the updated ephemeris data when the updated ephemeris data sent by the network element device is received; sending the updated ephemeris data to the access network node.

11. The ephemeris data processing method of claim 9, further comprising: receiving a registration request sent by a terminal; sending a registration acceptance response carrying the ephemeris data to the terminal when the registration request carries a support synchronous ephemeris data identifier; sending the updated ephemeris data to the terminal when the updated ephemeris data sent by the network element device is received.

12. The method of processing almanac data according to claim 8, wherein, After receiving target ephemeris data sent by a network element device, the method further comprises: determining a serviceable area and a serviceable time of a user plane function network element deployed on a satellite corresponding to the target ephemeris data according to the target ephemeris data; sending the serviceable area and the serviceable time to a terminal.

13. A communication device, comprising: at least one processor; at least one memory configured to store at least one program; when at least one of the programs is executed by the at least one processor, the method according to any one of claims 1 to 12 is implemented.

14. A computer-readable storage medium storing computer-executable instructions for performing the method of any one of claims 1 to 12.

15. A computer program product comprising a computer program or computer instructions stored in a computer-readable storage medium, a processor of a computer device reading the computer program or the computer instructions from the computer-readable storage medium, the processor executing the computer program or the computer instructions to cause the computer device to perform the method of any one of claims 1 to 12.

Images