Method and apparatus for providing service api

Abstract

Disclosed in the present application are a method and apparatus for providing a service API. The method is applied to a first functional entity. The method comprises: receiving a first request from a first API invoker, wherein the first request comprises at least one piece of parameter information to be met by a first service API that the first API invoker makes a request to invoke; and sending a first notification to the first API invoker, wherein the first notification is used for indicating that the first service API can be invoked, and the first service API is obtained by means of filling a preset service API generation framework template with the at least one piece of parameter information. In the embodiments of the present application, a first functional entity can obtain a first service API on the basis of requirements of a first API invoker, such that incompatibility does not occur when the first API invoker invokes the first service API, thereby improving the efficiency of the first API invoker in invoking the first service API.

Description

A method and device for providing a service API

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on December 22, 2023, with application number 202311795752.7 and invention name "A method and device for providing a service API", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a method and device for providing a service API. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) defines specifications for various northbound application programming interfaces (APIs). To avoid duplication and inconsistencies between API specifications, 3GPP is considering developing a common API framework (CAPIF) that would include common features applicable to all northbound APIs. CAPIF is typically deployed within carrier networks.

[0005] Currently, in CAPIF, API invokers are typically operator management systems (such as operations, administration, and maintenance (OAM) systems) or application systems. The protocols used by API invokers are compatible with the protocols provided by the operator for managing service APIs. API invokers can discover service APIs through the CAPIF core function entity and invoke service APIs through the API exposing function (AEF) entity.

[0006] However, the above calling process does not take into account the situation where the protocol applied by the API caller is incompatible with the protocol provided by the operator for managing the service API. For example, if the API caller is a third-party management system (such as a third-party OAM system) or a third-party application system, the API caller may encounter incompatibility when calling the service API. The API caller needs to convert the service API (such as converting the underlying protocol or underlying language of the service API) before calling the service API, resulting in low efficiency of the API caller in calling the service API. Summary of the Invention

[0007] The embodiments of the present application provide a method and device for providing a service API, which are used to improve the efficiency of API callers in calling the service API.

[0008] In the first aspect, an embodiment of the present application provides a method for providing a service API, which can be applied to a first functional entity or a chip in the first functional entity. Taking the application of the method to the first functional entity as an example, the method includes: the first functional entity can receive a first request from a first API caller, and the first request includes at least one parameter information that needs to be satisfied by the first service API requested to be called by the first API caller; the first functional entity can send a first notification to the first API caller, and the first notification is used to indicate that the first service API can be called, and the first service API is obtained by filling the at least one parameter information into a preset service API generation framework template.

[0009] In the implementation of this application, the first API caller can send at least one parameter information that the first service API needs to meet to the first functional entity. The first functional entity can obtain the first service API based on the needs of the first API caller, so that the first API caller will not encounter any incompatibility when calling the first service API, thereby improving the efficiency of the first API caller in calling the first service API.

[0010] In a possible implementation, the first request further includes a first parameter template, the at least one parameter information is carried in the first parameter template, and the first parameter template is sent by the first functional entity to the first API caller.

[0011] In this embodiment, the first API caller can fill at least one parameter information into the first parameter template in sequence and send it to the first functional entity, so that the first functional entity can quickly fill at least one parameter information in the first parameter template into the preset service API generation framework template to obtain the first service API, thereby improving the efficiency of the first functional entity in obtaining the first service API.

[0012] In a possible implementation, the first functional entity may also receive a second request from the first API caller, where the second request is used to request the first functional entity to provide the first parameter template, and the second request includes a first template identifier for indicating the first parameter template.

[0013] In this embodiment, the first functional entity can send the first parameter template to the first API caller only when receiving the second request from the first API caller, and the first functional entity can quickly determine the first parameter template through the first template identifier included in the second request, thereby improving transmission efficiency.

[0014] In one possible implementation, the first functional entity may also send a third request to the second functional entity, where the second functional entity is used to store at least one parameter template, and the third request is used to request the second functional entity to provide the first parameter template, and the third request includes a first template identifier for indicating the first parameter template; the first functional entity may also receive the first parameter template from the second functional entity.

[0015] This embodiment provides a method for a first functional entity to obtain a first parameter template, for example, by obtaining the first parameter template from a second functional entity that stores multiple parameter templates. Furthermore, the second functional entity can quickly determine the first parameter template based on the first template identifier included in the third request, thereby improving transmission efficiency.

[0016] In one possible implementation, the first request also includes one or more of the following: an identifier of the first API caller; a name of the first service API; a time of calling the first service API; information indicating that a second API caller other than the first API caller is allowed to call the first service API; and information indicating at least one API caller that is allowed to call the first service API.

[0017] In this implementation, the first functional entity can obtain the first service API through one or more items of information included in the first request, thereby improving the efficiency of the first functional entity in obtaining the first service API.

[0018] In a possible implementation, the first functional entity may also send a fourth request to the second functional entity, where the second functional entity is used to store the service API generation framework template, and the fourth request is used to request the second functional entity to provide the service API generation framework template; the first functional entity may also receive the service API generation framework template from the second functional entity.

[0019] In this embodiment, a method for the first functional entity to obtain the service API generation framework template is provided, for example, obtaining the service API generation framework template from the second functional entity that stores the service API generation framework template.

[0020] In a possible implementation, the first functional entity may also send a fifth request to the third functional entity, where the third functional entity is used to publish a service API, and the fifth request is used to request the publication of the first service API, and the fifth request includes information for indicating the acquisition of the first service API.

[0021] In this embodiment, a method for the first functional entity to publish the first service API is provided. For example, the first functional entity can publish the first service API through a third functional entity, so that the first API caller can call the first service API.

[0022] In a possible implementation, the information for indicating the acquisition of the first service API includes one or more of the following: an identifier of the first service API, the identifier of the first service API being allocated by the first functional entity; and an acquisition path of the first service API.

[0023] In this embodiment, multiple implementation methods are provided for indicating the information for obtaining the first service API, so that the method for the first functional entity to indicate the information for obtaining the first service API is more flexible, and accordingly, the method for the terminal device to obtain the first service API is also more flexible.

[0024] In a possible implementation, the fifth request further includes one or more of the following: a version of the first service API; a time of calling the first service API; and information indicating at least one API caller that is allowed to call the first service API.

[0025] In this embodiment, the third functional entity can determine the time to publish the first service API based on the time at which the first service API is called, allowing the first API caller to call the first service API at the time the first API caller needs to call the first service API, thereby improving the efficiency of the first API caller in calling the service API. Furthermore, when publishing the first service API, the third functional entity can publish information about at least one API caller that will be allowed to call the first service API, thereby ensuring that the first API caller has permission to call the first service API, thereby improving the efficiency of the first API caller in calling the service API.

[0026] In a possible implementation manner, the first notification includes one or more of the following: a name of the first service API; an identifier of the first service API, where the identifier of the first service API is allocated by the first functional entity.

[0027] In this embodiment, when the first API caller receives the first notification from the first functional entity, it can quickly determine that the first notification indicates that the first service API can be called through the name and / or identifier of the first service API included in the first notification, thereby improving transmission efficiency.

[0028] In a possible implementation, the first functional entity is deployed in a management domain of the communication system; or, the first functional entity is deployed outside the management domain of the communication system, and the first functional entity can communicate with a management functional entity in the management domain.

[0029] In this embodiment, two deployment modes of the first functional entity are provided. For example, the first functional entity can be deployed in the management domain of the communication system, or the first functional entity is deployed at a location outside the management domain of the communication system, and the first functional entity can communicate with the management functional entities in the management domain.

[0030] In the second aspect, an embodiment of the present application also provides a method for providing a service API, which can be applied to a first API caller or a chip in the first API caller. Taking the application of this method to the first API caller as an example, the method includes: the first API caller can send a first request to a first functional entity, and the first request includes at least one parameter information that needs to be satisfied by the first service API requested to be called by the first API caller; the first API caller can receive a first notification from the first functional entity, and the first notification is used to indicate that the first service API can be called, and the first service API is obtained by filling the at least one parameter information into a preset service API generation framework template.

[0031] In a possible implementation, the first request further includes a first parameter template, the at least one parameter information is carried in the first parameter template, and the first parameter template is sent by the first functional entity to the first API caller.

[0032] In a possible implementation, the first API caller may send a second request to the first functional entity, where the second request is used to request the first functional entity to provide the first parameter template, and the second request includes a first template identifier for indicating the first parameter template.

[0033] In one possible implementation, the first request also includes one or more of the following: an identifier of the first API caller; a name of the first service API; a time of calling the first service API; information indicating that a second API caller other than the first API caller is allowed to call the first service API; and information indicating at least one API caller that is allowed to call the first service API.

[0034] In a possible implementation manner, the first notification includes one or more of the following: a name of the first service API; an identifier of the first service API, where the identifier of the first service API is allocated by the first functional entity.

[0035] In a possible implementation, the method further includes: the first API caller may send a sixth request to a fourth functional entity, the fourth functional entity being used to open a service API, the sixth request being used to request a call to the first service API, the sixth request including an identifier of the first API caller.

[0036] The beneficial effects of the above-mentioned second aspect and its possible embodiments can refer to the above-mentioned description of the beneficial effects of the method described in the first aspect and any possible embodiment thereof.

[0037] In a third aspect, embodiments of the present application further provide a communication device comprising a processor and a memory; the memory is configured to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory to cause the device to perform any of the implementation methods described in the first or second aspects above. The memory can be volatile or non-volatile memory, such as a cache memory in a semiconductor chip.

[0038] In a fourth aspect, embodiments of the present application further provide a communication device, which may be a first API caller or a chip for the first API caller. The device has the function of implementing any of the implementation methods described in the first or second aspects above. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0039] In a fifth aspect, an embodiment of the present application further provides a communication device, comprising a unit or means for executing each step of any implementation method in the first aspect or the second aspect above.

[0040] In a sixth aspect, an embodiment of the present application further provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and execute any implementation method of the first or second aspect described above. The processor may be one or more processors.

[0041] In a seventh aspect, an embodiment of the present application further provides a communication device, comprising a processor coupled to a memory, the processor configured to call a program stored in the memory to execute any of the implementation methods of the first or second aspects described above. The memory may be located within or outside the device. The processor may also be one or more processors.

[0042] In an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when run on a communication device, enables any implementation method in the above-mentioned first aspect or second aspect to be executed.

[0043] In the ninth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run by a communication device, any implementation method in the above-mentioned first aspect or second aspect is executed.

[0044] In the tenth aspect, an embodiment of the present application also provides a chip system, including: a processor, used to execute any implementation method in the above-mentioned first aspect or second aspect.

[0045] In the eleventh aspect, an embodiment of the present application also provides a communication system, which includes: a first functional entity, used to execute any implementation method executed by the first functional entity in the above-mentioned first aspect or second aspect; a first API caller, used to execute any implementation method executed by the first API caller in the above-mentioned first aspect or second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] FIG1 is a schematic diagram of a CAPIF network architecture;

[0047] FIG2 is a flow chart of a method for calling a service API;

[0048] FIG3 is a schematic diagram of a network architecture of a communication system;

[0049] FIG4 is a schematic diagram of a network architecture of another communication system;

[0050] FIG5 is a flow chart of a method for providing a service API;

[0051] FIG6 is a flow chart of another method for providing a service API;

[0052] FIG7 is a flow chart of a communication device 700;

[0053] FIG8 is a schematic diagram of a flow chart of a communication device 800 . DETAILED DESCRIPTION

[0054] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

[0055] In the embodiments of this application, "when," "if," and "if" all indicate that the device will perform a corresponding action under certain objective circumstances. They do not limit the time, do not require the device to perform a judgment action when implemented, and do not imply any other limitations. Unless otherwise specified, "if" and "if" are interchangeable, and "when" and "under the circumstances" are interchangeable. "When" and "if" are interchangeable.

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

[0057] In this document, “used to indicate” can include being used for direct indication and being used for indirect indication. For example, when describing that a certain indication information is used to indicate information I, it can include that the indication information directly indicates I or indirectly indicates I, but it does not mean that the indication information must carry I.

[0058] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, it is also possible to use the arrangement order of each piece of information agreed in advance (such as specified in the protocol) to achieve the indication of specific information, thereby reducing the indication overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and indicate them uniformly to reduce the indication overhead caused by indicating the same information separately.

[0059] In addition, the specific indication method can also be various existing indication methods, such as but not limited to the above-mentioned indication methods and various combinations thereof. The specific details of the various indication methods can be referred to the prior art and will not be repeated herein. As can be seen from the above, for example, when it is necessary to indicate multiple information of the same type, there may be a situation where the indication methods for different information are different. In the specific implementation process, the required indication method can be selected according to specific needs. The embodiment of the present application does not limit the selected indication method. In this way, the indication method involved in the embodiment of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the information to be indicated.

[0060] In the embodiments of the present application, "sending" and "receiving" indicate the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, which can include direct sending through the air interface, and indirect sending through the air interface by other units or modules. "Receiving information from YY" can be understood as the source of the information being YY, which can include direct receiving from YY through the air interface, and indirect receiving from YY through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.

[0061] In other words, sending and receiving can be performed between devices, for example, between the first API caller and the first functional entity, or can be performed within the device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, trace or interface.

[0062] It is understandable that information may be processed between the source and destination of information transmission, such as coding, modulation, etc., but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated.

[0063] In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. For example, A / B means: A or B. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

[0064] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of multiple objects. For example, the first request and the second request refer to two different requests, and do not indicate the difference in content, priority or importance of the two requests. For a technical feature, "A", "B", "C" and "D" are used to distinguish the technical features in the technical feature. There is no order of precedence or size between the technical features described by "A", "B", "C" and "D".

[0065] The following first introduces the relevant technical solutions involved in the embodiments of this application.

[0066] See Figure 1, which is a schematic diagram of a CAPIF network architecture. The network architecture shown in Figure 1 mainly includes the following network elements:

[0067] The API caller is usually an operator management system (such as an operator OAM system) or an operator application system. The protocol used by the API caller is compatible with the protocol provided by the operator for managing the service API.

[0068] Service API is an interface that provides services to API callers.

[0069] The CAPIF core functional entity is the central storage for all service API policies and the center for authentication and authorization of API callers and service APIs.

[0070] CAPIF API is an interface that provides API callers with the entry point to CAPIF core functional entities.

[0071] The API open functional entity is an entry point for service providers to open services to the outside world. API callers can use the services provided by the service provider through the API open functional entity.

[0072] The API publishing function (APF) entity can publish the service API information to the CAPIF core function entity so that the API caller can find the service API information in the CAPIF core function entity.

[0073] The API management function (AMF) entity performs management of the service API, such as monitoring the status of the service API and recording call information.

[0074] In Figure 1, the public land mobile network (PLMN) trust domain represents an area trusted by a PLMN. The API provider domain represents an area where the API provider is located. The connection relationship between the above-mentioned network elements is as follows: the interface between the API caller outside the PLMN trust domain and the CAPIF core functional entity is the CAPIF-1e interface, and the interface between the API caller and the API open functional entity is the CAPIF-2e interface. The interface between the API caller within the PLMN trust domain and the CAPIF core functional entity is the CAPIF-1 interface, and the interface between the API caller and the API open functional entity is the CAPIF-2 interface. The interface between the CAPIF core functional entity and the API open functional entity is the CAPIF-3 interface, the interface between the CAPIF core functional entity and the API release functional entity is the CAPIF-4 interface, and the interface between the CAPIF core functional entity and the API management function is the CAPIF-5 interface.

[0075] In the network architecture shown in Figure 1, the service API is usually called using the process shown in Figure 2. As shown in Figure 2, the process of calling the service API is as follows:

[0076] Step 201: The API publishing function entity sends a service API publishing request to the CAPIF core function entity. The request carries information about the service API, which may include the name of the service API, the type of the service API, and interface information.

[0077] Step 202: The CAPIF core functional entity stores the information of the above service API.

[0078] Step 203: The CAPIF core functional entity sends a service API publishing response to the API publishing functional entity.

[0079] If the CAPIF core functional entity receives the service API information and stores it successfully, it will notify the API publishing functional entity of the successful release of the service API information through the service API release response. If the CAPIF core functional entity does not receive the service API information or does not store it successfully, it will notify the API publishing functional entity of the failure to release the service API information through the service API release response.

[0080] Step 204: The API caller sends a service API discovery request to the CAPIF core function entity, where the request carries the service API type, interface information, etc. The service API discovery request is used to query the service API information.

[0081] Step 205: The CAPIF core functional entity sends a service API discovery response to the API caller, where the response carries the information of the service API.

[0082] Step 206: The API caller sends a service API call request to the API open function entity, which carries the service API information.

[0083] Step 207: The API open function entity sends a service API call response to the API caller.

[0084] It is understandable that after the API open functional entity receives the service API call request from the API caller, it can determine whether the API caller has the authority to call the service API based on the pre-configured call policy or the call policy obtained from the CAPIF core functional entity.

[0085] The above process is the first time an API caller calls a service API. The API caller must first discover the service API information from the CAPIF core functional entity. After that, the API caller can call the service API directly without going through the CAPIF core functional entity.

[0086] However, the above call flow doesn't account for incompatibilities between the protocol used by the API caller and the protocol used to manage the service API provided by the operator. For example, if the API caller is a third-party management system (such as a third-party OAM system) or a third-party application system, the API caller may encounter incompatibility when calling the service API. The API caller needs to convert the service API (such as converting the underlying protocol or language of the service API) before calling the service API, resulting in low efficiency for the API caller to call the service API. Currently, the industry has no solution to this problem.

[0087] In view of this, an embodiment of the present application provides a method for providing a service API, in which the first API caller can send at least one parameter information that the first service API needs to meet to the first functional entity, and the first functional entity can obtain the first service API based on the needs of the first API caller, so that the first API caller will not encounter any incompatibility when calling the first service API, thereby improving the efficiency of the first API caller in calling the first service API.

[0088] The method provided in the embodiments of the present application can be applied to various communication systems, such as: a long term evolution (LTE) system, an evolved LTE (LTE-advanced, LTE-A) system, a universal mobile telecommunications system (UMTS), a fourth generation (4G) mobile communication system, a fifth generation (5G) mobile communication system, a beyond 5G (B5G) mobile communication system, or a sixth generation (6G) or other communication system evolved after 5G. The communication system can also be a device-to-device (D2D) network, a wireless fidelity (WiFi) network, a machine-to-machine (M2M) network, an Internet of Things (IoT) network, or other networks.

[0089] See Figure 3, which is a schematic diagram of a network architecture of a communication system. The architecture shown in Figure 3 mainly includes the following network elements:

[0090] The first API caller, also known as the first API calling entity or the first service consumer, can be used to: authenticate the first API caller by verifying its identity and / or other information, obtain authorization to call the service API before calling the service API, discover the service API, and call the service API. The first API caller can be an operator management system (such as an operator OAM system) or an operator application system (M2M application system, IoT application system, vehicle-to-everything (V2X) program system). The protocol applicable to the API caller is adapted to the protocol provided by the operator for managing service APIs. The operator management system or the operator application system can run in a terminal device or in a network device. For example, the first API caller can be a device in a PLMN network, such as a mobility management entity (MME), a radio access network (RAN) node, or a policy and charging rules function (PCRF) in a 4G mobile communication system, or an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), or an application function (AF) entity in a 5G mobile communication system. Alternatively, the first API caller may also be a third-party management system (such as a third-party OAM system) or a third-party application system. The protocol applicable to the API caller is incompatible with the protocol provided by the operator for managing the service API. This embodiment of the present application does not limit this.

[0091] The first functional entity, also known as the API lifecycle management (LCM) functional entity, is used to manage the lifecycle of the service API. The service API lifecycle includes design, development, testing, launch, update, and decommissioning.

[0092] The second functional entity, also known as the warehouse, is used to store at least one parameter template and a service API generation framework template. The parameter template is used to design the service API, which can be understood as the parameter template including at least one parameter for designing the service API. For example, parameter template 1 includes parameter 1, parameter 2, and parameter 3, and parameters 1, 2, and 3 are parameters for designing service API 1. The service API generation framework template is used to develop and test the service API, which can be understood as the service API generation framework template including at least one parameter for designing the service API and at least one parameter for the environment for developing and testing the service API. After filling the value of at least one parameter for designing the service API and the value of at least one parameter for the environment for developing and testing the service API into the service API generation framework template, the service API can be obtained. For example, the service API generation framework template includes parameter 1, parameter 2, parameter 3, and parameter 4, and parameters 1, 2, and 3 are parameters for designing service API 1, and parameter 4 is a parameter for the environment for developing and testing service API 1.

[0093] The third functional entity, also known as the API publishing functional entity, is responsible for publishing the service API. This entity can publish service API information (e.g., service API name, service API type, interface information, etc.) to the CAPIF core functional entity, allowing API callers to find the service API information there.

[0094] The fourth functional entity, also known as the API open functional entity, is used to open service APIs. It can be understood as a portal for service providers to open their services to the outside world. API callers can use the services provided by the service provider through the fourth functional entity.

[0095] The management function (MnF) entity is a service API provider and is used to provide service APIs.

[0096] The network function (NF) entity is a service provider and is used to provide services.

[0097] The first and second functional entities can manage service APIs in a design state, where a service API in a design state can be understood as a service API that cannot be discovered or called by API callers. For example, when a service API is in the design, development, or testing stages, the service API is in a design state. The third and fourth functional entities can manage service APIs in an operational state, where a service API in an operational state can be understood as a service API that can be discovered or called by API callers. For example, when a service API is in the online, update, or offline stages, the service API is in an operational state. The connection relationship between the above-mentioned network elements is as follows: the first, second, third, and fourth functional entities can be deployed as management functional entities in the management domain of the communication system; or, the first, second, third, and fourth functional entities can be deployed in the management domain of the communication system, which can be understood as the first, second, third, and fourth functional entities each being a newly added management functional entity in the management domain of the communication system. Figure 3 takes the first, second, third, and fourth functional entities as management functional entities deployed in the management domain of the communication system as an example.

[0098] FIG4 is a schematic diagram of a network architecture of another communication system. Compared to the system shown in FIG3 , FIG4 illustrates the connection relationship between the aforementioned network elements as follows: the first functional entity, the second functional entity, the third functional entity, and the fourth functional entity are deployed outside the management domain of the communication system, wherein the first functional entity, the second functional entity, the third functional entity, and the fourth functional entity can communicate with a management functional entity in the management domain of the communication system (e.g., via a service bus), the first functional entity, the second functional entity, the third functional entity, and the fourth functional entity can communicate with a network functional entity in the network domain of the communication system (e.g., via a service bus), and the management functional entity in the management domain of the communication system can communicate with a network functional entity in the network domain of the communication system.

[0099] It should be understood that the names of the aforementioned network elements are merely examples, and this application does not preclude the possibility that the network elements may be renamed in the future, or that their functions may be merged. As technology evolves, any device or network element capable of implementing the functions of the aforementioned network elements falls within the scope of protection of this application. Furthermore, in practical applications, the aforementioned communication system may also include other network elements, which are not limited in this application.

[0100] The communication system to which the embodiments of the present application are applicable is briefly introduced above. The method provided by the embodiments of the present application is introduced below in conjunction with the accompanying drawings. The various embodiments of this document can be applied to the communication system shown in Figure 3 or Figure 4. For example, the first API caller described in the various embodiments of this document can be the first API caller in Figure 3 or Figure 4; the first functional entity described in the various embodiments of this document can be the first functional entity in Figure 3 or Figure 4, and the second functional entity described in the various embodiments of this document can be the second functional entity in Figure 3 or Figure 4; the third functional entity described in the various embodiments of this document can be the third functional entity in Figure 3 or Figure 4; the fourth functional entity described in the various embodiments of this document can be the fourth functional entity in Figure 3 or Figure 4; the management functional entity described in the various embodiments of this document can be the management functional entity in Figure 3 or Figure 4; the network functional entity described in the various embodiments of this document can be the network functional entity in Figure 3 or Figure 4.

[0101] In the drawings corresponding to the various embodiments of the present application, all steps indicated by dotted lines are optional steps.

[0102] Refer to Figure 5, which is a flow chart of a method for providing a service API. Figure 5 introduces the method from the perspective of the interaction between the first API caller and the first functional entity. It should be noted that the embodiment of the present application only takes the execution through the first API caller and the first functional entity as an example, and is not limited to the first API caller and the first functional entity. For example, the embodiment of the present application can also be executed by more API callers. When more API callers are involved, the execution process of each API caller in these more API callers is the same. As shown in Figure 5, the process of the method for providing the service API includes the following steps.

[0103] S501: A first API caller sends a first request to a first functional entity. Correspondingly, the first functional entity receives the first request from the first API caller.

[0104] In an embodiment of the present application, the first functional entity can be used to manage the life cycle of a service API, such as designing a service API, developing a service API, testing a service API, launching a service API, updating a service API, and delisting a service API. The first request may include at least one parameter information that needs to be satisfied by the first service API requested to be called by the first API caller. The first service API may be an OAM service API or other types of service APIs, and this embodiment of the present application does not limit this. The at least one parameter information that needs to be satisfied by the first service API can be understood as at least one parameter information used to design the first service API, that is, the value of at least one parameter used to design the first service API.

[0105] For example, at least one parameter used to design a first service API includes parameter 1, parameter 2, and parameter 3, wherein parameter 1 is a class object of the first service API including at least one attribute, parameter 2 is an operation on an application object of the first service API, and parameter 3 is a feature of the first service API. The values ​​of at least one parameter used to design the first service API include value 1 of parameter 1, value 2 of parameter 2, and value 3 of parameter 3, value 1 indicates that the class object of the first service API is class object 1 with attributes 1, 2, and 3, value 2 indicates that the operation on the application object of the first service API is operation 1 including creation, modification, deletion, and query, and value 3 indicates that the features of the first service API are feature 1, feature 2, and feature 3.

[0106] In a possible implementation, the first request may further include, but is not limited to, one or more of the following:

[0107] The identifier of the first API caller; the name of the first service API, which may be a default name or a name set as needed by the first API caller, is not specifically limited in the embodiments of the present application; the time of calling the first service API, which may be understood as the time when the first service API can be called by the API caller; information used to indicate that a second API caller other than the first API caller is allowed to call the first service API;

[0108] Information used to indicate at least one API caller that is allowed to call the first service API, for example, the at least one API caller that is allowed to call the first service API includes a first API caller and a second API caller, the information used to indicate at least one API caller that is allowed to call the first service API may include an identifier of the first API caller and an identifier of the second API caller, or the information used to indicate at least one API caller that is allowed to call the first service API may also include location information of the first API caller and location information of the second API caller, which is not limited to the embodiments of the present application.

[0109] In one possible implementation, the first request may also include a first parameter template, and at least one parameter information that the first service API needs to satisfy may be carried in the first parameter template. The first parameter template may include at least one parameter that the first service API needs to satisfy or at least one parameter used to design the first service API, and the first parameter template may be sent by the first functional entity to the first API caller. It can be understood that the first API caller can determine the value of at least one parameter that the first service API needs to satisfy based on the at least one parameter that the first service API needs to satisfy included in the first parameter template. For example, the first parameter template includes parameter 1, parameter 2, and parameter 3, and the first request includes value 1 of parameter 1, value 2 of parameter 2, and value 3 of parameter 3. Alternatively, the first request may not include the first parameter template, and the at least one parameter information that the first service API needs to satisfy may not be carried in the first parameter template. This is defined in the embodiments of the present application.

[0110] During the specific implementation process, when at least one parameter information that the first service API needs to satisfy is carried in the first parameter template, the present application may further perform the steps shown in FIG6 before executing S501:

[0111] S501a: The first API caller sends a second request to the first functional entity. Correspondingly, the first functional entity receives the second request from the first API caller.

[0112] The second request may be used to request the first functional entity to provide a first parameter template, and the second request may include a first template identifier for indicating the first parameter template. The first template identifier may be a functional type of the first service API, such as an analysis service API, a configuration service API, a measurement service API, an energy-saving service API, etc., and / or a design language of the first service API, such as representational state transfer (RESRful), network configuration protocol (Netconf), yet another next generation (YANG), yet another markup language (YAML), etc. Optionally, the second request may also include the name of the first service API, so that the first functional entity can determine that the first parameter template corresponds to the first service API.

[0113] S501b: The first functional entity sends a third request to the second functional entity. Correspondingly, the second functional entity receives the third request from the second functional entity.

[0114] The second functional entity may be used to store at least one parameter template, and the third request may be used to request the second functional entity to provide a first parameter template. The third request may include a first template identifier for indicating the first parameter template.

[0115] The second functional entity may store the functional type of the service API and / or the correspondence between the design language of the service API and the parameter template as shown in Table 1 below.

[0116] Table 1

[0117] As shown in Table 1 above, different function types of the service API and / or different design languages ​​of the service API correspond to different parameter templates. For example, if the second request includes function type 1 and design language 1, the second functional entity may determine that the first parameter template is parameter template 1 (parameter a1, parameter a2, and parameter a2).

[0118] S501c: The second functional entity sends the first parameter template to the first functional entity. Correspondingly, the first functional entity receives the first parameter template from the second functional entity.

[0119] S501d: The first functional entity sends a first parameter template to the first API caller. Correspondingly, the first API caller receives the first parameter template from the first functional entity.

[0120] Optionally, if the second request includes the name of the first service API, the first functional entity may send the first parameter template and the name of the first service API to the first API caller. Accordingly, the first API caller may receive the first parameter template and the name of the first service API from the first functional entity, so that the first API caller can determine that the first parameter template corresponds to the first service API.

[0121] S501e: The first API caller determines at least one parameter information that the first service API needs to satisfy based on the first parameter template.

[0122] S502: The first functional entity sends a first notification to the first API caller. Correspondingly, the first API caller receives the first notification from the first functional entity.

[0123] In an embodiment of the present application, the first notification may be used to indicate that the first service API can be called. The first notification may include, but is not limited to, one or more of the following: the name of the first service API; or the identifier of the first service API, where the identifier of the first service API is assigned by the first functional entity.

[0124] During the specific implementation process, the first notification can be used to indicate that the state of the first service API is updated from the first state to the second state. The first state can be used to indicate that the first service API cannot be called by the API caller, for example, the first state can indicate that the first service API is in the design state, or the first state can indicate that the first functional entity is designing the first service API, or the first state can indicate that the first functional entity is developing the first service API, or the first state can indicate that the first functional entity is testing the first service API, or the second state can indicate that the first functional entity has taken the first service API offline, or the first state can indicate that the first functional entity is updating (or modifying, or upgrading) the first service API. The second state can be used to indicate that the first service API can be called, for example, the second state can indicate that the first service API is in the running state, or the second state can indicate that the first functional entity has put the first service API online, or the first functional entity has updated (or modified, or upgraded) the first service API.

[0125] The first service API can be obtained by the first functional entity filling at least one parameter information that the first service API needs to satisfy (ie, at least one parameter information used to design the first service API) into a preset service API generation framework template.

[0126] In one possible implementation, the service API generation framework template may include at least one parameter for designing the service API and at least one parameter for developing and testing the environment for the service API. Therefore, the first functional entity fills the value of at least one parameter that the first service API needs to meet (i.e., the value of at least one parameter for designing the first service API) and the value of at least one parameter for developing and testing the environment for the first service API into the service API generation framework template, and the first service API can be obtained.

[0127] During the specific implementation process, before executing S502, the present application may also execute the steps shown in FIG6 :

[0128] S502a: The first functional entity sends a fourth request to the second functional entity. Correspondingly, the second functional entity receives the fourth request from the first functional entity.

[0129] The second functional entity is used to store the service API to generate a framework template, and the fourth request is used to request the second functional entity to provide the service API to generate a framework template.

[0130] S502b: The second functional entity sends a service API generation framework template to the first functional entity. Correspondingly, the first functional entity receives the service API generation framework template from the second functional entity.

[0131] S502c: The first functional entity fills at least one parameter information that the first service API needs to satisfy into the service API generation framework template to obtain the first service API.

[0132] S502d: The first functional entity sends a fifth request to the third functional entity. Correspondingly, the third functional entity receives the fifth request from the first functional entity.

[0133] The third functional entity may be used to publish a service API. The fifth request may be used to request the publication of a first service API, which can be called by or after being published. The fifth request may include information for instructing the acquisition of the first service API. The information for instructing the acquisition of the first service API may include, but is not limited to, one or more of the following: an identifier of the first service API, the identifier of the first service API being assigned by the first functional entity; an acquisition path for the first service API, for example, the root directory of the first service API.

[0134] Optionally, the fifth request may also include, but is not limited to, one or more of the following: the version of the first service API; the time of calling the first service API; information indicating at least one API caller that is allowed to call the first service API. For example, when the fifth request includes the version of the first service API, after the third functional entity receives the fifth request from the first functional entity, it may publish the information of the first service API to the CAPIF core functional entity, wherein the information of the first service API may include the version of the first service API, so that when the first functional entity discovers the first service API through the CAPIF core functional entity, it can quickly determine the version of the first service API. When the fifth request includes the time of calling the first service API, after the third functional entity receives the fifth request from the first functional entity, it may determine the time of publishing the first service API based on the time of calling the first service API included in the fifth request, so that the first API caller can call the first service API at the time when the first API caller needs to call the first service API, thereby improving the discovery efficiency or calling efficiency of the service API. When the fifth request includes information indicating at least one API caller allowed to call the first service API, the third functional entity may publish information of the first service API to the CAPIF core functional entity after receiving the fifth request from the first functional entity, wherein the information of the first service API may include information of at least one API caller allowed to call the first service API.

[0135] In a possible implementation, after executing S502, the present application may further execute the steps shown in FIG6 :

[0136] S502e: The first API caller sends a sixth request to the fourth functional entity. Correspondingly, the fourth functional entity receives the sixth request from the first API caller.

[0137] The fourth functional entity may be used to open a service API, and the sixth request may be used to request to call the first service API. The sixth request may include an identifier of the first API caller.

[0138] During a specific implementation, after the fourth functional entity receives the sixth request from the first API caller, the fourth functional entity may determine whether the first API caller has permission to call the first service API based on a pre-configured calling policy or a calling policy obtained from the CAPIF core functional entity. For example, the fourth functional entity may obtain information indicating the identifier of at least one API caller allowed to call the first service API from the CAPIF core functional entity, and determine whether the first API caller has permission to call the first service API based on the identifier of the at least one API caller allowed to call the first service API and the identifier of the first API caller. If the identifier of the at least one API caller allowed to call the first service API includes the identifier of the first API caller, the fourth functional entity determines that the first API caller has permission to call the first service API, and the fourth functional entity sends the uniform resource locator (URL) of the first service API to the first API caller. If the identifier of the at least one API caller allowed to call the first service API does not include the identifier of the first API caller, the fourth functional entity determines that the first API caller does not have permission to call the first service API, and the fourth functional entity does not send the URL of the first service API to the first API caller.

[0139] According to the above scheme, the first API caller can send at least one parameter information that the first service API needs to meet to the first functional entity, and the first functional entity can obtain the first service API based on the needs of the first API caller, so that there will be no incompatibility when the first API caller calls the first service API, thereby improving the efficiency of the first API caller in calling the first service API.

[0140] The method provided by the embodiment of the present application is described above in conjunction with the accompanying drawings, and the device provided by the embodiment of the present application is described below in conjunction with the accompanying drawings.

[0141] Based on the same technical concept, embodiments of the present application provide a communication device that includes modules / units / means for executing the methods executed by the devices in the above method embodiments. The modules / units / means can be implemented in software or hardware, or the corresponding software implementation can be executed by hardware.

[0142] For example, see FIG. 7 , which is a schematic diagram of a communication device 700 . The device 700 includes a transceiver module 710 and a processing module 720 .

[0143] When the apparatus 700 is a first functional entity or is located in the first functional entity, the functions of the modules of the apparatus 700 are as follows:

[0144] The transceiver module 710 is used to receive a first request from a first API caller, where the first request includes at least one parameter information that needs to be satisfied by the first service API requested to be called by the first API caller; the transceiver module 710 is also used to send a first notification to the first API caller, where the first notification is used to indicate that the first service API can be called, and the first service API is obtained by filling the at least one parameter information into a preset service API generation framework template.

[0145] When the device 700 is the first API caller or is located at the first API caller, the functions of the modules of the device 700 are as follows:

[0146] The transceiver module 710 is used to send a first request to a first functional entity, where the first request includes at least one parameter information that needs to be satisfied by the first service API requested to be called by the first API caller; the transceiver module 710 is also used to receive a first notification from the first functional entity, where the first notification is used to indicate that the first service API can be called, and the first service API is obtained by filling the at least one parameter information into a preset service API generation framework template.

[0147] In specific implementation, the above-mentioned device 700 can have various product forms. Several possible product forms are introduced below.

[0148] Refer to Figure 8, which is a schematic diagram of a communication device 800. The communication device 800 includes a processor 810 and an interface circuit 820. The interface circuit 820 is used to receive signals from other communication devices outside the communication device and transmit them to the processor 810, or send signals from the processor 810 to other communication devices outside the communication device. The processor 810 is used to implement the method executed by the first functional entity or the first API caller in the above method embodiment through logic circuits or execution instructions.

[0149] The processor 810 and the interface circuit 820 are coupled to each other. It is understood that the interface circuit 820 can be a transceiver or an input / output interface. Optionally, the communication device 800 may further include a memory 830 for storing instructions executed by the processor 810, or storing input data required by the processor 810 to execute instructions, or storing data generated after the processor 810 executes instructions.

[0150] When the above-mentioned communication device is a module applied to the first functional entity or the first API caller, the module implements the function of the first functional entity or the first API caller in the above-mentioned method embodiment. The module receives information from other modules (such as a radio frequency module or an antenna) in the first functional entity or the first API caller, and the information is sent by the first functional entity to the first API caller or sent by the first API caller to the first functional entity; or, the module sends information to other modules (such as a radio frequency module or an antenna) in the first functional entity or the first API caller, and the information is sent by the first API caller to the first functional entity or sent by the first functional entity to the first API caller.

[0151] It should be understood that the processors mentioned in the embodiments of the present application can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor that is implemented by reading software code stored in a memory.

[0152] Exemplarily, the processor may be a central processing unit (CPU), or 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.

[0153] It should be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. 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), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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 RAM bus random access memory (DR RAM).

[0154] 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.

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

[0156] Based on the same technical concept, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program or instructions. When the computer program or instructions are executed by a processor, the method executed by the first functional entity or the first API caller in the above method embodiment is implemented.

[0157] Based on the same technical concept, an embodiment of the present application also provides a computer program product, comprising a computer program or instructions. When the computer program or instructions are executed by a processor, the method executed by the first functional entity or the first API caller in the above method embodiment is implemented.

[0158] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0159] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0160] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0161] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

Claims

1. A method for providing a service application programming interface API, characterized in that: Applicable to the first functional entity, comprising: Receiving a first request from a first API caller, where the first request includes at least one parameter information that needs to be satisfied by a first service API requested to be called by the first API caller; A first notification is sent to the first API caller, where the first notification is used to indicate that the first service API can be called, and the first service API is obtained by filling the at least one parameter information into a preset service API generation framework template.

2. The method according to claim 1, characterized in that The first request also includes a first parameter template, and the at least one parameter information is carried in the first parameter template, and the first parameter template is sent by the first functional entity to the first API caller.

3. The method according to claim 2, characterized in that Also includes: A second request is received from the first API caller, where the second request is used to request the first functional entity to provide the first parameter template, and the second request includes a first template identifier for indicating the first parameter template.

4. The method according to claim 2 or 3, characterized in that Also includes: Sending a third request to a second functional entity, where the second functional entity is used to store at least one parameter template, the third request is used to request the second functional entity to provide the first parameter template, and the third request includes a first template identifier used to indicate the first parameter template; The first parameter template is received from the second functional entity.

5. The method according to any one of claims 1 to 4, characterized in that: The first request also includes one or more of the following: The identifier of the first API caller; The name of the first service API; The time of calling the first service API; Information used to indicate that a second API caller other than the first API caller is allowed to call the first service API; Information used to indicate at least one API caller that is allowed to call the first service API.

6. The method according to any one of claims 1 to 5, characterized in that: Also includes: Sending a fourth request to a second functional entity, where the second functional entity is used to store the service API generation framework template, and the fourth request is used to request the second functional entity to provide the service API generation framework template; The service API generation framework template is received from the second functional entity.

7. The method according to any one of claims 1 to 6, characterized in that: Also includes: A fifth request is sent to a third functional entity, where the third functional entity is used to publish a service API, the fifth request is used to request the publication of the first service API, and the fifth request includes information for indicating the acquisition of the first service API.

8. The method according to claim 7, characterized in that The information for indicating the acquisition of the first service API includes one or more of the following: an identifier of the first service API, where the identifier of the first service API is allocated by the first functional entity; The acquisition path of the first service API.

9. The method according to claim 7 or 8, characterized in that The fifth request also includes one or more of the following: the version of the first service API; The time of calling the first service API; Information used to indicate at least one API caller that is allowed to call the first service API.

10. The method according to any one of claims 1 to 9, characterized in that: The first notification includes one or more of the following: The name of the first service API; The identifier of the first service API is allocated by the first functional entity.

11. The method according to any one of claims 1 to 10, characterized in that: The first functional entity is deployed in a management domain of a communication system; or, The first functional entity is deployed at a location outside the management domain of the communication system, and the first functional entity can communicate with a management functional entity in the management domain.

12. A method for providing a service API, characterized in that: Applicable to the first API caller, including: Sending a first request to a first functional entity, where the first request includes at least one parameter information that needs to be satisfied by the first service API requested to be called by the first API caller; A first notification is received from the first functional entity, where the first notification is used to indicate that the first service API can be called, and the first service API is obtained by filling the at least one parameter information into a preset service API generation framework template.

13. The method according to claim 12, characterized in that The first request also includes a first parameter template, and the at least one parameter information is carried in the first parameter template, and the first parameter template is sent by the first functional entity to the first API caller.

14. The method according to claim 13, characterized in that Also includes: A second request is sent to the first functional entity, where the second request is used to request the first functional entity to provide the first parameter template, and the second request includes a first template identifier used to indicate the first parameter template.

15. The method according to any one of claims 12 to 14, characterized in that: The first request also includes one or more of the following: The identifier of the first API caller; The name of the first service API; The time of calling the first service API; Information used to indicate that a second API caller other than the first API caller is allowed to call the first service API; Information used to indicate at least one API caller that is allowed to call the first service API.

16. The method according to any one of claims 12 to 15, characterized in that: The first notification includes one or more of the following: The name of the first service API; The identifier of the first service API is allocated by the first functional entity.

17. The method according to any one of claims 12 to 16, characterized in that: Also includes: A sixth request is sent to a fourth functional entity, where the fourth functional entity is used to open a service API, and the sixth request is used to request to call the first service API, and the sixth request includes an identifier of a caller of the first API.

18. A communication device, characterized in that: The method comprises a module for executing the method according to any one of claims 1 to 11, or a module for executing the method according to any one of claims 12 to 17.

19. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor implements the method as described in any one of claims 1 to 11 or implements the method as described in any one of claims 12 to 17 through a logic circuit or by executing code instructions.

20. A communication device, characterized in that: include: Memory for storing computer programs; A processor, configured to call and run the computer program from the memory to implement the method according to any one of claims 1 to 11, or to implement the method according to any one of claims 12 to 17.

21. A chip system, characterized in that: The method comprises a processor configured to execute the method according to any one of claims 1 to 11, or to execute the method according to any one of claims 12 to 17.

22. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a communication device, implements the method according to any one of claims 1 to 17.

23. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction, and when the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 17 is implemented.

Images