Network capability open method, apparatus and network device

Abstract

The present disclosure provides a network capability opening method, apparatus, and network device, and relates to the field of communication technologies. The method includes: obtaining the first network capability and connection capability of a satellite-related device including at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network; releasing the first network capability and the connection capability to a ground-based capability opening function entity, and obtaining a second network capability of a satellite-independent device released by the ground-based capability opening function entity, where the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform.

Description

Cross-reference to Related Applications

[0001] This application claims the priority of Chinese Patent Application No. 202210836183.5, filed in China on July 15, 2022, the entire content of which is incorporated herein by reference.

Technical Field

[0002] The present disclosure relates to the field of communication technologies, and particularly to a network capability open method, apparatus, and network device.

Background Art

[0003] In related technologies, the capabilities of mobile networks and converged networks are realized through one capability open network element, or through a plurality of centralized + distributed capability open network elements, or through a set of capability open network elements in a unified framework. The functions and interfaces of capability opening are designed for terrestrial networks and are relatively complex. In fixed, mobile, and satellite converged networks, compared with terrestrial fixed and mobile nodes, the computing, storage, and connection capabilities of satellite nodes are weak, the communication capacity and speed from satellites to the ground are low, and it is difficult to support the complete capability open functions and interfaces of related technologies. And in fixed, mobile, and satellite converged networks, satellite-based networks and terrestrial-based networks usually belong to different operators and are restricted by the resource conditions of satellite-based networks. Therefore, it is difficult to integrate the capability open systems and network capabilities of satellite-based networks and terrestrial-based networks. Therefore, there is still no solution for the capability opening of fixed, mobile, and satellite converged networks.

Summary of the Invention

[0004] The objective of the present disclosure is to provide a network capability open method, apparatus, and network device, which can realize the capability opening of fixed, mobile, and satellite converged networks.

[0005] To achieve the above object, an embodiment of the present disclosure provides a network capability release method applied to a satellite-based capability release function entity, the method comprising: acquiring the first network capability and connection capability of a satellite-related device including at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network; releasing the first network capability and the connection capability to a ground-based capability release function entity, and acquiring the second network capability of a satellite-independent device released by the ground-based capability release function entity, wherein the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform.

[0006] Optionally, the satellite-based capability release function entity is deployed on a target satellite, and the target satellite is determined based on the capability parameters of a plurality of satellites in a target area.

[0007] Optionally, the step of determining the target satellite based on the capability parameters of a plurality of satellites in the target area includes: determining a selected value based on the respective capability parameters of the plurality of satellites in the target area; and interacting the selected value among the plurality of satellites in the target area, and determining the satellite with the largest selected value as the target satellite.

[0008] Optionally, the satellite-based capability release function entity assigns a default value to the parameter of the network capability, and / or the message header field of the network capability sent by the satellite-based capability release function entity includes only the request method, the API name, and the Host host name.

[0009] Optionally, after obtaining the first network capability and connection capability of the satellite-related device, releasing the first network capability and the connection capability to a third-party application device; and / or further comprising receiving location information and connection capability transmitted by a multi-connection terminal, and transmitting the location information and the connection capability to the third-party application device.

[0010] Optionally, after obtaining the first network capability and connection capability of the satellite-related device, receiving a call request for the first network capability transmitted by a third-party application device; based on the call request for the first network capability, if it is determined that both the satellite-related device and the multi-connection terminal meet preset conditions, starting a call for the second network capability and feeding back a call response for the first network capability to the third-party application.

[0011] Optionally, after obtaining the second network capability of the satellite-independent device released by the ground-based capability release function entity, receiving a call request for the second network capability transmitted by a third-party application device; based on the call request for the second network capability, if it is determined that the multi-connection terminal meets a preset condition, starting a call for the second network capability with the ground-based capability release function entity and feeding back a call response for the second network capability to the third-party application.

[0012] Optionally, the method further comprises A step of performing a consistency check between the capability information stored in the satellite-based capability release function entity and the capability information stored in the ground-based capability release function entity for each first period, The step further includes that the capability information includes the first network capability, the connection condition, and the second network capability.

[0013] Optionally, the step of performing a consistency check between the capability information stored in the satellite-based capability release function entity and the capability information stored in the ground-based capability release function entity is as follows: Receiving a consistency check request sent by the ground-based capability release function entity, where the consistency check request carries the capability information stored in the ground-based capability release function entity, Based on the consistency check request, determining whether the capability information stored in the ground-based capability release function entity matches the capability information stored in the satellite-based capability release function entity, If they do not match, updating the stored capability information and feeding back the capability information stored in the satellite-based capability release function entity to the ground-based capability release function entity.

[0014] Optionally, the method further includes: Sending an authentication request to the ground-based capability release function entity for each second period, Or, Receiving an authentication request sent by the ground-based capability release function entity and performing an authentication process on the ground-based capability release function entity based on the authentication request.

[0015] Optionally, the method further includes: Sending a charging request to the ground-based capability release function entity for each third period, Or, Further comprising the step of receiving a charging request sent by the ground-based capability release function entity and charging the ground-based capability release function entity based on the charging request.

[0016] Embodiments of the present disclosure further provide a network capability release method applied to a ground-based capability release function entity, the method comprising: Receiving a first network capability and a connection capability of a satellite-related device released by a satellite-based capability release function entity, and releasing a second network capability of a satellite-independent device to the satellite-based capability release function entity, wherein the satellite-related device includes at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network, and the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform.

[0017] Optionally, the method comprises: Sending, to the satellite-based capability release function entity, a consistency check request for transporting the capability information stored in the ground-based capability release function entity every first period, wherein the capability information further includes the first network capability, the connection condition, and the second network capability.

[0018] Optionally, after sending a consistency check request to the satellite-based capability release function entity, Receiving the capability information stored in the satellite-based capability release function entity feedback by the satellite-based capability release function entity based on the consistency check request; and Updating the capability information stored in the ground-based capability release function entity based on the capability information stored in the satellite-based capability release function entity; and further including the step of.

[0019] Optionally, the method includes Sending an authentication request to the satellite-based capability release function entity every second period; Or Receiving an authentication request sent by the satellite-based capability release function entity, and performing an authentication process on the satellite-based capability release function entity based on the authentication request; and further including the step of.

[0020] Optionally, the method includes Sending a charging request to the satellite-based capability release function entity every third period; Or Receiving a charging request sent by the satellite-based capability release function entity, and charging the satellite-based capability release function entity based on the charging request; and further including the step of.

[0021] The embodiments of the present disclosure further provide a network capability release device applicable to a satellite-based capability release function entity, and the device includes An acquisition module for acquiring the first network capability and connection capability of a satellite-related device including at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network; A release module for releasing the first network capability and the connection capability to a ground-based capability release function entity, and acquiring a second network capability of a satellite-independent device released by the ground-based capability release function entity, where the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform.

[0022] Embodiments of the present disclosure further provide a network capability release device applied to a ground-based capability release function entity, and the device includes: an open module configured to receive a first network capability and a connection capability of a satellite-related device released by a satellite-based capability release function entity, and release a second network capability of a satellite-independent device to the satellite-based capability release function entity, where the satellite-related device includes at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network, and the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform.

[0023] Embodiments of the present disclosure further provide a network device, including a transceiver, a processor, and a memory, and including a program or instruction stored in the memory and executable by the processor. When the processor executes the program or instruction, steps in the network capability release method on the satellite-based capability release function entity side or the ground-based capability release function entity side are implemented.

[0024] Embodiments of the present disclosure further provide a readable storage medium storing a program or instruction, and when the program or instruction is executed by a processor, steps in the network capability release method on the satellite-based capability release function entity side or the ground-based capability release function entity side are implemented.

Advantages of the Invention

[0025] The beneficial effects of the above technical solution of the present disclosure are as follows. In an embodiment of the present disclosure, a satellite-based capability open function entity can support a satellite-related device to register a first network capability and a connection capability, and release the first network capability and the connection capability to a ground-based capability open function entity, and obtain a second network capability of a satellite-independent device released by the ground-based capability open function entity. Thereby, support for heterogeneous capability open systems is realized, that is, the capability open systems of the satellite-based network and the ground-based network can adopt different capability open frameworks, adapt to the differences in resources between the satellite-based network and the ground-based network, and reduce the message overhead between the capability open systems.

Brief Description of the Drawings

[0026]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Modes for Carrying Out the Invention

[0027] To more clearly illustrate the technical problems, technical solutions, and advantages to be solved by the present disclosure, the following will be described in detail in combination with the drawings and specific embodiments.

[0028] Note that throughout this specification, "one embodiment" or "an embodiment" means that a specific feature, structure, or characteristic related to the embodiment is included in at least one of the embodiments of the present disclosure. Therefore, the statements "in one embodiment" or "in an embodiment" that appear throughout this specification do not necessarily refer to the same embodiment. Also, these specific features, structures, or characteristics can be combined with one or more embodiments in any suitable manner.

[0029] In various embodiments of the present disclosure, it should be understood that the magnitude of the following process numbers does not mean the execution order of each process, and the execution order of each process should be determined by its function and internal logic and should not limit the implementation process of the embodiments of the present disclosure.

[0030] Also, in this specification, the terms "system" and "network" are often used in the same meaning.

[0031] It should be understood that in the embodiments provided by the present disclosure, "B corresponding to A" means that B is associated with A and B can be determined based on A. Note that determining B based on A does not mean determining B only based on A, but B can also be determined based on A and / or other information.

[0032] With the rapid development of high-throughput satellite communication technology and low-earth orbit satellite communication technology, satellite networks are continuously improving their communication capabilities in terms of capacity, speed, latency, reliability, etc., and can complement and cooperate with terrestrial fixed / satellite networks. Fixed, mobile, and satellite integrated networks support providing communication services such as voice, video, messaging, data, broadcast / multicast, international roaming, and overseas operation to multi-connection terminal users under one or more access methods of fixed access, mobile access, and satellite access, and are multi-access integrated networks that integrate the space and the ground. They have attracted attention in the global communication technology research in recent years and are also an important development direction of the information and communication industry. Generally, they are one of the key architecture support technologies for the extended technology (5G-Advanced, 5G-A) of the 5th Generation Mobile Communication Technology (5G) and the 6th Generation Mobile Communication Technology (6G). The fixed, mobile, and satellite integrated network architecture (ITU-T Y.FMSC-frame) defined by the Telecommunication Standardization Sector of the International Telecommunication Union (ITU-T) is as shown in Figure 1, and this architecture consists of multi-connection terminals, fixed access networks, mobile access networks, satellite access networks, terrestrial-based core networks, satellite-based core networks, terrestrial-based service platforms, satellite-based service platforms, terrestrial-based data networks, and satellite-based data networks.

[0033] The ability open of the mobile network and the converged network is realized by the ability open function, and the ability open function is a Network Exposure Function (NEF) defined by the 3rd Generation Partnership Project (3GPP (registered trademark)) standard or a Capability Exposure Function (CEF) defined by the ITU-T standard.Taking the 5G mobile network as an example, the main functions of its capability open system include supporting the opening to applications through the Application Programming Interface (API) method based on the Hyper Text Transfer Protocol (HTTP) / Hyper Text Transfer Protocol over Secure Socket Layer (HTTPS), supporting the encapsulation and mapping between network information and open API parameters, supporting APIs that are compatible with the 4th Generation Mobile Communication Technology (4G), connecting to 5G network elements such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management entity (UDM), and Policy Control Function entity (PCF) through the service interface to support the invocation of network capabilities such as network event subscription / notification and network data setting, supporting the acquisition and storage of network data, supporting the notification capability for network events, supporting the 5G session binding function, and supporting the execution of the session binding function by the Binding Support Function (BSF) to query the address information of the PCF.

[0034] The open capabilities of the mobile network and the converged network can be realized by a single open capability network element, or through multiple centralized + distributed open capability network elements, or through a set of open capability network elements in a unified framework. One example of the above unified framework is the Common API Framework (CAPIF) defined by the 3GPP TS 23.222 standard, and the functional model of CAPIF is as shown in Figure 2. CAPIF consists of a CAPIF core function, an API release function, an API release function, and an API management function. API callers inside or outside the trusted domain of the communication operator can use the capabilities of the mobile network or the converged network by calling the API.

[0035] The network capabilities of the fixed, mobile, and satellite converged network include fixed network capabilities, mobile network capabilities, satellite network capabilities, and the unique network capabilities of fixed, mobile, and satellite convergence. The unique network capabilities include: (1) satellite service continuity capability, which is the ability to maintain the continuity of audio / video services during the switch between satellite access and fixed / mobile access; (2) satellite handover service quality assurance capability, which is the ability to maintain the consistency of the service quality of audio / video services before and after the handover during the switch between satellite access and fixed / mobile access; (3) unified billing capability, which includes the ability to support the generation of unified billing statements when users use multiple access methods such as fixed access, mobile access, and satellite access, but is not limited to these. The above network capabilities exist in the fixed access network, mobile access network, satellite access network, ground-based core network, satellite-based core network, ground-based service platform, and satellite-based service platform.

[0036] In related technologies, there are the following problems in realizing the open capabilities of the fixed, mobile, and satellite converged network.

[0037] 1. In related technologies, the function and interface of capability openening are designed for terrestrial networks and are relatively complex. In a fixed, mobile, and satellite integrated network, compared with terrestrial fixed and mobile nodes, the computing, memory, and connection capabilities of satellite nodes are weak, the communication capacity from satellites to the ground and the communication speed from satellites to the ground are low, and it is difficult to support the complete capability openening function and interface of related technologies.

[0038] 2. In related technologies, the management, release, and openening mechanism of APIs are disclosed, but the capabilities and the paths of capability openening for third-party application openening are still static and quasi-static. In a fixed, mobile, and satellite integrated network, non-geostationary satellite orbit (NGSO) satellites are introduced, and the inter-satellite network connection and the network connection from satellites to the ground are very dynamic. The capabilities and the paths of capability openening for third-party application openening have the characteristics of changing based on time and space conditions. In related technologies, it is difficult to support dynamic capability openening for dynamic network topologies.

[0039] 3. In related technologies, the management, release, and openening of network capability APIs by one or more operators are supported, but the capability openening system and network capability APIs use a design method based on a unified framework. In a fixed, mobile, and satellite integrated network, satellite-based networks and terrestrial-based networks usually belong to different operators and are restricted by the resource conditions of satellite-based networks. Therefore, it is difficult for the capability openening systems and network capability APIs of satellite-based networks and terrestrial-based networks to adopt a unified capability openening framework. In related technologies, it is difficult to support heterogeneous capability openening systems of multiple operator networks.

[0040] The proposal of the present disclosure targets fixed, mobile, and satellite integrated networks, and provides corresponding solutions for network capability openening to address the above technical problems. The summary is as follows.

[0041] 1. In an embodiment of the present disclosure, a self-organizing selection method is used to select the most appropriate satellite node based on computing power, memory capacity, connection capacity, and software capabilities, and to deploy a satellite-based capability openening function, deploy the openening capabilities related to the satellite, and simplify the openening interface. The method of simplifying the openening interface includes assigning default values to the parameters of the network capability API, shortening the length of the message header field, and the like.

[0042] 2. In an embodiment of the present disclosure, the satellite access network, the satellite-based service platform, and the satellite-based core network support the registration of network capabilities and attached connection conditions in the satellite-based capability openening function. The connection conditions are the connection capabilities under specified time and space conditions, that is, the satellite access network provides a period [t1, t2] during which it has the connection conditions with the satellite-based capability openening function based on the ephemeris information of the satellite node where it is located, and provides the geographical location (longitude range, latitude range) of the satellite node where it is located within this period. The multi-connection terminal reports the Global Navigation Satellite System (GNSS) position and connection capabilities (including the supported connection types and the general connection speeds of each supported connection type) to the satellite-based / ground-based capability openening device. The above method realizes the support for dynamic network topologies.

[0043] 3. In an embodiment of the present disclosure, the satellite-based capability openening function and the ground-based capability openening function support bidirectional capability calls through the "inter-network capability openening interface", and also support a bidirectional capability release mechanism, a periodic capability authentication mechanism, and a periodic capability charging mechanism. The above method realizes the support for heterogeneous capability openening systems.

[0044] Next, in combination with the drawings, the solutions of the embodiments of the present disclosure will be described in detail. The embodiments of the present disclosure provide a fixed, mobile, and satellite fusion network capability open system, as shown in FIG. 3.

[0045] The fixed, mobile, and satellite fusion network capability open system is composed of logic units such as a multi-connection terminal, a fixed access network, a mobile access network, a satellite access network, a ground-based core network, a satellite-based core network, a ground-based service platform, a satellite-based service platform, a ground-based data network, and a satellite-based data network. Here, the ground-based capability open function is arranged in the ground-based core network, the satellite-based capability open function is arranged in the satellite-based core network, and the third-party application is arranged in both the ground-based data network and the satellite-based data network at the same time. The general outlines of the main functions of each logic unit are as follows.

[0046] Multi-connection terminal: Support reporting the GNSS position of the terminal to the satellite-based / ground-based capability open function, and support reporting the connection capability of the terminal (including the fixed / mobile / satellite connection types it supports and the general connection speeds of each supported connection type) to the satellite-based / ground-based capability open function.

[0047] Fixed, mobile, and satellite access networks: The satellite access network supports registering its network capabilities and attached connection conditions in the satellite-based capability open function. The connection conditions are the connection capabilities under specified time and interval conditions, that is, the satellite access network provides a period [t1, t2] with connection conditions to the satellite-based capability open function based on the ephemeris information of the satellite node where it is located, and provides the geographical location (longitude interval, latitude interval) of the satellite node where it is located within this period. The fixed and mobile access networks support registering their network capabilities in the ground-based capability open function.

[0048] Ground-based core network and satellite-based core network: The satellite-based core network deploys a satellite-based capability open function with satellite-related open capabilities and a simplified open interface. The ground-based core network deploys a ground-based capability open function with open capabilities independent of satellites and a standard open interface. The satellite-based core network supports the network capabilities and attached connection conditions in the satellite-based capability open function. The connection conditions are connection capabilities under specified time and space conditions (the same as above). The ground-based core network supports the registration of its network capabilities in the ground-based capability open function. The satellite-based capability open function and the ground-based capability open function support two-way capability calls via the "inter-network capability open interface".

[0049] Ground-based service platform and satellite-based service platform: The satellite-based service platform supports the registration of its network capabilities and attached connection conditions in the satellite-based capability open function. The connection conditions are connection capabilities under specified time and space conditions (the same as above). The ground-based service platform supports the registration of its network capabilities in the ground-based capability open function.

[0050] Ground-based data network and satellite-based data network: Third-party applications are deployed in the ground-based data network or the satellite-based data network as needed, and select the satellite-based capability open function or the ground-based capability open function to call the capabilities of the converged network.

[0051] As shown in Figure 4, the embodiments of the present disclosure provide a network capability open method applied to a satellite-based capability open function entity. The method specifically includes the following steps 41 to 42.

[0052] Step 41: Obtain the first network capabilities and connection capabilities of satellite-related devices including at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network.

[0053] Step 42: Release the first network capabilities and the connection capabilities to a terrestrial-based capability open function entity, and obtain the second network capabilities of non-satellite-dependent devices released by the terrestrial-based capability open function entity. Here, the non-satellite-dependent devices include at least one of a mobile access network, a fixed access network, a terrestrial-based core network, and a terrestrial-based service platform.

[0054] Optionally, the satellite-based capability open function entity can be arranged in a satellite-based core network, with satellite-related open capabilities and a simplified open interface arranged, and support for calling terrestrial-based network capabilities via an "inter-network capability open interface". The satellite-based capability open function performs management, release, and opening of locally registered network capabilities and network capabilities released by the terrestrial-based capability open function entity.

[0055] Optionally, when registering their releasable network capabilities with a satellite-based capability release function entity, a satellite access network, a satellite-based service platform, and a satellite-based core network need to provide connection conditions associated with releasing the network capabilities. The connection conditions are the connection capabilities under specified time and space conditions, that is, the satellite access network, the satellite-based service platform, and the satellite-based core network need to provide a period [t1, t2] during which they have the connection conditions with the satellite-based capability release function based on the ephemeris information of the satellite nodes where they are located, and the geographical locations (longitude range, latitude range) of the satellite nodes where they are located within this period. Considering that the current satellite ephemeris information includes the real-time trajectory information of each satellite node, it is possible to calculate whether there is a communication connection capability between each satellite node within any time period using related technologies, and therefore, it is possible to provide the above connection conditions.

[0056] Optionally, in addition to the conventional audio / video capability APIs, message capability APIs, data capability APIs, network slice capability APIs, edge computing capability APIs, and various composite capability APIs, the first network capabilities released by a satellite-based capability release function entity further include the unique capabilities of fixed, mobile, and satellite integrated networks. For example, a satellite service continuity capability, which is the ability to maintain the continuity of audio / video services when switching between satellite access and fixed / mobile access; a satellite handover service quality assurance capability, which is the ability to maintain the consistency of the service quality of audio / video services before and after switching when switching between satellite access and fixed / mobile access; and a unified charging capability, which is the ability to support the generation of a unified charging statement when the user uses multiple access methods such as fixed access, mobile access, and satellite access.

[0057] In the above solution, the satellite-based capability release function entity enables satellite-related devices to register the first network capability and the connection capability, and release the first network capability and the connection capability to the ground-based capability release function entity. The ground-based capability release function entity can obtain the second network capability of the satellite-independent device released thereby, thus realizing support for heterogeneous capability release systems. That is, the capability release systems of the satellite-based network and the ground-based network can adopt different capability release frameworks, adapt to the differences in resources between the satellite-based network and the ground-based network, and reduce the message overhead between the capability release systems.

[0058] Optionally, the satellite-based capability release function entity is deployed on the target satellite and determines the target satellite based on the capability parameters of multiple satellites within the target area.

[0059] Here, the step of determining the target satellite based on the capability parameters of multiple satellites within the target area is as follows: Multiple satellites within the target area determine selection values based on their respective capability parameters. Interact the selection values among multiple satellites within the target area, and determine the satellite with the largest selection value as the target satellite.

[0060] Specifically, due to the limitation of the communication capability and communication resources of a single satellite node, the satellite-based core network is usually provided on multiple satellite nodes, forming a simplified core network through a distributed networking method. When it is necessary to deploy the satellite-based capability release function, multiple satellite nodes in one area (designated longitude interval and latitude interval) use a self-organizing selection method to select the most appropriate satellite node to deploy the satellite-based capability release function. The selection method is, for example, Set selection parameters including computing power Comp, memory capacity Sto, connection capacity Con, software capacity Soft, etc., and each satellite node evaluates the possible values VComp, VSto, VCon, VSoft of each selection parameter; Set the normalized weights of the selection parameters WComp, WSto, WCon, WSoft; WComp + WSto + WCon + WSoft = 1; Each satellite node uses a parameter weighting algorithm to calculate its own weighted ability score V = VComp*WComp + VSto*WSto + VCon*WCon + VSoft*WSoft, and interacts the weighted ability scores among the satellite nodes in the area through the handshake protocol; Select the satellite node with the highest weighted ability score in the area and use it for the placement of the satellite-based ability release function.

[0061] Optionally, the satellite-based ability release function entity assigns default values to the parameters of the network ability, and / or the message header field of the network ability sent by the satellite-based ability release function entity only includes the request method, API name, and host name.

[0062] In this embodiment, the satellite-based ability release function entity shortens the length of the message of the network ability API by simplifying the release interface.

[0063] Specifically, due to being restricted by the communication ability and communication resources of a single satellite node, the satellite-based ability release function arranges a simplified release interface. The ways to simplify the release interface include, but are not limited to, assigning default values to the parameters of the network ability API and shortening the length of the message header field.

[0064] For example, default values are assigned to the parameters of the network capability API, and the network capability API usually includes a plurality of configurable parameters. The simplified open interface assigns default values to as many parameters as possible and does not transmit them through the network capability API, thereby shortening the length of the message of the network capability API. Specific examples are as shown in Table 1 and Table 2. [Table 1] [Table 2]

[0065] Also, for example, the length of the message header field is shortened. The message header field of the network capability API usually includes information such as the request method, API name, Host hostname, content type (Content-Type), content length (Content-Length), encoding format, and authentication information. The simplified open interface retains only the necessary information such as the request method, API name, and Host hostname, and other information may adopt default settings, may not be carried, or may not be transmitted in the message, thereby reducing the length of the message header field. Specific examples are as follows.

[0066] Multi-party call API message header field started by the standard open interface POST / appcall / v1 / MakeMultipartiesCall HTTP / 1.1 Host: 10.137.73.227:1302 Content-Type: application / json;charset=utf-8 Content-Length: XXX Accept: application / json Authorization: Bearer 2ZQsweeFFJS1zCsicMspWD

[0067] API message header field started by a simplified open interface POST / appcall / v1 / MakeMultipartiesCall HTTP / 1.1 Host: 10.137.73.227:1302

[0068] Optionally, after obtaining the first network capability and connection capability of the satellite-related device, releasing the first network capability and the connection capability to a third-party application device, and / or receiving location information and connection capability transmitted by a multi-connection terminal, and transmitting the location information and the connection capability to the third-party application device.

[0069] Optionally, after obtaining the first network capability and connection capability of the satellite-related device receiving a call request for the first network capability transmitted by a third-party application device; based on the call request for the first network capability, if it is determined that both the satellite-related device and the multi-connection terminal meet preset conditions, starting a call for the second network capability and feeding back a call response for the first network capability to the third-party application.

[0070] Specifically, when the satellite-based capability open function receives the requests of third-party applications, first, it checks the connection conditions of relevant network elements to determine whether the network capabilities of the satellite access network / satellite-based service platform / satellite-based core network can be invoked. Then, it checks the GNSS position and connection capabilities reported by the multi-connection terminal to determine whether the satellite access network / satellite-based service platform / satellite-based core network can provide services for the specified multi-connection terminal. After these two conditions are met, the satellite-based capability open function further determines the capability invocation path based on the ephemeris information and initiates a call request for the network capabilities of the satellite access network / satellite-based service platform / satellite-based core network. This method improves the success rate of network capability invocation in the satellite networking environment.

[0071] Optionally, after obtaining the second network capability of the satellite-independent device released by the ground-based capability open function entity, receiving a call request for the second network capability sent by the third-party application device; based on the call request for the second network capability, when it is determined that the multi-connection terminal meets the preset conditions, the ground-based capability open function entity initiates a call for the second network capability and feeds back a call response for the second network capability to the third-party application.

[0072] Specifically, the third-party application invokes the ground-based network capabilities through the satellite-based capabilities release function. The satellite-based capabilities release function checks the GNSS position and connection capabilities reported by the multi-connection terminal. When the conditions are met, it supports the ground-based capabilities release function to invoke the ground-based network capabilities, and the satellite-based capabilities release function returns an ability invocation response to the third-party application.

[0073] Here, the satellite-based capabilities release function and the ground-based capabilities release function support two-way ability invocation, that is, they support invoking the network capabilities of the other party through the "inter-network capabilities release interface", and support a two-way ability release mechanism, a periodic ability authentication mechanism, and a periodic ability charging mechanism.

[0074] Optionally, the method includes Performing a consistency check on the ability information stored in the satellite-based capabilities release function entity and the ability information stored in the ground-based capabilities release function entity every first period, The ability information includes the first network capabilities, the connection conditions, and the second network capabilities.

[0075] Optionally, the step of performing a consistency check on the ability information stored in the satellite-based capabilities release function entity and the ability information stored in the ground-based capabilities release function entity includes Receiving a consistency check request sent by the ground-based capabilities release function entity, where the consistency check request carries the ability information stored in the ground-based capabilities release function entity, Based on the consistency check request, determining whether the ability information stored in the ground-based capabilities release function entity matches the ability information stored in the satellite-based capabilities release function entity, If they do not match, update the stored capability information and feedback the stored capability information in the satellite-based capability release function entity to the ground-based capability release function entity.

[0076] Specifically, the capability release between capability release functions is different from the capability release for third-party applications. It provides all information of the network capability API including protocol requirements, interface requirements, authentication requirements, charging requirements, competition nesting relationships, etc. to the other party. After receiving a new network capability registration, the satellite-based capability release function immediately releases the network capability API in the ground-based capability release function and attaches connection conditions. Similarly, after receiving a new network capability, the ground-based capability release function immediately releases the network capability API in the satellite-based capability release function and attaches connection conditions.

[0077] To ensure the consistency of the same network capability API in different capability release functions, every settable T1 time, the satellite-based capability release function and the ground-based capability release function perform a capability calibration, that is, perform a consistency check on all network capability APIs released between networks and their accompanying connection conditions. In the consistency check, the ground-based capability release function initiates a consistency check request, which carries all the network capability API information released between networks stored in it. The satellite-based capability release function responds only to the inconsistent network capability API information, and the response message carries the stored related network capability API information. After the ground-based capability release function and the satellite-based capability release function interact, they update the inconsistent network capability API information.

[0078] Optionally, the method includes: Sending an authentication request to the ground-based capability release function entity every second period; Or, receiving an authentication request sent by the above-mentioned ground-based capability release function entity, and further including the step of performing an authentication process on the above-mentioned ground-based capability release function entity based on the above-mentioned authentication request.

[0079] Specifically, the trust level between the capability release functions is higher than the trust level between the capability release function and the third-party application. In order to reduce the authentication overhead, a periodic capability authentication mechanism is used between the capability release functions. The design of the periodic capability authentication message is as follows. Header field 1: Authentication Token, Header field 2: The number of released network capability APIs between the released networks, Header field 3: The quantity of the released network capability APIs between the currently valid networks, Header field 4: The time point of the next capability authentication.

[0080] A periodic capability authentication is performed on the satellite-based capability release function and the ground-based capability release function every configurable T2 time. In addition to the periodic capability authentication, no other authentication information other than the authentication information for the third-party application is carried in other messages of the inter-network capability release interface.

[0081] Optionally, the method includes the step of sending a charging request to the above-mentioned ground-based capability release function entity every third period, or receiving a charging request sent by the above-mentioned ground-based capability release function entity, and further including the step of charging the above-mentioned ground-based capability release function entity based on the above-mentioned charging request.

[0082] Specifically, different from the capacity charging for third-party applications, the capacity charging during the capacity release function does not need to write expenditures in real time. To reduce the charging overhead, a regular capacity charging mechanism is used during the capacity release function. The design of the regular capacity charging message is as follows. Header field 1: The number of currently valid inter-network open network capacity APIs, Header field 2: The list of network capacity APIs in header field 1, Header field 3: The list of the number of calls to the network capacity APIs in header field 1, Header field 4: The rate information of the network capacity APIs in header field 1, Header field 5: The time point of the next capacity charging.

[0083] A regular capacity charge is performed once for the satellite-based capacity release function and the ground-based capacity release function every configurable T3 time. In addition to the regular capacity charging, other messages of the inter-network capacity release interface do not carry any charging information other than the charging information for third-party applications.

[0084] As shown in FIG. 5, the embodiment of the present disclosure further provides a network capacity release method applied to a ground-based capacity release function entity, and the method specifically includes the following step 51.

[0085] Step 51: Receive the first network capacity and connection capacity of the satellite-related devices released by the satellite-based capacity release function entity, and release the second network capacity of the devices independent of the satellite to the satellite-based capacity release function entity.

[0086] Here, the satellite-related device includes at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network, and the device that does not rely on the satellite includes at least one of a mobile access network, a fixed access network, a terrestrial-based core network, and a terrestrial-based service platform.

[0087] Optionally, the terrestrial-based capability release function unit is arranged in the terrestrial-based core network. For example, a method of setting a release capability that does not rely on a satellite and a standard release interface in related technologies may be used, and it can support calling the satellite-based network capability through the "inter-network capability release interface". The terrestrial-based capability release function manages, releases, and opens the locally registered network capability and the network capability released by the satellite-based capability release function.

[0088] Optionally, the method further includes the step of sending a consistency check request for the capability information stored in the terrestrial-based capability release function entity to the satellite-based capability release function entity every first period.

[0089] Here, the capability information includes the first network capability, the connection condition, and the second network capability.

[0090] Optionally, after sending a consistency check request to the satellite-based capability release function entity, the method further includes the steps of receiving the capability information stored in the satellite-based capability release function entity feedback by the satellite-based capability release function entity based on the consistency check request, and updating the capability information stored in the terrestrial-based capability release function entity based on the capability information stored in the satellite-based capability release function entity.

[0091] Optionally, the method includes sending an authentication request to the satellite-based capability release function entity every second period, or receiving an authentication request sent by the satellite-based capability release function entity and performing an authentication process on the satellite-based capability release function entity based on the authentication request.

[0092] Optionally, the method includes sending a charging request to the satellite-based capability release function entity every third period, or receiving a charging request sent by the satellite-based capability release function entity and charging the satellite-based capability release function entity based on the charging request.

[0093] The method on the ground-based capability release function entity side in the embodiments of the present disclosure corresponds to the method on the satellite-based capability release function entity side. The embodiments of both may be referred to each other. For the sake of avoiding duplication, detailed descriptions are omitted here.

[0094] Hereinafter, taking the combination of the fixed, mobile, and satellite fusion network system in the embodiments of the present disclosure as an example where a third-party application simultaneously invokes the satellite-based network capability and the ground-based network capability, the process of releasing the fixed, mobile, and satellite fusion network capabilities will be described. As shown in FIG. 6, specifically, it includes the following content.

[0095] The satellite-based core network is arranged in a plurality of satellite nodes. Each satellite node uses a self-organizing selection method to arrange the satellite-based capability release function using the most appropriate satellite node, calculates its own weighted capability score using a parameter weighting algorithm, and selects the satellite node with the highest area weighted capability score for use in the arrangement of the satellite-based capability release function.

[0096] A satellite access network, a satellite-based service platform, and a satellite-based core network register their network capabilities and associated connection conditions with a satellite-based capability open function. The connection conditions are connection capabilities under specified time and space conditions, and include a period [t1, t2] with connection conditions to the satellite-based capability open function, and the geographical location (longitude range, latitude range) of the satellite nodes located within this period.

[0097] The satellite-based capability open function performs network capability API release with a ground-based capability open function and attaches connection conditions. The ground-based capability open function performs network capability API release with the satellite-based capability open function and attaches connection conditions. Both perform consistency checks on the network capability API every configurable T1 time.

[0098] The satellite-based capability open function releases the locally registered network capability API and the network capability API released by the ground-based capability open function to third-party applications. The third-party applications obtain network capability API information and subscribe to the satellite-based and ground-based network capability APIs.

[0099] The multi-connection terminal reports its GNSS position and connection capabilities (including the supported connection types and the general connection speeds of each supported connection type) to third-party applications through the satellite-based capability open function. The third-party applications select corresponding services for the user based on the GNSS position and connection capabilities of the multi-connection terminal. For example, based on the connection speed of the multi-connection terminal, select whether to start a video multi-party call or an audio multi-party call.

[0100] The third-party application invokes the satellite-based network capabilities through the satellite-based capability open function. The satellite-based capability open function first checks the connection conditions of relevant network elements, and then checks the GNSS position and connection capabilities reported by the multi-connection terminal. After both are satisfied, it invokes the satellite-based network capabilities of the satellite-based core network, the satellite-based service platform, and the satellite access network, establishes a communication connection with the multi-connection terminal if necessary, and the satellite-based capability open function returns a capability invocation response to the third-party application.

[0101] The third-party application invokes the terrestrial-based network capabilities through the satellite-based capability open function. The satellite-based capability open function checks the GNSS position and connection capabilities reported by the multi-connection terminal. After this condition is satisfied, it invokes the terrestrial-based network capabilities through the terrestrial-based capability open function, and the satellite-based capability open function returns a capability invocation response to the third-party application.

[0102] In the above solution of the present disclosure, a self-organizing selection method is used to arrange the satellite-based capability open function using the most appropriate satellite node based on computing power, memory capacity, connection capacity, and software capacity, and to arrange satellite-related open capabilities and a simplified open interface. The method of the simplified open interface includes assigning default values to the parameters of the network capability API, shortening the length of the message header field, etc. The satellite-based capability open function entity provided by the proposal of the present disclosure fully considers the capabilities and characteristics of the satellite node, reduces the overhead of the network capability API message, and can be applied to fixed, mobile, and satellite-integrated networks.

[0103] In the above solution of the present disclosure, a satellite access network, a satellite-based service platform, and a satellite-based core network are supported to register their network capabilities and associated connection conditions with a satellite-based capability open function. The connection conditions are connection capabilities under specified time and space conditions. That is, the satellite access network, based on the ephemeris information of the satellite node where it is located, provides a period [t1, t2] during which it has the connection conditions with the satellite-based capability open function, and the geographical location (longitude range, latitude range) of the satellite node where it is located within this period. The multi-connection terminal reports its GNSS position and connection capabilities (including the supported connection types and the general connection speeds of each supported connection type) to the satellite-based / terrestrial-based capability open function. The above method realizes the support for a dynamic network topology, and fully utilizes the ephemeris information and GNSS position to realize the support for a dynamic network topology, and can realize dynamic capability open in a fixed, mobile, and satellite fusion network.

[0104] In the above solution of the present disclosure, a satellite-based capability open function and a terrestrial-based capability open function are proposed to support bidirectional capability calls through an "inter-network capability open interface", and also support a bidirectional capability release mechanism, a periodic capability authentication mechanism, and a periodic capability charging mechanism. The above method realizes the support for heterogeneous capability open systems. That is, the capability open systems of the satellite-based network and the terrestrial-based network can adopt different capability open frameworks, adapt to the differences in resources between the satellite-based network and the terrestrial-based network, and reduce the message overhead between the capability open systems.

[0105] As shown in FIG. 7, an embodiment of the present disclosure provides a network capability open device 700 applied to a satellite-based capability open function entity. The device 700 includes An acquisition module 710 for acquiring the first network capabilities and connection capabilities of a satellite-related device including at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network, A release module 720 for releasing the first network capabilities and the connection capabilities to a ground-based capability release function entity and acquiring second network capabilities of a satellite-independent device released by the ground-based capability release function entity, where the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform. The release module 720 includes the above.

[0106] Optionally, the satellite-based capability release function entity is deployed on a target satellite, and the target satellite is determined based on the capability parameters of a plurality of satellites in the target area.

[0107] Optionally, the step of determining the target satellite based on the capability parameters of a plurality of satellites in the target area includes: A step in which a plurality of satellites in the target area determine a selected value based on their respective capability parameters; and A step of interacting the selected value among a plurality of satellites in the target area and determining the satellite with the largest selected value as the target satellite.

[0108] Optionally, the satellite-based capability release function entity assigns a default value to the parameter of the network capability, and / or The message header field of the network capability sent by the satellite-based capability release function entity includes only the request method, the API name, and the Host hostname.

[0109] Optionally, the device 700 A first release module for releasing the first network capability and the connection capability to a third-party application device; And / or A transfer module for receiving position information and connection capability transmitted by a multi-connection terminal and transmitting the position information and the connection capability to the third-party application device.

[0110] Optionally, the device 700 further includes: A first receiving module for receiving a call request for the first network capability transmitted by a third-party application device; Based on the call request for the first network capability, when it is determined that both the satellite-related device and the multi-connection terminal satisfy preset conditions, a call for the second network capability is started, and a first call module for feeding back a call response of the first network capability to the third-party application.

[0111] Optionally, the device 700 further includes: A second receiving module for receiving a call request for the second network capability transmitted by a third-party application device; Based on the call request for the second network capability, when it is determined that the multi-connection terminal satisfies preset conditions, a call for the second network capability is started to a ground-based capability release function entity, and a second call module for feeding back a call response of the second network capability to the third-party application.

[0112] Optionally, the device 700 further includes: A check module for checking the consistency between the capability information stored in the satellite-based capability release function entity and the capability information stored in the ground-based capability release function entity every first period. The capability information includes the first network capability, the connection condition, and the second network capability.

[0113] Optionally, the checking module is a receiving unit that receives a consistency check request sent by the ground-based capability release function entity, where the consistency check request carries the capability information stored in the ground-based capability release function entity, a checking unit that determines whether the capability information stored in the ground-based capability release function entity matches the capability information stored in the satellite-based capability release function entity based on the consistency check request, and a processing unit that, when they do not match, updates the stored capability information and feeds back the capability information stored in the satellite-based capability release function entity to the ground-based capability release function entity.

[0114] Optionally, the apparatus 700 includes a first transmission module for transmitting an authentication request to the ground-based capability release function entity every second period, or an authentication module that receives an authentication request sent by the ground-based capability release function entity and performs an authentication process on the ground-based capability release function entity based on the authentication request.

[0115] Optionally, the apparatus 700 includes a second transmission module for transmitting a charging request to the ground-based capability release function entity every third period, or a charging module that receives a charging request sent by the ground-based capability release function entity and charges the ground-based capability release function entity based on the charging request.

[0116] The above device in the embodiments of the present disclosure can implement each process of the above network capability release method on the side of the satellite-based capability release function entity, and can achieve similar technical effects. To avoid duplication, detailed descriptions are omitted here.

[0117] As shown in FIG. 8, the embodiments of the present disclosure provide a network capability release device 800 applied to a ground-based capability release function entity. The device 800 includes a release module 810 for receiving the first network capability and connection capability of satellite-related devices released by a satellite-based capability release function entity, and releasing the second network capability of non-satellite-dependent devices to the satellite-based capability release function entity. Here, the satellite-related devices include at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network. The non-satellite-dependent devices include at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform.

[0118] Optionally, the device 800 further includes a first transmission module for transmitting, to the satellite-based capability release function entity, a consistency check request for carrying the capability information stored in the ground-based capability release function entity every first period. Here, the capability information includes the first network capability, the connection condition, and the second network capability.

[0119] Optionally, the device 800 further includes a first reception module for receiving the capability information stored in the satellite-based capability release function entity feedback by the satellite-based capability release function entity based on the consistency check request. An update module for updating the capability information stored in the ground-based capability release function entity based on the capability information stored in the satellite-based capability release function entity.

[0120] Optionally, the apparatus 800 A second transmission module for transmitting an authentication request to the satellite-based capability release function entity every second period. Or An authentication module for receiving an authentication request transmitted by the satellite-based capability release function entity and performing an authentication process on the satellite-based capability release function entity based on the authentication request.

[0121] Optionally, the apparatus 800 A third transmission module for transmitting a charging request to the satellite-based capability release function entity every third period. Or A charging module for receiving a charging request transmitted by the satellite-based capability release function entity and charging the satellite-based capability release function entity based on the charging request.

[0122] The apparatus in the embodiments of the present disclosure can implement each process of the network capability release method on the ground-based capability release function entity side, and can achieve similar technical effects. To avoid duplication, detailed descriptions are omitted here.

[0123] Embodiments of the present disclosure further provide a network device. As shown in FIG. 9, it includes a transceiver 910, a processor 900, a memory 920, and a program or instruction stored in the memory 920 and executable by the processor 900. When executing the program or instruction, the processor 900 realizes each process of the network capability release method applied to the satellite-based capability release function entity side, or realizes each process of the network capability release method applied to the ground-based capability release function entity side, and can achieve similar technical effects. To avoid duplication, detailed description is omitted here.

[0124] The transceiver 910 is used to transmit and receive data under the control of the processor 900.

[0125] In FIG. 9, the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors including the processor 900 and the memory including the memory 920 are integrally connected. The bus architecture can also integrally connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art, so further description is omitted in this specification. The bus interface provides an interface. The transceiver 910 may be a plurality of components, that is, it includes a transmitter and a receiver, and provides a unit for communicating with various other devices via a transmission medium. The processor 900 is responsible for the management of the bus architecture and general processing, and the memory 920 can store data used by the processor 900 when executing operations.

[0126] Embodiments of the present disclosure provide a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, each process of the above network capability release method applied to the satellite-based capability release function entity side or each process of the above network capability release method applied to the ground-based capability release function entity side can be realized, and the same technical effects can be achieved. To avoid duplication, detailed description is omitted here.

[0127] Here, the processor is the processor in the network device described in the above embodiments. The readable storage medium includes computer-readable storage media such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0128] Note that the terminals depicted in this specification include, but are not limited to, smartphones, tablets, etc. And many of the functional components described will come to be called modules in order to more specifically emphasize their implementation independence.

[0129] In embodiments of the present disclosure, a module can be realized by software so as to be executed by various types of processors. For example, an executable code module of an identifier may include one or more physical or logic blocks of computer instructions. For example, it can be constructed as an object, a process, or a function. Nevertheless, the executable code of the identified module need not be physically located in one place and may be different instructions stored at different positions. When these instructions are logically combined, a module is formed and a predetermined purpose of the module is achieved.

[0130] In fact, an executable code module may be one instruction or a plurality of instructions, and may be distributed across a plurality of code segments, different programs, or among a plurality of memory devices. Similarly, the operation data is identifiable within the module, and may be implemented in any suitable form and organized within any suitable type of data structure. The operation data may be collected as one data set, or distributed at different locations (including on different storage devices), and may exist in the system or network as an electronic signal at least partially.

[0131] When the module can be realized by software, considering the level of existing hardware technology, for any module that can be realized by software, unless cost is considered, a person skilled in the art can construct the corresponding hardware circuit to realize the corresponding function, and the hardware circuit includes conventional very large scale integration (VLSI) circuits or gate arrays, and conventional semiconductors such as logic chips and transistors or other discrete components. The module can be realized by programmable hardware devices such as field programmable gate arrays, programmable array logic, and programmable logic devices.

[0132] The above exemplary embodiments have been described with reference to these drawings, and there are various forms and embodiments that do not depart from the spirit and teachings of the present disclosure. Therefore, the present disclosure should not be construed as limiting the exemplary embodiments provided herein. More appropriately, these exemplary embodiments are provided so that the present disclosure is thorough and complete, and at the same time convey the scope of the present disclosure to those skilled in the art. In these drawings, the sizes and relative sizes of components may be enlarged for clarity. The terms used herein are for the purpose of describing particular exemplary embodiments only and are not intended to be limiting. As used herein, unless the context clearly dictates otherwise, the singular forms "a", "one" and "the" shall include the plural forms. When the terms "comprising" and / or "including" are used in this specification, they represent the presence of the above features, integers, steps, operations, parts and / or components, but the presence or addition of one or more other features, integers, steps, operations, parts, components and / or other families is not excluded. Unless otherwise specified, when describing, a range of values includes the upper and lower limits of the range and any sub-ranges therebetween.

[0133] The above are the preferred embodiments of the present disclosure. Those skilled in the art may make some improvements and decorations without departing from the principles described in the present disclosure, and these improvements and decorations should also be regarded as within the protection scope of the present disclosure.

Claims

1. A network capability opening method, which is applied to a satellite-based capability opening function entity, comprising the steps of obtaining the first network capability and connection capability of satellite-related devices including at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network; releasing the first network capability and the connection capability to a ground-based capability opening function entity, and obtaining the second network capability of non-satellite-dependent devices released by the ground-based capability opening function entity, wherein the non-satellite-dependent devices include at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform; A network capability opening method comprising the above.

2. The network capability opening method according to claim 1, wherein the satellite-based capability opening function entity is deployed on a target satellite, and the target satellite is determined based on the capability parameters of a plurality of satellites in the target area.

3. The step of determining the target satellite based on the capability parameters of a plurality of satellites in the target area comprises: determining a selected value based on the respective capability parameters of a plurality of satellites in the target area; interacting the selected value among a plurality of satellites in the target area, and determining the satellite with the largest selected value as the target satellite. The network capability opening method according to claim 2, comprising the above.

4. The satellite-based capability opening function entity assigns a default value to the parameter of the network capability, and / or the message header field of the network capability transmitted by the satellite-based capability opening function entity only includes a request method, an application programming interface (API) name, and a host name.

5. After obtaining the first network capability and connection capability of the satellite-related devices, releasing the first network capability and the connection capability to a third-party application device, and / or Receiving the location information and connection capabilities transmitted by the multi-connection terminal, and transmitting the location information and the connection capabilities to the third-party application device, the network capability release method according to claim 1, further comprising.

6. After obtaining the first network capabilities and connection capabilities of the satellite-related device, Receiving a call request for the first network capabilities transmitted by the third-party application device; Based on the call request for the first network capabilities, when it is determined that both the satellite-related device and the multi-connection terminal satisfy preset conditions, starting the call for the second network capabilities and feeding back a call response for the first network capabilities to the third-party application, the network capability release method according to claim 1, further comprising.

7. After obtaining the second network capabilities of the satellite-independent device released by the ground-based capability release function entity, Receiving a call request for the second network capabilities transmitted by the third-party application device; Based on the call request for the second network capabilities, when it is determined that the multi-connection terminal satisfies preset conditions, starting the call for the second network capabilities to the ground-based capability release function entity and feeding back a call response for the second network capabilities to the third-party application, the network capability release method according to claim 1, further comprising.

8. Performing a consistency check on the capability information stored in the satellite-based capability release function entity and the capability information stored in the ground-based capability release function entity every first period, The network capability release method according to claim 1, further comprising the step that the capability information includes the first network capabilities, the connection conditions, and the second network capabilities.

9. The step of performing a consistency check on the capability information stored in the satellite-based capability release function entity and the capability information stored in the ground-based capability release function entity is Receiving a consistency check request transmitted by the above-ground base capability release function entity, wherein the consistency check request carries the capability information stored in the above-ground base capability release function entity; Based on the consistency check request, determining whether the capability information stored in the above-ground base capability release function entity matches the capability information stored in the above satellite-based capability release function entity; If they do not match, updating the stored capability information and feeding back the capability information stored in the above satellite-based capability release function entity to the above-ground base capability release function entity; The network capability release method according to claim 8, comprising:

10. Transmitting an authentication request to the above-ground base capability release function entity every second period; Or The network capability release method according to claim 1, further comprising receiving an authentication request transmitted by the above-ground base capability release function entity and performing an authentication process on the above-ground base capability release function entity based on the authentication request.

11. Transmitting a charging request to the above-ground base capability release function entity every third period; Or The network capability release method according to claim 1, further comprising receiving a charging request transmitted by the above-ground base capability release function entity and charging the above-ground base capability release function entity based on the charging request.

12. A network capability release method, applied to an above-ground base capability release function entity, Receiving the first network capability and connection capability of a satellite-related device released by a satellite-based capability release function entity, and releasing the second network capability of a satellite-independent device to the satellite-based capability release function entity. The step that the satellite-related device includes at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network, and the satellite-independent device includes at least one of a mobile access network, a fixed access network, a terrestrial-based core network, and a terrestrial-based service platform, a network capability open method.

13. The step of sending a consistency check request for carrying the capability information stored in the terrestrial-based capability open function entity to the satellite-based capability open function entity for each first period, The network capability open method according to claim 12, further including the step that the capability information includes the first network capability, the connection condition, and the second network capability.

14. After sending a consistency check request to the satellite-based capability open function entity, The step of receiving the capability information stored in the satellite-based capability open function entity fed back by the satellite-based capability open function entity based on the consistency check request, and The step of updating the capability information stored in the terrestrial-based capability open function entity based on the capability information stored in the satellite-based capability open function entity, the network capability open method according to claim 13.

15. The step of sending an authentication request to the satellite-based capability open function entity for each second period, Or, The network capability open method according to claim 12, further including the step of receiving an authentication request sent by the satellite-based capability open function entity and performing an authentication process on the satellite-based capability open function entity based on the authentication request.

16. The step of sending a charging request to the satellite-based capability open function entity for each third period, Or, The network capability open method according to claim 12, further including the step of receiving a charging request sent by the satellite-based capability open function entity and charging the satellite-based capability open function entity based on the charging request.

17. A network capability open device, which is applied to a satellite-based capability open function entity, An acquisition module for acquiring the first network capabilities and connection capabilities of a satellite-related device including at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network, An open module for releasing the first network capabilities and the connection capabilities to a ground-based capability open function entity and acquiring the second network capabilities of a satellite-independent device released by the ground-based capability open function entity, wherein the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform A network capability open device including the above.

18. A network capability open device, which is applied to a ground-based capability open function entity, Further including an open module that receives the first network capabilities and connection capabilities of a satellite-related device released by a satellite-based capability open function entity and releases the second network capabilities of a satellite-independent device to the satellite-based capability open function entity, The satellite-related device includes at least one of a satellite access network, a satellite-based service platform, and a satellite-based core network, and the satellite-independent device includes at least one of a mobile access network, a fixed access network, a ground-based core network, and a ground-based service platform. A network capability open device.

19. A network device Including a transceiver, a processor, a memory, and a program or instruction stored in the memory and executable by the processor. When the processor executes the program or instruction, it realizes the steps of the network capability open method according to any one of Claims 1 to 11 or the steps of the network capability open method according to any one of Claims 12 to 16. A network device.

20. A readable storage medium storing a program or instruction, The program or instruction, when executed by a processor, is a readable storage medium that realizes the steps of the network capability opening method according to any one of claims 1 to 11, or the steps of the network capability opening method according to any one of claims 12 to 16.

Images