Online business method, system and apparatus based on open application programming interface
First Claim
1. A method comprising:
- receiving a first invocation request that invokes a plurality of Application Programming Interfaces (APIs), the plurality of APIs including a first API and a second API;
determining whether an invocation relationship exists among the plurality of APIs; and
in response to determining that the invocation relationship exists among the plurality of APIs,determining an invocation sequence that invokes the second API through the first API;
determining a first Internet Service Provider (ISP) server that provides a first service corresponding to the first API;
requesting the first ISP server to send a second invocation request to a second ISP server that provides a second service corresponding to the second API according to the invocation sequence; and
receiving from the first ISP server a service page from the second ISP server corresponding to the second API that processes the second invocation request.
1 Assignment
0 Petitions
Accused Products
Abstract
The present disclosure introduces a method, a system and an apparatus of implementing online transaction according to Open API. In one aspect, a method includes: receiving a first invocation request to invoke an Open API from a third party development server according to a user'"'"'s transaction request; determining an ISP server corresponding to the Open API as requested to be invoked in the invocation request; sending the first invocation request to the determined ISP server; receiving a service page returned by the ISP server according to the first invocation request; and sending the service page to the third party development server for processing the service page and sending the processed service page to the user, the processing comprising embedding the service page into a page corresponding to the transaction request.
24 Citations
26 Claims
-
1. A method comprising:
-
receiving a first invocation request that invokes a plurality of Application Programming Interfaces (APIs), the plurality of APIs including a first API and a second API; determining whether an invocation relationship exists among the plurality of APIs; and in response to determining that the invocation relationship exists among the plurality of APIs, determining an invocation sequence that invokes the second API through the first API; determining a first Internet Service Provider (ISP) server that provides a first service corresponding to the first API; requesting the first ISP server to send a second invocation request to a second ISP server that provides a second service corresponding to the second API according to the invocation sequence; and receiving from the first ISP server a service page from the second ISP server corresponding to the second API that processes the second invocation request. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. An apparatus comprising:
-
one or more data processing equipment; a memory having stored thereon computer-executable components that are executable by the one or more data processing equipment, the computer-executable components including; a first receiving unit that receives a first invocation request that invokes a plurality of Application Programming Interfaces (APIs), the plurality of APIs including a first API and a second API; a first ISP invocation unit that; determines an invocation relationship among the plurality of APIs, the invoke relationship including an invocation sequence that invokes the second API through the first API; determines a first Internet Service Provider (ISP) server that provides a first service corresponding to the first API; and requests the first ISP server to send a second invocation request to a second ISP server that provides a second service corresponding to the second API according to the invocation sequence; and a first invocation result feedback unit that receives from the first ISP server a service page from the second ISP server corresponding to the second API that processes the second invocation request. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21)
-
-
22. A system comprising:
-
a third party development server, including one or more data processing equipment, that; receives a request of a user; sends an invocation request to invoke a plurality of Application Programming Interfaces (APIs) to a transaction implementation server based on the request of the user, the plurality of APIs including a first API and a second API, the invocation request including an invocation relationship among the plurality of APIs, the invoke relationship including an invocation sequence that invokes the second API through the first API; receives a service page returned from a first Internet Service Provider (ISP) server that provides a first service corresponding to the first API to the transaction implementation server, the service page being received by the first ISP server from a second ISP server that provides a second service corresponding to the second API; and embeds the service page into a page corresponding to the request before providing to the user. - View Dependent Claims (23, 24, 25, 26)
-
Specification