Communication system and communication apparatus based on network capability open architecture

Abstract

Embodiments of the present application provide a communication system and communication apparatus based on a network capability open architecture. The method comprises: a terminal device, a network device, a cloud device, and a campus or private network device can all serve as API providers to register respective first APIs with an API repository function in a network, and an API orchestrating function in the network can combine at least two first APIs provided by providers of the same type or different types so as to obtain a second API for a caller to call. The method can achieve the collaborative function of a terminal, a network and a cloud, support diversified services, and improve user experience.

Description

A communication system and communication device based on network capability open architecture Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a communication system and a communication device based on a network capability exposure architecture. Background Art

[0002] Existing network capability exposure architectures, such as the Common Application Programming Interface Framework (CAPIF) for the fifth generation (5G) network, allow application functions (AFs) to call different application programming interfaces (APIs) provided by different control plane network elements.

[0003] In this architecture, the service API is usually provided by the network (e.g., control plane network elements), and the API is called by third-party applications (e.g., AF). The network's openness is limited, making it difficult to support the diverse services proposed in communications.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a communication system and a communication device based on a network capability open architecture. The terminal, network, and cloud can provide service APIs, thereby supporting the collaborative functions of the terminal, network, and cloud and supporting diversified services.

[0006] In a first aspect, a communication system based on a network capability open architecture is provided, including a service application programmable interface (API) repository function and an API orchestration function, wherein the API repository function is used to receive at least one first registration request from a first device set, the first registration request including information of at least one first API provided by the first device, the first device being any one of the first device set, the first API being used to provide basic service functions, the first device set including at least one of a terminal device, a network device, a cloud device, a campus device or a private network device, the at least one first registration request from the first device set including information of at least two first APIs; the API orchestration function is used to combine the at least two first APIs provided by the first device set to obtain a second API.

[0007] In this application, the first API may also be referred to as a basic API, which is used to provide basic service functions.

[0008] Among them, basic service functions include, for example, UE location function, SMS verification function, voice verification function, data analysis function, etc.

[0009] In this application, the first device serves as the provider of the first API, and the first device may include any one of a terminal device, a network device, a cloud device, a campus device, or a private network device.

[0010] In this application, the API orchestration function can combine first APIs provided by different types of providers, or can combine first APIs provided by the same type of providers, and this embodiment of the application does not limit this.

[0011] According to this technical solution, terminal devices, network devices, cloud devices, campus devices, or private network devices can all act as API providers and register their respective primary APIs with the API repository function within the network capability exposure architecture. The API orchestration function within the network capability exposure architecture can then combine primary APIs from providers of the same or different types to create secondary APIs for the caller to invoke. This network capability exposure architecture can thus achieve device-network-cloud collaboration, support diverse services, and enhance user experience.

[0012] In combination with the first aspect, in a possible implementation, the system further includes an API open function, where the API open function is configured to receive a first call request, where the first call request is configured to request a call to the second API.

[0013] In this technical solution, the API open function is used to receive a first call request from a caller, thereby providing the second API to the caller. The caller can be a first device that has registered the first API with the API repository function, or a terminal device, network device, cloud device, campus device, or private network device that has not registered the first API.

[0014] In combination with the first aspect, in a possible implementation, the system further includes an API publishing function, and the API publishing function is used to publish the second API.

[0015] In this technical solution, the API publishing function is used to publish the second API combined by the API orchestration function for the caller to call.

[0016] In combination with the first aspect, in a possible implementation, when the first device is a cloud device, a device in a campus or a private network device, the API repository function receives the first registration request based on the hypertext transfer protocol (HTTP); when the first device is a terminal device, the API repository function receives the first registration request based on the control plane non-access stratum (NAS) protocol or the user plane part of GPRS tunneling protocol (GTP-U) protocol.

[0017] This technical solution shows that different types of providers register the first API in different ways. The above is only an exemplary description and is not limited to this in the embodiments of the present application.

[0018] In combination with the first aspect, in a possible implementation, the first registration request includes a first condition, where the first condition is a condition for using the at least one first API.

[0019] In this technical solution, when sending the first registration request, the first device can also send the caller's restriction conditions for calling the registered first API. For example, for the first API provided by the terminal device, the first condition can be the call time, the caller (a specific authorized group of users), the unit price, etc. This solution facilitates the first device to manage and maintain the first API, further improving the user experience.

[0020] In combination with the first aspect, in a possible implementation, the system also includes a requirement mapping function, which is used to receive a first functional requirement; the requirement mapping function is also used to determine a first API set based on the first functional requirement and send it to an API orchestration function, where the first API set includes the at least two first APIs provided by the second device set, and the devices in the second device set belong to the first device set; the API orchestration function is specifically used to combine the at least two first APIs in the first API set to obtain the second API.

[0021] In this technical solution, the API orchestration function combines the first API based on the caller's first functional requirements to obtain a second API that meets the caller's requirements. This solution combines the second API based on the user's functional requirements, which can better match user needs and improve user experience.

[0022] In combination with the first aspect, in a possible implementation, the API orchestration function is specifically configured to combine the at least two first APIs included in at least one first registration request from the first device set according to an operation policy to obtain the second API.

[0023] In this technical solution, the API orchestration function does not require actual business demand triggering. Instead, the first API provided by the first device is combined according to the operational policy to obtain the second API. For example, the first API can be combined to obtain a second API with a higher call frequency based on historical records. Alternatively, the API orchestration function can combine the first APIs based on predefined first API requirements to obtain a second API that meets more requirements. This technical solution can complete the combination of the second API offline and does not require actual business demand triggering, thus saving signaling, improving the call efficiency of the caller, and enhancing the user experience.

[0024] In combination with the first aspect, in a possible implementation, the system also includes an API scheduling function, and the API open function is also used to map the second API into the first API set and send the first call request and the first API set to the API scheduling function; the API scheduling function is used to determine the second API set based on the first API set, the second API set includes the at least two first APIs provided by the third device set, the devices in the third device set belong to the first device set, and the second API set is the same as or different from the first API set.

[0025] In this technical solution, the API scheduling function can reselect or optimize APIs in the API repository function based on the functions of the APIs in the first API set to form a second API set, thereby providing the caller with the choice of the optimal basic API that meets the functional requirements, effectively improving the user experience.

[0026] In combination with the first aspect, in a possible implementation, the API open function is also used to perform security authentication.

[0027] In this technical solution, the API open function can perform security authentication on the caller, ensuring the security of the system.

[0028] In combination with the first aspect, in a possible implementation, the system also includes an API monitoring function, which is used to update the first API in the API repository function according to the status of at least one of the first APIs; the API scheduling function is specifically used to determine the second API set based on the at least one first API and the first API set.

[0029] In this technical solution, the API monitoring function can monitor the status of the first API in real time and update the API repository for the API scheduling function to reselect the appropriate second API set. This solution can save the operation and maintenance costs of the network monitoring API and improve the user experience.

[0030] The second aspect provides a communication method based on a network capability exposure architecture. The method can be executed by a first device, or can also be executed by a chip or circuit configured in the first device. This application does not limit this.

[0031] The network capability exposure architecture includes a service application programmable interface API repository function, and the method is applied to a first device, which includes any one of a terminal device, a network device, a cloud device, a campus device or a private network device.

[0032] The first device is any one of a first device set, and the first device set includes at least one of a terminal device, a network device, a cloud device, a campus device, or a private network device.

[0033] The method includes: determining information of at least one first API, where the first API is used to provide basic service functions, and sending a first registration request to the API repository function, where the first registration request includes the information of the at least one first API.

[0034] The first API and the first device in this application can refer to the first aspect and will not be described in detail.

[0035] According to this technical solution, terminal devices, network devices, cloud devices, campus or private network devices can all act as API providers to register their respective first APIs to the API repository function in the network capability exposure architecture. Therefore, the network capability exposure architecture can realize the collaborative functions of terminals, networks and clouds, support specific services and improve user experience.

[0036] In combination with the second aspect, in a possible implementation, when the first device is a cloud device, a campus device, or a private network device, the first device sends the first registration request based on the HTTP protocol; when the first device is a terminal device, the first device sends the first registration request based on the control plane NAS protocol or the user plane GPT-U protocol.

[0037] In combination with the second aspect, in a possible implementation, the first registration request includes a first condition, where the first condition is a condition for the first device to use the at least one first API.

[0038] In combination with the second aspect, in a possible implementation, the network capability exposure architecture also includes a requirement mapping function, and the method also includes: sending a first functional requirement to the requirement mapping function, the requirement mapping function is used to determine a first API set based on the first functional requirement and send it to the API orchestration function, for the API orchestration function to combine the first API in the first API set to obtain the second API, the first API set includes the at least two first APIs provided by the second device set, and the devices in the second device set belong to the first device set.

[0039] The third aspect provides a communication method based on a network capability exposure architecture. The method can be executed by a second device, or can also be executed by a chip or circuit configured in the second device. This application does not limit this.

[0040] The network capability exposure architecture includes a service application programmable interface API exposure function and an API scheduling function. The method is applied to a second device, which includes any one of a terminal device, a network device, a cloud device, a campus device or a private network device.

[0041] The method includes: sending a first call request to the API open function, the first call request is used to request calling a second API; receiving a second API set from the API scheduling function, the second API set is determined by the API scheduling function according to the second API.

[0042] The first API in this application can refer to the first aspect and will not be described in detail.

[0043] According to this technical solution, terminal devices, network devices, cloud devices, campus or private network devices can all act as callers to send call requests to the API open function in the network capability exposure architecture, requesting to call the published second API. Therefore, the network capability exposure architecture can realize the call of the terminal, network and cloud, and improve the user experience.

[0044] In combination with the third aspect, in a possible implementation, the network capability exposure architecture also includes an API repository function, and the method also includes: determining information of at least one first API, the first API being used to provide basic service functions, and sending a first registration request to the API repository function, the first registration request including information of the at least one first API.

[0045] In combination with the third aspect, in a possible implementation, when the second device is a network device, a cloud device, a campus device or a private network device, the first registration request is sent based on the HTTP protocol; when the first device is a terminal device, the first registration request is sent based on the control plane NAS protocol or the user plane GPT-U protocol.

[0046] In combination with the third aspect, in a possible implementation, the first registration request includes a first condition, where the first condition is a condition for using the at least one first API.

[0047] In combination with the third aspect, in a possible implementation, the network capability exposure architecture also includes a requirement mapping function, and the method also includes: sending a first functional requirement to the requirement mapping function, the requirement mapping function is used to determine a first API set based on the first functional requirement and send it to the API orchestration function, for the API orchestration function to combine the first API in the first API set to obtain the second API, the first API set is a set of first APIs provided by the first device set, the first API set includes the at least two first APIs provided by the second device set, and the devices in the second device set belong to the first device set.

[0048] In a fourth aspect, a communication device is provided. The device may be a first device, or may be a chip or circuit configured in the first device, or may be a logic module or software capable of implementing all or part of the first device. This application is not limited to this.

[0049] The first device includes any one of a terminal device, a network device, a cloud device, a campus device or a private network device.

[0050] The first device is any one of a first device set, and the first device set includes at least one of a terminal device, a network device, a cloud device, a campus device, or a private network device.

[0051] The device includes: a processing unit for determining information of at least one first API, where the first API is used to provide basic service functions; a transceiver unit for sending a first registration request to the API repository function, where the first registration request includes information of the at least one first API.

[0052] The first API and the first device in this application can refer to the first aspect and will not be described in detail.

[0053] According to this technical solution, terminal devices, network devices, cloud devices, campus or private network devices can all act as API providers to register their respective first APIs to the API repository function in the universal application programming interface framework. Therefore, the universal application programming interface framework can realize the terminal, network and cloud collaboration functions, support specific services and improve user experience.

[0054] In combination with the fourth aspect, in a possible implementation, the general application programming interface framework further includes an API open function, and the transceiver unit is further used to send a first call request to the API open function, where the first call request is used to request to call the second API.

[0055] In combination with the fourth aspect, in a possible implementation, when the first device is a cloud device, a campus device, or a private network device, the transceiver unit is also used to send the first registration request based on the HTTP protocol; when the first device is a terminal device, the transceiver unit is also used to send the first registration request based on the control plane NAS protocol or the user plane GPT-U protocol.

[0056] In combination with the fourth aspect, in a possible implementation, the first registration request includes a first condition, where the first condition is a condition for the first device to use the at least one first API.

[0057] In combination with the fourth aspect, in a possible implementation, the network capability exposure architecture also includes a demand mapping function, and the transceiver unit is also used to send a first functional requirement to the demand mapping function, and the demand mapping function is used to determine a first API set based on the first functional requirement and send it to the API orchestration function, so that the API orchestration function combines the first API in the first API set to obtain the second API, and the first API set includes the at least two first APIs provided by the second device set, and the devices in the second device set belong to the first device set.

[0058] A fifth aspect provides a communication device, which may be a second device, or a chip or circuit configured in the second device, or a logic module or software capable of implementing all or part of the second device. This application is not limited to this.

[0059] The network capability exposure architecture includes a service application programmable interface API exposure function and an API scheduling function, and the second device includes at least one of a terminal device, a network device, a cloud device, a campus device or a private network device.

[0060] The device includes: a transceiver unit for sending a first call request to the API open function, wherein the first call request is used to request calling a second API; the transceiver unit is also used to receive a second API set from the API scheduling function, wherein the second API set is determined by the API scheduling function according to the second API.

[0061] The first API in this application can refer to the first aspect and will not be described in detail.

[0062] According to this technical solution, terminal devices, network devices, cloud devices, campus or private network devices can all act as callers to send call requests to the API open function in the general application programming interface framework, requesting to call the published second API. Therefore, the general application programming interface framework can realize calls from the terminal, network, and cloud, and improve user experience.

[0063] In combination with the fifth aspect, in a possible implementation, the network capability exposure architecture also includes an API repository function, and the device also includes a processing unit for determining information of at least one first API, where the first API is used to provide basic service functions, and a transceiver unit for sending a first registration request to the API repository function, where the first registration request includes information of the at least one first API.

[0064] In combination with the fifth aspect, in a possible implementation, when the second device is a network device, a cloud device, a campus device or a private network device, the transceiver unit is also used to send the first registration request based on the HTTP protocol; when the first device is a terminal device, the transceiver unit is also used to send the first registration request based on the control plane NAS protocol or the user plane GPT-U protocol.

[0065] In combination with the fifth aspect, in a possible implementation, the first registration request includes a first condition, where the first condition is a condition for using the at least one first API.

[0066] In combination with the fifth aspect, in a possible implementation, the network capability exposure architecture also includes a demand mapping function, and the transceiver unit is also used to send a first functional requirement to the demand mapping function, and the demand mapping function is used to determine a first API set based on the first functional requirement and send it to the API orchestration function, so that the API orchestration function combines the first API in the first API set to obtain the second API, and the first API set includes the at least two first APIs provided by the second device set, and the devices in the second device set belong to the first device set.

[0067] In combination with the fifth aspect, in a possible implementation, the API orchestration function is used to combine at least two first APIs included in at least one first registration request from the first device set according to an operation policy to obtain the second API.

[0068] In a sixth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0069] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0070] In a seventh aspect, the present application provides a communication device, which includes: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute the method provided by any one of the above aspects or its implementation.

[0071] In an eighth aspect, the present application provides a computer-readable storage medium, which stores program code for execution by a device, and the program code includes a method for executing any of the above aspects or its implementation method.

[0072] In a ninth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method provided by any one of the above aspects or its implementation.

[0073] In the tenth aspect, the present application provides a chip, which includes a processor and a communication interface. The processor reads instructions stored in the memory through the communication interface and executes the method provided by any one of the above aspects or its implementation method.

[0074] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by any of the above aspects or its implementation methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] FIG1 shows a schematic diagram of a network architecture applicable to an embodiment of the present application.

[0076] FIG2 shows a schematic diagram of a general application programming interface framework applicable to an embodiment of the present application.

[0077] FIG3 shows a schematic diagram of a general application programming interface framework 300 applicable to an embodiment of the present application.

[0078] FIG4 shows a schematic block diagram of a communication system 400 based on a universal application programming interface framework 300 applicable to an embodiment of the present application.

[0079] FIG5 shows a schematic block diagram of a communication method 500 based on the universal application programming interface framework 300 applicable to an embodiment of the present application.

[0080] FIG6 shows a schematic block diagram of a communication method 600 based on the universal application programming interface framework 300 applicable to an embodiment of the present application.

[0081] FIG7 shows a schematic diagram of a communication device 700 provided in an embodiment of the present application.

[0082] FIG8 shows a schematic diagram of a communication device 800 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0083] The technical solution in this application will be described below with reference to the accompanying drawings.

[0084] The technical solutions provided in this application can be applied to various communication systems, such as 5G or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions provided in this application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0085] First, a communication system applicable to this application is briefly introduced as follows.

[0086] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of the present application. As shown in Figure 1, the network architecture may include user equipment 110, (wireless) access network equipment 120, user plane network element 130, data network 140, access management network element 150, session management network element 160, network exposure network element 170, policy control network element 180, and application network element 190. Each network element involved in the network architecture is described below.

[0087] 1. User equipment (UE) 110: User equipment may also be called a terminal, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. The terminal in the embodiments of the present application can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network or a terminal in a future evolution network, etc.

[0088] Wearable devices, also known as wearable smart devices, are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0089] 2. (Radio) access network (R)AN) 120: Access network equipment can also be called access equipment. (R)AN can manage radio resources, provide access services to user equipment, and complete the forwarding of user equipment data between user equipment and the core network. (R)AN can also be understood as a base station in the network.

[0090] Exemplarily, the access network device in the embodiment of the present application may be any communication device with wireless transceiver functions for communicating with user equipment. The access network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WiFi) system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., and can also be 5G, such as gNB in ​​NR system, or transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in 5G system, or it can also be a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc. It can be understood that all or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0091] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. RRC layer information is generated by the CU and ultimately encapsulated by the DU's PHY layer into PHY layer information, or is converted from PHY layer information. Therefore, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by a combination of the DU and the AAU. It is understood that the access network device may include one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as an access network device in an access network (RAN) or as an access network device in a core network (CN), and this application does not limit this.

[0092] 3. User plane network element 130: As the interface with the data network, it performs functions such as user plane data forwarding, session / flow-level billing statistics, and bandwidth limiting. This includes packet routing and forwarding, as well as quality of service (QoS) processing for user plane data.

[0093] In the long term evolution (LTE) communication system, the user plane network element may be a serving gateway user plane (SGW-U) or a packet data network gateway user plane (PGW-U) or a network element jointly provided by the SGW-U and PGW-U. In the 5G communication system, the user plane network element may be a user plane function (UPF) network element.

[0094] 4. Data network 140: provides, for example, operator services, Internet access, or third-party services, including servers that implement video source encoding and rendering.

[0095] In a 5G communication system, the data network may be a data network (DN).

[0096] 5. Access management network element 150: mainly used for mobility management and access management, and can be used to implement other functions of the mobility management entity (MME) in addition to session management, such as lawful interception and access authorization / authentication.

[0097] In LTE communication systems, this access management element can be an MME element. In 5G communication systems, this access management element can be an access and mobility management function (AMF), which mainly performs functions such as mobility management and access authentication / authorization. In addition, it is responsible for transmitting user policies between the terminal and the policy control function (PCF) element.

[0098] 6. Session management network element 160: mainly used for session management, Internet protocol (IP) address allocation and management of user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification.

[0099] In an LTE communication system, the session management network element may be a serving gateway control plane (SGW-C) or a packet data network gateway control plane (PGW-C), or a combined SGW-C and PGW-C network element. In a 5G communication system, the session management network element may be a session management function (SMF) network element, which performs terminal IP address allocation, UPF selection, and billing and QoS policy control.

[0100] 7. Network open network element 170: In an LTE communication system, this network open network element may be a service capability exposure function (SCEF) network element. In a 5G communication system, this network open network element may be a network element function (NEF) network element, which is primarily used to expose the services and capabilities of 3GPP network functions to the AF and also allows the AF to provide information to the 3GPP network functions.

[0101] 8. Policy control network element 180: includes user contract data management functions, policy control functions, billing policy control functions, quality of service (QoS) control, etc. It is used to guide the unified policy framework of network behavior and provide policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).

[0102] In an LTE communication system, the policy control network element may be a policy control and charging function (PCRF). In a 5G communication system, the policy control network element may be a PCF.

[0103] In a 5G communication system, the application network element may be a network slice selection function (NSSF) network element.

[0104] 9. Application network element 190: In the 5G communication system, the application network element can be an application function (AF) network element, which represents the application function of a third party or operator. It is the interface for the 5G network to obtain external application data and is mainly used to convey the requirements of the application side to the network side.

[0105] In future communication systems, such as 6G communication systems, the above-mentioned network elements or devices may still use their names in 4G or 5G communication systems, or may have other names, and this is not limited in the embodiments of the present application. The functions of the above-mentioned network elements or devices may be completed by an independent network element or by several network elements. In actual deployment, the network elements in the core network may be deployed on the same or different physical devices. For example, as a possible deployment, AMF and SMF may be deployed on the same physical device. For another example, the network elements of the 5G core network may be deployed on the same physical device as the network elements of the 4G core network. This is not limited in the embodiments of the present application.

[0106] It is understood that Figure 1 is only an example and does not limit the scope of protection of this application. The communication method provided in the embodiment of this application may also involve network elements not shown in Figure 1. Of course, the communication method provided in the embodiment of this application may also include only some of the network elements shown in Figure 1.

[0107] In the network architecture shown in Figure 1, the terminal connects to the AMF via the N1 interface, the (R)AN connects to the AMF via the N2 interface, and the (R)AN connects to the UPF via the N3 interface. UPFs are connected to each other via the N9 interface, and the UPFs are interconnected with the DN via the N6 interface. The SMF controls the UPFs via the N4 interface.

[0108] It can be understood that the above-mentioned network architecture applied to the embodiment of the present application is only an example, and the network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application.

[0109] Among them, the control plane network elements, such as AMF AMF, SMF, AUSF, PCF, etc., can provide different service APIs respectively and open them to AF calls through NEF (network exposure function).

[0110] The following describes the network capability exposure architecture provided by this application.

[0111] FIG2 shows a schematic diagram of a general application programming interface framework applicable to an embodiment of the present application.

[0112] As shown in Figure 2, the general application programming interface framework mainly includes API caller (API invoker), general application programming interface framework core function (CAPIF core function), API open function (API exposing function), API publishing function (API publishing function), API management function (API management function), etc.

[0113] Among them, the API invoker is usually provided by a third-party application provider that has a service agreement with the PLMN operator, such as an OTT (over the top) manufacturer.

[0114] The main functions of the CAPIF core function include: 1) authenticating the API caller; 2) controlling access to the service API according to the policies configured by the PLMN operator; 3) storing logs of service API calls; and 4) publishing and searching service API information.

[0115] The API exposing function serves as the service API provider and the entry point for communication between the service API and the API caller. Its main functions include: 1) authenticating the API caller based on the authentication information provided by the CAPIF core function; and 2) logging the service API call in the CAPIF core function.

[0116] The main function of the API publishing function is for the API provider to publish service API information so that API callers can discover the service API and publish the service API information to the CAPIF core function.

[0117] The API management function is mainly used to perform service API management. Its main functions include: 1) auditing the service API call logs received from the CAPIF core function; 2) monitoring the status of the service API; 3) configuring the API provider's policy to the CAPIF core function.

[0118] In the above-mentioned general application programming interface framework, it supports the integrated network (for example, control plane network elements) as the provider capability of the Service API, but does not support the integrated terminals (for example, 2C) and industry partners (for example, 2B / OTT) to provide Service APIs. It will not be able to support the end-network-cloud collaboration function proposed in future communications.

[0119] In addition, for 3rd-party apps that call network capabilities, service API functions are scattered and numerous, making it difficult for callers / developers to accurately distinguish the service functions of each service API. At the same time, each service API provides basic service functions, making it difficult to support specific businesses, such as the complex and diversified businesses in future network communications.

[0120] In summary, the existing general application programming interface framework cannot support business scenarios such as UE calling network capabilities, network calling UE capabilities, and end-network-cloud collaborative processing.

[0121] In view of this, the embodiments of the present application provide a communication system and a communication device based on a network capability open architecture. The end, network, and cloud can provide service APIs and realize the orchestration and combination of different service APIs. In addition, the end, network, and cloud can also act as callers to call the above APIs, thereby supporting complex services such as end-network-cloud collaboration.

[0122] The following describes a network capability exposure architecture provided by this application.

[0123] This network capability exposure architecture can be applied to the 6th generation system (6GS).

[0124] FIG3 is a schematic block diagram of a general application programming interface framework 300 provided in an embodiment of the present application.

[0125] This universal application programming interface framework defines a capability exposure platform that is common to end-network-cloud. This capability exposure platform mainly includes request mapping function, API orchestration function, API supervisor / monitoring function, API scheduler function, API repository function, API publish function, API exposure function, API security function, and API charge function.

[0126] The capability exposure platform can be one or more network function entities enhanced based on the NEF. For example, one of the above functions corresponds to one network function entity, or multiple functions correspond to one network function entity. When multiple functions correspond to one network function entity, the functions in the network function entity have the ability to exchange information.

[0127] The names of the above functional modules are only examples. This application does not limit the names of the functional modules. The functions of each functional module are described below.

[0128] Requirements mapping function: maps the caller's functional requirements into one or more basic API requirements, where the functional requirements may include indicators, parameters, etc.

[0129] In this application, the basic API can be an API that provides basic service functions. For example, the basic API that the network equipment can provide includes UE location, SMS verification, voice verification, data analysis, data compression, AI reasoning, etc.; the basic API that the UE can provide includes UE location, UE data sharing, data collection, computing services, etc.

[0130] It is worth noting that basic service functions are not limited to a single service and can also be a combination of multiple service functions. For example, assuming that the AMF can provide three service functions, such as access control, location acquisition, and communication, then there can be three corresponding basic APIs, one for the three service functions; or two basic APIs, one for the access control service and the other for the combination of the location acquisition and communication services. In other words, there is no strong correlation between the complexity of the basic API and the corresponding function.

[0131] API orchestration function: combines multiple basic APIs into an API that supports specific functional requirements. That is, the API orchestration function can combine multiple basic APIs that support basic service functions to obtain an API that can implement specific functions.

[0132] It should be noted that the API orchestration function orchestrates and combines multiple basic APIs. The multiple basic APIs can be basic APIs from a single provider / single device / single domain, or basic APIs from different providers / different devices / different domains.

[0133] For example, some or all of the multiple basic APIs may come from the UE, from a network device, or from a private network or campus device, and this embodiment of the present application does not limit this.

[0134] For example, the API orchestration function can combine the UE location, data analysis, and AI reasoning provided by network devices to obtain an API to meet the business needs of providing service acceleration for UEs in specific locations.

[0135] For example, the API orchestration function can combine the data analysis and data compression provided by network devices with the UE data sharing and computing services provided by the UE to meet the business needs of terminal-assisted network environment modeling.

[0136] In this application, the API orchestration function can combine multiple basic APIs according to business needs, or can combine multiple basic APIs based on operation strategies.

[0137] For example, basic APIs are combined based on historical records or domain experience knowledge to meet corresponding functional requirements.

[0138] API monitoring function: monitors the status of each basic API, including availability, performance, cost, etc.

[0139] In this application, the API monitoring function may obtain the status of the basic API by sending a status query request to the provider / device of the basic API, or the provider / device of each basic API may report the status to the API monitoring function periodically or based on an event trigger mechanism. This embodiment of the application is not limited to this.

[0140] API scheduling function: can perform real-time scheduling of basic APIs provided by various providers / devices.

[0141] The API scheduling function is also responsible for API optimization and reselection. Preselection refers to selecting the optimal provider when different providers offer the same basic API. This selection takes into account factors such as performance and billing. Reselection involves reselecting the provider of the basic API, taking into account issues such as changes in the basic API state and latency caused by UE mobility.

[0142] For example, the basic API that provides location functionality is initially provided by AMF1 and is then provided by AMF2 after the UE location changes.

[0143] For example, the basic API that provides rendering functionality is initially provided by the cloud and then provided by the network after the UE location changes.

[0144] For example, the basic API for data analysis is initially provided by the RAN. When congestion occurs in the RAN, it is switched to being provided by the core network element (such as NWDAF).

[0145] API repository function: also known as API management function, responsible for API registration and maintenance.

[0146] API publishing function: publish basic APIs or orchestrated APIs for callers (UE, network, APP, campus / private network) to call.

[0147] API open function: used to receive API call requests from callers.

[0148] The API open function can also be used to perform security authentication on the caller. After passing the security authentication, the API call request will be forwarded to the API scheduling function.

[0149] The API openness feature also allows you to configure a quota for each caller. If there's enough quota, the call is allowed to proceed and the request is forwarded to the API scheduling function. Otherwise, a rejection response is sent to the caller. The quota calculation model can include resource usage, usage duration, number of calls, and more.

[0150] API security function: Used to authenticate callers. API security function can be deployed together with API openness function or separately.

[0151] In this application, the caller can be a UE, network, APP, campus or private network device, etc., and the embodiments of this application do not limit this.

[0152] In this application, the caller may also be referred to as the user, and the embodiments of this application do not limit this.

[0153] It should be noted that the above functional modules can be independent modules, or can be combined in any way, or integrated into existing functional modules, without limitation.

[0154] It should be noted that the above functional modules are merely exemplary descriptions, and actual applications may include other functional modules, which are not limited in the embodiments of the present application.

[0155] The communication system provided in the embodiments of the present application is described below.

[0156] FIG4 is a schematic block diagram of a communication system 400 based on a universal application programming interface framework 300 provided in an embodiment of the present application.

[0157] In this application, the first device set includes at least one of a terminal device, a network device (e.g., RAN, AMF, UPF, etc.), a cloud device, and a campus or private network device. A cloud device can be a server or gateway in a public or private cloud; a network device can be a core network or access network device, such as RAN, AMF, UPF, etc.; a campus device can be a network device that serves users gathered in a limited geographic space. The campus also belongs to a private network, such as a server or gateway on a campus network or enterprise network; and a private network device can be understood as an intranet network device, such as a server or gateway on a local area network.

[0158] In this application, the first API can be used as an example of a basic API, and the first API is used to provide basic service functions.

[0159] This communication system includes API repository function and API orchestration function.

[0160] The API repository function is configured to receive at least one first registration request from a first set of devices.

[0161] The first registration request includes information of at least one first API provided by the first device.

[0162] The first device is any one in the first device set.

[0163] At least one first registration request from the first set of devices includes information of at least two first APIs.

[0164] For example, the first device set includes two devices, and each of the two devices sends a first registration request, and each registration request includes information of a first API.

[0165] For another example, the first device set includes one device, and the one device sends two first registration requests, each registration request including information of a first API.

[0166] For another example, the first device set includes two devices, one of which sends a first registration request, and the other device sends two first registration requests, each of which includes information about a first API.

[0167] For another example, the first device set includes one device, and the one device sends a first registration request, where the first registration request includes information of two first APIs.

[0168] Accordingly, the first device is used to determine information of at least one first API and send a first registration request to the API repository function.

[0169] In the present application, the interaction between the API repository function and the first device can be carried out through existing protocol specifications, and the embodiments of the present application are not limited to this.

[0170] The first device may be any one of a terminal device, a network device, a cloud device, a campus device or a private network device.

[0171] Exemplarily, when the first device is a cloud device, a device in a campus or a private network device, the API repository function receives the first registration request based on the hypertext transfer protocol (HTTP); when the first device is a terminal device, the API repository function receives the first registration request based on the control plane non-access stratum (NAS) protocol or the user plane part of GPRS tunneling protocol (GTP-U).

[0172] Optionally, the first registration request further includes a first condition, where the first condition is used to indicate a condition or specification for using the first API.

[0173] Exemplarily, for the first API provided by the terminal device, the first condition may be usage time, caller (specific authorized group users), unit price, etc. For example, the terminal device may provide the first API service in a fixed time period. For another example, only specific authorized users can use the first API. When the caller requests to call the first API, it needs to determine whether the condition is met based on the condition.

[0174] For example, for a first API provided by a campus or private network device, the first condition can be the service scope, that is, the caller is only allowed to use it when it is within the specific service scope. The first condition can also be the unit price. Different devices may have different prices when providing APIs with the same function.

[0175] For example, for the first API provided by APP / OTT, the first condition may be unit price, user level, or users in a specific area.

[0176] For example, to enhance profitability, OTT / APP can open some first-class APIs that improve user experience to users of a certain level or in a specific area.

[0177] The API orchestration function is used to combine at least two first APIs provided by the first device set to obtain a second API, wherein the second API is an API that can support a specific service function.

[0178] It should be noted that the first API provided by the first device set may include terminal devices, network devices, cloud devices, campus or private network devices as first APIs provided by different providers, or may include first APIs provided by different devices / entities of a single provider / domain, such as a location service API provided by an AMF set composed of multiple AMFs. This embodiment of the present application is not limited to this.

[0179] It should be noted that the API orchestration function can combine at least two first APIs provided by the second device set to obtain a second API, where the devices in the second device set belong to the first device set. In other words, the API orchestration function selects first APIs registered by the second device set from multiple first APIs registered by the first device set for combination; in other words, the first device set may include multiple devices, different devices may provide first APIs with the same functionality or different functionality, and the API orchestration function selects some or all of the multiple first APIs for combination, where these some or all of the first APIs are provided by some of the multiple devices (the second device set).

[0180] For example, device #1 registers API #1 corresponding to function #a and API #2 for function #c with the API repository function, device #2 registers API #3 for function #a and API #4 for function #b with the API repository function, and device #3 registers API #5 for function #b and API #6 for function #c with the API repository function. Device #1, device #2, and device #3 constitute a first device set. The API orchestration function needs to combine APIs with function #a, function #b, and function #c. The API orchestration function can select API #2 (with function #c) registered by device #1, API #3 (with function #a) registered by device #2, and API #4 (with function #b) registered by device #2 to obtain a second API. Then device #1 and device #2 constitute a second device set.

[0181] For example, an API with function #a uses the same API identifier on different devices. Function #a corresponds to API #1, function #b corresponds to API #2, and function #c corresponds to API #3. Device #1 registers API #1 for function #a and API #3 for function #c. Device #2 registers API #1 for function #a and API #2 for function #b. Device #3 registers API #2 for function #b and API #3 for function #c. Devices #1, #2, and #3 form a first device set. If the API orchestration function requires combining APIs with functions #a, #b, and #c, API #1, API #2, and API #3 are selected to form the second API. For example, the API orchestration function can select API#1 registered by device #1, API#2 registered by device #2, and API#3 registered by device #3, and then device #1, device #2, and device #3 constitute the second device set. For another example, the API orchestration function can select API#1 registered by device #2, API#2 registered by device #2, and API#3 registered by device #3, and then device #2 and device #3 constitute the second device set.

[0182] Among them, the API orchestration function or API scheduling function selects the API provided by the appropriate provider / device based on factors such as availability, performance, and cost.

[0183] In the present application, the API orchestration function may combine the first APIs provided by the first device set based on functional requirements, and may also combine the first APIs provided by the first device set in an offline state.

[0184] In a possible implementation, the system further includes a demand mapping function.

[0185] The requirement mapping function is used to receive a first functional requirement, determine a first API set according to the first functional requirement, and send the first API set to the API orchestration function. The API orchestration function is specifically used to combine all first APIs included in the first API set to obtain a second API.

[0186] The first API set includes at least two first APIs provided by the second device set.

[0187] Among them, the first functional requirement can be the caller's business demand indicator or requirement, etc., which is not limited in the embodiment of the present application.

[0188] The first API set includes multiple first APIs that match the first functional requirement.

[0189] The caller can be the first device or other devices, such as any terminal device, network device, cloud device, private network or campus device, etc., which is not limited in this embodiment of the present application.

[0190] Exemplarily, the first device sends a first functional requirement to the requirement mapping function.

[0191] Exemplarily, a second device sends a first functional requirement to a requirement mapping function, where the second device includes at least one of a terminal device, a network device, a cloud device, a campus device, or a private network device. The second device may or may not send a registration request to the API repository function. This embodiment of the present application is not limited to this.

[0192] For example, the API orchestration function may combine multiple basic APIs based on an operational strategy.

[0193] For example, in an offline state, the API orchestration function combines at least two first APIs provided by the first device set to obtain a second API based on historical records or domain experience knowledge.

[0194] An optional understanding is that the API orchestration function does not need to be triggered by actual business needs. It can determine, based on historical records, to combine the first API to obtain a second API with a higher call frequency; or, the API orchestration function can combine the first API based on domain experience and knowledge to obtain a second API that meets more needs.

[0195] In a possible implementation, the communication system may further include an API open function.

[0196] The API open function is used to receive a first call request, and the first call request is used to request to call a second API.

[0197] Correspondingly, the caller may send a first call request to the API open function to request to call the second API.

[0198] The caller may be the first device or the second device, which is not limited in this embodiment of the present application.

[0199] It should be understood that the second API is obtained by combining multiple first APIs, but for the caller, the second API opened to the caller through the API opening function is an independent API.

[0200] Optionally, the API open function is also used for security authentication.

[0201] When the API open function receives the first call request, it calls the security function to perform security authentication on the caller. After passing the security authentication, it forwards the first call request to the API scheduling function.

[0202] In addition, the API open function can also configure the caller's margin. If there is margin, the call is allowed to continue and the call request is forwarded to the API scheduling function; otherwise, a rejection response will be sent to the caller.

[0203] Among them, the calculation mode of the balance may include: resource usage, usage time, number of calls, etc., which is not limited in the embodiment of the present application.

[0204] In a possible implementation, the communication system may further include an API scheduling function.

[0205] The API open function is also used to map the second API into the first API set and send the first call request and the first API set to the API scheduling function; accordingly, after receiving the first call request and the first API set, the API scheduling function determines the second API set based on the first API set, and the second API set includes at least two first APIs provided by the third device set. The devices in the third device set belong to the first device set, and the second API set is the same as or different from the first API set.

[0206] The API open function may map the second API requested by the caller into a first API set, where the first API set includes at least two first APIs provided by the second device set, and the API scheduling function may determine the second API set based on the first API set.

[0207] In one possible implementation, the API scheduling function may redetermine at least two first APIs provided by a third device set to form a second API set based on multiple first APIs in the first API set, that is, the first API set and the second API set are different.

[0208] In a possible implementation, the API scheduling function determines that the second API set is composed of multiple first APIs in the first API set, that is, the first API set and the second API set are the same.

[0209] It is understood that the API scheduling function can be responsible for the optimization and reselection of APIs. That is, for multiple APIs in the first API set, considering factors such as the performance and billing of the multiple APIs, the API repository function reselects multiple APIs that can implement the functions of the multiple APIs. The reselected multiple APIs constitute the second API set, and the reselected multiple APIs are the APIs provided by the devices in the third device set. It should be understood that the multiple APIs in the first API set are provided for the devices in the second device set, and the devices in the second and third device sets all belong to the first device set.

[0210] It can be understood that when the API scheduling function re-selects multiple APIs that can implement the multiple API functions in the API repository function, multiple APIs in the first API set are still selected, or the API mobilization function defaults to multiple APIs in the first API set as the preferred APIs. In this case, the first API set and the second API set are the same.

[0211] For example, device #1 registers API #1 corresponding to function #a and API #2 for function #c, device #2 registers API #3 for function #a and API #4 for function #b, and device #3 registers API #5 for function #b and API #6 for function #c. The API orchestration function needs to combine APIs with functions #a, #b, and #c. The API orchestration function can select API #2 with function #c registered by device #1, API #3 with function #a registered by device #2, and API #5 with function #b registered by device #3 to obtain the second API. Then the first The API set includes API#2, API#3 and API#5, and the corresponding second device set includes device #1, device #2 and device #3; the API scheduling function can re-determine multiple first APIs to form the second API set based on factors such as performance and billing. For example, it is determined to use API#1 with function #a provided by device #1, API#5 with function #b provided by device #3, and API#6 with function #c provided by device #3, that is, the second API set includes API#1, API#5 and API#6, and the corresponding third device set includes device #1 and device #3.

[0212] For another example, function #a corresponds to API #1, function #b corresponds to API #2, and function #c corresponds to API #3. Device #1 registers API #1 corresponding to function #a and API #3 for function #c, device #2 registers API #1 for function #a and API #2 for function #b, and device #3 registers API #2 for function #b and API #3 for function #c. If the API orchestration function needs to combine APIs with functions #a, #b, and #c, the second API set includes API #1, API #2, and API #3. In this case, the second API set is the same as the first API set. The API scheduling function can select appropriate devices to provide API #1, API #2, and API #3 respectively. For example, the corresponding third device set includes device #1 (providing API #1 and API #3) and device #2 (providing API #2), or device #1 (providing API #1), device #2 (providing API #2), and device #3 (providing API #3), etc. It should be understood that when two APIs with the same function can be provided by different providers, they can be identified by different APIs or by the same API. For example, in the above example, function #a may correspond to API #1 of device #1 and API #3 of device #2, or correspond to API #1 in both device #1 and device #2. The embodiments of the present application are not limited to this.

[0213] The API scheduling function can determine which first API to call, that is, which device to execute the call request of the first API, in real time based on factors such as the performance and billing of APIs provided by different providers.

[0214] For example, the first API represents the rendering function, which can be provided by RAN#1, UPF#1, UPF#2, and the cloud. At time #1, the API scheduling function is determined to be provided by RAN1, and at time #2, the API scheduling function is determined to be provided by UPF#1.

[0215] The API dispatch function sends the second API set to the caller.

[0216] The caller may be the first device or the second device, which is not limited in this embodiment of the present application.

[0217] In a possible implementation, the communication system may further include an API monitoring function.

[0218] The API monitoring function is used to update the first API in the API repository function according to the status of at least one first API.

[0219] The first API provided by the first set of devices may undergo a state change, and the state change may include changes in factors such as availability, performance, and cost.

[0220] The API monitoring function has the ability to monitor the first API state change and update the first API in the API repository function.

[0221] Exemplarily, the API monitoring function may send a request message to the first device to query the status change.

[0222] Exemplarily, the first device may report status changes to the API monitoring function periodically or based on an event triggering mechanism.

[0223] The API monitoring function updates the first API in the API repository function according to each first API state change.

[0224] Optionally, the API scheduling function may also be used to determine a second API set according to a change in the first API state.

[0225] For example, when the availability of API #3 with function #a registered by device #2 is updated to unavailable, the API scheduling function may select API #1 with function #a registered by device #1.

[0226] For another example, API#1 is the location service provided by AMF#1. When the UE moves, the location service can be provided by API#3 provided by AMF#2.

[0227] This solution can improve user experience, save network operation and maintenance costs, and also reduce user usage costs.

[0228] In a possible implementation, the communication system may further include an API billing function.

[0229] The API billing function is used to calculate and calculate billing based on the actual number of API calls. It also includes a billing policy that matches the usage conditions set when the first API was registered. For example, it defines which callers are allowed to use the first API and generate billing records, and which callers are prohibited from using the first API.

[0230] It should be noted that in this application, terminal devices, network devices, cloud devices, campus or private network devices can all register and call the first API, so there is a two-way billing model, that is, any caller needs to pay the provider of the first API. For example, when the terminal device calls the first API provided by the network device, the terminal device needs to pay the network device; when the network device calls the first API provided by the terminal device, it also needs to pay the terminal device.

[0231] It should be noted that the above functional modules can be independent modules, or can be combined in any way, or integrated into existing functional modules, without limitation.

[0232] It should be noted that the above functional modules are merely exemplary descriptions, and actual applications may include other functional modules, which are not limited in the embodiments of the present application.

[0233] According to this technical solution, terminal devices, network devices, cloud devices, campus devices, or private network devices can all act as API providers and register their own basic APIs with the API repository function within the network capability exposure architecture. The API orchestration function within the network capability exposure architecture can then combine basic APIs from providers of the same or different types to create a secondary API, which can be invoked by the caller through the API exposure and API scheduling functions. This network capability exposure architecture can thus achieve device-network-cloud collaboration, support diverse services, and enhance user experience.

[0234] The following describes a communication method based on the universal application programming interface framework 300 provided in this application.

[0235] FIG5 is a schematic block diagram of a communication method 500 based on the general application programming interface framework 300 provided in an embodiment of the present application.

[0236] The method 500 may include the following steps:

[0237] S510: A first device set sends a first registration request to an API repository function.

[0238] In the present application, the first device set includes at least one of a terminal device, a network device, a cloud device, a campus device or a private network device.

[0239] The first registration request includes information of at least one first API, and the first registration request is used to register the information of the at least one first API with the API repository function.

[0240] It should be noted that the first device set may include at least two devices, and the at least two devices (API providers) may each send one or more first registration requests to register one or more first APIs for each of the multiple devices. The first device combination may also include a single device, which sends at least one first registration request to register at least two APIs of the device. This embodiment of the present application is not limited to this.

[0241] The first device set registers at least two first APIs.

[0242] In this application, the first API can be used as an example of a basic API. The first device can register one or more basic APIs with the API repository function, and each basic API provides basic service functions.

[0243] In this application, terminal devices, network devices, cloud devices, campus or private network devices can act as API providers and register their respective APIs with the API repository function. Terminal devices can be devices such as UE and tablets, network devices can be devices such as RAN, UPF, AMF, NWDAF, cloud devices can be edge application servers (EAS) or edge enabler servers (EES), and campus or private network devices can be devices such as campus gateways.

[0244] S520: The API orchestration function combines the first APIs provided by the first device set to obtain a second API.

[0245] It should be understood that the API orchestration function and the API repository can exchange information, so the API orchestration function can obtain at least two first APIs registered by the first device set through the API repository function.

[0246] The API orchestration function combines at least two first APIs to obtain a second API that can support a specific service function. The at least two first APIs registered by the first device set may come from different devices or from the same device, without limitation.

[0247] In a possible implementation, the API orchestration function may combine the first APIs online based on the functional requirements of the caller, including the following steps S511-S513.

[0248] S511: The caller sends a first functional requirement to the requirement mapping function.

[0249] The first functional requirement includes the caller's business demand indicators or requirements, etc.

[0250] For example, the first functional requirement may be to complete data analysis, compression, and storage within a specific delay (eg, 1 second).

[0251] The caller may be the first device or the second device, and the second device may be understood as a device that has not registered the basic API with the API repository function. This embodiment of the present application does not limit this.

[0252] S512 , the requirement mapping function converts the first functional requirement into a first API requirement.

[0253] It is understandable that the demand mapping function can select corresponding multiple first APIs according to specific indicators or requirements.

[0254] For example, the first functional requirement is mapped into three first APIs: data analysis API, data compression API, and data storage API.

[0255] The first functional requirement also includes specific indicators or parameters, for example, the delay requirement is 1s.

[0256] S513: The requirement mapping function sends the first functional requirement and the first API requirement to the API orchestration function.

[0257] For example, analytics APIs, data compression APIs, data storage APIs, and latency requirements are sent to the API orchestration function.

[0258] It should be understood that the above steps S511-S513 are optional steps.

[0259] S520: The API orchestration function combines at least two first APIs to obtain a second API.

[0260] In a possible implementation, the API orchestration function may combine at least two first APIs to obtain a second API according to the first functional requirement and the first API requirement.

[0261] For example, when the latency is 1 second, the API orchestration function determines that the data analysis API, data compression API, and data storage API are provided by RAN and UPF; when the latency is 5 seconds, the API orchestration function determines that the data analysis API, data compression API, and data storage API are provided by UPF and cloud devices.

[0262] In another possible implementation, the API orchestration function may combine the first APIs according to the operation policy in an offline state to obtain the second API.

[0263] For example, for video content, video compression can be combined with QoS guarantee functions, and a second API can be opened to the outside world for users to call.

[0264] S521 , the requirement mapping function converts the second API into a caller-friendly description.

[0265] It should be understood that the demand mapping function and the API orchestration function can exchange information, so the demand mapping function can obtain the second API from the API orchestration function.

[0266] Considering that API providers belong to different fields and use different description languages ​​for APIs, the parameters contained in the orchestrated second API need to be standardized according to certain strategies.

[0267] For example, parameters related to location are uniformly converted into cities / districts or longitude and latitude, and parameters related to data storage and processing are uniformly encoded using the same coding method.

[0268] For another example, different descriptions are provided for different callers to adapt to differentiated needs.

[0269] The second API after the conversion description is saved in the API repository function.

[0270] This step S521 is an optional step.

[0271] S530: The API repository function publishes the second API through the API publishing function.

[0272] The API repository function publishes the second API after the conversion description through the API publishing function for the caller to call.

[0273] S540a: The first device sends first API status information to the API monitoring function.

[0274] The API monitoring function can monitor the status of the first API provided by the first device set.

[0275] The status information of the first API includes the availability, performance, cost, etc. of the first API.

[0276] For example, at time #1, the rendering API is available only in Region #1 for UE #1 and only in Region #2 for UE #2, at a price of X yuan / minute. NWDAF is available globally at a price of Y yuan / minute, and Cloud Device #1 is available in Regions #2 and #3 at a price of Z yuan / minute. However, at time #2, UE #1 is no longer available, and Cloud Device #1 may offer it at a price of M yuan / minute.

[0277] In a possible implementation, the devices in the first device set may send the first API status information to the API monitoring function periodically or based on an event trigger.

[0278] In another possible implementation, the API monitoring function may send a first API status request to the devices in the first device set, and the devices in the first device set may feed back first API status information to the API monitoring function.

[0279] S540b, the API monitoring function sends a first API status update message to the API repository function.

[0280] The API repository function updates the status of the first API in the API repository according to the first API status update message.

[0281] For example, if the performance of the first API #1 changes, the performance parameters of the first API #1 are modified.

[0282] It should be understood that the embodiment of the present application does not limit the execution timing of steps S540a and S540b.

[0283] For example, steps S540a and S540b may be performed after S510, that is, after the first device registers one or more first APIs with the API repository function, the registered one or more first APIs may be monitored in real time and the API repository function may be updated.

[0284] For another example, steps S540a and S540b may be performed after S550, that is, after the caller sends the first call request to the API open function, the caller may monitor the registered one or more first APIs in real time and update the API repository function.

[0285] According to this technical solution, terminal devices, network devices, cloud devices, campus or private network devices can all act as API providers to register their respective basic APIs to the API repository function in the network capability exposure architecture. The API orchestration function can combine the basic APIs provided by providers of the same or different types to obtain a second API based on the caller's functional requirements, or combine the basic APIs provided by providers of the same or different types according to the operation strategy in an offline state to obtain a second API, and publish the second API through the API publishing function. This solution can realize the terminal, network and cloud collaborative functions by combining at least two basic APIs to obtain a second API, support diversified services, and be suitable for more complex scenarios or specific scenarios.

[0286] The above steps are the process of composing and publishing the second API. The following describes the process of calling the second API.

[0287] FIG6 is a schematic block diagram of a communication method 600 based on the general application programming interface framework 300 provided in an embodiment of the present application.

[0288] The method 600 may include the following steps:

[0289] The caller can request to call the second API through the API opening function.

[0290] S610a, the caller sends a first call request to the API open function.

[0291] The first call request includes a second API.

[0292] The first call request is used to request to call the second API published by the API publishing function.

[0293] It should be understood that any terminal device, network device, cloud device, private network or campus device can act as a caller to send a first call request to the API open function.

[0294] S610b: The API open function maps the second API called by the first call request into a first API set.

[0295] The second API requested to be called in the first call request is a combination of multiple basic APIs, that is, a first API set.

[0296] The first API set includes a plurality of basic APIs provided by the second device set.

[0297] Optionally, the API open function can also perform security authentication on the caller.

[0298] It should be understood that different types of callers may correspond to different security authentication methods, and the security authentication methods may include: signing, configuration, etc.

[0299] For example, for the authentication of the terminal device, the contract information may be used, while for the APP call, the configuration data may be used. The embodiments of the present application do not limit this.

[0300] In addition, different callers may call the API in different ways or use different protocols.

[0301] For example, the APP uses the hypertext transfer protocol (HTTP) / service-based interface (SBI); the terminal device may use the control plane / user plane interface, which is not limited in the embodiments of the present application.

[0302] Optionally, the API open function can also perform balance authentication on the caller. The balance calculation mode may include: resource usage, usage time, number of calls, etc., which is not limited in this embodiment of the application.

[0303] The API open function can configure the caller's margin. If there is margin, the call is allowed to continue; otherwise, a rejection response will be sent to the caller.

[0304] S610c: The API open function sends a scheduling request to the API scheduling function.

[0305] The scheduling request is used to request the API calling function to schedule the first API included in the first API set.

[0306] The following step S620 is a process in which the caller requests the API scheduling function to call the second API.

[0307] S620: The caller sends a first call request to the API scheduling function.

[0308] The API scheduling function may determine a first API set that needs to be called according to the first call request.

[0309] In this manner, the API scheduling function can also map the second API requested to be called into the first API set.

[0310] The API dispatch function can also dispatch the API security function to perform security authentication on the caller.

[0311] S630: The API scheduling function determines a second API set according to the first API set.

[0312] In a possible implementation, the API scheduling function may determine to use multiple first APIs in the first API set as the second API set.

[0313] In another possible implementation, the API scheduling function may redetermine multiple first APIs according to functions of multiple first APIs in the first API set to form a second API set, where the second API set includes basic APIs provided by the third device set.

[0314] It should be understood that the functions of the basic APIs included in the second API set and the first API set are the same, but the corresponding partial or complete providers are different, that is, the APIs in the first API set are provided by the devices in the second device set, and the APIs in the second API set are provided by the devices in the third device set, and the devices in the second device set and the devices in the third device set are partially or completely different.

[0315] Optionally, the API scheduling function can optimize multiple first APIs in the first API set. For example, the optimal first API can be selected from multiple first APIs with the same function based on factors such as performance or billing. The optimal first API has the same function as the first API in the original first API set, but the provider may be different.

[0316] Optionally, steps S630a and S630b are performed. Detailed descriptions may be made of S530a and S530b in method 500 and will not be repeated here.

[0317] The API scheduling function can reselect multiple first APIs based on the updated APIs monitored in real time by the API monitoring function. For example, if the API monitoring function detects that the availability of the first API for the data sharing function is updated to unavailable, the API scheduling function will reselect the first API that can provide the data sharing function.

[0318] S640: The API scheduling function calls the second API set.

[0319] The API dispatching function calls a plurality of first APIs in the second API set.

[0320] Optionally, the API scheduling function can also count API call messages and report them to the API security function and API billing function.

[0321] According to this technical solution, terminal devices, network devices, cloud devices, campus devices, or private network devices can all act as callers to request the invocation of a second API published by the API publishing function. The API scheduling function can combine the status of the basic APIs updated in real time by the API monitoring function to optimize or reselect the basic APIs, thereby determining the second set of APIs as the callable API set. This solution enables terminal devices, network devices, cloud devices, campus devices, or private network devices to act as callers to call APIs based on specific needs, and further determines the optimal basic API combination through the API scheduling and API monitoring functions, thereby improving the user experience.

[0322] FIG7 shows a schematic diagram of a communication device 700 provided in an embodiment of the present application.

[0323] The device 700 includes a transceiver unit 710, which can be used to implement corresponding communication functions. The transceiver unit 7210 can also be called a communication interface or a communication unit.

[0324] The apparatus 700 may further include a processing unit 720 , which may be configured to perform data processing.

[0325] Optionally, the device 700 also includes a storage unit, which can be used to store instructions and / or data. The processing unit 720 can read the instructions and / or data in the storage unit so that the device can implement the actions of different devices in the aforementioned method embodiments.

[0326] As a design, the apparatus 700 is used to execute the actions performed by the first device in each of the above method embodiments.

[0327] Specifically, the processing unit 720 is used to determine the information of at least one first API, where the first API is used to provide basic service functions. The transceiver unit 710 is used to send a first registration request to the API repository function, where the first registration request includes the information of the at least one first API.

[0328] As a design, the apparatus 700 is used to execute the actions performed by the second device in each of the above method embodiments.

[0329] Specifically, the transceiver unit 710 is used to send a first call request to the API open function, and the first call request is used to request to call the second API; the transceiver unit 710 is also used to receive a second API set from the API scheduling function, and the second API set is determined by the API scheduling function according to the second API.

[0330] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0331] It should also be understood that the device 700 here is embodied in the form of a functional unit. The term "unit" here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 700 can be specifically a network device in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the network device in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

[0332] The apparatus 700 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the device in the above-mentioned method, or the apparatus 700 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the network device in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0333] In addition, the transceiver unit 710 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0334] It should be noted that the device in Figure 700 can be a network element or device in the aforementioned embodiment, or it can be a chip or chip system, such as a system on chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0335] Figure 8 shows a schematic diagram of a communication device 800 provided in an embodiment of the present application. The device 800 includes a processor 810, which is coupled to a memory 820. The memory 820 is used to store computer programs or instructions and / or data. The processor 810 is used to execute the computer programs or instructions stored in the memory 820, or read the data stored in the memory 820 to execute the methods in the above method embodiments. As shown in Figure 8, the device 800 also includes a transceiver 830, which is used to receive and / or send signals. For example, the processor 810 is used to control the transceiver 830 to receive and / or send signals.

[0336] Optionally, there are one or more processors 810 .

[0337] Optionally, there are one or more memories 820 .

[0338] It should be understood that the processor 810 and memory 820 described above can be combined into a single processing device, with the processor 810 configured to execute program code stored in the memory 820 to implement the aforementioned functions. In a specific implementation, the memory 820 can also be integrated into the processor 810 or independent of the processor 810. It should be understood that the processor 810 can also correspond to the various processing units in the aforementioned communication device, and the transceiver 830 can correspond to the various receiving units and transmitting units in the aforementioned communication device.

[0339] It should also be understood that the transceiver 830 may include a receiver (or receiver) and a transmitter (or transmitter). The transceiver may further include an antenna, and the number of antennas may be one or more. The transceiver may also be a communication interface or interface circuit.

[0340] Specifically, the communication device 800 may correspond to the terminal device in methods 500 to 600 according to the embodiments of the present application. The communication device 800 may include the units of the methods executed by the caller (first device or second device) in methods 500 and 600. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.

[0341] When the communication device 800 is a chip, the chip includes an interface unit and a processing unit, wherein the interface unit may be an input / output circuit or a communication interface; and the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip.

[0342] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0343] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0344] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0345] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0346] The present application also provides a computer-readable medium having a computer program stored thereon, which implements the functions of any of the above method embodiments when executed by a computer.

[0347] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0348] The present application also provides a system, which includes the aforementioned first device, second device and network capability exposure architecture.

[0349] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0350] In the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete way.

[0351] It should be understood that references to "embodiments" throughout this specification mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0352] It should be understood that in the various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The names of all nodes and messages in this application are merely names set by this application for the convenience of description. The names in the actual network may be different. It should not be understood that this application limits the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as the method or equivalent replacement of this application, and is within the scope of protection of this application.

[0353] It should also be understood that in this application, "when", "if" and "if" all mean that the UE or base station will take corresponding measures under certain objective circumstances. It does not limit the time, and does not require the UE or base station to take judgment actions when implementing it, nor does it mean that there are other limitations.

[0354] It should be noted that in the embodiments of the present application, "pre-setting", "pre-configuration", etc. can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, a terminal device). This application does not limit its specific implementation method, such as the preset rules, preset constants, etc. in the embodiments of the present application.

[0355] Additionally, the terms "system" and "network" are often used interchangeably. The term "and / or" is simply used to describe an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone.

[0356] As used herein, the term "at least one of" or "at least one of" refers to all or any combination of the listed items. For example, "at least one of A, B, and C" can mean: A alone, B alone, C alone, A and B together, B and C together, and A, B, and C together. As used herein, "at least one" means one or more. "A plurality" means two or more.

[0357] It should be understood that in the various embodiments of the present application, "B corresponding to A" means that B is associated with A and can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. The terms "include," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0358] It should be understood that in various embodiments of the present application, the first, second, and various numerical numbers are merely distinctions for ease of description and are not intended to limit the scope of the embodiments of the present application.

[0359] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0360] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0361] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0362] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0363] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0364] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0365] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication system based on a network capability open architecture, characterized in that: Includes API repository and API orchestration functions; The API repository function is used to receive at least one first registration request from a first device set, the first registration request includes information of at least one first API provided by a first device, the first device is any one of the first device set, the first API is used to provide a basic service function, the first device set includes at least one of a terminal device, a network device, a cloud device, a campus device or a private network device, and the at least one first registration request from the first device set includes information of at least two first APIs; The API orchestration function is used to combine the at least two first APIs to obtain a second API.

2. The system according to claim 1, characterized in that The system also includes an API open function, where the API open function is used to receive a first call request, where the first call request is used to request to call the second API.

3. The system according to claim 1 or 2, characterized in that: The system also includes an API publishing function, and the API publishing function is used to publish the second API.

4. The system according to any one of claims 1 to 3, characterized in that: When the first device is a cloud device, a campus device or a private network device, the API repository function receives the first registration request based on the Hypertext Transfer Protocol HTTP; when the first device is a terminal device, the API repository function receives the first registration request based on the control plane non-access layer NAS protocol or the user plane GPRS tunnel protocol GTP-U.

5. The system according to any one of claims 1 to 4, characterized in that: The first registration request includes a first condition, where the first condition is a condition for using the at least one first API.

6. The system according to any one of claims 1 to 5, characterized in that: The system further comprises a requirement mapping function, the requirement mapping function being configured to receive a first functional requirement; The requirement mapping function is further used to determine a first API set according to the first functional requirement and send the first API set to the API orchestration function, wherein the first API set includes the at least two first APIs provided by a second device set, and the devices in the second device set belong to the first device set; The API orchestration function is used to combine the at least two first APIs in the first API set to obtain the second API.

7. The system according to any one of claims 1 to 5, characterized in that: The API orchestration function is used to combine at least two first APIs included in at least one first registration request from the first device set according to an operation policy to obtain the second API.

8. The system according to any one of claims 1 to 7, characterized in that: The system also includes an API scheduling function; The API open function is further used to map the second API into the first API set, and send the first call request and the first API set to the API scheduling function; The API scheduling function is used to determine a second API set based on the first API set, the second API set includes the at least two first APIs provided by a third device set, the devices in the third device set belong to the first device set, and the second API set is the same as or different from the first API set.

9. The system according to claim 8, characterized in that The API open function is also used for security authentication.

10. The system according to claim 8 or 9, characterized in that The system also includes API monitoring capabilities, The API monitoring function is used to update the first API in the API repository function according to the status of at least one of the first APIs; The API scheduling function is used to determine the second API set according to the state of the at least one first API and the first API set.

11. A communication device, characterized in that: The communication device is used to execute the method executed in the communication system according to any one of claims 1 to 10.

12. A communication device, characterized in that: include: A processor, configured to execute a computer program stored in a memory, so that the apparatus executes the method performed in the communication system according to any one of claims 1 to 10.

13. The device according to claim 12, characterized in that The apparatus also includes the memory.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is enabled to execute the method executed in the communication system according to any one of claims 1 to 10.

15. A computer program product, characterized in that The computer program product comprises instructions for executing the method performed in the communication system of any one of claims 1 to 10.

16. A chip system, characterized in that: include: A processor, used to call and run a computer program from a memory, so that a communication device equipped with the chip system executes the method executed in the communication system according to any one of claims 1 to 10.

Images