CN108156122B

CN108156122B - Method, system and equipment for introducing capability of capability open platform

Info

Publication number: CN108156122B
Application number: CN201611110078.4A
Authority: CN
Inventors: 吴洪林; 严飞军; 施平
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Hangzhou Information Technology Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Hangzhou Information Technology Co Ltd
Priority date: 2016-12-06
Filing date: 2016-12-06
Publication date: 2021-08-13
Anticipated expiration: 2036-12-06
Also published as: CN108156122A

Abstract

The invention discloses a capacity introduction method of a capacity open platform, which comprises the following steps: receiving a capability product calling request sent by an application development terminal, wherein the capability product calling request carries first capability Token (Token) information; receiving a verification request of the first capacity Token information sent by a third party capacity open platform; and when the verification of the first capacity Token information is determined to pass based on the verification request of the first capacity Token information, sending effective information of the first capacity Token information to the third party capacity open platform, and synchronously storing calling record information of the first capacity Token information, which is called by the application development end, in the effective information. The invention also discloses a capability introduction system of the capability open platform, a third party capability open platform and an application development terminal.

Description

Method, system and equipment for introducing capability of capability open platform

Technical Field

The invention relates to a capability introduction technology, in particular to a capability introduction method, a system and equipment of a capability open platform.

Background

Currently, many internet enterprises have established their own capability opening platform for opening their own capabilities (EA) to an Application (AP) opening terminal, such as Tencent opening platform, Alibara opening platform, Baidu opening service platform, and the like. However, in the prior art, a capability open platform established by an internet enterprise is usually a capability open platform which completely introduces capabilities provided by a third party capability open platform (EP) into itself, and is integrated with the capabilities of the enterprise to be opened to an application development end. The adoption of the capacity introduction mode to provide the capacity service for the application development end has the following disadvantages:

1) the access mode is more single

In the prior art, an internet open platform only provides a single capability access mode. For example, the capability of the third-party capability open platform can only be completely introduced, and then the capability of the third-party capability open platform is integrated into the capability open platform of the enterprise itself, and is encapsulated into an Application Programming Interface (API), and is provided to the Application Development end in the form of a Software Development Kit (SDK), and when the Application Development end calls the capability of the third-party capability open platform, both the service flow and the authentication flow of the capability are completed on the internet capability open platform, and a corresponding capability access mode cannot be provided according to different capability characteristics in the third-party capability open platform. In order to cooperate with a single capability access mode of a capability open platform established by an internet enterprise, the third-party capability open platform usually needs to greatly modify the capability of the platform, so that the integration period of the third-party capability open platform into the internet capability open platform is very long.

2) Not applicable to the telecommunications industry

Since the capability interface of the telecommunication industry is often numerous in parameters, the application development end is complex to invoke the capability. The single capability access mode of the internet capability open platform in the prior art is obviously not applicable to the capability introduction of the telecommunication industry.

Disclosure of Invention

In view of this, embodiments of the present invention are intended to provide a method, a system, and a device for introducing capabilities of a capability openness platform, which can open corresponding capability access modes according to different capability characteristics in a third-party capability openness platform, and can complete capability introduction without greatly modifying capabilities of the third-party capability openness platform.

The technical scheme of the embodiment of the invention is realized as follows:

according to an aspect of the embodiments of the present invention, there is provided a capability introduction method for a capability open platform, the method including:

receiving an ability product calling request sent by an application development terminal, wherein the ability product calling request carries first ability Token information;

receiving a verification request of the first capacity Token information sent by a third party capacity open platform;

and when the verification of the first capacity Token information is determined to pass based on the verification request of the first capacity Token information, sending effective information of the first capacity Token information to the third-party capacity open platform, and synchronously storing calling record information of the first capacity Token information, which is called by the application development end, in the effective information.

In the above solution, before the receiving of the capability product invocation request sent by the application development end, the method further includes:

receiving an acquisition request of the ability Token information sent by the application development terminal;

based on the capability identification code ID in the acquisition request, when determining that the capability Token information belongs to a first capability, authenticating a capability product corresponding to the capability Token information and an application developed by using the capability product, and when determining that the capability product and the application pass authentication, generating the first capability Token information;

and sending the first capability Token information to the application development end.

In the foregoing solution, before the sending the first capability Token information to the application development end, the method further includes:

generating Uniform Resource Locator (URL) information of the third-party capability open platform based on the first capability Token information;

and sending the first ability Token information and the URL information to the application development end, wherein the first ability Token information and the URL information are used for sending a calling request of an ability product to the third party ability open platform by the application development end.

receiving a capacity cooperation request sent by a third-party capacity open platform;

checking the capacity cooperation information provided by the third-party capacity open platform based on the capacity cooperation request;

when the capability cooperation information is determined to pass the verification, generating a first ID;

and synchronously storing the first ID and the capability cooperation information, and sending a notification of successful application to the third-party capability open platform.

In the foregoing solution, after the notification of successful application is sent to the third party capability openness platform, the method further includes:

receiving a capacity online request sent by a third party capacity open platform;

checking the capacity online information provided by the third-party capacity open platform based on the capacity online request;

when the capability online information is confirmed to pass the verification, generating a second ID;

and synchronously storing the second ID and the capability online information, and sending a notification of capability online success to the third-party capability open platform.

In the foregoing solution, after the notification that the capability online successfully is sent to the third-party capability openness platform, the method further includes:

receiving a capability product online request sent by the third party capability open platform;

auditing the on-line information of the capacity product provided by the third party capacity open platform based on the on-line request of the capacity product;

when the online information of the capacity product is confirmed to pass the verification, a third ID is generated;

and synchronously storing the third ID and the online information of the capacity product, and sending a notification that the capacity product is successfully online to the third-party capacity open platform.

According to another aspect of the embodiments of the present invention, there is provided a capability introduction method for a capability open platform, the method including:

receiving a capability access request sent by an application development terminal;

generating capacity access Token information based on the capacity access request, and sending the capacity access Token information to a third-party capacity open platform for which the capacity access request is directed;

and receiving a verification result of the ability access Token information sent by the third party ability open platform, and switching a current interface to an interface of the third party ability open platform when the verification of the ability access Token information is determined to be passed based on the verification result of the ability access Token information, so that the application development end can call the ability in the third party ability open platform.

In the foregoing solution, after the switching the current interface to the interface of the third party capability open platform, the method further includes:

and synchronously storing the calling record information of the ability access Token information called by the application development end.

According to still another aspect of the embodiments of the present invention, there is provided a capability introduction method for a capability open platform, the method including:

when the first ability Token information is not locally stored, sending a verification request of the first ability Token information to an ability introducing system, and receiving a verification result sent by the ability introducing system;

and determining that the first ability Token information passes verification according to the verification result, and sending a notification of successful calling of an ability product to the application development end when the term of the first ability Token information is in the valid term.

In the above scheme, after sending the notification that the capability product invocation is successful to the application development end, the method further includes:

and synchronously storing the calling record information called by the application development terminal in the valid period of the first ability Token information to the ability introduction system.

sending a capability cooperation request to the capability introduction system, and receiving a capability cooperation notification sent by the capability introduction system based on the capability cooperation request;

when the capability cooperation request is determined to be successful according to the capability cooperation notification, sending a capability online request to the capability introduction system, and receiving a capability online notification sent by the capability introduction system based on the capability online request;

when the capability on-line request is determined to be successful according to the capability on-line notification, sending a capability product on-line request to the capability introduction system, and receiving a capability product on-line notification sent by the capability introduction system based on the capability product on-line request;

and when the capability product is determined to be successfully online according to the online notification of the capability product, calling the capability product through the capability introduction system supply and use development end.

receiving capacity access Token information generated by a capacity access request sent by an application development terminal by a capacity introduction system;

when the verification of the ability access Token information is determined to pass, sending a notification of successful verification of the ability access Token information to the ability introduction system;

and when determining that the capability introduction system switches the current interface to the interface of the third-party capability open platform according to the notification that the capability access Token information is successfully verified, receiving a capability product calling request sent by the application development end through the third-party capability open platform.

In the foregoing solution, after receiving the capability product invocation request sent by the application development terminal through the third party capability development platform, the method further includes:

and synchronously storing the calling record information of the ability access Token information called by the application development end to the ability introduction system.

sending an acquisition request of the ability Token information to an ability introduction system, wherein the acquisition request of the ability Token information carries an ability ID;

receiving first capability Token information generated by the capability introduction system based on the capability ID;

and calling the capability product of the third-party capability open platform according to the first capability Token information.

In the foregoing solution, before the capability product of the third party capability open platform is called according to the first capability Token information, the method further includes:

receiving URL information of a third-party capacity open platform generated by the capacity introduction system based on the first capacity Token information;

and calling the capability product of the third-party capability open platform according to the first capability Token information and the URL information of the third-party capability open platform.

sending a capability access request to a capability introduction system;

and when determining that the capability introduction system switches the current interface to the interface of the third-party capability open platform based on the capability access request, calling the capability product of the third-party capability open platform through the interface of the third-party capability open platform.

According to still another aspect of embodiments of the present invention, there is provided a capability introduction system of a capability open platform, the system including:

the access subsystem is used for receiving an ability product calling request sent by an application development end, wherein the ability product calling request carries first ability Token information;

the authentication subsystem is used for receiving a verification request of the first capacity Token information sent by the third party capacity open platform; and when the verification of the first capacity Token information is determined to pass based on the verification request of the first capacity Token information, sending effective information of the first capacity Token information to the third-party capacity open platform, and synchronously storing calling record information of the first capacity Token information, which is called by the application development end, in the effective information.

In the above scheme, the access subsystem is further configured to receive an acquisition request of the Token information sent by the application development end, and send the first Token information generated by the authentication subsystem based on the acquisition request to the application development end;

the authentication subsystem is further configured to authenticate an ability product corresponding to the ability Token information and an application developed by using the ability product when determining that the ability Token information belongs to a first ability based on the ability identification code ID in the acquisition request; and when the capability product and the application authentication are determined to pass, generating the first capability Token information, and sending the first capability Token information to the access subsystem.

In the above scheme, the access subsystem is further configured to generate URL information of a third party capability open platform based on the first capability Token information generated by the authentication subsystem; and sending the first ability Token information and the URL information to the application development end, wherein the first ability Token information and the URL information are used for sending a calling request of an ability product to the third party ability open platform by the application development end.

In the above solution, the system further includes: the system comprises a portal subsystem, an operation management subsystem and a capacity management subsystem; wherein,

the portal subsystem is used for receiving a capacity cooperation request sent by a third-party capacity open platform;

the operation management subsystem is used for auditing the capacity cooperation information provided by the third-party capacity open platform based on the capacity cooperation request received by the portal subsystem;

the capability management subsystem is used for generating a first ID when the operation management subsystem determines that the capability cooperation information is approved;

and the authentication subsystem is also used for synchronously storing the first ID and the capability cooperation information and sending a notification of successful application to the third-party capability open platform.

In the above scheme, the portal subsystem is further configured to receive a capability online request sent by a third-party capability open platform;

the operation management subsystem is further configured to audit capability online information provided by the third-party capability open platform based on the capability online request received by the portal subsystem;

the capability management subsystem is further configured to generate a second ID when the operation management subsystem determines that the capability online information is approved;

and the authentication subsystem is also used for synchronously storing the second ID and the capability online information and sending a notification of capability online success to the third-party capability open platform.

In the above scheme, the portal subsystem is further configured to receive a capability product online request sent by the third-party capability open platform;

the operation management subsystem is further configured to audit capability product online information provided by the third-party capability open platform based on the capability product online request received by the portal subsystem;

the capability management subsystem is further used for generating a third ID when the operation management subsystem determines that the online information of the capability product passes the verification;

the authentication subsystem is also used for synchronously storing the third ID and the online information of the capacity product and sending a notice of successful online of the capacity product to the third party capacity open platform

a portal subsystem and an access subsystem; wherein,

the portal subsystem is used for receiving the capacity access request sent by the application development end;

the access subsystem is used for generating capacity access Token information based on the capacity access request received by the portal subsystem and sending the capacity access Token information to a third-party capacity open platform for the capacity access request; receiving a verification request of the ability access Token information sent by the third party ability open platform; and when the verification of the ability access Token information is determined to pass based on the verification request of the ability access Token information, switching the current interface to the interface of the third-party ability open platform for the application development end to perform ability call in the third-party ability open platform.

In the above scheme, the access subsystem is further configured to synchronously store the call record information of the capability access Token information called by the application development end.

According to another aspect of the embodiments of the present invention, there is provided a third party capability opening platform, including:

the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving an ability product calling request sent by an application development end, and the ability product calling request carries first ability Token information;

the processing unit is used for sending a verification request of the first capacity Token information to a capacity introduction system and receiving a verification result sent by the capacity introduction system when the first capacity Token information is determined not to be locally stored;

and the sending unit is used for sending a notification that the calling of the capability product is successful to the application development end when the verification result confirms that the first capability Token information passes the verification and the period of the first capability Token information is in the valid period.

In the foregoing solution, the third-party capability open platform further includes:

and the storage unit is used for synchronously storing the calling record information called by the application development end in the valid period of the first ability Token information to the ability introduction system.

In the foregoing solution, the processing unit is further configured to send a capability cooperation request to the capability introduction system, and receive a capability cooperation notification sent by the capability introduction system based on the capability cooperation request; when the capability cooperation request is determined to be successful according to the capability cooperation notification, sending a capability online request to the capability introduction system, and receiving a capability online notification sent by the capability introduction system based on the capability online request; when the capability on-line request is determined to be successful according to the capability on-line notification, sending a capability product on-line request to the capability introduction system, and receiving a capability product on-line notification sent by the capability introduction system based on the capability product on-line request; and when the capability product is determined to be successfully online according to the online notification of the capability product, calling the capability product through the capability introduction system supply and use development end.

the receiving unit is used for receiving the ability access Token information generated by the ability access request sent by the application development end by the ability introduction system; and when the capability introduction system is determined to switch the current interface to the interface of the third-party capability open platform, receiving a capability product calling request sent by an application development terminal through the third-party capability open platform.

And the sending unit is used for sending a notification of successful verification of the capability access Token information to the capability introduction system when the verification of the capability access Token information is determined to pass, wherein the notification of successful verification of the capability access Token information is used for switching the current interface to the interface of the third-party capability open platform by the capability introduction system.

and the storage unit is used for synchronously storing the calling record information of the ability access Token information called by the application development end to the ability introduction system.

According to still another aspect of the embodiments of the present invention, there is provided an application development end, including:

a sending unit, configured to send an acquisition request of capability Token information to a capability introduction system, where the acquisition request of the capability Token information carries a capability ID;

a receiving unit, configured to receive first capability Token information generated by the capability introduction system based on the capability ID;

and the calling unit is used for calling the capability product of the third-party capability open platform according to the first capability Token information.

In the foregoing solution, the receiving unit is further configured to receive URL information of a third-party capability open platform generated by the capability introduction system based on the first capability Token information;

the calling unit is specifically configured to call a capability product of the third-party capability open platform according to the first capability Token information and the URL information of the third-party capability open platform.

a sending unit, configured to send a capability access request to the capability introduction system;

and the calling unit is used for calling the capacity product of the third-party capacity open platform through the interface of the third-party capacity open platform when the capacity introducing system is determined to switch the current interface to the interface of the third-party capacity open platform based on the capacity access request.

The embodiment of the invention provides a method, a system and equipment for introducing the capability of a capability open platform, which are used for receiving a capability Product (EAP) calling request sent by an application development terminal; receiving a verification request of the first capacity Token information sent by a third party capacity open platform based on the first capacity Token information carried in the capacity product calling request; and when the verification of the first capacity Token information is determined to pass based on the verification request of the first capacity Token information, sending effective information of the first capacity Token information to the third party capacity open platform, and synchronously storing calling record information of the first capacity Token information, which is called by the application development end, in the effective information. Therefore, the development threshold of the capability development end on the capability service is reduced, and the development speed of the capability service is increased; moreover, according to different capability characteristics in a third-party capability open platform, a plurality of corresponding capability introduction interfaces can be opened to support different capability access modes and realize cross-level, cross-province and cross-platform capability service opening and calling; obviously, the embodiment of the invention can complete the introduction of the capacity without greatly transforming the self capacity of the third-party capacity open platform, and has flexible and convenient operation and wider application range.

Drawings

Fig. 1 is a schematic flow chart illustrating an implementation process of a capability importing method of a capability open platform according to an embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating an exemplary process for introducing semi-proxy capabilities;

FIG. 3 is a schematic diagram illustrating an exemplary process for introducing full proxy capability according to an embodiment of the present invention;

FIG. 4 is a flow chart illustrating a capability collaboration application in an embodiment of the present invention;

FIG. 5 is a flowchart illustrating an on-line capability application according to an embodiment of the present invention;

FIG. 6 is a flowchart illustrating an online application of a capability product according to an embodiment of the present invention;

FIG. 7 is a flowchart illustrating an exemplary exit capability collaboration application process according to an embodiment of the present invention;

FIG. 8 is a flowchart illustrating capacity downline in an embodiment of the present invention;

FIG. 9 is a schematic flow chart of a capability product offline in an embodiment of the present invention;

FIG. 10 is a schematic diagram of a capacity product listing process according to an embodiment of the present invention;

FIG. 11 is a flow chart illustrating a capability product update process according to an embodiment of the present invention;

FIG. 12 is a schematic diagram illustrating a process of deployment after update of a capability product according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of a capacity product off-shelf process in an embodiment of the present invention;

FIG. 14 is a schematic flow chart illustrating an implementation of a capability importing method of another capability opening platform according to an embodiment of the present invention;

FIG. 15 is a flow chart illustrating the introduction of transparency capability in an embodiment of the present invention;

FIG. 16 is a flowchart illustrating an implementation of a capability introduction method for implementing another capability openness platform according to the present invention;

FIG. 17 is a flowchart illustrating an implementation of a capability introduction method for implementing another capability openness platform according to the present invention;

FIG. 18 is a flow chart illustrating an implementation of a capability introduction method for implementing another capability opening platform according to the present invention;

FIG. 19 is a flowchart illustrating an implementation of a capability introduction method for implementing another capability openness platform according to the present invention;

FIG. 20 is a schematic structural diagram of a capability introduction system of a capability openness platform according to an embodiment of the present invention;

FIG. 21 is a schematic structural diagram of a third party capability open platform according to an embodiment of the present invention;

fig. 22 is a schematic structural diagram of an application development terminal according to an embodiment of the present invention.

Detailed Description

The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present invention, are given by way of illustration and explanation only, not limitation.

Fig. 1 is a schematic flow chart illustrating an implementation process of a capability importing method of a capability open platform according to an embodiment of the present invention; as shown in fig. 1, the method includes:

step 101, receiving an ability product calling request sent by an application development terminal, wherein the ability product calling request carries first ability Token information;

the method is mainly applied to a capability introduction system, and various capabilities including telecommunication basic capabilities such as short message positioning, multimedia message positioning and the like are opened in the capability introduction system; own internet service capability; an application hosting capability; wireless city information source capability; the application development terminal can perform account registration and cancellation in the capability introduction system through various interfaces such as Web Service (Web Service) or Representational State Transfer (REST) and the like, and can also manage self account, purchase capability and developed application. When the application development end needs to purchase or call the capacity in the capacity introduction system, the capacity introduction system needs to send a capacity calling request to the capacity introduction system after completing registration, and the capacity introduction system receives the capacity calling request sent by the application development end and provides capacity selling or calling service to the application development end based on the capacity calling request.

102, receiving a verification request of the first capacity Token information sent by a third party capacity open platform;

here, the third party capability opening platform may price its own capability, form a capability product, and register in the capability introduction system through various form interfaces such as Web service or REST, so as to sell to the application opening terminal. Specifically, after the capability introduction system receives the capability calling request sent by the application development terminal, the third party capability opening platform is triggered to judge whether the first capability Token information is locally stored or not based on the first capability Token information and application identification code (ID, Identity) information carried in the capability product calling request, and when it is determined that the first capability Token information is not locally stored, the first capability Token information is stored, and a verification request of the first capability Token information is sent to the capability introduction system. Specifically, the capability introduction system is requested to perform authentication and verification on the first capability Token information, so as to ensure the security of the capability product being invoked. In the embodiment of the present invention, one third-party capability open platform may be introduced into the capability introduction system, or a plurality of third-party capability open platforms may be introduced, and one third-party capability open platform may provide one capability or a plurality of capabilities, and a plurality of third-party capability open platforms may provide different capabilities or the same capability, so as to implement mutual competition among the plurality of third-party capability open platforms.

Step 103, when it is determined that the first capability Token information passes the verification based on the verification request of the first capability Token information, sending effective information of the first capability Token information to the third party capability open platform, and synchronously storing calling record information of the first capability Token information, which is called by the application development end, in the effective information.

Here, after receiving the verification request of the first capability Token information sent by the third party capability open platform, the capability introduction system matches the first capability Token information with the capability Token information stored in the Token management library based on the verification request, and when the matching is successful, determines that the first capability Token information passes verification, and acquires the valid information of the first capability Token information. Specifically, the valid information includes a valid period, a remaining number of times of use, and the like of the first capability Token information. And sending the verification result of the first capacity Token information to the third party capacity open platform. And when the third-party capability open platform receives the verification result sent by the capability introduction system, the third-party capability open platform stores the effective information of the first capability Token information based on the verification result and sends a notification of capability calling success to the application development end. For example, when determining that the first capability Token information is in the validity period based on the capability validity information sent by the capability introduction system, sending a notification that the capability product call is successful to the application development end. And when the application development end forms a capability ordering relationship and a capability calling relationship based on the capability introduction system and the third-party capability development platform, synchronously storing the capability ordering and using records to the capability introduction system, wherein the capability ordering and using records comprise the using times of the first capability Token information. Then, the application development end can directly use the first capability Token information to make a capability call to a third party capability open platform until the term of the first capability Token information expires.

In the embodiment of the invention, the application development end only completes the capability authentication process in the capability introduction system, and the specific capability service process is completed in the third-party capability opening platform, so that the third-party capability opening platform can access the capability to the capability introduction system for capability display and sale without excessive capability modification on the capability of the third-party capability opening platform, thereby reducing the access threshold of the third-party capability opening platform and ensuring that the application development end can purchase more abundant capability products in the capability introduction system. And the direct interaction between the application development end and the third-party capability development platform is realized. Meanwhile, the application development end can also deploy and release the developed application in the capability introduction system for ordering, downloading and using by the mobile user.

In an embodiment of the present invention, before the receiving the capability product invocation request sent by the application development end, the method further includes:

based on the capability ID in the acquisition request, when determining that the capability Token information belongs to a first capability, authenticating a capability product corresponding to the capability Token information and an application developed by using the capability product, and generating the first capability Token information when determining that the capability product and the application pass the authentication;

sending the first capability Token information to the application development end,

here, when the capability introducing system purchases a capability product, the application development terminal needs to send a capability Token information acquisition request to the capability introducing system, and after receiving the capability Token information acquisition request, the capability introducing system matches the capability ID in the acquisition request with the capability information stored in the capability introducing system, and determines the attribute of the capability Token information according to a matching result. And when the capability introducing system determines that the capability Token information belongs to the first capability according to the matching result, authenticating a capability product corresponding to the capability Token information and an application developed by using the capability product. Specifically, the capability introduction system determines whether a relationship between a capability product corresponding to the capability Token information and an application developed by using the capability product is matched, determines that the authentication is passed when the matching is successful, generates the first capability Token information, and generates a Uniform Resource Locator (URL) of a third-party capability open platform based on the first capability Token information; then, the first capability Token information and the URL are sent to the application development terminal, and then the application development terminal may send a capability calling request to a third party capability development platform in the location of the URL based on the first capability Token information. In the embodiment of the present invention, the first capability refers to a semi-proxy capability, that is, when the application development end calls the capability, the capability authentication process is completed in the capability introduction system, and the capability service process is completed in the third party capability development platform. The specific semi-proxy capability introduction flow is shown in fig. 2.

Fig. 2 is a schematic diagram of an introduction flow of a half-proxy capability in an embodiment of the present invention, as shown in fig. 2, specifically including:

step 201, an application development end sends a capacity Token acquisition request to an access subsystem in a capacity introduction system;

step 202, the access subsystem acquires the capability ID of the capability product to be called based on the capability Token acquisition request;

step 203, the access subsystem judges the attribute of the capability product to which the capability Token information is directed based on the capability ID, and sends a request for calling authentication pricing by a half-proxy capability to the authentication subsystem in the capability introduction system when determining that the capability product to which the capability Token information is directed belongs to the half-proxy capability;

the access subsystem determines that the capability product to which the capability Token information is directed belongs to the semi-proxy capability, and performs attribute identification on the capability product to which the capability Token information is directed according to the registration information of the third-party capability open platform in the capability introduction system.

Step 204, the authentication subsystem calls an authentication pricing request based on the semi-proxy capability to authenticate the capability product corresponding to the capability Token information and the application developed by using the capability product;

step 205, when the authentication subsystem determines that the capability product and the application pass the authentication, the authentication subsystem sends a semi-proxy capability authentication pricing result to the access subsystem;

step 206, the access subsystem sends a request for acquiring the Token information of the half-proxy capability to the authentication subsystem;

step 207, the authentication subsystem generates the half-agent capability Token information based on the request for acquiring the half-agent capability Token information;

step 208, the authentication subsystem returns the generated Token information of the half-proxy capability to the access subsystem;

step 209, the access subsystem generates the URL information of the third party capability open platform according to the Token information of the half-proxy capability;

step 210, the access subsystem sends the generated half-agent capability Token information and the generated URL information to an application development terminal;

step 211, the application development end saves the half-agent capacity Token information and the URL information, and sends a capacity calling request to a third-party capacity development platform at the position of the URL information based on the half-agent capacity Token information;

step 212, after receiving the capability calling request, the third party capability open platform determines whether the capability Token information carried in the capability calling request is locally stored and/or whether the time limit of the capability Token information is within the valid period;

step 213, when the third party capability open platform determines that the capability Token information is not locally stored, storing the capability Token information, and sending a verification request of the capability Token information to the authentication subsystem;

step 214, the authentication subsystem verifies the ability Token information based on the verification request, and obtains the effective information of the ability Token information;

step 215, when the authentication subsystem determines that the verification of the capability Token information is successful, the authentication subsystem sends a verification result of the capability Token information and effective information of the capability Token information to the third party capability open platform;

here, the validity information of the capability Token information includes a validity period, a remaining number of uses, and the like.

Step 216, the third party capability openness platform saves the effective information of the capability Token information and sends a notification of capability calling success to the application openness end.

And step 217, the third-party capability open platform synchronizes the information of the application development end calling capability product to the authentication subsystem.

In the embodiment of the present invention, after the application development end receives the notification of successful capability invocation sent by the third party capability open platform, and when the capability Token information is used again to send the capability invocation request to the third party capability open platform, the third party capability open platform may directly send the capability invocation result to the application development end when determining that the capability Token information is in an effective state, and synchronize the usage record of the capability Token information to the authentication subsystem.

In the embodiment of the present invention, when the capability importing system determines that the capability product corresponding to the capability Token information belongs to the second capability, that is, the full proxy capability, the importing flow process of the full proxy capability shown in fig. 3 is used.

Fig. 3 is a schematic diagram of an introduction flow of the full proxy capability in the embodiment of the present invention, and as shown in fig. 3, the introduction flow of the full proxy capability includes:

step 301, an application development end sends an acquisition request of the ability Token information to an access subsystem;

step 302, the access subsystem acquires a capability ID based on the acquisition request of the capability Token information;

step 303, the access subsystem judges the attribute of the capability product corresponding to the capability Token information based on the capability ID, and sends an authentication request of the capability Token information to the authentication subsystem when determining that the capability product corresponding to the capability Token information belongs to the full proxy capability;

the access subsystem determines that the capability product corresponding to the capability Token information belongs to full proxy capability, and performs attribute identification on the capability product corresponding to the capability Token information according to the registration information of the third party capability open platform in the capability introduction system.

Step 304, the authentication subsystem checks the ability Token information based on the authentication request of the ability Token information;

specifically, all capability Token information in the third party capability open platform and attribute information of the capability Token information are stored in the authentication subsystem. And after receiving the authentication request of the capacity Token information sent by the third-party capacity open platform, the authentication subsystem matches the capacity Token information with the capacity Token information stored in the capacity introduction system based on the authentication request, and when the matching is successful, the authentication subsystem determines that the capacity Token information passes the verification.

305, the authentication subsystem returns the check result to the access subsystem;

step 306, the access subsystem receives the check result and sends a request for calling authentication pricing by full proxy capability to the authentication subsystem;

step 307, the authentication subsystem calls an authentication pricing request according to the full proxy capability, authenticates the capability product corresponding to the capability Token information and the application developed by using the capability product, and sends a full proxy capability authentication pricing result to the access subsystem when the authentication is passed;

308, the access subsystem receives the full agent capability authentication pricing result and sends a full agent capability calling request to a third party capability open platform;

step 309, the third party capability open platform sends a capability response result to the access subsystem based on the full proxy capability calling request;

step 310, the access subsystem receives the capability response result and sends the capability response result to the application development end;

and 311, the authentication subsystem generates application information developed by the application development terminal and use record information of the capability product called by the development application, and synchronously stores the generated application information and the use record information of the capability product to a third-party capability open platform.

In the embodiment of the invention, the third-party capability open platform has multiple capabilities, and each capability stores own capability Token information and attribute information of the capability Token information. The attribute information of the capability Token information includes a validity period, a remaining number of times of use, and the like of the capability Token information.

In this embodiment of the present invention, before receiving the capability call request sent by the application development terminal, the method further includes:

The third-party capability open platform specifically refers to third-party capability. Specifically, the intention of cooperation between the third-party capability open platform and the capability introduction system may be bidirectional, that is, the capability introduction system may find the target third-party capability open platform according to the requirement of the application development end for developing the application to achieve the cooperation relationship, or the third-party capability open platform may send a capability cooperation application to the capability introduction system to achieve the cooperation relationship, which is not limited herein. The following describes in detail an example in which a third-party capability open platform sends a capability cooperation application to a capability introduction system.

Firstly, a third-party capacity open platform logs in the capacity import system to register and register, and provides corresponding information such as qualification certification documents, capacity product data and successful cases according to a cooperation application template in the capacity import system; and after receiving the cooperation application information provided by the third-party capability open platform, the capability introduction system stores and audits the cooperation application information. Specifically, whether the data provided by the third-party capability open platform accords with the service direction of the capability introduction system is checked, and the feasibility of the capability product in the capability product data is evaluated according to the modification specification. And when the cooperation application information is determined not to accord with the service direction of the capability introduction system, sending related application development data and cooperation specification data to the third-party capability open platform, and modifying the provided capability product data by the third-party capability open platform according to the application development data and the cooperation specification data. When a transformation scheme of the capacity product is achieved between the third-party capacity open platform and the capacity introduction system, the third-party capacity open platform modifies the capacity product data according to the data sent by the capacity introduction system. The capacity introduction system is responsible for carrying out technical test on modified capacity products, the third-party capacity open platform is responsible for providing capacity support for the modified capacity products, when the capacity introduction system determines that the modified capacity products pass the technical test, the third-party capacity open platform ID is generated based on capacity cooperation application information of the third-party capacity open platform, and after the third-party capacity open platform ID and the capacity cooperation application information are synchronously stored, a notification of capacity cooperation application success is sent to the third-party capacity open platform. The flow of the specific capability collaboration application is shown in fig. 4.

Fig. 4 is a schematic flow chart of the capability collaboration application in the embodiment of the present invention, and as shown in fig. 4, the flow chart includes:

step 401, a third party capacity open platform logs in a portal subsystem in the capacity introduction system, and capacity cooperation application information is filled in from a service area through the third party capacity open platform in the portal subsystem;

specifically, the ability cooperation application information is filled according to the forms, the information required by the data, the relevant templates and other data provided by the third-party ability open platform self-service area in the portal subsystem.

Step 402, the portal subsystem sends the ability cooperation application information filled in by the third party ability open platform to the operation management subsystem in the ability introduction system;

step 403, the operation management subsystem receives the capability cooperation application information and verifies the capability cooperation application information; when the cooperative application information is confirmed to pass the verification, sending a capability verification result to a capability management subsystem;

step 404, registering the capability cooperation application information by a capability management subsystem according to the received auditing result, and generating a third party capability open platform ID;

step 405, the ability management subsystem synchronously saves the third party ability open platform ID and the ability cooperation application information to an authentication subsystem;

step 406, the authentication subsystem synchronously saves the third party capability open platform ID and the capability cooperation application information, and sends a synchronization result to the capability management subsystem;

step 407, the capacity management subsystem receives the synchronization result and sends the synchronization result to the operation management subsystem;

step 408, the operation management subsystem receives the synchronization result and sends a notification of success of the cooperation application to the portal subsystem;

step 409, the portal subsystem receives the notification of success of the cooperation application and sends the notification of success of the cooperation application to the third-party capability opening platform.

In this embodiment of the present invention, after the sending the notification of successful application to the third party capability openness platform, the method further includes:

Specifically, the third-party capability opening platform sends a capability online application to the capability introduction system, and after receiving the capability online application, the capability introduction system generates a second ID based on the capability online application, that is, after the capability ID, the capability online information provided by the third-party capability opening platform is checked. The specific audit objects include: capability information, capability service information, capability configuration information and the like of the application capability online. And when the verification is confirmed to be passed, synchronously storing the capability ID and the capability information in the capability on-line application, and sending a notification of capability on-line application success to a third party capability open platform. The flow of the specific capability on-line application is shown in fig. 5.

FIG. 5 is a flowchart illustrating an on-line capability application according to an embodiment of the present invention; as shown in fig. 5, the flow of the capability online application includes:

step 501, a third party capacity opening platform logs in a self-service area of the third party capacity opening platform in a portal subsystem, and fills a capacity on-line application in the self-service area of the third party capacity opening platform;

step 502, the portal subsystem sends the capability on-line application to the operation management subsystem;

step 503, the operation management subsystem saves the capability online application and sends the capability online application to the capability management subsystem;

step 504, the capacity management subsystem saves the capacity on-line application, generates a capacity ID based on the capacity on-line application, and sends a capacity on-line verification request to the operation management subsystem;

step 505, the operation management subsystem checks the information provided by the capability on-line application based on the capability on-line checking request;

step 506, the operation management subsystem saves the capability information when determining that the audit is passed, and sends the audit result to the capability management subsystem;

step 507, the ability management subsystem receives the checking result and sends an ability information synchronization request to the authentication subsystem;

step 508, the authentication subsystem synchronously saves the said ability information, and send the synchronous result of the ability information to the ability management subsystem;

509, the capacity management subsystem receives the synchronization result and sends a capacity information synchronization request to the access subsystem;

step 510, the access subsystem synchronously saves the capacity information and sends the synchronous result of the capacity information to the capacity management subsystem;

step 511, the capacity management subsystem receives the synchronization result and sends a notification of successful capacity on-line application to the operation management subsystem;

step 512, the operation management subsystem receives the notification that the capability on-line application is successful, and sends the notification that the capability on-line application is successful to the portal subsystem;

step 513, the portal subsystem receives the notification of successful capability on-line application, and sends the notification of successful capability on-line application to the third party capability open platform.

In this embodiment of the present invention, after sending the notification that the capability on-line succeeds to the third party capability openness platform, the method further includes:

Specifically, the third-party capability open platform sends a capability product on-line application to the capability introduction system, and after receiving the capability product on-line application, the capability introduction system generates a third ID, namely a capability product ID, based on the capability product on-line application; and auditing the data provided in the capability product on-line application, performing product testing on the capability product applying on-line in the capability product on-line application when the data provided in the capability product on-line application is determined to be approved, storing the capability product on-line application information and the capability product ID when the capability product testing is determined to be passed, and sending a notification of success of the capability product on-line application to a third-party capability open platform. Specifically, the flow of the online application of the capability product is shown in fig. 6.

Fig. 6 is a schematic flow chart of an online application of a capability product in an embodiment of the present invention, and as shown in fig. 6, the online application flow of the capability product includes:

601, a third party capacity opening platform logs in a self-service area of the third party capacity opening platform in a portal subsystem, and fills an online application of a capacity product through the self-service area of the third party capacity opening platform;

step 602, the portal subsystem sends the capability product on-line application to the operation management subsystem and the capability management subsystem;

603, a capacity management subsystem receives the capacity product on-line application and generates a capacity product ID based on the capacity product on-line application;

step 604, the capacity management subsystem sends a capacity product audit notification to the operation management subsystem;

605, the capacity management subsystem sends a capacity product service code application to the service support subsystem;

step 606, the service support subsystem receives the capability product service code application and sends a result notification of the capability product service code to the capability management subsystem;

step 607, the operation management subsystem audits the ability product data provided in the ability product on-line application based on the ability product audit notice, and saves the ability product data when the ability product data audit is passed;

step 608, the operation management subsystem performs a product test on the capability product for which the online application of the capability product is directed, and sends a test result of the capability product to the capability management subsystem when it is determined that the capability product test is passed;

step 609, the capability management subsystem receives the test result and sends a synchronous request of the capability product information to the authentication subsystem;

step 610, the authentication subsystem synchronously saves the capability product information and sends a synchronization result to the capability management subsystem;

611, the capacity management subsystem receives the synchronization result and sends a notification of successful online application of the capacity product to the operation management subsystem;

step 612, the operation management subsystem receives the notification that the capability product online application succeeds, and sends the notification that the capability product online application succeeds to the portal subsystem;

step 613, the portal subsystem receives the notification that the capability product application on line is successful, and sends the notification that the capability product application on line is successful to the third party capability open platform.

In the embodiment of the invention, the capability product instantiates a certain capability, the capability introducing system provides different charging strategy templates according to different capability types, and when a third-party capability open platform initiates a capability product shelving request, the capability product information applied for online is filled according to the charging strategy template provided by the capability introducing system, and other related data are attached.

In the embodiment of the present invention, the method further includes the step of the third party capability open platform exiting the cooperative application process, and the specific exiting cooperative application process is shown in fig. 7.

Fig. 7 is a schematic diagram of a capability collaboration application exit flow in the embodiment of the present invention, as shown in fig. 7, including:

step 701, a third party capacity opening platform logs in a self-service area of the third party capacity opening platform in a portal subsystem, and fills a third party capacity opening platform quit cooperation application in the self-service area of the third party capacity opening platform;

step 702, the portal subsystem sends the third party capability open platform quit cooperation application to the operation management subsystem;

step 703, the operation management subsystem receives the application for the third party capability opening platform to quit cooperation, verifies the use condition of the capability product issued by the third party capability opening platform in the capability introduction system, and sends a verification result to the capability management subsystem;

specifically, whether the capacity product issued by the third-party capacity open platform is currently used by the application development end is checked, if so, after the third-party capacity open platform exits the checking of the cooperation application and passes the checking, the third-party capacity open platform continues to provide online service for the capacity product being used by the application development end. On the contrary, if no capability product currently used by the application development end is found, after the third-party capability open platform exits the verification of the cooperation application and passes, the third-party capability open platform may stop providing the capability service to the application development end.

Step 704, the capability management subsystem receives the audit result, updates the cooperation state of the third-party capability open platform and the capability introduction system according to the audit result, and simultaneously shuts down all the capabilities and capability products issued by the capability open platform in the capability introduction system;

705, the ability management subsystem sends a synchronous request of the third party ability open platform information to the authentication subsystem;

step 706, the authentication subsystem synchronously saves the third party capability open platform information and sends the synchronization result to the capability management subsystem;

step 707, the capacity management subsystem receives the synchronization result and sends the synchronization result to the operation management subsystem;

step 708, the operation management subsystem receives the synchronization result and sends a notification of successful quit of the cooperation application to the portal subsystem;

step 709, the portal subsystem receives the notification that the cooperation application quits successfully, and sends the notification that the cooperation application quits successfully to the third-party capability open platform.

In the embodiment of the present invention, the method further includes a capability offline process, and a specific capability offline process is shown in fig. 8.

Fig. 8 is a schematic flow chart of a capability downline in the embodiment of the present invention, and as shown in fig. 8, the flow of the capability downline includes:

step 801, a third party capacity opening platform logs in a self-service area of the third party capacity opening platform in a portal subsystem, and fills a capacity offline application in the self-service area of the third party capacity opening platform;

step 802, the portal subsystem sends the capacity offline application to the capacity management subsystem;

step 803, the capacity management subsystem receives the capacity offline application and updates the current state of the capacity of the application offline based on the capacity offline application;

step 804, the capability management subsystem sends the state information of the capability to the operation management subsystem;

step 805, the operation management subsystem receives the status information of the capability and checks the current use condition of the capability;

specifically, whether the capability currently has the capability service used by the application development end is checked, when the capability service used by the application development end exists, the capability service is terminated, and a checking result is sent to the capability management subsystem;

step 806, the ability management subsystem registers the audit result and sends the registration result to the operation management subsystem;

step 807, the capacity management subsystem sends a synchronous storage request of the registration result to the authentication subsystem;

step 808, the authentication subsystem synchronously saves the registration result, stops all the capability services of the capability, and sends the synchronization result to the capability management subsystem;

step 809, the capacity management subsystem sends a synchronous storage request of the registration result to the access subsystem;

step 810, the access subsystem synchronously saves the registration result, stops all the capability services of the capability, and sends the synchronization result to the capability management subsystem;

step 811, the capacity management subsystem receives the synchronization result and sends a notification of successful capacity offline to the operation management subsystem;

step 812, the operation management subsystem receives the notification of successful capability offline and sends the notification of successful capability offline to the portal subsystem;

step 813, the portal subsystem receives the notification of successful capability offline, and sends the notification of successful capability offline to the third party capability opening platform.

In the embodiment of the invention, the capability offline does not represent the capability cooperation end between the third-party capability open platform to which the capability belongs and the capability introduction system.

In the embodiment of the present invention, the method further includes a process of offline the capability product, and the process of offline the specific capability product is as shown in fig. 9.

FIG. 9 is a schematic flow chart of a capability product offline in an embodiment of the present invention; as shown in fig. 9, the process of offline the capability product includes:

step 901, a third party capacity opening platform logs in a self-service area of the third party capacity opening platform in a portal subsystem, and fills an offline application of a capacity product through the self-service area of the third party capacity opening platform;

step 902, the portal subsystem sends the offline application of the capability product to the operation management subsystem;

step 903, the operation management subsystem receives the capacity product offline application and verifies the current use condition of the capacity product for which the capacity product offline application is directed;

and specifically, whether the capability product is used by the application development end currently exists is checked, and when the capability product is used by the application development end currently exists, all capability services of the application development end for using the capability product are ended.

Step 904, the operation management subsystem sends the auditing result of the capability product to the capability management subsystem;

step 905, registering the auditing result by the capacity management subsystem, and sending the registering result to the operation management subsystem;

step 906, the ability management subsystem sends the synchronous storage request of the registration result to the authentication subsystem;

step 907, the authentication subsystem synchronously saves the registration result, stops all capability services of the capability product, and sends a synchronization result to the capability management subsystem;

step 908, the capacity management subsystem receives the synchronization result and sends a synchronization storage request of the synchronization registration result to the operation management subsystem;

step 909, the operation management subsystem synchronously saves the registration result and sends the notification of successful offline of the capacity product to the portal subsystem;

step 910, the portal subsystem receives the notification of successful offline of the capability product and sends the notification of successful offline of the capability product to the third-party capability opening platform.

In the embodiment of the invention, the capacity product offline does not represent the capacity cooperation end between the third-party capacity open platform to which the capacity product belongs and the capacity introduction system.

In the embodiment of the present invention, the method further includes a capacity product shelf loading process, which is specifically shown in fig. 10.

Fig. 10 is a schematic flow diagram of a capacity product shelving process in an embodiment of the present invention, and as shown in fig. 10, the capacity product shelving includes:

step 1001, a third party capacity open platform logs in a self-service area of the third party capacity open platform in a portal subsystem, and fills a capacity product listing application through the self-service area of the third party capacity open platform;

step 1002, the portal subsystem sends the capacity product shelf application to the operation management subsystem;

step 1003, the operation management subsystem receives the ability product uploading application and verifies the data provided in the ability product uploading application;

step 1004, when the operation management subsystem determines that the audit is passed, registering the capability product, and sending an audit result to a portal subsystem;

step 1005, the portal subsystem agrees to put on the shelf the capacity product based on the auditing result, and sends a notice that the capacity product is successfully put on the shelf to the third-party capacity open platform.

In the embodiment of the present invention, the method further includes a capability product updating process, which is specifically shown in fig. 11.

Fig. 11 is a schematic diagram of a capability product updating process according to an embodiment of the present invention, as shown in fig. 11, the process includes:

step 1101, a third party capacity open platform logs in a self-service area of the third party capacity open platform in a portal subsystem, and fills a capacity product update application through the self-service area of the third party capacity open platform;

step 1102, the portal subsystem sends the capability product update application to the operation management subsystem;

1103, the operation management subsystem receives the capability product update application and verifies the data provided in the capability product update application;

step 1104, when the operation management subsystem determines that the audit is passed, updating the capability component of the capability product, registering an update result, and sending the audit result to the portal subsystem;

and 1105, the portal subsystem agrees to put the updated capacity product on shelf according to the auditing result, and sends a notification of successful update of the capacity product to the third-party capacity open platform.

In the embodiment of the present invention, the method further includes a deployment process after the capability product is updated, which is specifically shown in fig. 12.

Fig. 12 is a schematic diagram of a deployment flow after updating the capability product according to an embodiment of the present invention. As shown in fig. 12, includes:

step 1201, sending a capacity component upgrading information query request to a capacity management subsystem by applying a capacity component management framework in an development end;

when the terminal is started, the capacity component management framework sends a request for checking whether the version information of the current capacity component needs to be upgraded to the capacity management subsystem;

step 1202, the capacity management subsystem receives the request and checks the version upgrade information of the capacity component;

step 1203, after the capability management subsystem finds the version upgrade information of the capability component, sending a query result to the capability component management framework;

step 1204, the ability component management framework sends a request for downloading an ability component upgrade package to the ability management subsystem according to the query result;

step 1205, the capacity management subsystem receives a request for downloading a capacity component upgrade package and sends the capacity component upgrade package to the capacity component management framework;

and 1206, installing the capacity component management framework based on the capacity component upgrading package.

In the embodiment of the present invention, the method further includes a process of putting the capability product off shelf, as specifically shown in fig. 13.

FIG. 13 is a schematic diagram of an embodiment of a capacity product off-shelf process; as shown in fig. 13, the process includes:

step 1301, a third party capacity opening platform logs in a self-service area of the third party capacity opening platform in a portal subsystem, and fills a capacity product off-shelf application through the self-service area of the third party capacity opening platform;

step 1302, the portal subsystem sends the capacity product shelf-off application to the operation management subsystem;

step 1303, the operation management subsystem receives the capacity product off-shelf application and audits the data provided in the capacity product off-shelf application;

step 1304, when the operation management subsystem determines that the audit is passed, registering the capability product, and sending an audit result to a portal subsystem;

and step 1305, the portal subsystem agrees to the capacity product shelf-off based on the auditing result and sends a notice that the capacity product shelf-off is successful to the third-party capacity open platform.

Fig. 14 is a schematic flow chart illustrating an implementation process of another capability importing method for a capability open platform according to an embodiment of the present invention, and as shown in fig. 14, the method includes:

1401, receiving a capability access request sent by an application development end;

here, the application development end selects a link of the capability platform to be called in the capability importing system, and the capability importing system receives a capability access request after the application development end selects the link of the capability platform to be called.

Step 1402, generating capability access Token information based on the capability access request, and sending the capability access Token information to a third-party capability open platform for which the capability access request is directed;

here, after receiving the capability access request, the capability introduction system generates capability access Token information based on the capability access request, performs attribute identification on a capability product to which the capability access Token information is directed, and sends the capability access Token information to a third-party capability open platform when determining that the capability product belongs to a third capability, that is, a transparent capability. The transparent capability refers to that when the application development end calls the capability, the capability authentication flow and the capability service flow are both completed on the corresponding third-party capability open platform, and the capability introduction system is only responsible for showing, inquiring and searching the capability product and does not participate in the specific flow of capability calling, so that the application development end and the third-party capability open platform are directly interacted.

Step 1403, receiving a verification result of the capability access Token information sent by the third party capability opening platform, and switching a current interface to an interface of the third party capability opening platform when it is determined that the verification of the capability access Token information is passed based on the verification result of the capability access Token information, so that the application initiation end can invoke the capability in the third party capability opening platform.

Specifically, after receiving the capability access Token information, the third party capability opening platform verifies the capability access Token information, when determining that the verification of the capability access Token information is passed, the third party capability opening platform returns a notification of successful verification to the capability introduction system, the capability introduction system jumps to a current interface of the third party capability opening platform, the application development end is provided for directly calling a capability product on the third party capability opening platform, and meanwhile, the third party capability opening platform synchronously stores calling record information of the capability access Token information called by the application development end to the capability introduction system. Specifically, the flow of introduction of the transparency capability is shown in fig. 15.

Fig. 15 is a schematic diagram of a process of introducing the transparency capability in the embodiment of the present invention, as shown in fig. 15, the process includes:

step 1501, the application development end accesses the capability link in the portal subsystem;

step 1502, the portal subsystem generates capability access Token information based on the capability link information, and sends the capability access Token information to the access subsystem;

step 1503, the access subsystem saves the ability access Token information and sends the ability access Token information and the ability link to the portal subsystem;

step 1504, the portal subsystem sends the capability access Token information to a third-party capability open platform for which the capability link is directed;

step 1505, the third party ability opening platform checks the ability access Token information;

step 1506, when the third party capability open platform determines that the capability access Token information passes verification, the portal subsystem jumps the current interface to the third party capability open platform interface;

step 1507, the application development end calls the capability product in the third party capability development platform interface.

Fig. 16 is a schematic flow chart of an implementation of a capability importing method for implementing another capability opening platform according to the present invention, as shown in fig. 16, the method includes:

step 1601, receiving an ability product calling request sent by an application development terminal, wherein the ability product calling request carries first ability Token information;

here, the method is mainly applied to a third party capability opening platform, and before the third party capability opening platform receives a capability product calling request sent by an application development terminal, the method further includes:

the third-party capacity open platform sends a capacity cooperation request to a capacity introduction system and receives a capacity cooperation notice sent by the capacity introduction system based on the capacity cooperation request;

when the third-party capacity open platform determines that the capacity cooperation request is successful according to the capacity cooperation notification, sending a capacity online request to the capacity introduction system, and receiving a capacity online notification sent by the capacity introduction system based on the capacity online request;

when the third party capability open platform determines that the capability on-line request is successful according to the capability on-line notification, sending a capability product on-line request to the capability introduction system, and receiving a capability product on-line notification sent by the capability introduction system based on the capability product on-line request;

and when the third-party capability opening platform determines that the capability product is successfully on-line according to the capability product on-line notification, the capability product is called by the capability introduction system supply and use opening end.

Step 1602, when it is determined that the first capability Token information is not stored locally, sending a verification request of the first capability Token information to a capability introduction system, and receiving a verification result sent by the capability introduction system;

step 1603, when it is determined that the first ability Token information passes verification according to the verification result and the term of the first ability Token information is in the valid term, sending a notification that the ability product is successfully called to the application development end.

In this embodiment of the present invention, after sending a notification that the capability product invocation is successful to the application development end, the method further includes:

and the third-party capability open platform synchronously stores the calling record information of the first capability Token information called by the application development terminal in the valid period to the capability introduction system.

Fig. 17 is a schematic flow chart illustrating an implementation process of a capability introduction method for implementing another capability opening platform according to the present invention, where as shown in fig. 17, the method includes:

step 1701, receiving capacity access Token information generated by the capacity access request sent by the application development terminal by the capacity introduction system;

step 1702, sending a notification of successful verification of the information about the capability access Token to the capability introduction system when it is determined that the verification of the information about the capability access Token passes;

step 1703, when it is determined that the capability import system switches the current interface to the interface of the third party capability open platform according to the notification that the verification of the capability access Token information is successful, receiving a capability product calling request sent by the application development end through the third party capability open platform.

The method is mainly applied to a third-party capability open platform, specifically, an application development end sends a capability access request of the third-party capability open platform to a capability introduction system, and the capability introduction system generates capability access Token information based on the capability access request and sends the capability access Token information to the third-party capability open platform for which the capability access request is directed; after receiving the ability access Token information, the third-party ability open platform verifies the ability access Token information, and when the verification is determined to be passed, sends a notification that the ability access Token information is successfully verified to the ability introduction system, and the ability introduction system receives the notification that the ability access Token information is successfully verified and switches the current interface to the interface of the third-party ability open platform, at this time, the application development end can call the ability through the interface of the third-party ability open platform. And simultaneously, the third-party capability open platform synchronously saves the calling record information of the capability access Token information called by the application development end to the capability introduction system.

Fig. 18 is a schematic flow chart of an implementation of a capability introduction method for implementing another capability opening platform according to the present invention, and as shown in fig. 18, the method includes:

step 1801, sending an acquisition request of capability Token information to a capability introduction system, where the acquisition request of capability Token information carries a capability ID;

step 1802, receiving first capability Token information generated by the capability introduction system based on the capability ID;

and 1803, calling a capability product of the third-party capability open platform according to the first capability Token information.

Here, the method is mainly applied to an application development side, and the application development side may perform capability calling or may perform application publishing in the capability introduction system. When the capacity introduction system calls the capacity, firstly sending an acquisition request of capacity Token information to the capacity introduction system, generating first capacity Token information by the capacity introduction system based on a capacity ID in the acquisition request of the capacity Token information, sending the first capacity Token information to the application development end, and calling a capacity product of a third party capacity development platform according to the first capacity Token information after the application development end receives the first capacity Token information. Specifically, the application development terminal is further configured to receive URL information of a third party capability development platform generated by the capability introduction system based on the first capability Token information; and calling the capability product of the third-party capability open platform according to the first capability Token information and the URL information of the third-party capability open platform.

Fig. 19 is a schematic flow chart illustrating an implementation process of a capability introduction method for implementing another capability opening platform according to the present invention, as shown in fig. 19, the method includes:

step 1901, sending a capability access request to the capability introduction system;

step 1902, when it is determined that the capability introduction system switches the current interface to the interface of the third party capability open platform based on the capability access request, the capability product of the third party capability open platform is invoked through the interface of the third party capability open platform.

Here, the application development end performs capability query and search through the capability introduction system, and when the current interface of the capability introduction system is switched to the interface of the third party capability open platform corresponding to the capability of the application development search, the application development end can call the capability product of the third party capability open platform through the interface of the third party capability open platform. The direct interaction between the application development end and the third-party capability development platform is realized, and the behavior of introducing system charging fraud by the capability is avoided.

Fig. 20 is a schematic structural diagram of a capability introduction system of a capability openness platform according to an embodiment of the present invention. As shown in fig. 20, the system 200 includes: an access subsystem 2001, configured to receive a capability product invocation request sent by the application development terminal 400; the authentication subsystem 2002 receives a verification request of the first capability Token information sent by the third party capability open platform 300 based on the first capability Token information carried in the capability product calling request; when it is determined that the verification of the first capability Token information passes based on the verification request of the first capability Token information, sending effective information of the first capability Token information to the third party capability opening platform 300, and synchronously storing call record information of the first capability Token information, called by the application opening end 400, in the effective information.

Specifically, the access subsystem 2001 is mainly used for opening various capabilities, such as telecommunication basic capabilities of short message, multimedia message positioning, and the like; own internet service capability; an application hosting capability; wireless city information source capability; data capacity, third-party internet capacity and the like, and also provides various interfaces such as Web Service or REST for the application development terminal 400 and the third-party capacity development platform 300, so as to complete the unified access of applications, application products, capacity and capacity products, and also can control Service Level Agreement management (SLA) on the accessed applications, and by interfacing with the authentication subsystem 2002, the authentication subsystem 2002 is triggered to perform unified authentication and charging on the applications and the application products issued by the application development terminal 400 and the application development terminal 400, and the capacity products provided by the third-party capacity development platform 300 and the third-party capacity development platform 300. Specifically, both the application development side 400 and the third party capability development platform 300 may perform account registration and deregistration in the capability introduction system 200 through various interfaces such as Web Service or REST, and the application development side 400 may also manage its own account, purchased capability, and developed application. The third party capability exposure platform 300 may price its capabilities, form a capability product, and sell it to the application development terminal 400 in the capability introduction system 200.

When the application development terminal 400 needs to purchase or invoke capabilities in the capability introduction system 200, a capability invocation request needs to be sent to the access subsystem 2001, when the access subsystem 2001 receives the capability invocation request sent by the application development terminal 400, the capability invocation request is sent to the third party capability development platform 300, and the third party capability development platform 300 provides capability sale or invocation service to the application development terminal 400 based on the capability invocation request. Specifically, the third party capability openness platform 300 determines whether the first capability Token information is locally stored based on the first capability Token information and the application ID information carried in the capability calling request, stores the first capability Token information when it is determined that the first capability Token information is not locally stored, and sends a verification request of the first capability Token information to the authentication subsystem 2002. Specifically, the authentication subsystem 2002 is requested to perform authentication and verification on the first capability Token information, so as to ensure the security of the capability product being invoked.

After receiving the verification request of the first capability Token information sent by the third party capability open platform 300, the authentication subsystem 2002 matches the first capability Token information with the capability Token information stored in the Token management base based on the verification request, and when the matching is successful, determines that the verification of the first capability Token information is passed, and obtains the effective information of the first capability Token information. Specifically, the valid information includes a valid period, a remaining number of times of use, and the like of the first capability Token information. And sends the verification result of the first capability Token information to the third party capability openness platform 300. When the third party capability openness platform 300 receives the verification result sent by the capability introduction system 200, based on the verification result, it stores the valid information of the first capability Token information, and sends a notification of successful capability product invocation to the application openness terminal 400. For example, when it is determined that the first capability Token information is in the validity period based on the capability validity information sent by the authentication subsystem 2002, a notification that the capability product invocation is successful is sent to the application development side 400. And when the application development terminal 400 forms a capability subscription relationship and a capability calling relationship with the third party capability development platform 300 based on the capability introduction system 200, the subscription and usage records of the capability are synchronously stored in the access subsystem 2001 and the authentication subsystem 2002, wherein the usage times of the first capability Token information are included. Thereafter, the application developer 400 may make a capability call to the third party capability development platform 300 directly using the first capability Token information until the expiration of the term of the first capability Token information. In the embodiment of the present invention, the authentication subsystem 2002 includes an authentication module and a security module, wherein the security module is mainly used for completing functions such as pseudo code management, Token management, identity authentication, and data security management; the authentication module mainly completes the functions of authentication, order request management, AP information synchronization, user information synchronization, product information synchronization, order relation synchronization, ticket generation, ticket synchronization and the like of capability calling.

In the embodiment of the present invention, the application development end 400 only completes the capability authentication process in the capability introduction system 200, and the specific capability service processes are all completed in the third party capability development platform 300, so that the third party capability development platform 300 can access the capability introduction system 200 for capability display and sale without performing excessive capability modification on the capability of the third party capability development platform 300, thereby reducing the access threshold of the third party capability development platform 300, and enabling the application development end 400 to purchase more abundant capability products in the capability introduction system 200. Direct interaction between the application development terminal 400 and the third party capability development platform 300 is achieved. Meanwhile, the application development terminal 400 may also deploy and publish the developed application in the capability introduction system 200 for the mobile user to subscribe, download and use.

In this embodiment of the present invention, the access subsystem 2001 is further configured to receive an acquisition request of the capability Token information sent by the application development terminal 400; the authentication subsystem 2002 is further configured to authenticate, when it is determined that the capability Token information belongs to the first capability based on the capability identifier ID in the acquisition request, the capability product corresponding to the capability Token information and the application developed by using the capability product, generate the first capability Token information when it is determined that the capability product and the application pass authentication, and send, by the access subsystem 2001, the first capability Token information to the application development terminal 400, so that the application development terminal 400 sends, based on the first capability Token information, a request for calling the capability product to the third party capability development platform 300.

Specifically, when the capability introducing system 200 purchases a capability product, the application development terminal 400 needs to send a capability Token information acquisition request to the access subsystem 2001, and after receiving the capability Token information acquisition request, the access subsystem 2001 matches the capability ID in the acquisition request with the stored capability information, and determines the attribute of the capability Token information according to the matching result. When the access subsystem 2001 determines that the capability Token information belongs to the first capability according to the matching result, an authentication request of a capability product and an application developed by using the capability product, to which the capability Token information is directed, is sent to the authentication subsystem 2002, and after receiving the authentication request of the capability product and the application, the authentication subsystem 2002 authenticates the capability product and the application. Specifically, the authentication subsystem 2002 determines whether a relationship between an ability product corresponding to the ability Token information and an application developed using the ability product is matched, when the matching is successful, the authentication is determined to be passed, the first ability Token information is generated and sent to the access subsystem 2001, and after receiving the first ability Token information, the access subsystem 2001 generates a URL of a third party ability open platform based on the first ability Token information; the first capability Token information and the URL are then sent to the application development terminal 400, and then the application development terminal 400 may send a capability calling request to the third party capability development platform 300 at the location of the URL based on the first capability Token information. In the embodiment of the present invention, the first capability specifically refers to a semi-proxy capability, that is, when the application development terminal 400 calls a capability, the capability authentication process is completed in the capability introduction system 200, and the capability service process is completed in the third party capability development platform 300. The ability to incorporate specific semi-proxy capabilities is illustrated in figure 2 in the method embodiment. When the access subsystem 2001 determines that the capability Token information belongs to the second capability, i.e., the full proxy capability, an introduction flow process of the full proxy capability as shown in fig. 3 is used. With particular reference to figure 3 of the method embodiment.

In an embodiment of the present invention, the system further includes: a portal subsystem 2003, an operations management subsystem 2004, and a capacity management subsystem 2005; wherein,

the portal subsystem 2003 is used for receiving the capability cooperation request sent by the third-party capability opening platform 300;

the operation management subsystem 2004 is configured to audit the capability cooperation information provided by the third party capability opening platform 300 based on the capability cooperation request received by the portal subsystem 2003;

the capability management subsystem 2005 is configured to, when the operation management subsystem 2004 determines that the capability cooperation information is approved, generate a first ID;

the authentication subsystem 2002 is further configured to store the first ID and the capability cooperation information synchronously, and send a notification of successful application to the third party capability open platform 300.

Specifically, the portal subsystem 2003 is a centralized presentation portal for the capability introduction service, and is responsible for providing the capability sale service to the application development terminal 400 and providing the capability access service to the third party capability development platform 300. In the embodiment of the present invention, the intention of collaboration between the third party capability open platform 300 and the capability import system 200 may be bidirectional, that is, the capability import system 200 may find the third party capability open platform 300 of the target according to the requirement of the application development terminal 400 to achieve a collaboration relationship, or the third party capability open platform 300 may send a capability collaboration application to the capability import system 200 to achieve a collaboration relationship, which is not limited herein. The following description will be made in detail by taking an example in which the third party capability opening platform 300 sends a capability cooperation application to the capability introduction system 200.

Firstly, a third-party capability open platform 300 logs in an EP/AP self-service area in the portal subsystem 2003, and provides corresponding information such as qualification documents, capability product data and success cases according to a cooperation application template provided by the EP/AP self-service area; after receiving the cooperation application information provided by the third party capability opening platform 300, the portal subsystem 2003 sends the capability cooperation application information to the operation management subsystem 2004, and the operation management subsystem 2004 receives the capability cooperation application information and verifies the capability cooperation application information. Specifically, whether the data provided by the third-party capability open platform 300 conforms to the business direction of the capability introduction system is checked, and the feasibility of the capability product in the capability product data is evaluated according to the modification specification. And when the cooperation application information is determined not to conform to the service direction of the capability introduction system, sending related application development data and cooperation specification data to the third-party capability open platform 300, and modifying the provided capability product data by the third-party capability open platform 300 according to the application development data and the cooperation specification data. When a transformation scheme of a capability product is achieved between the third party capability opening platform 300 and the capability introduction system 200, the third party capability opening platform 300 modifies the capability product data according to the data sent by the capability introduction system 200. Wherein, the capability introduction system 200 is responsible for technical testing of the modified capability product, the third party capability open platform 300 is responsible for providing capability support for the modified capability product, when the operations management subsystem 2004 determines that the modified capability product passes the technical test, sending the test result to the capacity management subsystem 2005, generating, by the capacity management subsystem 2005, a third party capacity openness platform ID based on the capacity cooperation application information of the third party capacity openness platform 300, and synchronously store the third party capability open platform ID and the capability cooperation application information to the authentication subsystem 2002, and the authentication subsystem 2002 sequentially sends the synchronization result to the capacity management subsystem 2005 and the operation management subsystem 2004, after receiving the synchronization result, the operation management subsystem 2004 sends a notification of success of capability cooperation application to the third party capability open platform. The flow of the specific capability cooperation application is shown in fig. 4 in the method embodiment. In the embodiment of the present invention, the operation management subsystem 2004 is mainly used for issuing management of portal contents such as application and application products, capability and capability products, auditing management of application and application products, capability and capability products, and the like, and for providing customer service support to the application development terminal 400, providing statistical analysis data required by the operation system to the system operation terminal, and managing the cooperation relationship with the third party capability development platform 300. The capacity management subsystem 2005 is mainly used for undertaking management work of information related to capacity, and includes: life cycle management, a policy configuration center, charging policy management, state query, AP/EP information maintenance and capability component remote management. The life cycle management is mainly used for managing the life cycles of the capacity, the capacity product, the application issued by the application development end and the application product provided by the third-party capacity open platform; the strategy configuration center is mainly used for capacity authentication configuration information management, capacity resource configuration management, application authentication configuration information management, application development end SLA, SLA strategy configuration management, application security strategy configuration management and the like.

In the embodiment of the present invention, the system further includes a third party capability open platform exit cooperative application process, and a specific exit cooperative application process is shown in fig. 7.

In this embodiment of the present invention, the portal subsystem 2003 is further configured to receive a capability online request sent by the third party capability opening platform 300;

the operation management subsystem 2004 is further configured to, based on the capability online request received by the portal subsystem 2003, check the capability online information provided by the third party capability open platform 300;

the capability management subsystem 2005 is further configured to generate a second ID when the operation management subsystem 2004 determines that the capability online information is approved;

the authentication subsystem 2002 is further configured to store the second ID and the capability online information synchronously, and send a notification that the capability online is successful to the third party capability open platform 300.

Specifically, the third party capability opening platform 300 logs in the portal subsystem 2003 and fills in a capability on-line application in an EP/AP self-service area in the portal subsystem 2003; the portal subsystem 2003 receives the capability online application, sends the capability online application to the operation management subsystem 2004, the operation management subsystem 2004 stores the capability online application and submits the capability online application to the capability management subsystem 2005, and the capability management subsystem 2005 receives the capability online application and generates a second ID based on the capability online application, namely a capability ID, and then sends a capability online verification request to the operation management subsystem 2004; after receiving the capability on-line verification request, the operation management subsystem 2004 verifies the capability on-line information provided by the third party capability opening platform 300. The specific audit objects include: capability information, capability service information, capability configuration information and the like of the application capability online. And when the verification is determined to pass, synchronously storing the capability ID and the capability information in the capability on-line application, and sending a notification of success of the capability on-line application to the third-party capability open platform 300. The flow of the specific capability on-line application is shown in fig. 5 in the method embodiment.

In the embodiment of the present invention, the system further includes a capability offline process, and a specific capability offline process is shown in fig. 8.

In this embodiment of the present invention, the portal subsystem 2003 is further configured to receive a capability product online request sent by the third party capability opening platform 300;

the operation management subsystem 2004 is further configured to audit capability product online information provided by the third party capability open platform 300 based on the capability product online request received by the portal subsystem 2003;

the capability management subsystem 2005 is further configured to generate a third ID when the operation management subsystem 2004 determines that the online information of the capability product is approved;

the authentication subsystem 2002 is further configured to store the third ID and the online information of the capability product synchronously, and send a notification that the capability product is successfully online to the third party capability open platform 300

Specifically, the third party capability opening platform 300 logs in a portal subsystem 2003, and fills in an online application of a capability product from a service area through an AP/EP in the portal subsystem 2003; the portal subsystem 2003 receives the capability product on-line application, and then sends the capability product on-line application to the operation management subsystem 2004 and the capability management subsystem 2005, and the capability management subsystem 2005 receives the capability product on-line application, and then generates a third ID, namely a capability product ID, based on the capability product on-line application; and sends a capability product audit notification to the operations management subsystem 2004. In an embodiment of the present invention, the system further comprises a service support subsystem 2006. The capacity management subsystem 2005 is configured to send a capacity product service code application to the service support subsystem 2006 while sending a capacity product audit notification to the operation management subsystem 2004, and the service support subsystem 2006 receives the capacity product service code application and sends a result notification of the capacity product service code to the capacity management subsystem 2005. In addition, after receiving the audit notification, the operation management subsystem 2004 audits the data provided in the capability product on-line application, and when determining that the data provided in the capability product on-line application passes the audit, performs a product test on the capability product applied on-line in the capability product on-line application, and when determining that the capability product test passes, stores the capability product on-line application information and the capability product ID. And sends a notification of successful online application of the capability product to the third party capability opening platform 300. Specifically, the flow of the online application of the capability product is shown in fig. 6. In the embodiment of the present invention, the capability product instantiates a certain capability, the authentication subsystem 2002 provides different charging policy templates according to types of different capabilities, and when the third party capability open platform 300 initiates a capability product shelf request to the portal subsystem 2003, the capability product information applied for online is filled according to the charging policy template provided by the authentication subsystem 2002, and other related data are attached. In the embodiment of the present invention, the service support subsystem 2006 is mainly used for generating an order relationship of a capability service, synchronizing the order relationship, applying a capability service code provided by a capability introduction system, charging for capability use, synchronizing capability use records, and providing a settlement function for a third party capability open platform and an application development end, so that other departments can obtain benefits for providing capability and developing applications.

In the embodiment of the present invention, the system further includes a process of offline the capability product, and the process of offline the specific capability product is as shown in fig. 9.

In this embodiment of the present invention, the portal subsystem 2003 is further configured to receive a capability access request sent by the application development terminal 400;

the access subsystem 2001 is further configured to generate capability access Token information based on the capability access request received by the portal subsystem 2003, and send the capability access Token information to the third-party capability open platform 300 to which the capability access request is directed; receiving a verification request of the ability access Token information sent by the third party ability open platform 300; when the verification of the capability access Token information is determined to pass based on the verification request of the capability access Token information, switching the current interface to the interface of the third party capability open platform 300 for the application development end to perform capability calling in the third party capability open platform 300.

Here, after receiving the capability access request, the portal subsystem 2003 generates capability access Token information based on the capability access request, sends the generated capability access Token information to the access subsystem 2001, the access subsystem 2001 stores the capability access Token information, performs attribute identification on a capability product to which the capability access Token information is directed, and sends the capability access Token information to the third party capability opening platform 300 when the access subsystem 2001 determines that the capability product belongs to a third capability, that is, a transparent capability. The transparent capability here means that when the application development terminal 400 calls the capability, both the capability authentication flow and the capability service flow are completed in the corresponding third-party capability open platform 300, and the capability introduction system is only responsible for the presentation, query and search of the capability product, and does not participate in the specific flow of the capability call, so that the application development terminal 400 and the third-party capability open platform 300 perform direct interaction. After receiving the capability access Token information, the third party capability openness platform 300 verifies the capability access Token information, and when it is determined that the capability access Token information is verified, sends a notification of successful verification to the access subsystem 2001, and after receiving the notification of successful verification, the access subsystem 2001 triggers the portal subsystem 2003 to jump the current interface to the interface of the third party capability openness platform 300, and the application development end 400 directly performs capability product calling on the third party capability openness platform 300, and meanwhile, the third party capability openness platform 300 synchronously stores calling record information of the capability access Token information called by the application development end 400 to the access subsystem 2001. The flow of introduction of specific transparency capability is shown in fig. 15 in the method embodiment.

Fig. 21 is a schematic structural diagram of a third party capability opening platform according to an embodiment of the present invention, and as shown in fig. 21, the third party capability opening platform 300 includes:

a receiving unit 3001, configured to receive an ability product invocation request sent by an application development end, where the ability product invocation request carries first ability Token information;

a processing unit 3002, configured to send, to a capability import system, a verification request of the first capability Token information when determining that the first capability Token information received by the receiving unit 3001 is not locally stored, and receive a verification result sent by the capability import system;

a transmission unit 3003; the application development end is configured to determine, according to the verification result received by the processing unit 3002, that the first capability Token information passes verification, and when the term of the first capability Token information is valid, send a notification that the capability product invocation is successful to the application development end.

In this embodiment of the present invention, the third party capability opening platform 300 further includes: a saving unit (not shown in the figure), configured to synchronously save, to the capability importing system, the call record information that the first capability Token information is called by the application development end within the validity period.

In this embodiment of the present invention, the processing unit 3002 is further configured to send a capability cooperation request to the capability introduction system, and receive a capability cooperation notification sent by the capability introduction system based on the capability cooperation request; when the capability cooperation request is determined to be successful according to the capability cooperation notification, sending a capability online request to the capability introduction system, and receiving a capability online notification sent by the capability introduction system based on the capability online request; when the capability on-line request is determined to be successful according to the capability on-line notification, sending a capability product on-line request to the capability introduction system, and receiving a capability product on-line notification sent by the capability introduction system based on the capability product on-line request; and when the capability product is determined to be successfully online according to the online notification of the capability product, calling the capability product through the capability introduction system supply and use development end.

In this embodiment of the present invention, the receiving unit 3001 is further configured to receive capability access Token information generated by the capability introduction system based on the capability access request sent by the application development end; and when the capability introduction system is determined to switch the current interface to the interface of the third-party capability open platform, receiving a capability product calling request sent by an application development terminal through the third-party capability open platform.

The sending unit 3003 is further configured to send, to the capability introduction system, a notification that the verification of the capability access Token information is successful when it is determined that the verification of the capability access Token information is passed, where the notification that the verification of the capability access Token information is successful is used for the capability introduction system to switch the current interface to the interface of the third-party capability open platform.

In this embodiment of the present invention, the saving unit (not shown in the figure) is further configured to synchronously save the call record information, called by the application development end, of the capability access Token information to the capability importing system.

Fig. 22 is a schematic structural diagram of an application development end according to an embodiment of the present invention, and as shown in fig. 22, the application development end 400 includes:

a sending unit 4001, configured to send an acquisition request of capability Token information to a capability introduction system, where the acquisition request of the capability Token information carries a capability ID;

a receiving unit 4002, configured to receive first capability Token information generated by the capability introduction system based on the capability ID;

the calling unit 4003 calls the capability product of the third-party capability open platform according to the first capability Token information.

In this embodiment of the present invention, the receiving unit 4002 is further configured to receive URL information of a third party capability open platform generated by the capability importing system based on the first capability Token information;

the calling unit 4003 is specifically configured to call a capability product of the third party capability open platform according to the first capability Token information and the URL information of the third party capability open platform.

In this embodiment of the present invention, the sending unit 4001 is further configured to send a capability access request to a capability introduction system;

the invoking unit 4003 element is further configured to invoke, by the interface of the third-party capability open platform, a capability product of the third-party capability open platform when it is determined that the capability importing system switches the current interface to the interface of the third-party capability open platform based on the capability access request.

In practical applications, the access subsystem 2001, the authentication subsystem 2002, the portal subsystem 2003, the operation management subsystem 2004, the capability management subsystem 2005, and the service support subsystem 2006 may all be implemented by a Central Processing Unit (CPU), a microprocessor unit (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like located in the capability introduction system.

The receiving unit 3001, the processing unit 3002, the sending unit 3003, and the storing unit may be implemented by a Central Processing Unit (CPU), a microprocessor unit (MPU), a Digital Signal Processor (DSP), or a Field Programmable Gate Array (FPGA), which is located on the third-party capability open platform.

The sending unit 4001, the receiving unit 4002, and the called unit 4003 may be implemented by a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), or a Field Programmable Gate Array (FPGA), etc., which are located at the application development end.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, systems according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A capability introduction method of a capability opening platform is characterized by comprising the following steps:

receiving a capability product calling request sent by an application development terminal, wherein the capability product calling request carries Token information of a first capability;

2. The method of claim 1, wherein prior to receiving the capability product invocation request sent by the application development side, the method further comprises:

3. The method according to claim 2, wherein before said sending the first capability Token information to the application development end, the method further comprises:

4. The method of claim 1, wherein prior to receiving the capability product invocation request sent by the application development side, the method further comprises:

5. The method according to claim 4, wherein after the sending the notification of successful application to the third party capability openness platform, the method further comprises:

6. The method of claim 5, wherein after the sending of the notification that the capability on-line is successful to the third party capability openness platform, the method further comprises:

7. A capability introduction method of a capability opening platform is characterized by comprising the following steps:

8. The method of claim 7, wherein after the switching the current interface to the interface of the third party capability open platform, the method further comprises:

9. A capability introduction method of a capability opening platform is characterized by comprising the following steps:

10. The method of claim 9, wherein after sending the notification to the application development end that the capability product invocation was successful, the method further comprises:

11. The method of claim 9, wherein prior to receiving the capability product invocation request sent by the application development side, the method further comprises:

12. A capability introduction method of a capability opening platform is characterized by comprising the following steps:

13. The method of claim 12, wherein after receiving the capability product invocation request sent by the application development side through the third party capability development platform, the method further comprises:

14. A capability introduction method of a capability opening platform is characterized by comprising the following steps:

calling a capability product of a third-party capability open platform according to the first capability Token information;

before calling the capability product of the third-party capability open platform according to the first capability Token information, the method further comprises the following steps:

correspondingly, the calling the capability product of the third-party capability open platform according to the first capability Token information includes: and calling the capability product of the third-party capability open platform according to the first capability Token information and the URL information of the third-party capability open platform.

15. A capability introduction method of a capability opening platform is characterized by comprising the following steps:

sending a capability access request to a capability introduction system;

16. A capability introduction system for a capability openness platform, the system comprising:

17. The system according to claim 16, wherein the access subsystem is further configured to receive an acquisition request of the Token information sent by the application development end, and send the Token information of the first capability generated by the authentication subsystem based on the acquisition request to the application development end;

18. The system according to claim 17, wherein the access subsystem is further configured to generate URL information of a third party capability open platform based on the first capability Token information generated by the authentication subsystem; and sending the first ability Token information and the URL information to the application development end, wherein the first ability Token information and the URL information are used for sending a calling request of an ability product to the third party ability open platform by the application development end.

19. The system of claim 16, further comprising: the system comprises a portal subsystem, an operation management subsystem and a capacity management subsystem; wherein,

20. The system of claim 19, wherein the portal subsystem is further configured to receive a capability on-line request sent by a third party capability opening platform;

21. The system of claim 20, wherein the portal subsystem is further configured to receive a capability product on-line request sent by the third party capability opening platform;

and the authentication subsystem is also used for synchronously storing the third ID and the online information of the capacity product and sending a notification that the capacity product is successfully online to the third-party capacity open platform.

22. A capability introduction system for a capability openness platform, the system comprising:

a portal subsystem and an access subsystem; wherein,

23. The system according to claim 22, wherein the access subsystem is further configured to synchronously save call record information of the capability access Token information called by the application development end.

24. A third party capability opening platform, comprising:

25. The open platform of third party capabilities of claim 24, further comprising:

26. The platform of claim 24, wherein the processing unit is further configured to send a capability cooperation request to the capability introduction system, and receive a capability cooperation notification sent by the capability introduction system based on the capability cooperation request; when the capability cooperation request is determined to be successful according to the capability cooperation notification, sending a capability online request to the capability introduction system, and receiving a capability online notification sent by the capability introduction system based on the capability online request; when the capability on-line request is determined to be successful according to the capability on-line notification, sending a capability product on-line request to the capability introduction system, and receiving a capability product on-line notification sent by the capability introduction system based on the capability product on-line request; and when the capability product is determined to be successfully online according to the online notification of the capability product, calling the capability product through the capability introduction system supply and use development end.

27. A third party capability opening platform, comprising:

the receiving unit is used for receiving the ability access Token information generated by the ability access request sent by the application development end by the ability introduction system; when the capacity introduction system is determined to switch the current interface to the interface of the third-party capacity open platform, receiving a capacity product calling request sent by an application development terminal through the third-party capacity open platform;

28. The open platform of third party capabilities of claim 27, further comprising:

29. An application development terminal, comprising:

the calling unit is used for calling the capability product of the third-party capability open platform according to the first capability Token information;

the receiving unit is further configured to receive URL information of a third party capability open platform generated by the capability introduction system based on the first capability Token information;

30. An application development terminal, comprising: