Calculation network service API management method, device, equipment, medium and program product

Abstract

The invention provides a computing network service API management method and device, electronic equipment, a storage medium and a program product, and relates to the technical field of communication. The method comprises the steps that a network computing service API is deployed in a terminal, the terminal obtains a network computing service API calling request sent by an application, and the network computing service API calling request comprises an application identifier of the application; then, based on the application identifier of the application and the parameter format of the computing network service API calling request, judging whether the calling of the computing network service API by the application is accepted or not; the computing network service API calling response is returned to the application, the computing network service API calling response comprises the first identification bit, and the first identification bit is used for indicating whether the computing network service API accepts calling of the application or not. In the embodiment, the computing network service API is deployed on the terminal side, so that the computing network resource opening of the network side is realized, and compared with an application layer scheme, the dependency on an upper application layer can be reduced, the calling of the computing network resource of the network side is facilitated, and the calling efficiency of the computing network resource is improved.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus, device, medium and program product for managing a computing network service API (Application Programming Interface). Background Technology

[0002] The convergence of communication, intelligence, and computing is a key feature of 6G (6th generation mobile networks). 6G networks not only provide communication services but also computing power and intelligent services. Looking at the development trend of terminals, they will become more intelligent and evolve into intelligent agents with decision-making capabilities, able to call upon various resources and applications according to scenario requirements to autonomously complete complex tasks. However, compared to the network side, the terminal's computing resources are limited. In complex computing scenarios, the terminal cannot complete tasks using its own computing resources alone. Therefore, the terminal needs to call upon the computing network resources on the network side.

[0003] In related technologies, when an application running on a terminal wants to call computing resources on the network side, the application's call request information needs to be transmitted to the corresponding application server through application layer signaling. The application server then formally requests the required computing resources from the network side through the capability open interface provided by the network side.

[0004] With the deployment of terminal computing power, how to enable applications to directly access network resources through the terminal is an urgent problem to be solved.

[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0006] This disclosure provides a method, apparatus, device, medium, and program product for managing computing network service APIs, enabling applications to directly access computing network resources on the network side through terminals, thereby improving the efficiency of accessing computing network resources.

[0007] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0008] According to one aspect of this disclosure, a method for managing a computing network service API is provided, comprising: the method being applied to a terminal, comprising: acquiring a computing network service API call request sent by an application, wherein the computing network service API is deployed in the terminal and is used to call computing network resources on the network side, and the computing network service API call request includes an application identifier of the application; determining whether to accept the application's call to the computing network service API based on the application identifier of the application and the parameter format of the computing network service API call request; and returning a computing network service API call response to the application, wherein the computing network service API call response includes a first identifier bit, the first identifier bit being used to indicate whether the application's call to the computing network service API is accepted.

[0009] In some exemplary embodiments, determining whether to accept an application's call to the computing network service API based on the application's application identifier and the parameter format of the computing network service API call request includes: determining whether the application has the permission to call the computing network service API based on the application's application identifier; if the application has the permission to call the computing network service API, determining whether the parameter format of the computing network service API call request is consistent with the parameter format of the computing network service API, the parameter format of the computing network service API being determined by the network side; if the parameter format of the computing network service API call request is consistent with the parameter format of the computing network service API, then determining to accept the application's call to the computing network service API; if the application does not have the permission to call the computing network service API or the parameter format of the computing network service API call request is inconsistent with the parameter format of the computing network service API, then determining to reject the application's call to the computing network service API.

[0010] In some exemplary embodiments, it also includes:

[0011] The system retrieves a subscription request for computing network service API information sent by the application, which includes the application identifier of the application. If the terminal meets the conditions for calling the computing network service API, the system determines whether the application has the permission to call the computing network service API based on the application identifier. The system then sends a computing network service API information notification to the application, wherein the computing network service API information notification includes a second identifier bit, which is used to indicate whether the application has the permission to call the computing network service API.

[0012] In some exemplary embodiments, determining whether an application has permission to call the computing network service API based on the application identifier of the application includes: determining whether the application identifier of the application is in a first application list, wherein the first application list includes application identifiers that are allowed to call the computing network service API, and the first application list is determined by the network side; if the application identifier of the application is in the first application list, then it is determined that the application has permission to call the computing network service API; if the application identifier of the application is not in the first application list, then it is determined that the application does not have permission to call the computing network service API.

[0013] In some exemplary embodiments, determining whether an application has permission to call the computing network service API based on the application's application identifier further includes: determining whether the application's application identifier is in a second application list, wherein the second application list includes application identifiers that are prohibited from calling the computing network service API, and the second application list is determined by the network side; if the application's application identifier is in the second application list, then it is determined that the application does not have permission to call the computing network service API.

[0014] In some exemplary embodiments, the computing network service API call request further includes: computing network service identifier, computing network service requirement, and computing network service information; the method further includes: if the application's call to the computing network service API is accepted, sending a computing network service request to the network side, wherein the computing network service request includes a terminal identifier, a PDU (Protocol Data Unit Session) session identifier, a computing network service identifier, a computing network service requirement, computing network service information, and computing capabilities; receiving a computing network service response returned by the network side, wherein the computing network service response includes a computing network QoS policy and a computing network resource address, the computing network resource address being determined based on the selected computing network node, and the computing network QoS policy including at least a computing network resource type and a computing network resource size; returning a computing network service API call response to the application, wherein a first identifier bit is used to indicate acceptance of the application's call to the computing network service API, and the computing network service API call response further includes at least one of the following: a terminal identifier, a PDU session identifier, an application identifier, a computing network service identifier, a computing network resource type, a computing network resource size, and a computing network resource address.

[0015] In some exemplary embodiments, when an application is denied a call to the computing network service API, the computing network service API call response may further include: the reason for denying the call to the computing network service API.

[0016] In some exemplary embodiments, the conditions for a terminal to call the computing network service API include at least one of the following: the terminal supports the computing network service API; the terminal has registered with the network side, and the registration request indicates that the terminal supports the computing network service API; the terminal is permitted by the network side to provide the computing network service API.

[0017] In some exemplary embodiments, when the terminal determines that the application has permission to call the computing network service API, the computing network service API information notification also includes: the parameter format of the computing network service API; when the terminal determines that the application does not have permission to call the computing network service API, the computing network service API information notification also includes: the reason for prohibiting the call to the computing network service API.

[0018] In some exemplary embodiments, the method further includes: sending a registration request to the network side, the registration request being used to instruct the terminal to support the computing network service API; and receiving a registration response sent by the network side, the registration response including a third identifier bit, the third identifier bit being used to indicate whether the terminal is allowed to provide the computing network service API.

[0019] In some exemplary embodiments, the third identifier bit is used to indicate when the terminal is allowed to provide the computing network service API. The registration response also includes: a first application list, a second application list, and the parameter format of the computing network service API.

[0020] According to another aspect of this disclosure, a computing network service API management device is also provided. This device is configured on a terminal and includes: a call request acquisition module, used to acquire computing network service API call requests sent by an application, wherein the computing network service API is deployed in the terminal and used to call computing network resources on the network side, and the computing network service API call request includes an application identifier of the application; a call judgment module, used to determine whether to accept the application's call to the computing network service API based on the application identifier of the application and the parameter format of the computing network service API call request; and a call response return module, used to return a computing network service API call response to the application, wherein the computing network service API call response includes a first identifier bit, the first identifier bit being used to indicate whether the application's call to the computing network service API is accepted.

[0021] According to another aspect of this disclosure, an electronic device is also provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the network service API management method of any of the above via executing the executable instructions.

[0022] According to another aspect of this disclosure, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the network service API management method described above.

[0023] According to another aspect of this disclosure, a computer program product is also provided, comprising: a computer program or instructions, wherein the computer program or instructions, when executed by a processor, implement a computer network service API management method for any of the above.

[0024] The network service API management method provided in the embodiments of this disclosure deploys a network service API on the terminal. The terminal obtains a network service API call request sent by an application, wherein the network service API call request includes the application's application identifier. Then, based on the application's application identifier and the parameter format of the network service API call request, it determines whether to accept the application's call to the network service API. A network service API call response is returned to the application, and the network service API call response includes a first identifier bit, which indicates whether the application's call to the network service API is accepted. In this embodiment, by deploying the network service API on the terminal side, network-side network resources are opened up. Compared with application-layer solutions, this reduces dependence on the upper application layer, facilitates the mobilization of network-side network resources, and improves the efficiency of network resource mobilization.

[0025] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0026] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0027] Figure 1 A schematic diagram of an exemplary application system architecture to which the network service API management method of the embodiments of this disclosure can be applied is shown;

[0028] Figure 2 This diagram illustrates a flowchart of a computer network service API management method according to an embodiment of the present disclosure;

[0029] Figure 3 This diagram illustrates a terminal architecture for deploying a computing network service API according to an embodiment of the present disclosure.

[0030] Figure 4 This diagram illustrates a registration flowchart for a computing network service API according to an embodiment of the present disclosure;

[0031] Figure 5 This diagram illustrates an interactive flowchart of a computer network service API registration embodiment of the present disclosure;

[0032] Figure 6 This diagram illustrates a configuration flowchart for a computing network service API according to an embodiment of the present disclosure.

[0033] Figure 7 This diagram illustrates an interactive flowchart of a computing network service API configuration according to an embodiment of the present disclosure.

[0034] Figure 8 This diagram illustrates a flowchart of a network service API call method according to an embodiment of the present disclosure;

[0035] Figure 9 This diagram illustrates a flowchart of a method for determining call permissions in an embodiment of this disclosure;

[0036] Figure 10 This diagram illustrates a flowchart of another method for determining call permissions in an embodiment of this disclosure;

[0037] Figure 11 This diagram illustrates a network architecture interaction diagram in a computing-network convergence scenario according to an embodiment of the present disclosure.

[0038] Figure 12 This diagram illustrates a call flowchart for another computing network service API in an embodiment of this disclosure;

[0039] Figure 13 This illustration shows a flowchart of another computing network service API call in an embodiment of the present disclosure;

[0040] Figure 14 This diagram illustrates a computing network service API management device according to an embodiment of the present disclosure.

[0041] Figure 15 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0042] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0043] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0044] To facilitate understanding, before introducing the embodiments of this disclosure, the following explanations are provided for several terms involved in the embodiments of this disclosure:

[0045] APIs are predefined functions or protocols used for interaction and communication between different software applications. APIs define how applications request and use other software or services without needing to know their internal implementation details.

[0046] NAS (Non-access stratum): This is the signaling transmission protocol between the terminal and the core network. It is mainly used to handle signaling related to user mobility and session management, and does not involve the specific access technology of the radio access network.

[0047] AMF (Access and Mobility Management Function): This is a network element in the 5G network core network, primarily used for terminal access management and mobility management. It includes handling user registration, authentication, location updates, and handover processes, while also interacting with other network elements to collaboratively manage and provide services to user equipment.

[0048] CNMF (Computing and Network Management Function): This is a functional entity used to coordinate and manage computing and network resources within the network. It can be deployed as a functional module alongside SMF (Session Management Function) and PCF (Policy Control Function), or it can exist independently as a core network element. Its main functions include: managing the resource status of computing and network nodes such as terminals, RAN (Radio Access Network), UPF (User Plane Function), and cloud computing nodes; coordinating decisions on computing and network QoS (Quality of Service); and selecting computing and network nodes.

[0049] UE (User Equipment): also known as terminal equipment or terminal, including but not limited to: mobile phones, tablets, IoT devices, etc.

[0050] UDM (Unified Data Management): This is the network element in a 5G network responsible for the unified management of user data. The UDM stores user subscription data, context information, and other data. Other network elements can obtain the necessary user data from the UDM through specific interfaces to support various network functions and services.

[0051] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0052] Figure 1 A schematic diagram of an exemplary application system architecture for which the network service API management method of the embodiments of this disclosure can be applied is shown. For example... Figure 1 As shown, the system architecture includes a terminal device 101, a network 102, and a network-side device 103. The network 102 is used as a medium to provide a communication link between the terminal device 101 and the network-side device 103, and can be a wired network or a wireless network.

[0053] Optionally, the aforementioned wireless or wired networks use standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wired or wireless networks, private networks, or any combination of virtual private networks. In some embodiments, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network. Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Networks (VPNs), and Internet Protocol Security (IPSec) can be used to encrypt all or some links. In other embodiments, custom and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0054] The terminal device in this embodiment can also be referred to as UE. In specific implementation, the terminal device can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), wearable device, or vehicle device, etc. It should be noted that the specific type of terminal device is not limited in this embodiment.

[0055] The network-side device 103 can be a base station, relay, or access point, etc. The base station can be a 5G or later version base station (e.g., 5G NR NB), or a base station in other communication systems (e.g., eNB base station). It should be noted that the specific type of network-side device is not limited in this embodiment of the disclosure.

[0056] Those skilled in the art will know that Figure 1 The number of terminals, networks, and network-side devices shown is merely illustrative; any number of terminals, networks, and network-side devices can be included as needed. This disclosure does not limit the scope of the embodiments.

[0057] Under the above system architecture, this disclosure provides a method for managing computing network service APIs, which can be executed by any user device with computing capabilities.

[0058] In some embodiments, the network service API management method provided in this disclosure can be executed by a terminal device in the above-described system architecture; in other embodiments, the network service API management method provided in this disclosure can be executed by a server in the above-described system architecture; in still other embodiments, the network service API management method provided in this disclosure can be implemented by the terminal device and the server in the above-described system architecture through interaction.

[0059] Figure 2 This diagram illustrates a flowchart of a network service API management method according to an embodiment of the present disclosure, such as... Figure 2 As shown, the network service API management method provided in this embodiment includes the following steps S202-S206.

[0060] S202. Obtain the computing network service API call request sent by the application. The computing network service API is deployed in the terminal and is used to call computing network resources on the network side. The computing network service API call request includes the application identifier of the application.

[0061] An application (APP), also known as a software program, refers to a software program running on a terminal, such as a video playback app, an autonomous driving assistance app, or a voice assistant on a mobile phone. In real-world scenarios, applications may need to access network resources to complete complex tasks due to insufficient terminal computing power. For example, an autonomous driving assistance app may need to access network resources to perform high-precision map calculations. An application identifier (APP Id) is a string or code used to uniquely identify an application on the terminal. For example, the identifier for a video editing app is example.videoeditor. This application identifier is used to verify whether the application has permission to call network service APIs.

[0062] The Computing Network Service API (API) is an application programming interface deployed on the terminal side, used to enable interaction between applications on the terminal and the terminal itself. NAS (Network Attached Storage) is used to enable interaction between the terminal and the network side. After the application on the terminal requests and invokes the Computing Network Service API, the UE (User Equipment) then requests resources from the network side via the NAS protocol. For example, the AI ​​(Artificial Intelligence) agent on the terminal can request and invoke the Computing Network Service API, and then request GPU computing power from nodes within the network via the NAS protocol to quickly complete image recognition tasks.

[0063] A network service API call request refers to a request message initiated by an application to a terminal to request network-side computing resources. This message includes the application identifier required for the call. For example, a video app, due to insufficient local computing power, sends a network service API call request to the terminal to request network-side encoding acceleration resources.

[0064] Terminals, also known as user equipment (UE), include devices such as smartphones, smart cars, and industrial sensors. They serve as the carriers of computing network service APIs, receiving application requests and forwarding them to the network side. These computing network service APIs deployed on the terminal can be understood as interface modules integrated into the terminal's operating system or underlying framework. Applications on the terminal can directly call these APIs to request computing network resources without going through the application layer. For example, the newly added "requestComputingResource()" interface in the terminal's system-level API library allows various applications to call it directly.

[0065] In one exemplary implementation, this embodiment provides a terminal architecture diagram for deploying a computing network service API, such as... Figure 3 As shown, terminal 300 includes APPs 310, API framework 320, native library functions and runtime environment 330, hardware abstraction layer 340 and operating system kernel layer 350.

[0066] Among them, APPs are software programs that end users directly interact with and use, such as social media software, navigation applications, and video clients on mobile phones, and office software and browsers on computers. When the terminal's own computing resources are insufficient to complete the tasks that the APPs want to perform, the APPs pass their request for network resources to the underlying API framework 320 by calling APIs.

[0067] API framework 320 transforms API call requests initiated by apps into standardized instructions that the underlying system can understand, and distributes them to the corresponding native library functions and runtime environment 330. The native library functions and runtime environment 330 execute the standardized instructions passed by API framework 320, such as calling pre-encapsulated underlying functions to complete interactions with network resources. The runtime environment provides the basic environment for the execution of functions in the native library, ensuring that operations do not conflict during multi-task concurrency and improving efficiency.

[0068] The hardware abstraction layer 340 receives hardware operation requests from the native library, transforms these requests into standard instructions preset by the hardware manufacturer, and transmits these instructions to the operating system kernel layer 350 to trigger actual hardware interaction.

[0069] The operating system kernel layer 350 directly controls the hardware devices in the terminal, is responsible for scheduling underlying resources, and ultimately completes the physical interaction with the network side. Specifically, it receives instructions from the hardware abstraction layer, schedules underlying resources, and directly drives the network hardware to perform physical operations. For example, it converts the network request assembled at the upper layer into electrical signals / radio waves through hardware and sends them to the base station or router, ultimately transmitting them to the network side; or, when the network side returns resources, the operating system kernel layer 350 receives the signals through hardware, parses them into data, and then passes them through the hardware abstraction layer 340, native library functions and runtime environment 330, and API framework 320 before finally returning them to the APPs 310.

[0070] Apps define and distribute network resource requirements and API framework standardization requirements; native libraries / runtime environments execute specific technical operations; a hardware abstraction layer adapts to the hardware and transmits operation commands; the operating system kernel drives the hardware to complete the physical interaction with the network side; and the results are passed back to the apps through a reverse layer and finally presented to the user. This allows apps to focus on business logic without worrying about terminal hardware or network protocol details, while ensuring that the calling process is efficient, stable, and scalable.

[0071] The network side refers to the infrastructure of a mobile communication network, including the core network, edge nodes, and cloud, encompassing network elements such as AMF, CNMF, and UDM. It coordinates and allocates computing resources, such as CPU / GPU resources on edge servers and distributed computing capabilities in the cloud. Network resources refer to the collective computing and network resources available on the network side, including but not limited to computing location, computing power, network bandwidth, and latency. For example, an edge node might have a 16-core CPU, 100GB of memory, and a 5G low-latency link.

[0072] In one possible implementation, the terminal and the network side have established a PDU session. When the application deployed on the terminal detects that the terminal cannot meet the application requirements during operation, it generates a computing network service API call request according to the parameter format of the computing network service API received in the configuration phase and sends it to the terminal. The terminal directly receives the computing network service API call request sent by the application running on its own.

[0073] Terminals that cannot meet application requirements include, but are not limited to: insufficient terminal computing power, excessive terminal load, insufficient terminal battery power, security requirements such as data not leaving the network, application server's inability to meet the RTT latency requirements of computing network services, and excessive application server load.

[0074] S204. Based on the application identifier and the parameter format of the computing network service API call request, determine whether to accept the application's call to the computing network service API.

[0075] Application identifiers are used to verify the identity of applications. The parameter format of a computing network service API call request refers to the format of the parameters carried in the request, including: parameter type, order, value range, and syntax structure.

[0076] In one possible embodiment, the application identifier in the computing network service API call request is extracted and compared with a preset list of applications allowed to call the computing network service API to verify whether the application is a registered and authorized legitimate user. If the application identifier is not in the list of applications allowed to call the computing network service API or the application identifier has expired, the application's call to the computing network service API is directly rejected.

[0077] If the application is listed in the list of applications allowed to call the computing network service API, the identity verification passes. The next step is to verify that the parameter format of the computing network service API call request conforms to the API's parameter format specifications. These specifications are determined by the network side.

[0078] For example, verifying whether the data type of the parameter is the data type required by the specification and whether the parameter structure is complete. The completeness of the parameter structure can include whether any required parameters are missing and whether the parameter syntax is correct. Another example is whether the data type meets the specification requirements, which can include whether the date format and IP address format are standardized, etc.

[0079] Whether to accept an application's call to the computing network service API can refer to the terminal determining whether to accept the application's call to the computing network service API and then request computing network resources on the network side after verifying the application identifier and the parameter format of the computing network service API call request.

[0080] If the application identifier is valid and the parameter format meets the specifications, the application is allowed to call the computing network service API and the corresponding function is executed; if the application identifier is invalid or the parameter format does not meet the specifications, the application is rejected from calling the computing network service API and the reason for rejection is returned.

[0081] S206. Return the computing network service API call response to the application. The computing network service API call response includes a first flag, which is used to indicate whether the application's call to the computing network service API is accepted.

[0082] The response to a computing network service API call can be understood as the result information returned to the application by the terminal after receiving and processing the computing network service API call request sent by the application. This information includes the request processing status, execution result, and other content.

[0083] The first flag is a specific field or symbol in the response to a computer network service API call that indicates whether the application's call to the computer network service API is accepted. For example, a first flag of "ACCEPT" indicates that the application's call to the computer network service API is accepted, while a first flag of "REJECT" indicates that the application's call to the computer network service API is rejected.

[0084] In one possible implementation, after receiving the response to the computing network service API call, the application first parses the first flag in the response. If the first flag indicates acceptance of the application's call to the computing network service API, the application continues to call the computing network resources on the network side through the computing network service API. If the first flag indicates rejection of the application's call to the computing network service API, the application initiates a new computing network service API call request based on the reason for rejection included in the response, or the computing network service API call process ends.

[0085] The computing network service API management method provided in this embodiment deploys a computing network service API on the terminal. The terminal obtains a computing network service API call request sent by an application, wherein the computing network service API call request includes the application's application identifier. Then, based on the application's application identifier and the parameter format of the computing network service API call request, it determines whether to accept the application's call to the computing network service API. A computing network service API call response is returned to the application, and the computing network service API call response includes a first identifier bit, which indicates whether the application's call to the computing network service API is accepted. In this embodiment, by deploying the computing network service API on the terminal side, the computing network resources on the network side are opened up. Compared with application layer solutions, this reduces the dependence on the upper application layer, facilitates the mobilization of computing network resources on the network side, and improves the efficiency of computing network resource mobilization.

[0086] In the above embodiments, the calling process of the computing network service API is introduced. Before the calling process of the computing network service API, the registration process and the configuration process of the computing network service API need to be executed first. The registration process and the configuration process of the computing network service API are described below.

[0087] This embodiment describes the registration process for the computing network service API. For example... Figure 4 As shown, the registration process for the computing network service API provided in this embodiment includes steps S402-S404.

[0088] S402. Send a registration request to the network side. The registration request is used to instruct the terminal to support the computing network service API.

[0089] The network side refers to the infrastructure of the mobile communication network, including the core network, edge nodes, and cloud, encompassing network elements such as AMF, CNMF, and UDM, which are used to coordinate and manage network resources. For example, the AMF in the core network processes terminal registration requests, while the CNMF schedules computing resources.

[0090] A registration request can be understood as a message initiated by a terminal to the network side to complete network access registration, thereby informing the network of its own capabilities. For example, it informs the network side that the terminal supports the computing network service API.

[0091] The registration request is used to indicate that the terminal supports the computing network service API. It indicates that the registration request contains specific fields or identifiers, which clearly inform the network side that the terminal has deployed the computing network service API and has the ability to call the computing network resources of the network side through the computing network service API.

[0092] In one possible implementation, when a terminal registers with the network, it adds a specific identifier to the registration request, explicitly informing the network that it has the ability to access computing network resources through the computing network service API. For example, when a smartphone registers upon startup, it includes the identifier "Support=ComputeNetworkAPI" in the registration request. When the network receives and parses the registration request and obtains the "Support=ComputeNetworkAPI" identifier, it knows that the terminal has deployed the computing network service API and that the terminal itself has the ability to access computing network resources through the computing network service API.

[0093] S404. Receive a registration response sent by the network side. The registration response includes a third identifier bit, which is used to indicate whether the terminal is allowed to provide the computing network service API. When the third identifier bit is used to indicate that the terminal is allowed to provide the computing network service API, the registration response also includes a first application list, a second application list, and the parameter format of the computing network service API.

[0094] The registration response refers to the reply message returned by the network to the registration request sent by the terminal, which informs the terminal whether the registration was successful and related configuration information. The registration response includes key information such as whether the registration was successful and the network service permissions that the terminal can use. For example, after the terminal registers with the network, the "registration accepted" message returned by the network is the registration response.

[0095] The third flag can be understood as a flag in the registration response used to explicitly indicate specific permissions. Specifically, it represents a clear authorization flag from the network side regarding whether the terminal has permission to access the computing network service API. If the third flag is "allowed," the terminal can provide the application with the ability to call the computing network service API; if the third flag is "prohibited," the terminal cannot access the computing network service API. For example, the third flag is represented in binary form, such as "1" for allowed and "0" for prohibited.

[0096] The network side sets a third identifier field in the registration response, which includes the terminal's permission information for providing computing network service APIs in the registration response, so that the terminal can clearly know whether it is qualified to open the computing network service API.

[0097] In one possible implementation, the terminal parses the registration response and uses a third identifier to determine whether it is permitted to provide the computing network service API. If the third identifier is "permitted," the terminal activates its local computing network service API module, prepares to receive application call requests, and performs subsequent permission control based on the parameter format and application list in the registration response. If the third identifier is "prohibited," the terminal does not activate the computing network service API, and applications cannot call the computing network service API to request network computing resources.

[0098] Adding the authorization result of the computing network service API to the registration process enables the computing network capabilities of the terminal and the network side to work together in accordance with a unified signaling process, which meets the requirements of integrated management in 6G intelligent computing convergence and improves network efficiency.

[0099] When the network side allows terminals to provide computing network service APIs, the registration response also includes: a first application list, a second application list, and the parameter format of the computing network service API; the first application list refers to the list of applications allowed to call the computing network service API, and the second application list refers to the list of applications prohibited from calling the computing network service API.

[0100] The first application list is a pre-defined list of applications authorized to call the computing network service API, set up by the network side. This list includes multiple application identifiers (APP IDs). For example, the first application list might include an autonomous driving assistance APP, which would allow the autonomous driving assistance APP on the terminal to access the network's computing resources to process real-time traffic data.

[0101] The second application list is a network-side restricted list of applications that are not allowed to call the computing network service API. This list includes multiple application identifiers. For example, the second application list might include lightweight game apps. In this case, lightweight game apps on the terminal are prohibited from calling the computing network service API to avoid wasting resources.

[0102] The parameter format of the computing network service API is a specification required by the network side that applications must follow when calling the computing network service API. This includes the fields and format requirements that must be included in the API call request. For example, the API call request must include: application identifier, computing network service identifier, computing network service requirements, and computing network service information. Computing network service requirements include: computing network service RTT latency, inference accuracy, security requirements, and power consumption requirements. Computing network service information includes: computing network service data volume, computing network service priority, edge-side computation latency range, and RT latency, ensuring that the network side can correctly parse the requirements.

[0103] In this embodiment, by transmitting the permission list and parameter format in the registration response, a closed loop of network-side authorization, efficient terminal verification, and application specification invocation is realized, which improves the controllability and invocation efficiency of computing network resources and provides technical support for 6G computing network convergence scenarios.

[0104] Based on the above embodiments, this embodiment optimizes the registration process, wherein the network side includes AMF, CNMF, and UDM. For example... Figure 5 As shown, the registration process mainly includes steps S502-S524.

[0105] S502, the UE sends a registration request to the AMF.

[0106] The registration request is used to instruct the terminal to support the "Computing Network Service API". In other words, the registration request is used to explicitly inform the network side that the terminal has deployed the Computing Network Service API and has the ability to call the computing network resources on the network side through the Computing Network Service API.

[0107] S504, AMF sends a retrieval request to UDM.

[0108] AMF sends a retrieval request to UDM via Nudm_SDM_Get.

[0109] The retrieval request instructs the UDM to retrieve the UE context from network service subscription data and CNMF data. For example, network service subscription data may include whether the terminal is authorized to use the network service API; the UE context in the CNMF data may include network management context information related to the terminal.

[0110] S506, UDM returns the retrieval response to AMF.

[0111] UDM returns a retrieval response to AMF via Nudm_SDM_Get response.

[0112] The retrieval response includes network service subscription data and additional information. The network service subscription data includes: permitted network service API usage, a list of applications allowed to call the network service API (first application list), a list of applications prohibited from calling the network service API (second application list), and the network service API parameter format. Additional information includes: if the CNMF stored in the UDM and the AMF belong to the same PLMN (Public Land Mobile Network), then CNMF information is returned additionally. For example, CNMF information includes the CNMF identifier, CNMF address, etc.

[0113] S508, Subscription to the Internet Service Contract: Data Updates / Notifications.

[0114] If the computing network service API is permitted, the AMF subscribes to the UDM for updates to the computing network service subscription data via Nudm_SDM_Subscribe (UDM's session management data subscription service). When the computing network service subscription data is updated, the UDM will notify the AMF.

[0115] S510, AMF selects CNMF.

[0116] When selecting a CNMF, the AMF can do so based on the CNMF address pre-configured locally by the AMF, the CNMF information returned by the UDM, or by discovering an available CNMF through the NRF.

[0117] S512, AMF sends an activation request to CNMF.

[0118] AMF sends an activation request via Ncnmf_ComputingService_Activate request, which includes: SUPI (Subscription Permanent Identifier), AMF ID, AMF address, etc.

[0119] S514, CNMF sends a registration request to UDM.

[0120] The CNMF sends a registration request to the UDM through Nudm_UECM_Registration (UE Context Management Registration Service of UDM). The registration request includes: SUPI, CNMF identifier, CNMF address, UE context information related to computing network services, etc., so that UDM records the association between the CNMF and the terminal.

[0121] S516, CNMF sends a retrieval request to UDM.

[0122] CNMF retrieves network service contract data from UDM via Nudm_SDM_Get.

[0123] The search request includes: data on the subscription of computing network services, such as: a list of apps that are allowed to call the computing network service API, a list of apps that are prohibited from calling the computing network service API, and the format of the computing network service API parameters.

[0124] S518, UDM sends a retrieval response to CNMF.

[0125] UDM sends a retrieval response to CNMF via Nudm_SDM_Get response, which includes: allowing the "Computing Network Service API", a list of apps allowed to call the Computing Network Service API, a list of apps prohibited from calling the Computing Network Service API, and the format of the Computing Network Service API parameters.

[0126] S520, Subscription network service contract data updates / notifications.

[0127] CNMF subscribes to UDM for updates / notifications of computing network service subscription data. When the computing network service subscription data is updated, UDM will notify AMF.

[0128] CNMF subscribes to UDM's network service subscription data updates via Nudm_SDM_Subscribe.

[0129] S522 and CNMF send an activation response to AMF.

[0130] CNMF sends an activation response to AMF via the Ncnmf_ComputingService_Activate response, which includes SUPI, CNMF ID, CNMF address, etc.

[0131] S524, AMF returns a registration response to UE.

[0132] The registration response includes a third flag, which indicates that the terminal's network service API is allowed, meaning the network side has permission to access the network service API on the terminal. In addition, the registration response also includes: a list of applications allowed to call the network service API, a list of applications prohibited from calling the network service API, and the parameter format of the network service API.

[0133] It should be noted that CNMF may be deployed as a functional module along with SMF and PCF, or it may exist independently as a core network element.

[0134] This embodiment describes the configuration process for the computing network service API. For example... Figure 6 As shown, the configuration process of the computing network service API provided in this embodiment includes steps S602-S606.

[0135] S602. Obtain the application's subscription request for computing network service API information, which includes the application's application identifier.

[0136] A network service API information subscription request can be understood as a request initiated by an application to a terminal to request information related to the network service API. In essence, the information subscription request is a reservation mechanism for information acquisition. The application expresses its need for continuous attention to network service API information through this network service API information subscription request.

[0137] The application initiates the subscription request for computing network service API information. It includes the application's application identifier and the subscription request for computing network service API information. It is the initial interaction between the application and the terminal to establish a push link for computing network service API information.

[0138] If the application and the terminal are components within the same device, such as a local app running on the terminal, they can transmit network service API information subscription requests through inter-process communication (IPC) mechanisms. For example, a mobile app can send a network service API information subscription request to the local terminal module via a message queue.

[0139] S604. If the terminal meets the conditions for calling the computing network service API, determine whether the application has the permission to call the computing network service API based on the application's application identifier. The conditions for the terminal to meet the conditions for calling the computing network service API include at least one of the following: the terminal supports the computing network service API; the terminal has registered with the network side, and the registration request indicates that the terminal supports the computing network service API; the terminal has been allowed by the network side to provide the computing network service API.

[0140] The conditions for calling the computing network service API can be understood as the prerequisites that the terminal must meet in order to support the application's call to the computing network service API it has deployed.

[0141] Terminal support for network service APIs can be understood as the terminal possessing the hardware and software environment necessary to run the network service APIs, enabling them to start and process requests normally. Terminal registration with the network side and indication of terminal support for network service APIs can be understood as the terminal submitting identity information (such as terminal identifier and location information) to the network side through a preset protocol and completing authentication, thus being incorporated into the network side's network resource management system and becoming a schedulable node. Terminal permission from the network side to provide network service APIs can be understood as the terminal opening the call channel for network service APIs with permissions granted by the network side, allowing applications to initiate requests, rather than being in a disabled or isolated state.

[0142] In this embodiment, by clarifying the conditions for the terminal to call the computing network service API, a standardized access mechanism from the terminal to the network side is constructed, which improves the efficiency of computing network resource scheduling and the ability of ecosystem collaboration.

[0143] Access permission refers to an application's qualification to use the computing network service API. It determines whether an application can call computing network resources through the computing network service API, including whether calls are allowed and the scope of resources that can be called. For example, application 1 is authorized to call the computing power resources of edge nodes, while application 2 was denied access to computing network resources through the computing network service API due to lack of authentication.

[0144] A terminal meeting the conditions for calling the computing network service API means that the terminal has met the basic requirements for providing computing network service API calls and has the ability to process call requests. For example, the terminal has completed network-side registration and been included in the computing network resource pool, and the terminal hardware supports the computing power scheduling function required by the API.

[0145] The terminal maintains a primary application list. After confirming that it meets the conditions for calling the computing network service API, the terminal extracts the application identifier from the computing network service API information subscription request and determines whether the application identifier is in the primary application list. If it is in the primary application list, it indicates that the application has the permission to call the computing network service API. If it is not in the primary application list, it indicates that the application does not have the permission to call the computing network service API.

[0146] S606. Send a network service API information notification to the application. The network service API information notification includes a second identifier bit, which is used to indicate whether the application has the permission to call the network service API. If the terminal determines that the application has the permission to call the network service API, the network service API information notification also includes: the parameter format of the network service API; if the terminal determines that the application does not have the permission to call the network service API, the network service API information notification also includes: the reason for prohibiting the call to the network service API.

[0147] The network service API information notification can be understood as the response information returned by the terminal to the application after receiving the application's network service API information subscription request, including: the subscription processing result and related status. The second identifier can be understood as a field or identifier in the network service API information notification indicating whether the application has the permission to call the network service API. The second identifier is used to clearly inform the application whether it is allowed to call the network service API, providing a basis for the application to initiate subsequent call processes.

[0148] In one possible implementation, the terminal determines whether an application has permission to call the network service API based on the application identifier, and then generates a notification. If the application has permission to call the network service API, the second identifier is set to "permission granted" (e.g., "0"), and supplementary information, such as the parameter format of the network service API, can be attached to the notification. If the application does not have permission to call the network service API, the second identifier is set to "no permission granted" (e.g., "1"), and a reason for rejection can be attached, such as: abnormal API service status, or the app not being contracted.

[0149] Furthermore, when the computing network service API information is updated, a computing network service API information notification is sent to the application.

[0150] When the terminal determines that the application has the permission to call the computing network service API, it returns the parameter format of the computing network service API to the application through the computing network service API information notification. This enables the application to construct the calling request of the computing network service API according to the unified specification requirements, avoids call failure due to format mismatch, and reduces the resource consumption of invalid interactions.

[0151] When the terminal determines that the application does not have the permission to call the computing network service API, the reason for the prohibition is returned to the application through the computing network service API information notification. The reason for the denial is clearly stated so that the application can clearly understand the root cause of the permission problem, avoid ambiguity in the denial result, reduce unnecessary repeated requests, and reduce the processing pressure on the terminal.

[0152] In this embodiment, a configuration process for the computing network service API is formed through the subscription request, permission judgment, and notification mechanism of computing network service API information, and the interaction efficiency is improved through standardized interaction.

[0153] Based on the above embodiments, this embodiment optimizes the configuration process, such as... Figure 7 As shown, the configuration process of the computing network service API mainly includes steps S702-S704.

[0154] S702, The application sends a request to the terminal to subscribe to the computing network service API information.

[0155] Applications can subscribe to the terminal's computing network service API information. That is, the application sends a computing network service API information subscription request to the terminal, and the computing network service API information subscription request includes the application identifier.

[0156] When a terminal supports the computing network service API and has been registered and authorized, the terminal determines the application's access permission to call the computing network service API based on the relevant information in the registration response returned by the network side.

[0157] S704, The terminal returns a notification of computing network service API information to the application.

[0158] When the terminal determines that the application identifier is within the list of applications allowed to call the computing network service API, it returns a computing network service API information notification to the subscribed application, including: a second identifier bit and the computing network service API parameter format, such as: application identifier, computing network service identifier, computing network service requirement, computing network service information, etc. In this case, the second identifier bit is used to indicate that calling the computing network service API is permitted.

[0159] When the terminal determines that an application's identifier is either on the list of applications prohibited from calling the computing network service API or not on the list of applications allowed to call the computing network service API, i.e., when calling is prohibited, it returns a computing network service API information notification to the subscribed application, including the second identifier and the reason for prohibition. In this case, the second identifier is used to indicate that calling the computing network service API is prohibited. Reasons for prohibition include: abnormal API service status, application not being subscribed, etc.

[0160] Furthermore, when the computing network service API information is updated, a computing network service API information notification is sent to the application.

[0161] For example, the network service API information notification message is as follows:

[0162] When calling the computing network service API is allowed

[0163]

[0164] When calling the computing network service API is prohibited

[0165]

[0166] In this embodiment, the application can subscribe to the terminal's computing network service API information. When the terminal supports the computing network service API and has registered and been authorized, the terminal determines the APP's access permission to call the computing network service API based on the information obtained during the registration phase, and also needs to notify the application authorized to call the API of the parameter format required to call the API.

[0167] Based on the above embodiments, this embodiment optimizes the API call process for computing network services, such as... Figure 8 As shown, it mainly includes steps S802-S822.

[0168] S802, Obtain the API call request for computing services sent by the application.

[0169] The computing network service API is deployed in the terminal and is used to call computing network resources on the network side. The computing network service API call request includes the application identifier of the application, and also includes: computing network service identifier, computing network service requirements, and computing network service information.

[0170] The application sends a computing network service API call request to the terminal. The computing network service API call request follows the computing network service API parameter format specified by the UE in the computing network service API information notification. The computing network service API call request includes: application identifier, computing network service identifier, computing network service requirement, and computing network service information.

[0171] In one possible implementation, the network service API call request further includes: determining the network service API call request based on the requester. The source of the network service API request information can be either the application's client or the application's server.

[0172] When the client making the API call to the computing network service is the application's client, it can be understood that the terminal itself cannot complete the task that the application needs to perform, such as: insufficient terminal computing power, excessive terminal load, insufficient terminal battery, security requirements such as data not leaving the network, etc.

[0173] When the requester of the computing network service API is an application client, the terminal may have already sent the UE identifier, PDU session identifier, computing network service identifier, computing network service requirements, and computing capabilities to the server through the application layer. In this case, the computing network service requirements include: computing network service RTT latency, inference accuracy, security requirements, and power consumption requirements. The computing network service information includes: computing network service data volume, computing network service priority, terminal-side computing latency range, and RT latency.

[0174] The source of the computing network service API request information is the application's server. This can be understood as the inability to complete the tasks that the application needs to perform due to reasons on the application's server side, such as: being unable to meet the RTT latency requirements of the computing network service, or the application server being overloaded.

[0175] When the requester of the computing network service API is the application's server, then the computing network service requirements include computing network service RTT latency, inference accuracy, security requirements, etc. Computing network service information includes: computing network service data volume, computing network service priority, and RT latency.

[0176] For example, a network service API call request is as follows: (

[0178] APPId, / / APP identifier

[0179] ServiceId, / / Identifier for network services

[0180] ServiceReq, / / Network service requirements

[0181] ServiceInfo, / / Network service information )

[0183] S804. Determine whether the application has the permission to call the computing network service API based on the application identifier. If yes, execute S806; otherwise, execute S816.

[0184] In this embodiment, two methods are provided to determine whether an application has the permission to call the computing network service API: one is to use a first application list to determine whether an application has the permission to call the computing network service API, and the other is to use a second application list to determine whether an application has the permission to call the computing network service API.

[0185] In one possible implementation, such as Figure 9 As shown, the method for determining access permissions mainly includes steps S902-S906.

[0186] S902. Determine if the application identifier is in the first application list. If yes, execute S904; otherwise, execute S906.

[0187] The first application list includes application identifiers that are allowed to call the computing network service API. The first application list is determined by the network side.

[0188] The first application list is a whitelist maintained uniformly by the network side, containing the identifiers of all applications authorized to call the computing network service API. After obtaining this first application list from the network side during the registration process, the terminal stores the first application list locally.

[0189] Upon receiving a request to access the computing network service API, the application identifier included in the request is compared with the application identifiers in the first application list to determine if they match. If they match, the process proceeds to the allow process; otherwise, the process proceeds to the deny process.

[0190] S904. Ensure that the application has the permission to call the computing network service API.

[0191] When an application identifier exists in the first application list, the terminal determines that the application has passed the network-side access control and has the authority to call the computing network service API. The terminal will allow the API call request initiated by the application and further process its business requirements.

[0192] S906. It is determined that the application does not have the permission to call the computing network service API.

[0193] When an application's identifier is not in the first application list, the terminal determines that the application has not been authorized by the network side and does not have the permission to make calls. The terminal will reject the application's API call request and may return a reason for the prohibition to the application, such as not being in the authorized list, to prevent unauthorized applications from occupying network resources.

[0194] In this embodiment, through a whitelist mechanism (first application list), the terminal can strictly control which applications can call the computing network service API, effectively preventing unauthorized access by malicious applications, unregistered applications, or non-compliant applications, and reducing the risk of resource abuse, data leakage, or network attacks.

[0195] In one possible implementation, such as Figure 10 As shown, the permission judgment method mainly includes steps S1002-S1004.

[0196] S1002. Determine if the application identifier is in the second application list. If so, execute S1004.

[0197] The second application list includes application identifiers that are prohibited from calling the computing network service API. The second application list is determined by the network side.

[0198] The second application list is a blacklist maintained by the network side, containing the identifiers of all applications explicitly prohibited from calling the computing network service API. After obtaining this second application list from the network side during the registration process, the terminal stores the second application list locally.

[0199] Upon receiving a request to access the computing network service API, the application identifier included in the request is compared with the application identifiers in the second application list to determine if they match. If they do not match, the process proceeds to the allow process; if they match, the process proceeds to the deny process.

[0200] S1004. It is determined that the application does not have the permission to call the computing network service API.

[0201] When an application's identifier exists in the second application list, it is determined that the application is explicitly prohibited from calling the backup computing network service API by the network side. The application's call to the backup computing network service API is directly rejected without further verification of other conditions, thus blocking the risk at its source.

[0202] In this embodiment, a blacklist mechanism (second application list) is used to accurately block high-risk applications, preventing them from abusing their access to the computing network service API and reducing the probability of large-scale security incidents.

[0203] S806. Determine whether the parameter format of the network service API call request is consistent with the parameter format of the network service API. The parameter format of the network service API is determined by the network side. If yes, execute S808; otherwise, execute S816.

[0204] The parameter format of the computing network service API is a standard format uniformly defined and published by the network side, and it is a syntax rule that all legitimate call requests must follow. During the terminal registration process, the network side sends the parameter format of the computing network service API to the terminal, and the terminal stores it locally.

[0205] After confirming that the application has the permission to call the computing network service API, the parameter format of the computing network service API call request is compared with the parameter format of the computing network service API. If they match, the computing network service API accepts the application's call. If they do not match, the computing network service API rejects the application's call.

[0206] S808, Determine if the network service API accepts application calls.

[0207] S810: Send a network service request to the network side.

[0208] The computing network service request includes terminal identifier, PDU session identifier, computing network service identifier, computing network service requirements, computing network service information, and computing capabilities.

[0209] If the client requesting the computing network service API call is determined to be a client of the application, the terminal sends a computing network service request to the core network. The computing network service request includes the terminal identifier, PDU session identifier, computing network service identifier, computing network service requirements, computing network service information, and computing capabilities. The computing network service requirements include: computing network service RTT latency, inference accuracy, security requirements, and power consumption requirements. The computing network service information includes: computing network service data volume, computing network service priority, edge-side computing latency range, and RT latency.

[0210] If the API call requester for the computing network service is determined to be the server of the application, the terminal sends a computing network service request to the core network. The computing network service request includes the terminal identifier, PDU session identifier, computing network service identifier, computing network service requirements, computing network service information, and computing capabilities. The computing network service requirements include: computing network service RTT latency, inference accuracy, security requirements, and power consumption requirements. The computing network service information includes: computing network service data volume, computing network service priority, and RT latency.

[0211] S812. Receive the computing network service response returned by the network side, wherein the computing network service response includes the computing network QoS policy and the computing network resource address, the computing network resource address is determined based on the selected computing network node, and the computing network QoS policy includes at least the computing network resource type and the computing network resource size.

[0212] In one possible implementation, after receiving a computing network service request, the network side (network elements such as CNMF / PCF / SMF in the core network) performs resource coordination and scheduling, and returns a computing network service response to the terminal. The computing network service response includes computing network QoS policies and computing network resource addresses.

[0213] A computing network QoS policy refers to the service quality assurance rules allocated to computing network services, such as bandwidth, latency, and packet loss rate, to ensure that services meet requirements during transmission and computation. A computing network QoS policy must at least include the type and size of computing network resources.

[0214] If it is determined that the client requesting the computing network service API is the client of the application, the core network CNMF / PCF / SMF will directly and collaboratively make decisions on computing network QoS and computing network resource addresses based on all information in the computing network service request.

[0215] If the requester of the computing network service API is determined to be the server of the application, the core network CNMF / PCF / SMF will collaboratively determine the end-side computing latency range and computing network service data volume based on all information in the computing network service request, and then collaboratively decide on computing network QoS and computing network resource address.

[0216] Network resources include: GPU computing power, memory resources, storage resources, etc.; network resource size refers to the specific quota of resources, such as 16-core CPU, 32GB memory, etc.

[0217] The computing network resource address refers to a virtual address (not a real physical address) mapped through the network. It ensures the security of resource access while avoiding the exposure of network-side architecture details. The computing network resource address is determined based on the selected computing network node.

[0218] S814. Return a response to the computing network service API call to the application. If the application's call to the computing network service API is accepted, the response to the computing network service API call shall also include at least one of the following: terminal identifier, PDU session identifier, application identifier, computing network service identifier, computing network resource type, computing network resource size, and computing network resource address.

[0219] After confirming acceptance of the application's call to the computing network service API, the terminal returns a computing network service API call response to the application that initiated the request. At this time, the first flag in the computing network service API call response is set to the accept status, indicating that the application's call to the computing network service API is accepted.

[0220] S816. Determine whether to reject the application's call to the computing network service API.

[0221] S818. Return the computing network service API call response to the application. If the application is refused to call the computing network service API, the computing network service API call response shall also include: the reason for refusing to call the computing network service API.

[0222] After determining that the application's call to the computing network service API is rejected, the terminal returns a computing network service API call response to the application that initiated the request. At this time, the first flag in the computing network service API call response is set to a rejected state, indicating that the application's call to the computing network service API is rejected.

[0223] In addition, the response to the computing network service API call also includes the reason why the computing network service API refused to be called. For example: abnormal API service status, the APP is not subscribed, or the parameter format of the API call request is incorrect.

[0224] In this embodiment, the specific reason for the rejection is passed to the application in the call response, so that the application can clearly understand the root cause of the rejection and avoid repeated requests, which would lead to resource waste.

[0225] For example, the response to a network service API call is as follows:

[0226] When the call is accepted,

[0227]

[0228] When the call is refused,

[0229]

[0230] In this embodiment, by combining information such as terminal identifier and service requirements in the network service request with the QoS policy and node selection returned by the network side, accurate resource matching is achieved, avoiding mismatch and redundancy.

[0231] This embodiment provides a schematic diagram of network architecture interaction in a computing-network convergence scenario, such as... Figure 11 As shown, APP1110 interacts with terminal 101 via the computing network service API, initiating a computing network service API call request. Upon receiving the request, terminal 101 determines whether to accept the application's call. If accepted, terminal 101 sends a computing network service request to CN control function 1120 via Non-Access Stratum (NAS) signaling and receives the computing network service response returned by CN control function 1120 via NAS. Finally, terminal 101 responds to APP via API, completing the computing network service loop.

[0232] RAN 1130 is a radio access network that provides a radio connection between the UE and the core network and is responsible for the radio transmission and forwarding of data.

[0233] The CN control function 1120 parses and schedules network requests based on computing power-related functions, and combines other functions to ensure basic capabilities such as sessions and mobility.

[0234] In one possible implementation, such as Figure 12 As shown, the API call process for the computing network service provided in this embodiment includes steps S1202-S1208.

[0235] S1202, The application sends a network service API call request to the terminal.

[0236] S1204. The terminal sends a network service request to the network side.

[0237] If the terminal determines that it accepts the application's call to the computing network service API, it sends a computing network service request to the network side.

[0238] S1206, The network-side terminal sends a network service response.

[0239] The network side (AMF / CNMF / SMF / UPF) performs network node status management, network node coordination and selection, and network QoS policy formulation based on the terminal identifier, PDU session identifier, network service identifier, network service requirements, network service information, and computing capabilities sent by the terminal. It then sends a network service response to the terminal, which includes the network QoS policy and network resource address.

[0240] S1208, The terminal sends a response to the network service API call to the application.

[0241] The network resource type, size, and address returned by the network side are added to the network service API call response. The first flag in the network service API call response indicates that the application's call to the network service API is accepted.

[0242] Applications request network-side computing resources by calling the UE's computing service API. The APP initiates the computing service API call request based on the information obtained during the configuration phase. The UE notifies the network through NAS, and the network returns the computing service API call result, which includes the computing resource type, computing resource size, computing resource address, etc.

[0243] In one possible implementation, such as Figure 13 As shown, the calling process of the computing network service API provided in this embodiment includes steps S1302-S1304.

[0244] S1302, The application sends a network service API call request to the terminal.

[0245] S1304. The terminal sends a response to the network service API call to the application.

[0246] If the terminal determines that it will reject the application's call to the computing network service API, it sends a computing network service API call response to the application. The first flag of the computing network service API call response indicates that the computing network service API has rejected the application's call. The computing network service API call response also includes the reason for rejecting the call to the computing network service API.

[0247] It should be noted that the acquisition, storage, use, and processing of data in this disclosed technical solution comply with the relevant provisions of laws and regulations. All types of data, such as personal identity data, operational data, and behavioral data related to individuals, customers, and groups, obtained in this disclosed embodiment have been agreed upon by the users.

[0248] Based on the same disclosed concept, this disclosure also provides a network service API management device, as described in the following embodiments. Since the principle by which this device solves the problem is similar to that of the above method embodiments, the implementation of this device embodiment can refer to the implementation of the above method embodiments, and repeated details will not be repeated.

[0249] Figure 14 This diagram illustrates a network service API management device according to an embodiment of the present disclosure, such as... Figure 14 As shown, the device includes: a call request acquisition module 1410, a call judgment module 1420, and a call response return module 1430.

[0250] The application includes a request acquisition module 1410, which acquires a network service API call request sent by the application. The network service API is deployed in the terminal and is used to call network resources on the network side. The network service API call request includes the application's application identifier. The call judgment module 1420 is used to determine whether to accept the application's call to the network service API based on the application's application identifier and the parameter format of the network service API call request. The call response return module 1430 is used to return a network service API call response to the application. The network service API call response includes a first identifier bit, which indicates whether to accept the application's call to the network service API.

[0251] In some exemplary embodiments, the call judgment module 1420 includes: a permission judgment unit, used to determine whether the application has the permission to call the computing network service API based on the application identifier of the application; a format judgment unit, used to determine whether the parameter format of the computing network service API call request is consistent with the parameter format of the computing network service API if the application has the permission to call the computing network service API, wherein the parameter format of the computing network service API is determined by the network side; an accept call unit, used to determine to accept the application's call to the computing network service API if the parameter format of the computing network service API call request is consistent with the parameter format of the computing network service API; and a reject call unit, used to determine to reject the application's call to the computing network service API if the application does not have the permission to call the computing network service API or the parameter format of the computing network service API call request is inconsistent with the parameter format of the computing network service API.

[0252] In some exemplary embodiments, the system further includes: a configuration module, configured to obtain a subscription request for computing network service API information sent by an application, wherein the subscription request for computing network service API information includes an application identifier of the application; if the terminal meets the conditions for calling the computing network service API, the module determines whether the application has the permission to call the computing network service API based on the application identifier; and sends a computing network service API information notification to the application, wherein the computing network service API information notification includes a second identifier bit, the second identifier bit being used to indicate whether the application has the permission to call the computing network service API.

[0253] In some exemplary embodiments, the permission determination unit is specifically used to determine whether the application identifier of the application is in the first application list. The first application list includes application identifiers that are allowed to call the computing network service API, and the first application list is determined by the network side. If the application identifier of the application is in the first application list, it is determined that the application has the permission to call the computing network service API. If the application identifier of the application is not in the first application list, it is determined that the application does not have the permission to call the computing network service API.

[0254] In some exemplary embodiments, the permission determination unit is specifically used to determine whether the application identifier of the application is in the second application list, wherein the second application list includes application identifiers that are prohibited from calling the computing network service API, and the second application list is determined by the network side; if the application identifier of the application is in the second application list, it is determined that the application does not have the permission to call the computing network service API.

[0255] In some exemplary embodiments, the computing network service API call request further includes: computing network service identifier, computing network service requirement, and computing network service information; it also includes: a call response determination module, configured to, if accepting the application's call to the computing network service API, send a computing network service request to the network side, wherein the computing network service request includes a terminal identifier, a PDU session identifier, a computing network service identifier, a computing network service requirement, computing network service information, and computing power; receive a computing network service response returned by the network side, wherein the computing network service response includes a computing network QoS policy and a computing network resource address, the computing network resource address being determined based on the selected computing network node, and the computing network QoS policy including at least a computing network resource type and a computing network resource size; and return a computing network service API call response to the application, wherein the first identifier bit is used to indicate that the computing network service API accepts the application's call, and the computing network service API call response further includes at least one of the following: a terminal identifier, a PDU session identifier, the application identifier, the computing network service identifier, the computing network resource type, the computing network resource size, and the computing network resource address.

[0256] In some exemplary embodiments, when an application's call to the computing network service API is denied, the computing network service API call response may also include: the reason for the computing network service API's denial of the call.

[0257] In some exemplary embodiments, the conditions for a terminal to call the computing network service API include at least one of the following:

[0258] The terminal supports the computing network service API;

[0259] The terminal has registered with the network side, and the registration request indicates that the terminal supports the computing network service API;

[0260] The terminal is permitted by the network side to provide computing network service APIs.

[0261] In some exemplary embodiments, when the terminal determines that the application has the permission to call the computing network service API, the computing network service API information notification also includes: the parameter format of the computing network service API;

[0262] If the terminal determines that the application does not have permission to call the computing network service API, the computing network service API information notification will also include: the reason for prohibiting the call to the computing network service API.

[0263] In some exemplary embodiments, the system further includes: a registration module, configured to send a registration request to the network side, the registration request being used to instruct the terminal to support the computing network service API; and to receive a registration response sent by the network side, the registration response including a third identifier bit, the third identifier bit being used to indicate whether the terminal is allowed to provide the computing network service API.

[0264] In some exemplary embodiments, the third identifier bit is used to indicate when the terminal is allowed to provide the computing network service API. The registration response also includes: a first application list, a second application list, and the parameter format of the computing network service API.

[0265] It should be noted that the examples and application scenarios implemented by the modules in the above device embodiments and the corresponding steps in the method embodiments are the same, but are not limited to the content disclosed in the above method embodiments. It should also be noted that the above modules, as part of the device, can be executed in a computer system such as a set of computer-executable instructions.

[0266] Those skilled in the art will understand that various aspects of this disclosure can be implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which can be collectively referred to herein as a "circuit", "module" or "system".

[0267] Based on the same disclosed concept, this disclosure also provides an electronic device, which includes: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the network service API management method described above by executing the executable instructions. Since the principle by which this electronic device embodiment solves the problem is similar to that of the above method embodiments, the implementation of this electronic device embodiment can refer to the implementation of the above method embodiments, and repeated details will not be described again.

[0268] The following reference Figure 15 To describe an electronic device 1500 according to such an embodiment of the present disclosure. Figure 15 The electronic device 1500 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0269] like Figure 15 As shown, the electronic device 1500 is manifested in the form of a general-purpose computing device. The components of the electronic device 1500 may include, but are not limited to: at least one processing unit 1510, at least one storage unit 1520, and a bus 1530 connecting different system components (including storage unit 1520 and processing unit 1510).

[0270] The storage unit stores program code that can be executed by the processing unit 1510, causing the processing unit 1510 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure. For example, the processing unit 1510 can perform the following steps of the above method embodiment: obtaining a computing network service API call request sent by an application, wherein the computing network service API is deployed in the terminal and is used to call computing network resources on the network side, and the computing network service API call request includes the application's application identifier; determining whether to accept the application's call to the computing network service API based on the application's application identifier and the parameter format of the computing network service API call request; and returning a computing network service API call response to the application, wherein the computing network service API call response includes a first identifier bit, which is used to indicate whether the application's call to the computing network service API is accepted.

[0271] Storage unit 1520 may include readable media in the form of volatile storage units, such as random access memory (RAM) 15201 and / or cache memory 15202, and may further include read-only memory (ROM) 15203.

[0272] Storage unit 1520 may also include a program / utility 15204 having a set (at least one) program module 15205, such program module 15205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0273] Bus 1530 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0274] Electronic device 1500 can also communicate with one or more external devices 1540 (e.g., keyboard, pointing device, Bluetooth device, etc.), one or more devices that enable a user to interact with electronic device 1500, and / or any device that enables electronic device 1500 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1550. Furthermore, electronic device 1500 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1560. As shown, network adapter 1560 communicates with other modules of electronic device 1500 via bus 1530. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 1500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0275] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0276] Based on the same disclosed concept, this disclosure also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the network service API management method described above. Since the principle by which this computer-readable storage medium embodiment solves the problem is similar to that of the above method embodiments, the implementation of this computer-readable storage medium embodiment can refer to the implementation of the above method embodiments, and repeated details will not be elaborated further.

[0277] More specific examples of computer-readable storage media in this disclosure may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0278] In this disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.

[0279] Optionally, the program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0280] In practical implementation, program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0281] Based on the same disclosed concept, this disclosure also provides a computer program product, including: a computer program or instructions, which, when executed by a processor, implement the network service API management method of any one of the above method embodiments. Since the principle by which this computer program product embodiment solves the problem is similar to that of the above method embodiments, the implementation of this computer program product embodiment can refer to the implementation of the above method embodiments, and repeated details will not be elaborated further.

[0282] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0283] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0284] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0285] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the appended claims.

Claims

1. A method for managing network service APIs, characterized in that, The method is applied to a terminal and includes: Obtain the application programming interface (API) call request for computing network services sent by the application. The computing network service API is deployed in the terminal and is used to call computing network resources on the network side. The computing network service API call request includes the application identifier of the application. Based on the application identifier of the application and the parameter format of the computing network service API call request, determine whether to accept the application's call to the computing network service API; The application is returned a computing network service API call response, which includes a first identifier bit indicating whether the application's call to the computing network service API is accepted.

2. The method for managing network service APIs according to claim 1, characterized in that, The determination of whether to accept the application's call to the computing network service API based on the application identifier of the application and the parameter format of the computing network service API call request includes: Based on the application identifier of the application, determine whether the application has the permission to call the computing network service API; If the application has the permission to call the computing network service API, then it is determined whether the parameter format of the computing network service API call request is consistent with the parameter format of the computing network service API. The parameter format of the computing network service API is determined by the network side. If the parameter format of the request to call the computing network service API is consistent with the parameter format of the computing network service API, then the application's call to the computing network service API is accepted. If the application does not have the permission to call the computing network service API, or if the parameter format of the request to call the computing network service API is inconsistent with the parameter format of the computing network service API, then the application's call to the computing network service API will be rejected.

3. The method for managing network service APIs according to claim 1, characterized in that, Also includes: Obtain the application's subscription request for computing network service API information, wherein the application identifier of the application is included in the subscription request for computing network service API information. If the terminal meets the conditions for calling the computing network service API, determine whether the application has the permission to call the computing network service API based on the application identifier of the application. Send a computing network service API information notification to the application. The computing network service API information notification includes a second identifier bit, which is used to indicate whether the application has the permission to call the computing network service API.

4. The method for managing network service APIs according to claim 2 or 3, characterized in that, The step of determining whether an application has permission to call the computing network service API based on the application's application identifier includes: Determine whether the application identifier of the application is in the first application list, the first application list includes application identifiers that are allowed to call the computing network service API, and the first application list is determined by the network side; If the application identifier of the application is in the first application list, then it is determined that the application has the permission to call the computing network service API; If the application's application identifier is not in the first application list, then it is determined that the application does not have the permission to call the computing network service API.

5. The method for managing network service APIs according to claim 4, characterized in that, The step of determining whether an application has the permission to call the computing network service API based on the application's application identifier further includes: Determine whether the application identifier of the application is in the second application list, the second application list includes application identifiers that are prohibited from calling the computing network service API, and the second application list is determined by the network side; If the application's application identifier is in the second application list, then it is determined that the application does not have the permission to call the computing network service API.

6. The method for managing network service APIs according to claim 2, characterized in that, The computing network service API call request also includes: computing network service identifier, computing network service requirements, and computing network service information; the method also includes: If the application's call to the computing network service API is accepted, a computing network service request is sent to the network side, wherein the computing network service request includes a terminal identifier, a PDU session identifier, a computing network service identifier, a computing network service requirement, a computing network service information, and computing capabilities; The network service response returned by the network side is received. The network service response includes: network QoS policy and network resource address. The network resource address is determined based on the selected network node. The network QoS policy includes at least network resource type and network resource size. The application is returned a computing network service API call response. The first identifier bit is used to indicate that the application's call to the computing network service API is accepted. The computing network service API call response also includes at least one of the following: terminal identifier, PDU session identifier, application identifier, computing network service identifier, computing network resource type, computing network resource size, and computing network resource address.

7. The method for managing network service APIs according to claim 6, characterized in that, In the event that the application's call to the computing network service API is denied, the computing network service API call response may also include: the reason for denying the call to the computing network service API.

8. The method for managing network service APIs according to claim 3, characterized in that, The terminal meets at least one of the following conditions for calling the computing network service API: The terminal supports the computing network service API; The terminal has registered with the network side, and the registration request indicates that the terminal supports the computing network service API; The terminal is permitted by the network side to provide the computing network service API.

9. The method for managing network service APIs according to claim 3, characterized in that, The terminal determines that the application has the permission to call the computing network service API, and the computing network service API information notification also includes: the parameter format of the computing network service API; If the terminal determines that the application does not have the permission to call the computing network service API, the computing network service API information notification also includes: the reason for prohibiting the call to the computing network service API.

10. The method for managing network service APIs according to claim 1, characterized in that, Also includes: Send a registration request to the network side, the registration request being used to instruct the terminal to support the computing network service API; The system receives a registration response sent by the network side. The registration response includes a third identifier bit, which is used to indicate whether the terminal is allowed to provide computing network service APIs.

11. The method for managing network service APIs according to claim 10, characterized in that, When the third identifier indicates that the terminal is allowed to provide the computing network service API, the registration response also includes: a first application list, a second application list, and the parameter format of the computing network service API.

12. A network service API management device, characterized in that, The device is configured in a terminal and includes: The request acquisition module is used to acquire the application programming interface (API) call request for computing network services sent by the application. The computing network service API is deployed in the terminal and is used to call computing network resources on the network side. The computing network service API call request includes the application identifier of the application. The judgment module is invoked to determine whether to accept the application's call to the computing network service API based on the application identifier of the application and the parameter format of the computing network service API call request; The call response return module is used to return a computing network service API call response to the application. The computing network service API call response includes a first identifier bit, which is used to indicate whether the application's call to the computing network service API is accepted.

13. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the computing network service API management method according to any one of claims 1 to 11 by executing the executable instructions.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the network service API management method according to any one of claims 1 to 11.

15. A computer program product comprising: A computer program or instruction, characterized in that, when executed by a processor, the computer program or instruction implements the network service API management method according to any one of claims 1 to 11.

Images