EP3863312B1 - Api publishing method and device - Google Patents

Api publishing method and device Download PDF

Info

Publication number
EP3863312B1
EP3863312B1 EP19881835.3A EP19881835A EP3863312B1 EP 3863312 B1 EP3863312 B1 EP 3863312B1 EP 19881835 A EP19881835 A EP 19881835A EP 3863312 B1 EP3863312 B1 EP 3863312B1
Authority
EP
European Patent Office
Prior art keywords
api
entity
ccf
information
target
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP19881835.3A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP3863312A1 (en
EP3863312A4 (en
Inventor
Cuili GE
Niranth Amogh
Yanmei Yang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP3863312A1 publication Critical patent/EP3863312A1/en
Publication of EP3863312A4 publication Critical patent/EP3863312A4/en
Application granted granted Critical
Publication of EP3863312B1 publication Critical patent/EP3863312B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/36—Software reuse
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • This application relates to the field of communications technologies, and in particular, to an API publish method and an apparatus.
  • an operator may provide a network service or a network capability for an application in a form of an application programming interface (application program interface, API).
  • API application programming interface
  • the 3rd generation partnership project (third generation partnership project, 3GPP) defines a common API framework (common API framework, CAPIF), which is mainly used for API publication, discovery, and management.
  • CAPIF common API framework
  • an application can conveniently and quickly use an API.
  • CAPIF core function CCF
  • CCF common application programming interface core
  • One CCF entity usually supports functions of publishing and performing authentication on an API in one region.
  • an API is published to only one CCF entity when being published.
  • V2X vehicle to everything
  • users of a same V2X application may come from different public land mobile networks (public land mobile network, PLMN); and on the other hand, a service coverage of a same V2X application may cross PLMNs.
  • PLMN public land mobile network
  • one local application may further cross a plurality of regions.
  • interconnection and interworking between different PLMNs and interconnection and interworking between a plurality of regions in a same PLMN How to publish an API to a plurality of CCF entities is a problem that needs to be resolved.
  • the document Huawei at all: "API publish and API discover for CAPIF interconnection", XP051545232 is an early standardization document regarding API sharing. Especially, the API publishing and API discover procedure are shown there.
  • the technical solution provided in this application may be applied to a CAPIF system architecture shown in FIG. 1A and FIG. 1B .
  • the system architecture may include an API invoking entity (API invoker), a CCF entity, an API exposure function (API exposing function, AEF) entity, an API publish function (API publishing function, APF) entity, an API management function (API management function, APIMF) entity, and the like.
  • the API invoking entity is a logical function entity that invokes, accesses, and uses an API, and may also be referred to as an API invoker.
  • Capabilities supported by the API invoking entity may include: authentication performed on the API invoking entity, where for example, the authentication is implemented by authenticating an identifier of the API invoking entity and other information, mutual authentication with a CAPIF, obtaining authorization before accessing an API, discovering APIs, invoking an API, and the like.
  • the API invoking entity may be a third-party application that signs a service agreement with a PLMN operator, or may be an application of a PLMN operator, for example, a machine to machine (machine to machine, M2M) application, an internet of things (internet of vehicles, IoT) application, or a V2X application.
  • M2M machine to machine
  • IoT internet of things
  • V2X V2X
  • the CCF entity is configured to provide an API of a CAPIF.
  • Capabilities supported by the CCF entity may include: performing authentication on an API invoking entity based on an identifier of the API invoking entity and other information, performing mutual authentication with the API invoking entity, providing authorization to the API invoking entity before the API invoking entity accesses the API, publishing, storing, and supporting discovery of the API, being responsible for access control of the API according to a policy of a PLMN operator, storing a log invoked by the API and providing the log to an authorization entity, performing charging based on the API log, detecting invocation of the API, registration of the API invoking entity, storing a configuration policy, auditing the invoked log, and the like.
  • the AEF entity is configured to provide an API, and is also an entry used by the API invoking entity to invoke the API.
  • Capabilities supported by the AEF entity may include: performing authentication on an API invoking entity based on an identifier of the API invoking entity and other information that is provided by a CCF entity, determining authorization provided by the CCF entity, synchronizing an API log to the CCF entity, and the like.
  • the APF entity provides an API publish function, so that the API invoking entity can discover an API.
  • a capability supported by the APF entity may include: publishing an API function.
  • the APIMF entity provides an API management function. Capabilities supported by the APIMF entity may include: auditing an API invoking log provided by a CCF entity, monitoring an event reported by the CCF entity, configuring, for an API, a policy of an API provider, detecting a status of an API, and registering an API invoking entity.
  • the AEF entity, the APF entity, and the APIMF entity belong to an API provider domain.
  • One API provider domain may include one APF entity, one APIMF entity, and one or more AEF entities.
  • the system architecture may include one or more trusted domains.
  • a trusted domain may be a PLMN network domain.
  • a trusted domain A is a PLMN network domain of an operator A
  • a trusted domain B is a PLMN network domain of an operator B.
  • a same operator controls and provides sufficient security protection for entities in one trusted domain.
  • different trusted domains may be obtained internally through division based on different security control granularities.
  • a trusted domain may be a network corresponding to a region in a PLMN network domain.
  • a trusted domain A is a PLMN network of an operator Z in a northwest region
  • a trusted domain B is a PLMN network of an operator Z in the Beijing region.
  • a trusted domain is referred to as a domain.
  • a domain may include an API invoking entity, an AEF entity, an APF entity, an APIMF entity, and one or more CCF entities.
  • an API exposure entity 1, an API publish entity 1, an API management entity 1, a CCF entity 1, an API exposure entity 2, an API publish entity 2, an API management entity 2, a CCF entity 2, and an API invoking entity 1 belong to a trusted domain A; and an API exposure entity 3, an API publish entity 3, an API management entity 3, a CCF entity 3, and an API invoking entity 2 belong to a trusted domain B.
  • an AEF entity may communicate with a CCF entity through a CAPIF-3 interface
  • an APF entity may communicate with a CCF entity through a CAPIF-4 interface
  • an APIMF entity may communicate with a CCF entity through a CAPIF-5 interface
  • different CCF entities may communicate with each other through a CAPIF-6 interface.
  • an API invoking entity may invoke an API in the trusted domain through a CAPIF-2 interface.
  • An API invoking entity not belonging to a trusted domain may invoke an API in the trusted domain through a CAPIF-2e interface.
  • an API invoking entity 1 has a subscription relationship with an operator A, and a PLMN network domain of the operator A is a trusted domain A.
  • the API invoking entity 1 belongs to the trusted domain A. That is, the API invoking entity 1 is in the trusted domain A.
  • Each trusted domain may have a top-level (domain-bound) CCF entity, and the trusted domain may be further connected to no low-level CCF entity or a plurality of low-level CCF entities.
  • a top-level CCF entity in a trusted domain may be further connected to a top-level CCF entity in another trusted domain, and CCF entities in different trusted domains communicate with each other through CAPIF-6e interface.
  • CAPIF-6 an interface between two CCFs in a CAPIF in a same trusted domain
  • CAPIF-6e may support functions that are of the CAPIF-3 interface, the CAPIF-4 interface, and the CAPIF-5 interface and that are of cross-system security.
  • the function entities in FIG. 1A and FIG. 1B may be implemented by one physical device, or may be jointly implemented by a plurality of physical devices, or may be a logical function module in one physical device. This is not specifically limited in this embodiment of this application.
  • the API invoking entity, the AEF entity, the APF entity, the APIMF entity, or the CCF entity may be a device in a PLMN network, for example, may be a device in a 4G or 5G mobile communications system.
  • the API invoking entity, the AEF entity, the APF entity, the APIMF entity, or the CCF entity may run in a terminal device, or may run in a network device.
  • the API invoking entity may be a mobility management entity (mobility management entity, MME), a radio access network (radio access network, RAN) device, a policy and charging rules function (policy and charging rules function, PCRF) entity, a home subscriber server (home subscriber server, HSS), a broadcast/multicast service center (broadcast-multicast service center, BM-SC), a serving-call session control function (service-call session control function, S-CSCF), an application function (application function, AF) entity, or the like in the 4G communications system; or the API invoking entity may be an access and mobility management function (access and mobility management function, AMF) entity, a session management function (session management function, SMF) entity, a unified data management (unified data management, UDM) entity, a user plane function (user plane function, UPF) entity, a policy control function (policy control function, PCF) entity, an authentication server function (authentication server function, AUSF) entity, a network exposure function (network),
  • the AEF entity may be a service capability exposure function (service capability exposure function, SCEF) entity running in a 4G network.
  • SCEF service capability exposure function
  • the AEF entity may be a NEF entity running in a 5G network, or an AMF entity, an SMF entity, a UDM entity, a PCF entity, an NRF entity, an AUSF entity, or an NSSF entity.
  • the CCF entity may be independently deployed in an independent network entity; or the CCF entity and an entity that is in an API provider domain may be deployed together in the SCEF entity in the 4G network or in the NEF entity in the 5G network.
  • each of the API invoking entity, the AEF entity, the APF entity, the APIMF entity, and the CCF entity in FIG. 1A and FIG. 1B can be implemented by an apparatus 200 in FIG. 2 .
  • FIG. 2 is a schematic structural diagram of hardware of an apparatus 200 according to an embodiment of this application.
  • the apparatus 200 includes at least one processor 201, a communications bus 202, a memory 203, and at least one communications interface 204.
  • the processor 201 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits configured to control execution of a program in a solution of this application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communications bus 202 may include a channel for transmitting information between the foregoing components.
  • the communications interface 204 is configured to communicate, by using any apparatus such as a transceiver, with another device or communications network such as the Ethernet, a radio access network (radio access network, RAN), or a wireless local area network (wireless local area networks, WLAN).
  • a transceiver such as the Ethernet, a radio access network (radio access network, RAN), or a wireless local area network (wireless local area networks, WLAN).
  • radio access network radio access network, RAN
  • WLAN wireless local area network
  • the memory 203 may be a read-only memory (read-only memory, ROM) or another type of static storage device that can store static information and an instruction, a random access memory (random access memory, RAM) or another type of dynamic storage device that can store information and an instruction, or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another compact disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Bluray optical disc, and the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in a form of an instruction or a data structure and that can be accessed by a computer, but is not limited thereto.
  • the memory may exist independently, and is connected to the processor by using the bus.
  • the memory may be integrated with the processor.
  • the memory 203 is configured to store application program code for executing the solutions in this application, and the processor 201 controls the execution.
  • the processor 201 is configured to execute the application program code stored in the memory 203, to implement the API publish method provided in the following embodiments of this application.
  • the processor 201 may include one or more CPUs such as a CPU 0 and a CPU 1 in FIG. 2 .
  • the apparatus 200 may include a plurality of processors such as a processor 201 and a processor 208 in FIG. 2 .
  • processors may be a single-core (single-CPU) processor, or may be a multi-core (multi-CPU) processor.
  • the processor herein may be one or more devices, circuits, and/or processing cores configured to process data (for example, a computer program instruction).
  • the apparatus 200 may further include an output device 205 and an input device 206.
  • the output device 205 communicates with the processor 201, and may display information in a plurality of manners.
  • the output device 205 may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a cathode ray tube (cathode ray tube, CRT) display device, a projector (projector), or the like.
  • the input device 206 communicates with the processor 201, and may receive an input from a user in a plurality of manners.
  • the input device 206 may be a mouse, a keyboard, a touchscreen device, a sensing device, or the like.
  • the apparatus 200 may be a general-purpose communications device or a special-purpose communications device.
  • the apparatus 200 may be a desktop computer, a portable computer, a network server, a palmtop computer (personal digital assistant, PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device having a structure similar to that in FIG. 2 .
  • a type of the apparatus 200 is not limited in this embodiment of this application.
  • an API publish entity publishes APIs to a CCF entity
  • the CCF entity may publish these APIs to another CCF entity inside a domain to which the CCF entity belongs, or publish these APIs to another CCF entity outside the domain to which the CCF entity belongs.
  • a process in which a CCF entity publishes an obtained API to another CCF entity is referred to as sharing an API.
  • the CCF entity performing the sharing process is a source CCF entity
  • the one or more CCF entities receiving the shared API are target CCF entities for sharing the API.
  • a CAPIF system architecture may include a plurality of domains, and each domain may include one or more CCF entities.
  • each domain may include one or more CCF entities.
  • the domain to which the target CCF entity belongs is a target domain for sharing the API by the source CCF entity.
  • a CCF entity 1 belongs to a trusted domain A
  • a CCF entity 3 belongs to a trusted domain B. If the CCF entity 1 shares an API with the CCF entity 3, the trusted domain B is a target domain for sharing the API by the CCF entity 1.
  • A/B may represent A or B.
  • and/or describes only an association relationship for describing associated objects and represents that three relationships may exist.
  • a and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists.
  • a plurality of means two or more than two unless otherwise specified.
  • terms such as “first” and “second” are used in the embodiments of this application to distinguish between same items or similar items that have basically same functions.
  • API publish methods provided in the embodiments of this application with reference to FIG. 1A and FIG. 1B and FIG. 2 .
  • An embodiment of this application provides an API publish method. As shown in FIG. 3 , the method may include the following steps.
  • a first CCF entity determines a tobe-shared API.
  • An API provider may publish an API in an AEF entity to a CCF entity by using an API publish entity.
  • an API invoking entity can discover and obtain, by using the CCF entity, the API provided by the AEF entity, to invoke the API.
  • Invoking an API may also be understood as accessing an API.
  • the API invoking entity can obtain a required resource and service such as a broadcast transmission resource and a video acceleration service by invoking an API.
  • the first CCF entity may be a CCF entity in a CAPIF system architecture.
  • the API publish entity of the API provider is connected to the first CCF entity through a CAPIF-4 interface.
  • the first CCF entity is a domain-bound CCF entity in a domain.
  • the first CCF entity is the CCF entity 1 in FIG. 1A and FIG. 1B .
  • the first CCF entity may share the API published to the first CCF entity with a target CCF entity.
  • the API invoking entity can discover and obtain the shared API by using the target CCF entity.
  • the first CCF entity determines the to-be-shared API.
  • the first CCF entity receives a first API publish request message from the API publish entity, and determines the to-be-shared API based on the first API publish request message.
  • the first CCF entity determines the to-be-shared API according to a third preset rule.
  • the first CCF entity shares information about the to-be-shared API with the target CCF entity of the to-be-shared API.
  • the first CCF entity determines the target CCF entity of the to-be-shared API.
  • the first CCF entity receives a first API publish request message from the API publish entity, and determines the target CCF entity of the to-be-shared API based on the first API publish request message.
  • the first CCF entity determines the target CCF entity of the to-be-shared API according to a fourth preset rule.
  • the first CCF entity shares the information about the to-be-shared API with the target CCF entity of the to-be-shared API.
  • Information about an API may include an API identifier, an API type, interface information of the API, or the like.
  • the API identifier is used to identify the API.
  • the API identifier may be a number (for example, a letter, a digit, a special symbol, or a free combination of at least two of a letter, a digit, and a special symbol) of the API, or may be a name of the API, an index of the API, a uniform resource identifier (uniform resource locator, URL) of the API, or the like.
  • the API type may be a V2X service, an IoT service, an M2M service, or the like.
  • the interface information of the API may be a fully qualified domain name (fully qualified domain name, FQDN) of an AEF entity, an internet protocol (internet protocol, IP) address of the AEF entity, a port number of the AEF entity, an IP address and a port number of the AEF entity, or the like.
  • FQDN fully qualified domain name
  • IP internet protocol
  • the information about the API may be unique information in the domain.
  • the API identifier is a unique identifier in the domain.
  • the information about the API may be global information.
  • the API identifier is a globally unique identifier.
  • the global information may be understood as information that is about the API and that can be identified in all domains in the CAPIF system.
  • a global address may be understood as an address that can be identified in all the domains in the CAPIF system.
  • the first CCF entity may share the API with another CCF entity, so that the API is published to a plurality of CCF entities.
  • the API invoking entity can discover and obtain the API by using the plurality of CCF entities.
  • An embodiment of this application provides an API publish method. As shown in FIG. 4 , the method may include the following steps.
  • An API publish entity determines information about an API and sharing information of the API.
  • the API publish entity determines the information about the API, where the API is a to-be-shared API, and determines the sharing information of the API.
  • the API publish entity may be an APF entity, or the API publish entity may be an APIMF entity.
  • the API publish entity may alternatively be another entity in a CAPIF system architecture. This is not limited in this embodiment of this application. In this embodiment of this application, an example in which the API publish entity is an APF entity is used for description.
  • the API publish entity receives a user instruction (for example, a user selects a to-be-published API and a target CCF entity of the to-be-published API by using a human-computer interactive operation page), and obtains the to-be-shared API and a target CCF entity of the to-be-shared API.
  • a user instruction for example, a user selects a to-be-published API and a target CCF entity of the to-be-published API by using a human-computer interactive operation page
  • the API publish entity may determine the to-be-shared API and a target CCF entity of the to-be-shared API according to a fifth preset rule.
  • the fifth preset rule may be a mapping relationship between commercial subscription information and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a domain of a target CCF entity), an API type, a mapping relationship between an API type and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a logical domain or a geographic region of a target CCF entity), or the like.
  • an operator B and an operator A have a subscription for sharing an API for use.
  • the operator B can obtain and use any API of the operator A.
  • An API publish entity of the operator A determines, based on subscription information indicating sharing of an API for use with the operator B, to publish the API to a trusted domain (for example, the CCF entity 3 in FIG. 1A and FIG. 1B ) corresponding to the operator B.
  • the fifth preset rule may be sharing an API of a V2X type with a CCF entity 3, and sharing an API of an IoT type with a CCF entity 2.
  • an API 1 is an API of the V2X type
  • an APF entity 1 determines to share the API 1 with the CCF entity 3
  • an API 2 is an API of the IoT type
  • the APF entity 1 determines to share the API 2 with the CCF entity 2.
  • the API publish entity 1 may alternatively determine, according to another rule, a target CCF entity for sharing an API. This is not limited in this embodiment of this application.
  • the API publish entity publishes the API to a CCF entity (briefly referred to as a CCF entity corresponding to the API publish entity) connected to the API publish entity through a CAPIF-4 interface.
  • the API publish entity does not determine whether to share the API, but the CCF entity corresponding to the API publish entity determines whether to share the API.
  • the API publish entity sends a third API publish request message to the corresponding CCF entity.
  • the third API publish request message includes the information about the API.
  • the third API publish request message may be a service API publish request (service API publish request), or a service API configuration request (service API configuration request).
  • the API publish entity sends the information about the API to the CCF entity corresponding to the API publish entity.
  • the API publish entity 1 sends information about an API 1, an API 2, and an API 3 to the CCF entity 1.
  • the API publish entity may not generate the sharing information of the API, or may not send the sharing information of the API to the CCF entity.
  • the API publish entity determines whether to share the API. If the API publish entity determines to prohibit sharing of the API, in an example, the API publish entity sends the information about the API and indication information of prohibiting sharing of the API to a first CCF entity; and in another example, the API publish entity sends only the information about the API to a first CCF entity, indicating that sharing of the API is prohibited. If determining to share the API, the API publish entity determines the sharing information of the API.
  • the sharing information of the API is used to indicate to a first CCF entity to share the API.
  • the sharing information may include at least one of sharing indication information, intra-domain target CCF entity information, or target domain indication information.
  • the sharing indication information is used to indicate that the API is to be shared.
  • the target domain indication information is used to indicate a target domain, and the target domain is different from a domain to which the first CCF entity belongs.
  • the intra-domain target CCF entity information is used to indicate the information about the target CCF entity of the API in the domain to which the first CCF entity belongs.
  • the indication information of prohibiting sharing of the API and the sharing indication information may be represented by using different values of a same parameter. For example, a parameter value is 0, indicating that sharing is prohibited; a parameter value is 1, indicating that sharing is allowed; or a parameter value is 2, indicating that whether sharing is allowed is not specified.
  • the indication information of prohibiting sharing of the API and the sharing indication information may be implemented by using different parameters.
  • the intra-domain target CCF entity information may be an identifier of a CCF entity, an FQDN domain name, an IP address, an IP address and a port number, a URL, or the like.
  • the target domain indication information may be an identifier of the target domain, for example, a PLMN ID or a domain name (for example, domain.com).
  • the target domain indication information may include an identifier of the target domain and inter-domain target CCF entity information.
  • the inter-domain target CCF entity information may be an identifier of a CCF entity, an FQDN domain name, an IP address, an IP address and a port number, a URL, or the like.
  • the sharing information may further include information about the target CCF entity.
  • the information about the target CCF entity may be an identifier of the target CCF entity, an FQDN domain name, an IP address, an IP address and a port number, a URL, or the like.
  • the sharing indication information, the intra-domain target CCF entity information, or the target domain indication information may appear by being combined in a plurality of manners. This is not limited in this embodiment of this application.
  • the sharing information is sharing indication information; the sharing information is intra-domain target CCF entity information; the sharing information is target domain indication information; the sharing information includes sharing indication information and intra-domain target CCF entity information; the sharing information includes sharing indication information and target domain indication information; the sharing information includes intra-domain target CCF entity information and target domain indication information; or the sharing information includes sharing indication information, intra-domain target CCF entity information, and target domain indication information.
  • the information about the target CCF entity may appear independently, or may appear by being combined with the sharing indication information, the intra-domain target CCF entity information, or the target domain indication information. This is not limited in this embodiment of this application.
  • the trusted domain A is a PLMN network domain of the operator A
  • the CCF entity 1 is a CCF entity deployed in the Xi'an region by the operator A and is configured to manage an API provided by an AEF entity in the Xi'an region
  • the CCF entity 2 is a CCF entity deployed in the Ningxia region by the operator A and is configured to manage an API provided by an AEF entity in the Ningxia region.
  • the API publish entity 1 is the operator A in the Xi'an region
  • the API publish entity 2 is the operator A in the Ningxia region
  • the trusted domain B is a PLMN network domain of the operator B.
  • the API publish entity determines to publish the API 1 to the CCF entity 1.
  • the API publish entity determines to share the API 2 to the Ningxia region, and in this case, determines to publish the API 2 to the CCF entity 1; and the CCF entity 1 publishes the API 2 to the CCF entity 2.
  • the API publish entity determines to share the API 3 to the Ningxia region and the PLMN network domain of the operator B, and in this case, determines to publish the API 3 to the CCF entity 1; and the CCF entity 1 publishes the API 3 to the CCF entity 2 and the CCF entity 3.
  • the API publish entity 1 may determine not to specify sharing of the API 1, but specify that to-be-shared APIs include the API 2 and the API 3.
  • the API publish entity determines that the sharing information is sharing indication information.
  • the sharing indication information indicates to the first CCF entity (the CCF entity 1) to share the to-be-shared APIs (the API 2 and the API 3).
  • the CCF entity determines a target CCF entity for sharing the APIs.
  • the API publish entity determines that a target CCF entity for sharing the API 2 is the CCF entity 2, and determines that the sharing information includes intra-domain target CCF entity information.
  • the intra-domain target CCF entity information includes information about the CCF entity 2.
  • the API publish entity determines that a target CCF entity for sharing the API 2 is the CCF entity 2, and determines that the sharing information includes information about the target CCF entity, that is, includes information about the CCF entity 2.
  • the API publish entity determines that target CCF entities for sharing the API 3 includes the CCF entity 2 and the CCF entity 3, and determines that the sharing information includes intra-domain target CCF entity information and target domain indication information.
  • the intra-domain target CCF entity information includes information about the CCF entity 2, and the target domain indication information indicates the trusted domain B (a domain to which the CCF entity 3 belongs).
  • the API publish entity determines that target CCF entities for sharing the API 3 includes the CCF entity 2 and the CCF entity 3, and determines that the sharing information includes information about the target CCF entities (the CCF entity 2 and the CCF entity 3).
  • the trusted domain A is a PLMN network domain of the operator A
  • the CCF entity 1 is a top-level (which is also referred to as domain-bound) CCF entity deployed by the operator A and is configured to manage APIs in the entire network domain of the operator A and another CCF entity
  • the CCF entity 2 is a CCF entity deployed in the Ningxia region by the operator A and is configured to manage an API provided by an AEF entity in the Ningxia region.
  • the trusted domain B is a PLMN network domain of the operator B
  • the CCF entity 3 is a top-level (which is also referred to as domain-bound) CCF entity in the PLMN network domain of the operator B and is configured to manage APIs in the entire network domain of the operator B and another CCF entity in the domain.
  • the API publish entity 2 in the Ningxia region determines that the API 2 needs to be shared to the entire network of the operator A, and in this case, publishes the API 2 to the CCF entity 2; and the CCF entity 2 publishes the API 2 to the CCF entity 1.
  • the API publish entity 2 in the Ningxia region determines that the API 3 needs to be shared to the PLMN network domain of the operator A and the PLMN network domain of the operator B, and in this case, publishes the API 3 to the CCF entity 2; and the CCF entity 2 publishes the API 3 to the CCF entity 1 and the CCF entity 3. Then, the API publish entity 2 may determine that to-be-shared APIs are the API 2 and the API 3.
  • the API publish entity determines that the sharing information is sharing indication information, and the sharing indication information indicates the first CCF entity (the CCF entity 2) to share the to-be-shared APIs (the API 2 and the API 3).
  • the API publish entity determines that a target CCF entity for sharing the API 2 is the CCF entity 1, and determines that the sharing information includes intra-domain target CCF entity information.
  • the intra-domain target CCF entity information includes information about the CCF entity 1.
  • the API publish entity determines that a target CCF entity for sharing the API 2 is the CCF entity 1, and determines that the sharing information includes information about the target CCF entity, that is, includes information about the CCF entity 1.
  • the API publish entity determines that target CCF entities for sharing the API 3 include the CCF entity 1 and the CCF entity 3, and determines that the sharing information includes intra-domain target CCF entity information and target domain indication information.
  • the intra-domain target CCF entity information includes information about the CCF entity 1, and the target domain indication information indicates the trusted domain B (a domain to which the CCF entity 3 belongs).
  • the API publish entity determines that target CCF entities for sharing the API 3 include the CCF entity 1 and the CCF entity 3, and determines that the sharing information includes information about the target CCF entities (the CCF entity 2 and the CCF entity 3).
  • the API publish entity sends a first API publish request to the first CCF entity.
  • the API publish entity sends the first API publish request to the first CCF entity.
  • the first API publish request includes the information about the API and the sharing information of the API.
  • the first API publish request message may be a service API publish request (service API publish request), or a service API configuration request (service API configuration request).
  • one first API publish request includes information about one API and sharing information of the API.
  • a first API publish request includes information about the API 1 and sharing information of the API 1.
  • the first CCF entity shares the API 1 based on the sharing information of the API 1, and the to-be-shared API is the API 1.
  • one first API publish request includes information about a plurality of APIs and sharing information corresponding to each API.
  • a first API publish request includes information about the API 1 and sharing information of the API 1, information about the API 2 and sharing information of the API 2, and information about the API 3 and sharing information of the API 3.
  • the first CCF entity shares each API based on sharing information of each API.
  • the first CCF entity shares the API 1 based on the sharing information of the API 1, shares the API 2 based on the sharing information of the API 2, and shares the API 3 based on the sharing information of the API 3.
  • To-be-shared APIs are the API 1, the API 2, and the API 3.
  • one first API publish request includes information about a plurality of APIs and one piece of sharing information corresponding to the plurality of APIs.
  • a first API publish request includes information about the API 1, information about the API 2, information about the API 3, and sharing information, and the first CCF entity shares the API 1, the API 2, and the API 3 based on the sharing information.
  • To-be-shared APIs are the API 1, the API 2, and the API 3.
  • the information about the API may include the sharing information of the API, that is, the sharing information of the API may be used as an attribute of the API.
  • the information about the API may include an API identifier, an API type, and sharing information of the API.
  • the information about the API and the sharing information of the API may each be independent information. This is not limited in this embodiment of this application.
  • one first API publish request includes information about one API and sharing information of the one API
  • the technical solution in which the first API publish request includes information about one API and sharing information of the one API is also applicable to scenarios in which one first API publish request includes information about a plurality of APIs and sharing information corresponding to each API, and one first API publish request includes information about a plurality of APIs and one piece of sharing information corresponding to the plurality of APIs. Details are not described again in this embodiment of this application.
  • the first CCF entity receives the first API publish request.
  • the first CCF entity may store received information about the API.
  • the first CCF entity sends a first API publish response message to the API publish entity.
  • the first CCF entity sends the first API publish response message to the API publish entity.
  • the first API publish response message may include publish result indication information, to indicate that the API is successfully published or the API is unsuccessfully published.
  • the API publish response message may be a service API publish response (service API publish response), or a service API configuration response (service API configuration response).
  • the API publish entity receives the first API publish response message.
  • the API publish entity may indicate whether to share an API in an API publish request message that is to be sent to the first CCF entity, and more further, may further indicate a target CCF entity of the API.
  • the first CCF entity may share information about the API with another CCF entity based on the sharing information, so that the API is published to a plurality of CCF entities.
  • an API invoking entity can discover and obtain the API by using the plurality of CCF entities.
  • An embodiment of this application provides an API publish method. As shown in FIG. 5 , the method may include the following steps.
  • a first CCF entity determines a to-be-shared API and a target CCF entity of the to-be-shared API.
  • the first CCF entity determines the to-be-shared API and the target CCF entity of the to-be-shared API.
  • the target CCF entity may include a first target CCF entity and/or a second target CCF entity; and a domain to which the first target CCF entity belongs is the same as a domain to which the first CCF entity belongs, and a domain to which the second target CCF entity belongs is different from the domain to which the first CCF entity belongs.
  • the first CCF entity determines a to-be-shared API and a target CCF entity of the to-be-shared API based on a received first API publish request.
  • the first API publish request includes information about an API and sharing information of the API.
  • the first CCF entity determines the to-be-shared API based on the information about the API and the sharing information of the API.
  • the first CCF entity determines that the API indicated by the information about the API in the first API publish request is the to-be-shared API.
  • the first CCF entity determines the to-be-shared API based on the information about the API in the first API publish request according to a sixth preset rule.
  • the sixth preset rule may include determining the to-be-shared API based on a mapping relationship between commercial subscription information and a target CCF entity that is for publishing, or determining the to-be-shared API based on an API type, a type of an API, or a mapping relationship between an API type and a target CCF entity that is for publishing.
  • determining the to-be-shared API by the first CCF entity according to the sixth preset rule refer to the description of determining the target CCF entity of the to-be-shared API by the API publish entity according to the fifth preset rule in S401 in Embodiment 2. Details are not described herein again.
  • the first CCF entity may alternatively determine the to-be-shared API in another manner, for example, according to another preset rule. This is not limited in this embodiment of this application.
  • the first CCF entity determines the target CCF entity of the to-be-shared API based on sharing information.
  • the sharing information is sharing indication information
  • the first CCF entity determines a target CCF entity according to a first preset rule.
  • the first preset rule may include determining the target CCF entity for API sharing based on a mapping relationship between commercial subscription information and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a domain of a target CCF entity), or determining the target CCF entity for API sharing based on a mapping relationship between an API type and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a logical domain or a geographic region of a target CCF entity).
  • the first CCF entity may alternatively determine the target CCF entity of the to-be-shared API in another manner, for example, according to another preset rule. This is not limited in this embodiment of this application.
  • the sharing information includes intra-domain target CCF entity information (where, for example, the sharing information is intra-domain target CCF entity information, or the sharing information is sharing indication information and intra-domain target CCF entity information), and the first CCF entity determines a first target CCF entity based on the intra-domain target CCF entity information.
  • the intra-domain target CCF entity information includes information about the CCF entity 2, and the first CCF entity determines that the first target CCF entity includes the CCF entity 2.
  • the sharing information includes target domain indication information (where, for example, the sharing information is target domain indication information, or the sharing information includes sharing indication information and target domain indication information), and the first CCF entity determines a second target CCF entity based on the target domain indication information.
  • the target domain indication information is an identifier of a target domain
  • the first CCF entity determines the second target CCF entity in the target domain according to a second preset rule.
  • the second preset rule is that the target CCF entity is a domain-bound CCF entity in the target domain.
  • the target domain indication information is an identifier of the trusted domain B in FIG. 1A and FIG.
  • a domain-bound CCF entity in the trusted domain B is a CCF entity 3, and the first CCF entity determines that the second target CCF entity includes the CCF entity 3.
  • the target domain indication information includes an identifier of a target domain and inter-domain target CCF entity information, and the first CCF entity determines the second target CCF entity in the target domain based on the inter-domain target CCF entity information.
  • the identifier of the target domain is an identifier of the trusted domain B in FIG. 1A and FIG. 1B
  • the inter-domain target CCF entity information includes information about the CCF entity 3, and the first CCF entity determines that the second target CCF entity includes the CCF entity 3 in the trusted domain B.
  • the sharing information includes sharing indication information, intra-domain target CCF entity information, and target domain indication information; and the first CCF entity determines a first target CCF entity based on the intra-domain target CCF entity information, and determines a second target CCF entity based on the target domain indication information.
  • the sharing indication information is a numerical value, and the first CCF entity determines the target CCF entity based on a value of the sharing indication information. For example, if the sharing indication information is "00", it indicates that the to-be-shared API is shared with a CCF entity inside a domain to which the first CCF entity belongs, and the first CCF entity determines, as the target CCF entity, the CCF entity indicated by the intra-domain target CCF entity information.
  • the sharing indication information is "01" it indicates that the to-be-shared API is shared with a CCF entity outside a domain to which the first CCF entity belongs, and the first CCF entity determines, as the target CCF entity, the CCF entity indicated by the target domain indication information.
  • the sharing information includes information about a target CCF entity (where, for example, the sharing information is information about the target CCF entity, or the sharing information is sharing indication information and information about the target CCF entity, or the sharing information is sharing indication information, information about the target CCF entity, and the target domain indication information, or the sharing information is information about the target CCF entity and the target domain indication information), and the first CCF entity determines the target CCF entity based on the information about the target CCF entity.
  • the first CCF entity may determine, as a target CCF entity, a CCF entity indicated by the information about the target CCF entity, and the target CCF entity may include a first target CCF entity and/or a second target CCF entity.
  • the information about the target CCF entity includes information about a CCF entity 2, and the first CCF entity determines that the target CCF entity includes the CCF entity 2.
  • the information about the target CCF entity includes information about a CCF entity 3, and the first CCF entity determines that the target CCF entity includes the CCF entity 3.
  • the information about the target CCF entity includes information about a CCF entity 2 and a CCF entity 3, and the first CCF entity determines that the target CCF entity includes the CCF entity 2 and the CCF entity 3.
  • the first CCF entity determines a to-be-shared API according to a third preset rule; and further, the first CCF entity determines a target CCF entity according to a fourth preset rule.
  • the first CCF entity obtains the to-be-shared API from locally stored APIs according to the third preset rule, and determines the target CCF entity of the to-be-shared API in the locally stored APIs according to the fourth preset rule.
  • information about a locally stored API may be information about an API that is stored by the first CCF entity after the first CCF entity receives the information about the API from the API publish entity.
  • the information about the API may be obtained by the first CCF entity from a third API publish request message of the API publish entity.
  • the third preset rule may include determining the to-be-shared API based on a mapping relationship between commercial subscription information and a target CCF entity that is for publishing, or determining the to-be-shared API based on an API type or a mapping relationship between an API type and a target CCF entity that is for publishing.
  • determining the to-be-shared API by the first CCF entity according to the third preset rule refer to the description of determining the API publish range by the API publish entity according to the fifth preset rule in S401 in Embodiment 2. Details are not described herein again.
  • the first CCF entity may alternatively determine the to-be-shared API in another manner, for example, according to another preset rule. This is not limited in this embodiment of this application.
  • the fourth preset rule may include determining the target CCF entity based on a mapping relationship between commercial subscription information and a target CCF entity that is for publishing, or determining the target CCF entity based on an API type or a mapping relationship between an API type and a target CCF entity that is for publishing.
  • determining the target CCF entity by the first CCF entity according to the fourth preset rule refer to the description of determining the API publish range by the API publish entity according to the fifth preset rule in S401 in Embodiment 2. Details are not described herein again.
  • the first CCF entity may alternatively determine the target CCF entity in another manner, for example, according to another preset rule. This is not limited in this embodiment of this application.
  • the first CCF entity shares the information about the API with the target CCF entity.
  • the first CCF entity sends a second API publish request to the target CCF entity.
  • the second API publish request includes the information about the API.
  • the second API publish request message may be a service API publish request (service API publish request), or a service API configuration request (service API configuration request), or an interconnection API publish request (interconnection API publish request).
  • the first CCF entity may modify information about the to-be-shared API into global information, and when sharing the information about the API with the second target CCF entity, the first CCF entity adds the global information of the API. For example, the first CCF entity modifies a local identifier of the API into a global identifier, and modifies a local interface address of the API into a global address.
  • the first CCF entity may perform topology hiding on the to-be-shared API, to be specific, select an AEF entity as a topology hiding entry point for each to be-shared API, and replace interface information of the to-be-shared API with information about the topology hiding entry point, namely, the AEF entity.
  • the target CCF entity receives the information about the API.
  • the target CCF entity receives the second API publish request.
  • the second API publish request includes the information about the API, and the target CCF entity may store the received information about the API.
  • the target CCF entity sends a second API publish response message to the first CCF entity.
  • the target CCF entity sends the second API publish response message to the first CCF entity.
  • the second API publish response message may include publish result indication information, to indicate that the API is successfully published or the API is unsuccessfully published.
  • the API publish response message may be a service API publish response (service API publish response), or a service API configuration response (service API configuration response), or an interconnection API publish response (interconnection API publish response).
  • the first CCF entity receives the second API publish response message.
  • steps of Embodiment 2 and Embodiment 3 may alternatively be combined.
  • the first CCF entity determines the to-be-shared API and the target CCF entity of the to-be-shared API in the manner 1, that is, based on the received first API publish request, steps in Embodiment 2 and Embodiment 3 may be combined.
  • the first CCF entity may send the first API publish response message to the API publish entity in S404; or S404 is not performed, and in S505, the first CCF entity sends the first API publish response message to the API publish entity after receiving the second API publish response message.
  • each CCF entity may further send a notification message to an API invoking entity that subscribes to the API, to notify the API invoking entity that there is a new API or there is an API in which the API invoking entity is interested.
  • the first CCF entity may determine to share the API with another CCF entity, so that the API is published to a plurality of CCF entities.
  • the API invoking entity can discover and obtain the API by using the plurality of CCF entities.
  • An embodiment of this application provides an API publish method. As shown in FIG. 5A , the method may include the following steps.
  • An API publish entity determines information about an API and sharing information of the API.
  • the API publish entity determines the information about the API, where the API is a to-be-shared API, and determines the sharing information of the API.
  • the API publish entity may be an APF entity, or the API publish entity may be an APIMF entity.
  • the API publish entity may alternatively be another entity in a CAPIF system architecture. This is not limited in this embodiment of this application. In this embodiment of this application, an example in which the API publish entity is an APF entity is used for description.
  • the API publish entity may obtain the to-be-shared API and a target CCF entity of the to-be-shared API according to an instruction of a user.
  • the to-be-shared API and the target CCF entity of the to-be-shared API may be determined according to a preset rule. For a specific method, refer to the description in S401, and details are not described herein again.
  • the API publish entity determines whether to share the API. If the API publish entity determines to share the API, the API publish entity determines the sharing information of the API. The sharing information of the API is used to indicate the first CCF entity to share the API.
  • the sharing information may include sharing range indication information, and the sharing range indication information is used to indicate a sharing range of the API.
  • the sharing range of the API may include one or more CCF entities inside a domain to which the first CCF entity belongs, and/or CCF entities outside a domain to which the first CCF entity belongs.
  • a value of the sharing range indication information is 0, indicating that a sharing range of the API is one or more CCF entities inside the domain to which the first CCF entity belongs; a value of the sharing range indication information is 1, indicating that a sharing range of the API is one or more CCF entities outside the domain to which the first CCF entity belongs; or a value of the sharing range indication information is 2, indicating that a sharing range of the API includes: one or more CCF entities inside the domain to which the first CCF entity belongs and one or more CCF entities outside the domain to which the first CCF entity belongs.
  • the sharing information may further include information about the target CCF entity, including information about the CCF entities inside the domain to which the first CCF entity belongs, and/or information about the CCF entities outside the domain to which the first CCF entity belongs.
  • the information about the target CCF entity may be an identifier of the target CCF entity, an FQDN domain name, an IP address, an IP address and a port number, a URL, or the like.
  • the sharing range indication information indicates that the sharing range of the API is the CCF entities inside the domain to which the first CCF entity belongs
  • the information about the target CCF entity includes information about the CCF entities inside the domain to which the first CCF entity belongs.
  • the sharing range indication information indicates that the sharing range of the API is the CCF entities outside the domain to which the first CCF entity belongs
  • the information about the target CCF entity includes information about the CCF entities outside the domain to which the first CCF entity belongs.
  • the sharing range indication information indicates that the sharing range of the API is the CCF entities inside the domain to which the first CCF entity belongs and the CCF entities outside the domain to which the first CCF entity belongs
  • the information about the target CCF entity includes information about the CCF entities inside the domain to which the first CCF entity belongs and information about the CCF entities outside the domain to which the first CCF entity belongs.
  • the sharing information may further include target domain indication information, the target domain indication information is used to indicate a target domain to which the target CCF entity belongs, and the target domain is different from the domain to which the first CCF entity belongs.
  • the target domain indication information may be an identifier of the target domain, for example, a PLMN ID or a domain name (for example, domain.com).
  • the target domain indication information may include an identifier of the target domain and information about the target CCF entity.
  • the information about the target CCF entity may be an identifier of the target CCF entity, an FQDN domain name, an IP address, an IP address and a port number, a URL, or the like.
  • the sharing range of the API is a sharing range of the API.
  • the trusted domain A is a PLMN network domain of the operator A
  • the CCF entity 1 is a CCF entity deployed in the Xi'an region by the operator A and is configured to manage an API provided by an AEF entity in the Xi'an region
  • the CCF entity 2 is a CCF entity deployed in the Ningxia region by the operator A and is configured to manage an API provided by an AEF entity in the Ningxia region.
  • the API publish entity 1 is the operator A in the Xi'an region
  • the API publish entity 2 is the operator A in the Ningxia region
  • the trusted domain B is a PLMN network domain of the operator B.
  • the API publish entity determines to publish the API 1 to the CCF entity 1.
  • the API publish entity determines to share the API 2 to the Ningxia region, and in this case, determines to publish the API 2 to the CCF entity 1; and the CCF entity 1 publishes the API 2 to the CCF entity 2.
  • the API publish entity determines to share the API 3 to the Ningxia region and the PLMN network domain of the operator B, and in this case, determines to publish the API 3 to the CCF entity 1; and the CCF entity 1 publishes the API 3 to the CCF entity 2 and the CCF entity 3.
  • the API publish entity 1 may determine not to specify sharing of the API 1, but specify that to-be-shared APIs include the API 2 and the API 3.
  • the API publish entity 1 determines sharing information of the API 2 and the API 3.
  • the API publish entity determines that the sharing information is sharing range indication information.
  • the sharing range indication information indicates that a sharing range of the API 2 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs.
  • the first CCF entity determines a target CCF entity for sharing the API 2, and the target CCF entity is the CCF entities inside the domain (the trusted domain A) to which the first CCF entity belongs.
  • the sharing range indication information indicates that a sharing range of the API 3 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs and CCF entities outside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs.
  • the first CCF entity determines a target CCF entity for sharing the API 3, and the target CCF entity includes the CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs and the CCF entities outside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs.
  • the API publish entity determines that the sharing information is sharing range indication information and information about the target CCF entity.
  • the API publish entity determines that sharing information corresponding to the API 2 includes sharing range indication information, indicating that a sharing range of the API 2 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs; and the information about the target CCF entity includes information about the CCF entity 2.
  • the API publish entity determines that sharing information corresponding to the API 3 includes sharing range indication information, indicating that a sharing range of the API 3 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs and CCF entities outside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs; and the information about the target CCF entity includes information about the CCF entity 2 and information about the CCF entity 3.
  • the API publish entity determines that the sharing information includes target domain indication information. For example, the API publish entity (the API publish entity 1) determines that sharing information corresponding to the API 3 includes sharing range indication information, indicating that a sharing range of the API 3 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs and CCF entities outside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs; and the information about the target CCF entity includes information about the CCF entity 2, and the target domain indication information includes information about the trusted domain B.
  • sharing range indication information indicating that a sharing range of the API 3 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs and CCF entities outside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs
  • the information about the target CCF entity includes information about the CCF entity 2
  • the target domain indication information includes information about the trusted domain B.
  • the API publish entity sends a first API publish request to the first CCF entity.
  • the API publish entity sends the first API publish request to the first CCF entity.
  • the first API publish request includes the information about the API and the sharing information of the API. For detailed description, refer to S402, and details are not described herein again.
  • the first CCF entity receives the first API publish request.
  • the first CCF entity receives the first API publish request.
  • the first API publish request includes the information about the API and the sharing information of the API.
  • the first CCF entity determines the to-be-shared API based on the information about the API; and determines that an API indicated by the information about the API in the first API publish request is the to-be-shared API. For example, if the information about the API includes the information about the API 2 and the information about the API 3, the first CCF entity determines that the to-be-shared API includes the API 2 and the API 3.
  • the first CCF entity determines the target CCF entity of the to-be-shared API based on the sharing information of the API.
  • the target CCF entity may include a first target CCF entity and/or a second target CCF entity, a domain to which the first target CCF entity belongs is the same as the domain to which the first CCF entity belongs, and a domain to which the second target CCF entity belongs is different from the domain to which the first CCF entity belongs.
  • the sharing information is sharing range indication information
  • the sharing range indication information indicates a sharing range of the API
  • the sharing range of the API includes one or more CCF entities inside the domain to which the first CCF entity belongs and/or one or more CCF entities outside the domain to which the first CCF entity belongs.
  • the first CCF entity determines the sharing range of the API according to the sharing range indication information. If the sharing range is one or more CCF entities inside the domain to which the first CCF entity belongs, the first CCF entity determines the target CCF entity in the CCF entities inside the domain to which the first CCF entity belongs.
  • the first CCF entity determines the target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs.
  • the sharing range includes one or more CCF entities inside the domain to which the first CCF entity belongs and one or more CCF entities outside the domain to which the first CCF entity belongs, the first CCF entity determines the first target CCF entity in the CCF entities inside the domain to which the first CCF entity belongs, and determines the second target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs, and the target CCF entity includes the first target CCF entity and the second target CCF entity.
  • the first CCF entity determines, according to a seventh preset rule, the target CCF entity in the CCF entities inside the domain to which the first CCF entity belongs.
  • the target CCF entity is the first target CCF entity.
  • the sharing range of the to-be-shared API is one or more CCF entities outside the domain to which the first CCF entity belongs, the first CCF entity determines, according to an eighth preset rule, the target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs.
  • the target CCF entity is the second target CCF entity.
  • the first CCF entity determines, according to a seventh preset rule, the first target CCF entity in the CCF entities inside the domain to which the first CCF entity belongs, and determines, according to an eighth preset rule, the second target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs.
  • the first CCF entity receives the first API publish request from the API publish entity (the API publish entity 1).
  • the first API publish request includes information about the API 2 and corresponding sharing range indication information, and a value of the sharing range indication information is 0, indicating that a sharing range of the API 2 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity belongs.
  • the first CCF entity determines the target CCF entity in the trusted domain A according to the seventh preset rule.
  • the seventh preset rule is that the target CCF entity includes all CCF entities inside the domain (trusted domain A) to which the first CCF entity belongs.
  • the first CCF entity determines that the target CCF entity includes the CCF entity 2.
  • the seventh preset rule is a mapping relationship between commercial subscription information and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a domain of a target CCF entity), an API type, a mapping relationship between an API type and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a logical domain or a geographic region of a target CCF entity), or the like.
  • the seventh preset rule may be sharing an API of an IoT type with the CCF entity 2.
  • the first CCF entity determines to share the API 2 with the CCF entity 2, that is, the target CCF entity includes the CCF entity 2.
  • the first CCF entity may alternatively determine the target CCF entity in another manner, for example, according to another preset rule. This is not limited in this embodiment of this application.
  • the first API publish request further includes information about the API 3 and corresponding sharing range indication information, and a value of the sharing range indication information is 2, indicating that a sharing range of the API 3 includes one or more CCF entities inside the domain to which the first CCF entity belongs and one or more CCF entities outside the domain to which the first CCF entity belongs.
  • the first CCF entity determines, according to the seventh preset rule, the first target CCF entity inside the domain to which the first CCF entity belongs, and determines, according to the eighth preset rule, the second target CCF entity outside the domain to which the first CCF entity belongs.
  • the eighth preset rule includes a mapping relationship between commercial subscription information and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a domain of a target CCF entity), an API type, a mapping relationship between an API type and a target CCF entity that is for publishing (which may also be understood as a mapping relationship between an API type and a logical domain or a geographic region of a target CCF entity), or the like.
  • an operator B and an operator A have a subscription for sharing an API for use. To be specific, the operator B can obtain and use any API of the operator A.
  • the first CCF entity determines, based on subscription information for sharing an API for use between the operator A and the operator B, to publish the API to a trusted domain (for example, a domain corresponding to the CCF entity 3 in FIG. 1A and FIG. 1B ) corresponding to the operator B.
  • the eighth preset rule may be sharing an API of a V2X type to the CCF entity 3.
  • the first CCF entity determines to share the API 3 with the CCF entity 3.
  • the first CCF entity may alternatively determine the second target CCF entity in another manner, for example, according to another preset rule. This is not limited in this embodiment of this application.
  • the seventh preset rule and the eighth preset rule may be rules corresponding to each other.
  • the seventh preset rule is determining a target CCF entity based on an API type
  • the eighth preset rule is determining a target CCF entity based on the API type.
  • the seventh preset rule and the eighth preset rule may alternatively be corresponding rules not corresponding to each other.
  • the seventh preset rule is determining a target CCF entity based on an API type
  • the eighth preset rule is determining a target CCF entity based on a mapping relationship between commercial subscription information and a target CCF entity that is for publishing. This is not limited in this embodiment of this application.
  • the sharing information includes sharing range indication information and information about the target CCF entity.
  • the sharing range indication information indicates that a sharing range of the API is one or more CCF entities inside the domain to which the first CCF entity belongs, the first CCF entity determines, as the target CCF entity, a CCF entity indicated by the information about the target CCF entity, and the target CCF entity is the CCF entity inside the domain to which the first CCF entity belongs.
  • sharing information corresponding to the API 2 includes sharing range indication information, indicating that a sharing range of the API 2 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs; information about the target CCF entity includes information about the CCF entity 2; and the first CCF entity determines the CCF entity 2 as the target CCF entity.
  • the sharing range indication information indicates that a sharing range of the API is one or more CCF entities outside the domain to which the first CCF entity belongs, the first CCF entity determines, as the target CCF entity, a CCF entity indicated by the information about the target CCF entity, and the target CCF entity is the CCF entity outside the domain to which the first CCF entity belongs.
  • sharing information corresponding to an API 4 includes sharing range indication information, indicating that a sharing range of the API 4 is one or more CCF entities outside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs; the information about the target CCF entity includes information about the CCF entity 3; and the first CCF entity determines the CCF entity 3 as the target CCF entity.
  • the sharing range indication information indicates that a sharing range of the API is one or more CCF entities inside the domain to which the first CCF entity belongs and CCF entities outside the domain to which the first CCF entity belongs; the first CCF entity determines, as the target CCF entity, a CCF entity indicated by the information about the target CCF entity; and the target CCF entity includes the CCF entity inside the domain to which the first CCF entity belongs and the CCF entity outside the domain to which the first CCF entity belongs.
  • sharing information corresponding to the API 3 includes sharing range indication information, indicating that a sharing range of the API 3 is one or more CCF entities inside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs and CCF entities outside the domain (the trusted domain A) to which the first CCF entity (the CCF entity 1) belongs;
  • the information about the target CCF entity includes information about the CCF entity 2 and information about the CCF entity 3;
  • the first CCF entity determines the CCF entity 2 as the first target CCF entity, determines the CCF entity 3 as the second target CCF entity;
  • the target CCF entity includes the first target CCF entity and the second target CCF entity.
  • the sharing information further includes target domain indication information, and the target domain indication information is used to indicate a target domain to which the target CCF entity belongs.
  • the first CCF entity determines the second target CCF entity in one or more CCF entities inside the target domain.
  • the target domain indication information is an identifier of the target domain
  • the first CCF entity determines the second target CCF entity in the target domain according to a second preset rule.
  • the second preset rule is that the target CCF entity is a domain-bound CCF entity in the target domain.
  • the target domain indication information is an identifier of the trusted domain B in FIG. 1A and FIG. 1B
  • a domain-bound CCF entity in the trusted domain B is the CCF entity 3
  • the first CCF entity determines that the second target CCF entity includes the CCF entity 3.
  • the target domain indication information includes an identifier of the target domain and inter-domain target CCF entity information, and the first CCF entity determines the second target CCF entity in the target domain based on the inter-domain target CCF entity information.
  • the identifier of the target domain is an identifier of the trusted domain B in FIG. 1A and FIG. 1B
  • the inter-domain target CCF entity information includes information about the CCF entity 3
  • the first CCF entity determines that the second target CCF entity includes the CCF entity 3 in the trusted domain B.
  • information about the CCF entity outside the domain to which the first CCF entity belongs may be indicated by the information about the target CCF entity that is in the sharing information, or may be indicated by the target domain indication information in the sharing information. This is not limited in this embodiment of this application.
  • the first CCF entity shares the information about the API with the target CCF entity.
  • the information about the API with the target CCF entity refer to the description in S502, and details are not described herein again.
  • the target CCF entity receives the information about the API.
  • the target CCF entity sends a second API publish response message to the first CCF entity.
  • the second API publish response message to the first CCF entity, refer to the description in S504, and details are not described herein again.
  • the first CCF entity receives the second API publish response message.
  • each CCF entity may further send a notification message to an API invoking entity that subscribes to the API, to notify the API invoking entity that there is a new API or there is an API in which the API invoking entity is interested.
  • the first CCF entity may determine, according to indication information of the API publish entity, to share the API with another CCF entity, so that the API is published to a plurality of CCF entities.
  • the API invoking entity can discover and obtain the API by using the plurality of CCF entities.
  • the API publish entity and the CCF entity include corresponding hardware structures and/or software modules for performing the functions.
  • a person skilled in the art should be easily aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps may be implemented by hardware or a combination of hardware and computer software in this application. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.
  • function module division may be performed on the API publish entity and the CCF entity based on the foregoing method examples.
  • function modules may be divided corresponding to functions, or two or more functions may be integrated into one processing module.
  • the integrated module may be implemented in a form of hardware, or may be implemented in a form of a software function module.
  • module division is an example, and is merely a logical function division. In actual implementation, another division manner may be used. A description is made below by using an example in which function modules are divided corresponding to functions.
  • FIG. 6 is a schematic structural diagram of an apparatus 600 according to an embodiment of this application.
  • the apparatus 600 may be a CCF entity, and can implement a function of the first CCF entity in the methods provided in the embodiments of this application.
  • the apparatus 600 may be an apparatus that can support a CCF entity in implementing a function of the first CCF entity in the methods provided in the embodiments of this application.
  • the apparatus 600 may be a hardware structure, a software module, or a combination of a hardware structure and a software module.
  • the apparatus 600 may be implemented by a chip system. In this embodiment of this application, the chip system may include a chip, or may include a chip and another discrete component. As shown in FIG. 6 , the apparatus 600 includes a processing module 601 and a sending module 602.
  • the processing module 601 is configured to determine a to-be-shared API.
  • the sending module 602 is configured to share information about the to-be-shared API with a target CCF entity of the to-be-shared API.
  • the apparatus 600 further includes a receiving module 603.
  • the receiving module 603 is configured to receive a first API publish request.
  • the first API publish request includes information about an API and sharing information of the API.
  • the processing module 601 is specifically configured to determine the to-be-shared API based on the first API publish request.
  • the processing module 601 is further configured to determine the target CCF entity based on the sharing information.
  • the sharing information includes the at least one of sharing indication information, information about the target CCF entity, or target domain indication information; and the sharing indication information is used to indicate that the API is to be shared, the target domain indication information is used to indicate a target domain, and the target domain is different from a domain to which the first CCF entity belongs.
  • the processing module 601 if the sharing information includes sharing indication information, the processing module 601 is configured to determine the target CCF entity according to a first preset rule; or if the sharing information includes information about the target CCF entity, the processing module 601 is configured to determine the target CCF entity based on the information about the target CCF entity; or if the sharing information includes the target domain indication information, the processing module 601 is configured to determine a second target CCF entity based on the target domain indication information.
  • the second target CCF entity is one or more CCF entities in the target CCF entity, and a domain to which the second target CCF entity belongs is different from the domain to which the first CCF entity belongs.
  • the sharing information includes sharing range indication information; and the sharing range indication information is used to indicate a sharing range of the API.
  • the processing module 601 is configured to determine the target CCF entity in the CCF entities inside the domain to which the first CCF entity belongs.
  • the processing module 601 is configured to determine the target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs.
  • the processing module 601 is configured to: determine a first target CCF entity in the CCF entities inside the domain to which the first CCF entity belongs, and determine a second target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs, where the target CCF entity includes the first target CCF entity and the second target CCF entity.
  • the first target CCF entity is one or more CCF entities in the target CCF entity, and a domain to which the first target CCF entity belongs is the same as the domain to which the first CCF entity belongs.
  • the second target CCF entity is one or more CCF entities in the target CCF entity, and a domain to which the second target CCF entity belongs is different from the domain to which the first CCF entity belongs.
  • the sharing information further includes target domain indication information, and the target domain indication information is used to indicate a target domain to which the target CCF entity belongs.
  • determining, by the processing module 601, the target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs specifically includes: determining, by the processing module 601, the target CCF entity in one or more CCF entities inside the target domain.
  • determining, by the processing module 601, a second target CCF entity in the CCF entities outside the domain to which the first CCF entity belongs specifically includes: determining, by the processing module 601, the second target CCF entity in one or more CCF entities inside the target domain.
  • the processing module 601 is specifically configured to determine the second target CCF entity in the target domain according to a second preset rule; or if the target domain indication information includes an identifier of the target domain and inter-domain target CCF entity information, the processing module 601 is specifically configured to determine the second target CCF entity in the target domain based on the inter-domain target CCF entity information.
  • the processing module 601 is specifically configured to determine the to-be-shared API according to a third preset rule.
  • the processing module 601 is specifically configured to determine the target CCF entity according to a fourth preset rule.
  • the target CCF entity includes a first target CCF entity and/or a second target CCF entity.
  • a domain to which the first target CCF entity belongs is the same as the domain to which the first CCF entity belongs, and a domain to which the second target CCF entity belongs is different from the domain to which the first CCF entity belongs.
  • sharing, by the sending module 602, information about the to-be-shared API with a target CCF entity of the to-be-shared API specifically includes: sharing, by the sending module 602, the information about the to-be-shared API with the second target CCF entity, where the information about the to-be-shared API is global information.
  • the information about the to-be-shared API includes interface information of the to-be-shared API, and the interface information is information about a topology hidden entry point.
  • the processing module 601 may be configured to perform at least S301 in FIG. 3 , S501 in FIG. 5 , or S603 in FIG. 5A , and/or perform another step described in this application.
  • the sending module 602 may be configured to perform at least S302 in FIG. 3 , S404 in FIG. 4 , S502 in FIG. 5 , or S604 in FIG. 5A , and/or perform another step described in this application.
  • the receiving module 603 may be configured to perform at least one S403 in FIG. 4 , S505 in FIG. 5 , or S603 and S607 in FIG. 5A , and/or perform another step described in this application. Details are not described herein again.
  • FIG. 8 is a schematic structural diagram of an apparatus 700 according to an embodiment of this application.
  • the apparatus 700 may be an API publish entity, and can implement a function of the API publish entity in the methods provided in the embodiments of this application.
  • the apparatus 700 may alternatively be an apparatus that can support an API publish entity in implementing a function of the API publish entity in the methods provided in the embodiments of this application.
  • the apparatus 700 may be a hardware structure, a software module, or a combination of a hardware structure and a software module.
  • the apparatus 700 includes a processing module 701 and a sending module 702.
  • the processing module 701 is configured to determine information about an API and sharing information of the API.
  • the sharing information is used to indicate to a first CCF entity to share the API.
  • the sending module 702 is configured to send a first API publish request to the first CCF entity.
  • the first API publish request includes the information about the API and the sharing information of the API.
  • the sharing information includes at least one of sharing indication information, information about a target CCF entity, or target domain indication information; and the sharing indication information is used to indicate that the API is to be shared, the target domain indication information is used to indicate a target domain, and the target domain is different from a domain to which the first CCF entity belongs.
  • the sharing information includes sharing range indication information; and the sharing range indication information is used to indicate a sharing range of the API.
  • the sharing information further includes target domain indication information, and the target domain indication information is used to indicate a target domain to which the target CCF entity belongs.
  • the target domain indication information is an identifier of the target domain; or the target domain indication information includes an identifier of the target domain and inter-domain target CCF entity information, and the inter-domain target CCF entity information is used to indicate information about the target CCF entity of the to-be-shared API in the target domain.
  • the processing module 701 may be configured to perform at least S401 in FIG. 4 , or S601 in FIG. 5A , and/or perform another step described in this application.
  • the sending module 702 The sending module 702 may be configured to perform at least S402 in FIG. 4 , S602 in FIG. 5A , and/or perform other steps described in this application. Details are not described herein again.
  • the apparatus 600 or the apparatus 700 may be presented in a form of integrating each function module in the apparatus.
  • the "module” herein may be a specific ASIC, a circuit, a processor executing one or more software or firmware programs, a storage device, an integrated logic circuit, and/or another device that can provide the foregoing functions.
  • the apparatus 600 or the apparatus 700 may use a form shown in FIG. 2 .
  • the processing module 601 in FIG. 6 or FIG. 7 or the processing module 701 in FIG. 8 may be implemented by using the processor 201 or the processor 208; the sending module 602 in FIG. 6 or FIG. 7 , the receiving module 603 in FIG. 7 , or the sending module 702 in FIG. 8 may be implemented by using the communications interface 204.
  • the apparatus provided in the embodiments of this application may be applied to the foregoing API publish method. Therefore, for technical effects that can be obtained by the apparatus, refer to the foregoing method embodiments. Details are not described herein again.
  • the program may be stored in a computer-readable storage medium.
  • the computer-readable storage medium includes a ROM, a RAM, an optical disc, and the like.
  • An embodiment of this application further provides a storage medium.
  • the storage medium may include a memory 203.
  • All or some of the foregoing embodiments may be implemented by software, hardware, firmware, or any combination thereof.
  • a software program is used to implement the embodiments, the embodiments may be implemented completely or partially in a form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the procedure or functions according to the embodiments of this application are all or partially generated.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable apparatuses.
  • the computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (digital subscriber line, DSL)) or wireless (for example, infrared, radio, or microwave) manner.
  • the computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD)), a semiconductor medium (for example, a solid-state drive (solid state disk, SSD)), or the like.
  • a magnetic medium for example, a floppy disk, a hard disk, or a magnetic tape
  • an optical medium for example, a digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid-state drive (solid state disk, SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)
EP19881835.3A 2018-11-05 2019-08-02 Api publishing method and device Active EP3863312B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201811309187 2018-11-05
CN201910033213.7A CN111148076B (zh) 2018-11-05 2019-01-14 一种api发布方法及装置
PCT/CN2019/099041 WO2020093742A1 (zh) 2018-11-05 2019-08-02 一种api发布方法及装置

Publications (3)

Publication Number Publication Date
EP3863312A1 EP3863312A1 (en) 2021-08-11
EP3863312A4 EP3863312A4 (en) 2021-10-13
EP3863312B1 true EP3863312B1 (en) 2023-04-26

Family

ID=70516629

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19881835.3A Active EP3863312B1 (en) 2018-11-05 2019-08-02 Api publishing method and device

Country Status (4)

Country Link
US (1) US11533596B2 (zh)
EP (1) EP3863312B1 (zh)
CN (1) CN111148076B (zh)
WO (1) WO2020093742A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022067736A1 (zh) * 2020-09-30 2022-04-07 华为技术有限公司 一种通信方法及装置
CN114915430B (zh) * 2021-01-28 2024-07-12 中国移动通信有限公司研究院 实现动态能力开放的方法、装置、通信设备及存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101894919B1 (ko) * 2014-10-28 2018-09-05 콘비다 와이어리스, 엘엘씨 기본 네트워크들과의 서비스 계층 과금 상관을 위한 방법들 및 장치들
CN107836007B (zh) * 2015-07-31 2023-04-11 难题知识产权有限责任公司 发现并发布api信息
EP3366026A4 (en) * 2015-10-20 2018-09-19 ZTE Corporation Exposing services using network interfaces
EP3264727B1 (en) * 2016-07-01 2024-05-08 Nokia Solutions and Networks Oy Database, network entity and method for the support of user location change reporting
US10942794B2 (en) * 2017-05-02 2021-03-09 Samsung Electronics Co.. Ltd. Method and apparatus for providing network-based northbound application programming interface in a wireless communication system
EP3753234A4 (en) * 2018-04-06 2021-04-14 Samsung Electronics Co., Ltd. PROCESS AND DEVICE FOR CARRYING OUT BOARDING

Also Published As

Publication number Publication date
EP3863312A1 (en) 2021-08-11
WO2020093742A1 (zh) 2020-05-14
US20210258753A1 (en) 2021-08-19
EP3863312A4 (en) 2021-10-13
CN111148076B (zh) 2023-03-24
US11533596B2 (en) 2022-12-20
CN111148076A (zh) 2020-05-12

Similar Documents

Publication Publication Date Title
US11805478B2 (en) Network slice selection method, device, and system
US20210218585A1 (en) Local area network communication method, device, and system
EP3592012B1 (en) Subscription update method, device and system
US11540244B2 (en) MEC information obtaining method and apparatus
JP7027558B2 (ja) 認可取り消しの方法および装置
US12081403B2 (en) Communication method and apparatus
US11070433B2 (en) Network function NF management method and NF management device
US10897699B2 (en) Subscription update method, device, and system
WO2020147663A1 (zh) 一种令牌处理方法及装置
US20220263672A1 (en) Data Sharing Method, Device, and System
US20230359515A1 (en) Method and Apparatus for Application Programming Interface Management
US11533596B2 (en) API publish method and apparatus
EP3682619B1 (en) Service layer message templates in a communications network
US11726848B2 (en) API topology hiding method, device, and system
CN112105026B (zh) 一种授权控制的方法、装置以及存储介质
TWI461023B (zh) 用於管理物件中定義條件之方法

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210505

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

A4 Supplementary search report drawn up and despatched

Effective date: 20210909

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 8/36 20180101ALI20210903BHEP

Ipc: H04L 29/08 20060101AFI20210903BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20220705

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602019028185

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0004500000

Ipc: G06F0008360000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20221202

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/50 20180101ALI20221118BHEP

Ipc: H04W 4/40 20180101ALI20221118BHEP

Ipc: H04L 67/00 20220101ALI20221118BHEP

Ipc: G06F 8/36 20180101AFI20221118BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602019028185

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1563328

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230515

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230524

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20230426

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1563328

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230426

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230828

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230826

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230727

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602019028185

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

26N No opposition filed

Effective date: 20240129

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230802

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230802

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230831

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230426

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230802

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230802

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230831

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240702

Year of fee payment: 6

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240701

Year of fee payment: 6