CN103731427A - Conversation processing method, device and system - Google Patents
Conversation processing method, device and system Download PDFInfo
- Publication number
- CN103731427A CN103731427A CN201310754454.3A CN201310754454A CN103731427A CN 103731427 A CN103731427 A CN 103731427A CN 201310754454 A CN201310754454 A CN 201310754454A CN 103731427 A CN103731427 A CN 103731427A
- Authority
- CN
- China
- Prior art keywords
- api
- session
- handling process
- agency
- external transactions
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Library & Information Science (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to the technical field of computers, in particular to a conversation processing method, device and system. The conversation processing method, device and system are used for realizing conversation correlation when multiple APIs on an API agent are called in sequence by an API calling device. According to the method, when the API agent executes the processing process of the first API, conversation data of a conversation corresponding to the first API are cached; when the API agent executes the processing process of the second API, the conversation data cached when the processing process of the first API is executed are obtained according to an external event ID which is used for identifying the conversation corresponding to the first API and is included in a request for calling the second API, and the conversation is processed according to the obtained conversation data. The API agent obtains the conversation data of the conversation corresponding to the first API according to the external event ID included in the request for calling the second API, and processes the conversation according to the obtained conversation data, and therefore conversation correlation between the first API and the second API is realized.
Description
Technical field
The present invention relates to field of computer technology, relate in particular to a kind of method, apparatus and system of Dialog processing.
Background technology
Along with the fast development of Internet technology, increasing service can provide by the Internet, such as: make a reservation, book tickets, shopping etc.Under traditional approach, the WEB door that ISP sets up by oneself, for user provides service, while often changing due to customer demand, needs ISP according to customer demand, to constantly update the interface of WEB door, and maintenance difficulties is larger.
Therefore, part ISP by the service providing with application programming interface (Application Programming Interface, API) mode is opened to the outside world, third party developer or Internet firm utilize these API to develop multiple application, to meet user individual, multifarious demand.
As shown in Figure 1, the method of current a kind of conventional opening API is: calling the client of API and the API(API Backend of Internet service is really provided, API rear end) between increase API agency (API agency), the service that terminal use (End User) uses API rear end to provide by client, the local application (Native App) of running client or web application (Web App), via API proxy access API rear end, the service of using API rear end to provide.
API in Fig. 1 acts on behalf of conventionally also referred to as API gateway (API Gateway), ability open platform (Capability Open Platform) or API open platform (API Open Platform), realizes the function such as management, control, charging, interface protocol normalization of API Calls in API agency.
In Fig. 1, when the local application of terminal use on running client or web application, local application or web application need to call the API of API rear end.For the API Calls of API rear end is managed, control or interface format normalization etc., direct application programs opening API of API rear end, but opening API acts on behalf of to API, then act on behalf of opening API to application program by API.
In the open process of current API, call the invocation facility of the API on API agency, hereinafter to be referred as " API Calls equipment " (can be client in Fig. 1 or API rear end etc.) initiation between API Calls, is repeatedly independently, without setting up session association.But under some special business scenario, wish API Calls repeatedly to carry out session association but utilize the method for current opening API to realize.
Such as, in the process of the API Calls shown in Fig. 2, the main flow process of interacting message is as follows:
Client call API1;
API agency arranges session data and preserves;
The API2 of API proxy call API rear end;
The data that arrange before API agency obtains;
The API3 of API proxy call API rear end;
API agency arranges session data according to the data of returning of API3;
API acts on behalf of that comprehensive API3 calls return information and the data of fetching from session are carried out logical process;
API agency returns to calling of API1 and returns to client.
In the flow process shown in Fig. 2, can only in the API Calls flow process of a client, carry out setting and the extraction of session data, if client is initiated API Calls twice, call for the second time and cannot obtain the session data that API Calls arranges for the first time.
To sum up, current API open technique cannot realize API Calls equipment when successively calling multiple API of API agency, and the session data that the API calling below arranges while obtaining API Calls above, to realize the session association of multiple API Calls.
Summary of the invention
The embodiment of the present invention provides a kind of method, apparatus and system of Dialog processing, in order to realize the session association of API Calls equipment when successively calling the multiple API on API agency.
First aspect, the embodiment of the present invention provides a kind of method of Dialog processing, and described method comprises:
API agency receives the request of calling an API of sending from calling the API Calls equipment of the first API API;
Described API agency carries out the handling process of an API according to the request of calling an API, in the handling process of execution the one API, and the session data of the session that buffer memory the one API is corresponding;
Described API agency receives the request of calling the 2nd API of sending from calling the API Calls equipment of the 2nd API;
Described API agency carries out the handling process of the 2nd API according to the request of calling the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of the described session of buffer memory in the handling process of carrying out an API, according to the described session data obtaining, described session is processed.
In conjunction with first aspect, in the possible implementation of the first, described method also comprises:
Described API agency, carrying out in the handling process of an API, determines the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the API Calls equipment of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
Described API agency is in the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, judge that the external transactions ID of the session that an API definite in the handling process of carrying out an API is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises.
In conjunction with first aspect, in the possible implementation of the second, described method also comprises:
Described API agency, carrying out in the handling process of an API, determines the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the application of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
Described API agency is in the handling process of execution the one API, after determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the described session of buffer memory;
Described API agency is in the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, according to the sign of API supplier corresponding to the 2nd API sign, API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, judge that the internal affairs ID generating is consistent with the internal affairs ID generating in the handling process of execution the 2nd API in the handling process of execution the one API.
In conjunction with the possible implementation of the second of the possible implementation of the first of first aspect, first aspect, first aspect, in the third possible implementation of first aspect,
The handling process that described API agency carries out an API comprises: described API agency carries out the handling process of an API based on the expandable mark language XML file for describing an API handling process;
The handling process that described API agency carries out the 2nd API comprises: described API agency carries out the handling process of the 2nd API based on the XML file for describing the 2nd API handling process.
Second aspect, the embodiment of the present invention also provides a kind of method of Dialog processing, and described method comprises:
API API agency, carry out in the handling process of an API, the response of the API that API Calls equipment returns from described API Agency, obtain the external transactions ID of the session that an API is corresponding; Or API Calls equipment is to described API agency transmission external transactions ID, so that described API agency is defined as the described external transactions ID receiving the external transactions ID of the session that the one API is corresponding.
Described API Calls equipment sends the request of calling the 2nd API to described API agency, described request comprises the external transactions ID of the described session that a described API is corresponding, so that described API acts on behalf of according to the external transactions ID of described session, obtain described API agency at the session data of carrying out the described session of buffer memory in an API handling process, and according to the session data of the described session of obtaining, described session is processed.
The third aspect, the embodiment of the present invention also provides a kind of application programming interface API agency, and described API agency comprises:
The first processing module, the request of calling an API of sending for the API Calls equipment receiving from calling the first API API; According to the request of calling an API, carry out the handling process of an API, in the handling process of execution the one API, the session data of the session that buffer memory the one API is corresponding;
The second processing module, the request of calling the 2nd API of sending for the invocation facility receiving from calling the 2nd API; According to the request of calling the 2nd API, carry out the handling process of the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of described the first processing module described session of buffer memory in the handling process of carrying out an API, according to the described session data obtaining, described session is processed.
In conjunction with the third aspect, in the possible implementation of the first, described the first processing module also for: carrying out the handling process of an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the API Calls equipment of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
Described the second processing module also for: carrying out the handling process of the 2nd API, obtain before described the first processing module carries out the session data of the described session of buffer memory in the handling process of an API, judge that the external transactions ID of the session that the API that determines is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises in the handling process of carrying out an API.
In conjunction with the third aspect, in the possible implementation of the second, described the first processing module also for: carrying out the handling process of an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the invocation facility of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding; After determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the described session of buffer memory;
Described the second processing module also for: carrying out the handling process of the 2nd API, obtain before described the first processing module carries out the session data of the described session of buffer memory in the handling process of an API, according to API supplier corresponding to the 2nd API sign, the sign of the API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, the internal affairs ID that judgement generates in the handling process of execution the 2nd API is consistent with the internal affairs ID that described the first processing module generates in the handling process of execution the one API.
In conjunction with the possible implementation of the second of the possible implementation of the first of the third aspect, the third aspect, the third aspect, in the third possible implementation of the third aspect,
Described the first processing module is specifically for the handling process of carrying out an API based on expandable mark language XML file for describing an API handling process;
Described the second processing module is specifically for the handling process of carrying out the 2nd API based on XML file for describing the 2nd API handling process.
Fourth aspect, the embodiment of the present invention also provides a kind of API Calls equipment, and described equipment comprises:
The first processing module, for the handling process of carrying out an API API API agency, obtains the external transactions ID of the session that an API is corresponding from described API Agency the response of an API who returns; Or send external transactions ID to described API agency, so that described API agency is defined as the described external transactions ID receiving the external transactions ID of the session that the one API is corresponding;
The second processing module, for sending the request of calling the 2nd API to described API agency, described request comprises the external transactions ID of the described session that a described API is corresponding, so that described API acts on behalf of according to the external transactions ID of described session, obtain described API agency at the session data of carrying out the described session of buffer memory in an API handling process, and according to the session data of the described session of obtaining, described session is processed.
The 5th aspect, the embodiment of the present invention also provides a kind of system of Dialog processing, comprises application programming interface API agency and API Calls equipment,
Described API agency is used for: according to the request of calling an API receiving, carry out the handling process of an API, and in the handling process of execution the one API, the session data of the session that buffer memory the one API is corresponding; According to the request of calling the 2nd API receiving from described API Calls equipment, carry out the handling process of the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of the described session of buffer memory in the handling process of carrying out an API, according to the described session data obtaining, described session is processed;
Described API Calls equipment is used for: to described API agency, send the request of calling the 2nd API, described request comprises the external transactions ID of the described session that an API is corresponding.
In the possible implementation in the 5th aspect, the first aspect the 5th, described API agency also for: in the handling process of carrying out an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to described API Calls equipment; Described API Calls equipment also for: described API agency, carry out the handling process of an API, receive the external transactions ID of the described session of described API agent advertisement; Or
Described API Calls equipment also for: described API agency, carry out the handling process of an API, external transactions ID issued to described API agency; Described API agency also for: receive the external transactions ID sending from described API Calls equipment, and the external transactions ID of reception be defined as to the external transactions ID of the session that an API is corresponding;
Described API agency also for: in the handling process of carrying out the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, judge that the external transactions ID of the session that an API definite in the handling process of carrying out an API is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises.
In the possible implementation in the 5th aspect, the second aspect the 5th, described API agency also for: in the handling process of carrying out an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to described API Calls equipment; Described API Calls equipment also for: described API agency, carry out the handling process of an API, receive the external transactions ID of the described session of described API agent advertisement; Or
Described API Calls equipment also for: described API agency, carry out the handling process of an API, external transactions ID issued to described API agency; Described API agency also for: receive the external transactions ID sending from described API Calls equipment, and the external transactions ID of reception be defined as to the external transactions ID of the session that an API is corresponding;
Described API agency also for: in the handling process of carrying out an API, after determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the described session of buffer memory; In the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, according to the sign of API supplier corresponding to the 2nd API sign, API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, judge carrying out the internal affairs ID that generates in the handling process of the 2nd API and to generate internal affairs ID in the handling process of execution the one API consistent.
In conjunction with the possible implementation of the second of the possible implementation of the first of the 5th aspect, the 5th aspect, the 5th aspect, in the third the possible implementation aspect the 5th, described API agency specifically for:
Based on the expandable mark language XML file for describing an API handling process, carry out the handling process of an API;
Based on the XML file for describing the 2nd API handling process, carry out the handling process of the 2nd API.
The method, apparatus and system of the Dialog processing that the employing embodiment of the present invention provides, API Calls equipment is when calling the 2nd API, calling in the request of the 2nd API, carried the external transactions ID for identifying the session that an API is corresponding, make API agency to obtain the session data of carrying out the session of buffer memory in an API handling process according to the external transactions ID calling in the request of the 2nd API, and according to the session data obtaining, session is processed, thereby realized the session association of an API and the 2nd API.
Further, API acts on behalf of according to the sign of API supplier's sign, API rear end, and external transactions ID, generates corresponding internal affairs ID, thereby realize API agency, by multiple API suppliers, provides API, its can with multiple API back end interfaces.
Further, API acts on behalf of the handling process of the XML file execution API based on for describing API handling process, when the handling process of API need to be revised, without carrying out code compilation, redeploy, without the operation that stops API agency, just can realize the modification to API handling process.
The embodiment of the present invention also provides another kind of API agency, API generation method and API manner of execution, in order to solve in existing API generation method, adopts the mode of coding to generate API, and method complexity, is not easy the problem realizing.
The 6th aspect, the embodiment of the present invention provides a kind of application programming interface API agency, and described API agency comprises:
API developers, for graphical API development interface is provided, and the API receiving in the described development interface providing for generating API generates instruction; According to the described API receiving, generate instruction and generate the API proxy resources that is used for the handling process of describing described API; The described API proxy resources generating is issued to API agent engine;
API agent engine, the described API proxy resources sending for preserving the described API developers of reception, and receiving after the request of API described in API Calls equipment calls, according to the request of calling described API, carry out the handling process of API described in described API proxy resources; If there is the operation of buffer memory session data in the handling process of described API, according to the request of calling described API, generates session data, and the session data of generation is cached in data buffer storage; If there is the operation of obtaining session data in the handling process of described API, according to the request of calling described API, from data buffer storage, read session data;
Data buffer storage, the session data generating for buffer memory API agent engine, and the session data that API agent engine is read sends to API agent engine.
The 7th aspect, the embodiment of the present invention provides a kind of method that generates application programming interface API, and described method comprises:
The API that API developers in API agency receives for generating API in graphical API development interface generates instruction;
Described API developers generates instruction according to the described API receiving and generates the API proxy resources that is used for the handling process of describing described API;
Described API developers is issued the API agent engine in described API agency by the described API proxy resources generating, so that described API agent engine receiving after the request of API described in API Calls equipment calls, according to the request of calling described API receiving, carry out the handling process of API described in described API proxy resources.
Eight aspect, the embodiment of the present invention provides a kind of method of executive utility DLL (dynamic link library) API handling process, and described method comprises:
API agent engine in API agency receives the request of calling API that API Calls equipment sends;
Described API agent engine is according to the request of calling described API receiving, carry out the handling process of API described in the API proxy resources for describing described API, wherein said API resource is that the API developers in described API agency generates and issue described API agent engine according to the API generation instruction for generating described API receiving;
If there is the operation of buffer memory session data in the handling process of described API, described API agent engine generates session data according to the request of calling described API, and the session data of generation is cached in the data buffer storage in described API agency; If there is the operation of obtaining session data in the handling process of described API, described API agent engine reads session data according to the request of calling described API from described data buffer storage.
The another kind of API agency, API generation method and the API manner of execution that adopt the embodiment of the present invention to provide, by graphic interface is provided, receive API and generate instruction, according to the API receiving, generate instruction and generate API proxy resources, API agent engine is being received after the request of calling API, carry out the handling process in API proxy resources, thereby without coding, easily generate API.
Accompanying drawing explanation
Fig. 1 is the schematic diagram of the method for current a kind of conventional opening API;
Fig. 2 is the flow chart of current a kind of API Calls process;
The structural representation of the session processing system that Fig. 3 provides for the embodiment of the present invention;
The structural representation that the first API that Fig. 4 provides for the embodiment of the present invention acts on behalf of;
The structural representation of the API developers that Fig. 5 provides for the embodiment of the present invention;
The structural representation of the API agent engine that Fig. 6 provides for the embodiment of the present invention;
The affairs ID mapping method schematic diagram that Fig. 7 provides for the embodiment of the present invention;
The API that Fig. 8 provides for the embodiment of the present invention creates the layout interface schematic diagram of payment;
The session parameter that Fig. 9 provides for the embodiment of the present invention arranges the schematic diagram at interface;
The interface schematic diagram that external transactions ID create-rule is set that Figure 10 provides for the embodiment of the present invention;
The interface schematic diagram that external transactions ID is set that Figure 11 provides for the embodiment of the present invention;
Figure 12 preserves regular interface schematic diagram for the session data that arranges that the embodiment of the present invention provides;
The API that Figure 13 provides for the embodiment of the present invention creates the schematic diagram of the flow file paying;
The schematic diagram that conversation strategy file is set that Figure 14 provides for the embodiment of the present invention;
Figure 15 is the schematic diagram that embodiment of the present invention API confirms the layout interface paying;
The interface schematic diagram of session parameter is obtained in the setting that Figure 16 provides for the embodiment of the present invention;
Figure 17 obtains regular interface schematic diagram for the external transactions ID that arranges that the embodiment of the present invention provides;
Figure 18 is that in the embodiment of the present invention, API confirms that payment and API create the schematic diagram of the session association paying;
Figure 19 is in the embodiment of the present invention, and API supplier realizes the method flow diagram of API session association;
Figure 20 is the method flow diagram of the embodiment of the present invention one;
Figure 21 is the method flow diagram of the embodiment of the present invention two;
The structural representation that the second API that Figure 22 provides for the embodiment of the present invention acts on behalf of;
The structural representation that the third API that Figure 23 provides for the embodiment of the present invention acts on behalf of;
The procedure schematic diagram of the first Dialog processing that Figure 24 provides for the embodiment of the present invention;
The procedure schematic diagram of the second Dialog processing that Figure 25 provides for the embodiment of the present invention;
The structural representation that the 4th kind of API that Figure 26 provides for the embodiment of the present invention acts on behalf of;
The structural representation of the API Calls equipment that Figure 27 provides for the embodiment of the present invention;
The procedure schematic diagram of a kind of API of generation that Figure 28 provides for the embodiment of the present invention;
The procedure schematic diagram of a kind of API of execution handling process that Figure 29 provides for the embodiment of the present invention.
Embodiment
The embodiment of the present invention provides a kind of method, apparatus and system of Dialog processing, in order to realize the session association of API Calls equipment when successively calling the multiple API on API agency.
In the method for a kind of Dialog processing providing in the embodiment of the present invention, API agency receives the request of calling an API of sending from calling the API Calls equipment of an API; API agency carries out the handling process of an API according to the request of calling an API, in the handling process of execution the one API, and the session data of the session that buffer memory the one API is corresponding; API agency receives the request of calling the 2nd API of sending from calling the API Calls equipment of the 2nd API; API agency carries out the handling process of the 2nd API according to the request of calling the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of the session of buffer memory in the handling process of carrying out an API, according to the session data obtaining, session is processed.
During the embodiment of the present invention is passed through, call the invocation facility of the 2nd API when calling the 2nd API, calling in the request of the 2nd API, carried the external transactions ID for identifying the session that an API is corresponding, make API agency to obtain the session data of carrying out the session of buffer memory in an API handling process according to the external transactions ID calling in the request of the 2nd API, and according to the session data obtaining, session is processed, thereby realized the session association of an API and the 2nd API.
The embodiment of the present invention also provides a kind of API agency, API generation method and API manner of execution, in order to solve in existing API generation method, adopts the mode of coding to generate API, and method complexity, is not easy the problem realizing.
The API agency that the embodiment of the present invention provides comprises: API developers, and for graphical API development interface is provided, and the API receiving in the described development interface providing for generating API generates instruction; According to the described API receiving, generate instruction and generate the API proxy resources that is used for the handling process of describing described API; The described API proxy resources generating is issued to API agent engine; API agent engine, the described API proxy resources sending for preserving the described API developers of reception, and receiving after the request of API described in API Calls equipment calls, according to the request of calling described API, carry out the handling process of API described in described API proxy resources; If there is the operation of buffer memory session data in the handling process of described API, according to the request of calling described API, generates session data, and the session data of generation is cached in data buffer storage; If there is the operation of obtaining session data in the handling process of described API, according to the request of calling described API, from data buffer storage, read session data; Data buffer storage, the session data generating for buffer memory API agent engine, and the session data that API agent engine is read sends to API agent engine.
By graphic interface is provided, receive API and generate instruction, according to the API receiving, generate instruction and generate API proxy resources, API agent engine is being received after the request of calling API, carries out the handling process in API proxy resources, thereby without coding, easily generates API.
Below, by reference to the accompanying drawings the embodiment of the present invention is elaborated.
The structural representation of the session processing system that Fig. 3 provides for the embodiment of the present invention.As shown in Figure 3, this system comprises: API Calls equipment 301 and API agency 302, wherein
API agency 302 for: according to the request of calling an API receiving, carry out the handling process of an API, carrying out in the handling process of an API, the session data of the session that buffer memory the one API is corresponding; According to the request of calling the 2nd API receiving from API Calls equipment 301, carry out the handling process of the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of the described session of buffer memory in the handling process of carrying out an API, according to the described session data obtaining, session is processed;
API Calls equipment 301 for: to API agency 302, send the request of calling the 2nd API, request comprises the external transactions ID of the session that an API is corresponding.
The session processing system that the embodiment of the present invention provides has been realized the session association of an API and the 2nd API.When specific implementation, according to different application scenarioss, the mode that realizes an API and the 2nd API session association at least comprises following two kinds:
Mode one
API agency 302, carrying out in the handling process of an API, determines the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to API Calls equipment 301;
Mode two
API Calls equipment 301 is carried out in the handling process of API API agency 302, external transactions ID is issued to API agency 302, API agency 302 the external transactions ID receiving from API Calls equipment 301 is defined as the external transactions ID of the session that an API is corresponding.
A specific embodiment of mode one can be referring to embodiment mono-below, and a specific embodiment of mode two can be referring to embodiment bis-below.
In above-mentioned two kinds of modes, API agency 302 is in the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, also need to be in the case of judging that external transactions ID that the external transactions ID of session corresponding to an API of determining comprise with the request of calling the 2nd API is consistent, the external transactions ID comprising according to the request of calling the 2nd API obtains the session data of buffer memory in the handling process of execution the one API.
Here, API Calls equipment 301 can be any API Calls equipment that calls the API on API agency 302, such as: can be client or API rear end in Fig. 1.
When API Calls equipment 301 is client, API Calls equipment 301 inside comprise local application and/or web application, API Calls equipment 301, by calling local application or the web application in it, is realized to API agency 302 and is sent the request of calling API.When API Calls equipment 301 is API rear end, API Calls equipment 301, by calling the application program in it, sends the request of calling API to API agency 302.
Generally, API agency 302 only provides API by an API supplier (API Provider), and its only with an API back end interface, now the external transactions ID by session can a unique definite session, obtains the session data of this session.In the embodiment of the present invention, provide a kind of optional scheme, adopted this possibility, can realize API agency 302 and provide API by multiple API suppliers, its can with multiple API back end interfaces,
When API agency 302 provides API by multiple API suppliers, between different API suppliers' external transactions ID, may lead to a conflict because of repetition; When API agency 302 docking multiple API rear end, the external transactions ID of different API rear end also may lead to a conflict because of repetition.For head it off, in the possibility of the embodiment of the present invention, when API acts on behalf of 302 inter-process, need according to and API Calls equipment 301 between the external transactions ID of the session used when mutual generate the inner internal affairs ID(Inner Transaction ID that use of API agency 302), according to the internal affairs ID generating, can distinguish different API suppliers and different API rear ends.
Particularly, API agency 302 is in the processing procedure of execution the one API, after determining the external transactions ID of the session that an API is corresponding, need to be according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the session of buffer memory;
API agency 302 is in the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, need to and call the external transactions ID that the request of the 2nd API comprises according to the sign of API supplier corresponding to the 2nd API sign, API rear end that the 2nd API is corresponding, generate corresponding internal affairs ID;
API agency 302, under judging that the internal affairs ID generating in the handling process of carrying out the 2nd API is consistent with the external transactions ID generating in carrying out the handling process of an API, just can obtain the session data of the session of buffer memory in the handling process of an API.
API agency 302, carry out in the handling process of an API, can generate session data by buffer memory, such as, API Calls equipment 301 is initiated delivery operation by the request of calling an API, API agency 302 can, using the note check code in payment process as session data buffer memory, compare with the note check code of terminal use's input so that follow-up.API acts on behalf of 302 buffer memory session datas, and according to the external transactions ID of session, generates the internal affairs ID of session, the corresponding relation of the internal affairs ID of words that record generates and the session data of the session of buffer memory.
API agency 302 is for different API, when generating the internal affairs ID of session according to the external transactions ID of session, it is the identical create-rule based on introducing below, and for the different API of same session, its API supplier is identical, API rear end is also identical, and the external transactions ID of session in the API handling process that API Calls equipment 301 carries in the request of calling the 2nd API, therefore can realize the internal affairs ID generating in the handling process of the internal affairs ID that generates and an above-mentioned API identical in the handling process of above-mentioned the 2nd API, thereby in the handling process of the 2nd API, can obtain the session data of this session of buffer memory in an API handling process, thereby realize the session association of an API and the 2nd API.
The mode that generates the internal affairs ID of session according to the external transactions ID of session has multiple, as long as can distinguish different API suppliers and different API rear ends.Such as: can be by splicing as character string, i.e. internal affairs ID=API supplier ID+Transaction ID NameSpace+external transactions ID; Or use physical database or memory database relation table to preserve mapping relations etc.Here Transaction ID NameSpace is for distinguishing different API rear ends, and different API rear ends has different Transaction ID NameSpaces.
Here, API supplier's sign can be determined according to the title of API or the sign of API called in the request of API.Such as, in API agency 302, the API that arranging different API suppliers provides has different title prefixes, and records the corresponding relation of prefix and the API supplier sign of API Name.When API agency 302 is receiving after the request of calling API, according to the prefix of the title of API, determine API supplier's sign like this.Or in API agency 302, recorded the corresponding relation of sign and the API supplier sign of API, API Calls equipment 301 calls the sign of carrying API in the request of API, API agency 302 is receiving after the request of calling certain API, according to the sign of the API carrying in request, search the corresponding relation of sign and the API supplier sign of the API having recorded, can determine the API supplier's that this API is corresponding sign.
Or, API supplier's sign can be according to the universal resource identifier of API (Uniform Resource Identifier, URI) determine, in the URI of API, contain API supplier's API name prefix, by API name prefix, can determine API supplier's sign.
The sign of API rear end also can determine according to the sign of the title of API or API, and method is similar with the method for sign of determining API supplier above, repeats no more here.In addition, can also adopt mode below: if API Calls equipment 301 is client, in the request of calling API, carry the information of API rear end, such as IP address, API rear end title or API rear end sign etc., API agency 302 is receiving after this request of calling API, obtain above-mentioned information, according to the corresponding relation of the sign of the above-mentioned information of record and API rear end, determine the sign of API rear end.If API Calls equipment 301 is API rear end, call in the request of API without the information of carrying API rear end, API agency 302 can determine corresponding API rear end from this source address of calling the request of API.
In mode one, in the handling process of an API, API agency 302 need to determine the external transactions ID of session, and definite external transactions ID is returned to API Calls equipment 301.Here, API agency 302 determines that the method for the external transactions ID of session can include but not limited to following method:
Method one, generation automatically;
Method two, by calling in the request of an API, obtain;
Method three, from the response of API rear end, obtain.
It should be noted that, although only show an API Calls equipment 301 in Fig. 3, can there is session in API agency 302 in fact simultaneously and between multiple API Calls equipment 301.Be that API agency 302 may receive that multiple API Calls equipment 301 calls the request of API, API agency 302 can safeguard different sessions for different API Calls equipment 301, and the external transactions ID that each session is corresponding different, to distinguish different sessions.Thereby API agency 302, when receiving that certain API Calls equipment 301 calls the request of the 2nd API, obtains the session data of this session according to the external transactions ID carrying in the request of the 2nd API, can realize the differentiation of the session data of different sessions.
Below, for the definition mode of an API and the 2nd API in API agency 302, be illustrated.
Conventionally, the each API in API agency is developed by one or more API suppliers.Under traditional development scheme, by API supplier, encode to develop each API, there is code compilation, redeploy process, may need the operation that first stops API agency just can complete the loading of rewriting post code, API agency's use has been caused to impact.
In the preferred version that the embodiment of the present invention provides, extend markup language (eXtensible Markup Language, the XML) file based on for describing API is carried out the handling process of API.No longer by writing the mode of code, define the handling process of API, but adopt XML file to define.Such benefit is exactly, and when the handling process of API is modified, without carrying out code compilation, redeploys, and without the operation that stops API agency, just can realize the modification to API handling process.
Thereby, alternatively, API agency 302 specifically for:
Based on the XML file for describing an API handling process, carry out the handling process of an API, based on the XML file for describing the 2nd API handling process, carry out the handling process of the 2nd API.
The operation principle of the session processing system above, the embodiment of the present invention being provided is described.To the embodiment of the present invention, provide a kind of API agency who realizes API by graphic interface to be illustrated below.As this optional implementation of one that realizes the API agency of API by graphic interface, this API agency also may be used on, in the session processing system shown in Fig. 3, realizing the session association between multiple API.
In traditional API implementation method, API supplier realizes each API by coding.The mode of coding has higher requirements to API supplier's programming levels, and easily introduces wrong (Bug) in cataloged procedure, and the cycle of development& testing all can be long.In view of this, the embodiment of the present invention provides the API agency who realizes API by graphic interface shown in Fig. 4.
The structural representation that the first API that Fig. 4 provides for the embodiment of the present invention acts on behalf of, this API agency realizes the exploitation of API with graphic interface.As shown in Figure 4, this API acts on behalf of a side and one or more application terminals interface, and another and one or more API rear end (system of API active service is provided) interface externally also provide API development interface to one or more API suppliers.
Below, first the composition structure of the API agency in Fig. 4 is illustrated, then the method that realizes API by graphical API development interface is described.
First, as shown in Figure 4, this API agency comprises:
API acts on behalf of logic development device, is called for short API developers (API Builder) 401, for graphical API development interface is provided to API supplier;
Can there be multiple implementation at pattern development interface, such as: the graphic interface of WEB online mode, or graphic user interface (graphical user interface, GUI) Integrated Development Environment (Integrated Development Environment, IDE), such as the IDE interface of Eclipse;
API agent engine (API Proxy Engine) 402, for the API proxy resources developed based on API developers 401 (for describing the file of handling process of API), carry out the handling process of API (such as the execution of session association logic, create session, session data is saved in data buffer storage 403, from data buffer storage 403, read session data, to application terminal, provide API, and call API that API rear end provides etc.), alternatively, from the API parameter of API rear end, obtain the external transactions ID of session, generate internal affairs ID, complete the mapping of internal affairs ID and external transactions ID,
Data buffer storage (Data Cache) 403, for the session data of the current each session of buffer memory (session having created and also do not finish), alternatively, can support memory cache mode to store, and can support physical disk mode storage of session data by the file system 405 in connection layout 4 or database 404.
Particularly, API developers 401, for graphical API development interface is provided, and the API receiving in this development interface providing for generating API generates instruction; According to this API receiving, generate instruction and generate the API proxy resources that is used for the handling process of describing this API; This API proxy resources generating is issued to API agent engine 402;
In API agency shown in Fig. 4, API developers 401, API agent engine 402, data buffer storage 403 all can pass through trunking mode scalability and capacity, meet the requirement of reliability simultaneously.
Alternatively, this API agency also comprises: database (Database) 404 and/or file system (File) 405,
Wherein, database 404 for: the session data of data buffer storage 403 buffer memorys is preserved by database, can in equipment fault situation, be promoted reliability or expand buffer memory capacity by physical store, total relation database or non-relational database all can;
File system 405 for the session data of data buffer storage 403 buffer memorys is carried out to persistent storage with file mode, can promote reliability or expand buffer memory capacity by physical store in equipment fault situation.
About the storage of session data, can there is multiple implementation, such as, as shown in figure 22, in API agency, not comprising database or file system, session data is kept in data buffer storage.Or when storage of session data, adopt the mode shown in Figure 23, i.e. data buffer storage independently not in API agency, directly by session data buffer storage in API agent engine.In addition, in Figure 22, Figure 23, API agency can be docked multiple API rear end, and simultaneously for multiple clients provide API Calls interface.
Below, API developers 401 is elaborated.As shown in Figure 5, API developers 401 comprises:
Web graphic interface (Web GUI Interface) 4011, for providing graphical API that configuration interface is provided to API supplier;
API acts on behalf of generation module (API Proxy Generating Module) 4012, for the configuration information producing according to Web graphic interface 4011 API suppliers' operation, generate API proxy resources (API Proxy Resource), API agent engine 402 is acted on behalf of according to API API proxy resources that generation module 4012 produces and is carried out API and act on behalf of logic.
Alternatively, when specific implementation, the function that API can be acted on behalf of to generation module is realized by API agent engine 402.
The logic of the API proxy resources generating is specifically to be arranged by Web graphic interface 4011, saves as API and carries out flow file, and flow file is in series by multiple API strategies, and alternatively, these files are preserved in XML mode.As previously mentioned, adopt XML mode to preserve, can avoid, in traditional API implementation method, after to the code revision of API, amended code being compiled the process redeploying.
Below, API agent engine 402 is illustrated.
As shown in Figure 6, API agent engine 402 comprises:
API acts on behalf of Executive Module (API Proxy Execute Module) 4021, for carrying out according to API proxy resources corresponding to API request of loading, in the process of implementation, if there is the strategy that session or session data are set in discovery API handling process, resolve the API proxy resources file loading, to obtain or to generate the external transactions ID of session, realize the mapping of the external transactions ID of session and the internal affairs ID of session, the storage of session data or obtain;
Alternatively, API agent engine 402 also comprises affairs ID mapping block (Transaction ID Mapping Module) 4022, for realizing the mapping of external transactions ID and internal affairs ID.
Alternatively, API acts on behalf of Executive Module 4021 also for, the mapping of calling affairs ID mapping block 4022 and complete external transactions ID and internal affairs ID.API acts on behalf of Executive Module 4021 and calls the exemplary message of mapping that affairs ID mapping block 4022 completes external transactions ID and internal affairs ID as shown in example one.Alternatively, the function of affairs ID mapping block 4022 can directly be acted on behalf of Executive Module 4021 by API and complete, and is about to affairs ID mapping block 4022 and is incorporated into API and acts on behalf of in Executive Module 4021.
The mapping method of external transactions ID and internal affairs ID as shown in Figure 7.In Fig. 7, affairs ID NameSpace corresponding A PI rear end, different API rear ends has different affairs ID NameSpaces.Affairs ID mapping block generates internal affairs ID according to external transactions ID, API supplier's sign and affairs ID NameSpace, and is stored in data buffer storage 403.Alternatively, key-the value of the session data in data buffer storage 403 can be character string independently to the value in (Key-Value) (Value), also can be comprise complex format data as XML, JSON, can also be the binary data obtaining after data object serializing.
When realizing, same API supplier's affairs ID NameSpace can not repeat, same affairs ID NameSpace can be used in multiple API rear end of same API supplier, also can use different affairs ID NameSpaces, depend on the conflict that whether has external transactions ID NameSpace between different API rear ends, if there is conflict, need to use different affairs ID NameSpaces, if do not conflicted, can use identical affairs ID NameSpace, also can use different affairs ID NameSpaces.
The method that affairs ID mapping block 4022 is mapped as internal affairs ID by external transactions ID has a lot, such as, the mode that can adopt character string to splice, i.e. internal affairs ID=API supplier's sign+TransactionID NameSpace+external transactions ID; Or use physical database or memory database relation table to preserve mapping relations etc.
Alternatively, the agency of the API shown in Fig. 4 can realize different API is carried out to session association.As shown in figure 19, API supplier realizes API: create and pay (createPayment) and API: the step of confirming payment (ConfirmPayment) session association is as follows:
S1901, API supplier enter the interface (as shown in Figure 8, create and pay as example take API) of API developers 401;
S1902, API supplier arrange API and create payment, at API, create in payment and need to arrange session and buffer memory session data;
S1903, API supplier place the icon of the API strategy of " session (SetSession) is set " in API request or responding process;
S1904, API supplier click the icon of " session is set ", the parameter that session is set of opening as shown in Figure 9 arranges interface, at this interface inediting session attribute, wherein, session attribute can comprise: external transactions ID(is external transactions ID) obtain manner, external transactions ID create-rule (such as general unique identifier (Universally Unique Identifier, UUID)), external transactions ID NameSpace, session data are preserved rule, external transactions ID arranges rule etc.;
In step S1904, API supplier can arrange interface in the parameter that session is set and click after " editor " icon of " external transactions ID create-rule ", opens interface as shown in figure 10, carries out the setting of external transactions ID create-rule; API supplier can arrange interface in the parameter that session is set and click after " editor " icon of " external transactions ID arranges rule ", opens interface as shown in figure 11, carries out the setting of external transactions ID; API supplier can arrange interface in the parameter that session is set and click after " editor " icon of " session data is preserved rule ", opens interface as shown in figure 12, carries out session data and preserves regular setting.
By the setting of the 1st step to the 3 steps, the flow file that the API establishment generating pays as shown in figure 13, as can be seen from Figure 13,, for session (SetSession) is set, by another file (269378FC-DF75-D94B-35AA-F3B7D98A373F), define.
By in step S1904, session being set, strategy file 269378FC-DF75-D94B-35AA-F3B7D98A373F.xml as shown in figure 14 in the session (Set Session) that arranges of generation.
S1905, API supplier, in the interface of API developers 401 as shown in figure 15, arrange API and confirm to pay (confirmPayment), need to obtain session data in this API;
S1906, API supplier place the icon of " obtaining session " API strategy in API request or responding process;
S1907, API supplier click the icon of " obtaining session ", at the session parameter that obtains as shown in figure 16, arrange in interface, fill in the attribute that obtains session, the attribute that wherein obtains session can comprise: external transactions ID obtain manner, external transactions ID NameSpace, external transactions ID obtains rule.
In step S1907, API supplier can arrange interface in the parameter that session is set and click after " editor " icon of " external transactions ID obtains rule ", opens interface as shown in figure 17, carries out external transactions ID and obtains regular setting.
From Figure 16 and Figure 17, can find out, in API confirms to pay, external transactions ID obtains from API request, and can find out from Figure 11 and Figure 14, when session is set, external transactions ID is created in the response paying and taken back to API and create the invocation facility (response.body.paymentinfo.paymentID) paying by API, so when API creates the invocation facility paying when calling API confirmation payment, if be placed in by creating from API the external transactions ID obtaining the response paying before the request that API confirmation pays of calling, in the handling process of confirming to pay at API, just can obtain by this external transactions ID the session data of buffer memory when API creates payment, thereby realized, API confirms to pay and API creates the session association between paying.
Figure 18 realizes API to confirm that payment and API create the schematic diagram of the session association paying.As shown in figure 18, " paying sign " of in the 1st step, API being created in the response paying is set to external transactions ID; " paying sign " in the request of in the 2nd step, API being confirmed to pay is assigned to external transactions ID; The external transactions ID in the 3rd step, the 2nd step being obtained becomes internal affairs ID; In the 4th step, the internal affairs ID obtaining according to mapping in the 3rd step obtains session data.
After Figure 19 carries out session association, the API agent processes API that the embodiment of the present invention provides creates payment and processes API and confirm that the flow process paying can reference example one.
Below, the API agency's who provides by three example explanation embodiment of the present invention inside story definition.
Example one
In API agent engine 402, API acts on behalf of Executive Module 4021 and calls affairs ID mapping block 4022 and complete the exemplary message definition of the mapping of external transactions ID and internal affairs ID.
Obtain internal affairs ID(API and act on behalf of Executive Module 4021-> affairs ID mapping block 4022)
1) request message definition (as table 1):
Table 1
2) response message definition (as table 2)
Table 2
Parameter name | Value explanation | Field type |
Resultcode | Result code, 0 represents successfully | Integer |
ResultDesc | Result is described | Character string |
InnerTransactionID | Internal affairs ID | Character string |
Example two
Session (API agent engine 402-> data buffer storage 403) is set
1) request message definition (as table 3):
Table 3
2) response message definition (as table 4):
Table 4
parameter name | value explanation | field type |
resultcode | result code.0 represents successfully | integer |
resultDesc | result is described | character string |
Example three
Obtain session (API agent engine 402<-data buffer storage 403)
1) request message definition (as table 5):
Table 5
2) response message definition (as table 6):
Table 6
Below, by specific embodiment, the present invention is illustrated.
Embodiment mono-,
Embodiment mono-has provided a kind of API agency and has processed API establishment payment and processing API and confirm the flow process paying.
The flow process of embodiment mono-as shown in figure 20.In Figure 20, the application program on terminal use's running client is called the API on API agency; API agent engine and data buffer storage be as API agency's a part, realization and application program and paying centre alternately, and buffer memory session data, paying centre is API rear end.As shown in figure 20, this flow process comprises the steps:
S2001, terminal use, in the process running application, trigger billing operation;
S2002, application program send to API agent engine the request that API establishment pays of calling;
S2003, API agent engine are used the rule that generates note check code to generate note check code;
S2004, API agent engine confirm that API creates the strategy that has the session of arranging in payment;
S2005, API agent engine create the external transactions ID obtain manner paying according to API, determine and need automatically to generate external transactions ID;
S2006, API agent engine, according to external transactions ID create-rule, generate external transactions ID;
S2007, API agent engine create session, and according to data cached rule, the API that calls sending from application program is created to the parameter of obtaining the request paying, and the note check code generating, be assembled into session data, and session data is stored in data buffer storage;
S2008, API agent engine arrange rule according to external transactions ID, external transactions ID is set to API and creates in the response parameter paying;
In the response that S2009, API agent engine pay in API establishment, returning to external affairs ID is to application program;
S2010, application program represent interface, warning terminal user input note check code;
S2011, API agent engine send note check code to terminal use (by modes such as notes, the coding strategy that sends note check code is also independent strategy, does not belong in conversation strategy is set);
S2012, terminal use input note check code in client;
S2013, application program send calls the request that API confirmation pays, and carries external transactions ID and note check code in request;
S2014, API agent engine determine that API confirms that payment exists the strategy that obtains session data;
S2015, API agent engine be according to the rule of obtaining of external transactions ID, and from call the request that API confirms to pay, obtains external transactions ID;
S2016, API agent engine, according to the external transactions ID obtaining, are obtained the session data of buffer memory from data buffer storage;
S2017, API agent engine obtain payment information and note check code from the session data of buffer memory, and note check code is carried out to verification;
If S2018 verification succeeds, API agent engine is organized API Calls request according to the session data of buffer memory;
S2019, call the payment interface API of paying centre;
The payment interface API of S2020, paying centre completes actual deducting fees after operation, and payment result is returned to API agent engine;
S2021, API agent engine are returned to payment result to application program
S2022, application program represent payment result to terminal use.
In embodiment mono-, API agency creates in the handling process paying at API, buffer memory session data, comprise note check code, and the external transactions ID of session is returned to client, client is when calling API confirmation payment, the external transactions ID obtaining using create the response paying from API and note check code are issued API agency as call parameters, API agency is according to receiving that external transactions ID obtains the note check code of buffer memory, by the note check code of buffer memory and the note check code comparison of obtaining from the request of calling API confirmation payment, if identical, call the payment interface API of paying centre, complete payment.In said process, by creating in the handling process paying external transactions ID is returned to client at API, so that client is carried in the request of calling API confirmation payment, thereby realized, API establishment pays and API confirms the session association between payment.
Embodiment bis-
Embodiment bis-has provided a kind of API agency and has realized the handling process that note transmission result is notified.As shown in figure 21, the API on the application call API agency in client; API in API proxy call short message service center (being API rear end) realizes message and sends, and this flow process comprises the steps:
S2101: the open API of application call API agency sends message;
The transmission message API of S2102:API proxy call short message service center sends message.
S2103: short message service center is placed in message queue by the message of receiving;
S2104: the return messages ID of short message service center acts on behalf of to API;
S2105:API agency creates session, using message id as external transactions ID, and the information such as sign, message sender, message receiver, message content of calling the application program that sends short message interface is carried out to buffer memory as session data;
S2106:API agent advertisement application program, message has sent to short message service center;
S2107: short message service center takes out message from message queue, sends to message receiver;
S2108: API agency informs by the transmission result of message in short message service center, and the API state notifying that it calls on API agency carries message id (this message id is identical with the message id in step S2104) and state information in the request of calling API state notifying;
S2109:API agency obtains the session data of buffer memory in S2105 step according to the message id of receiving, the sign of the program that is applied from the session data obtaining and message content, and the while is found the loopback address of application program according to the sign of application program.
S2110:API acts on behalf of the loopback address of the application program by finding, and informs application program, the transmission result of note.
In embodiment bis-, by short message service center, in the handling process of API transmission message, to API agency, send message id, API acts on behalf of the external transactions ID using message id as session, and buffer memory session data, when API agency's API state notifying calls in short message service center, in the request of calling API, carry this message id, so that API agency can be obtained before when processing API transmission message, the session data of buffer memory, sends the session association between message and API state notifying thereby realized API.
By adopting the method for embodiment bis-, compared with existing SMS sending method, can realize notification message transmit leg, message sends successfully.
The embodiment of the present invention also provides a kind of method, API Calls equipment and the second API agency of Dialog processing, it is similar that method, API Calls equipment and the API providing due to the embodiment of the present invention acts on behalf of the system of the Dialog processing that the principle of dealing with problems provides to the embodiment of the present invention, its enforcement can be with reference to the enforcement of this system, repeats part and repeat no more.
The procedure schematic diagram of the first Dialog processing that Figure 24 provides for the embodiment of the present invention.As shown in figure 24, the method comprises:
S2401:API agency receives the request of calling an API of sending from calling the API Calls equipment of an API;
S2402:API agency carries out the handling process of an API according to the request of calling an API, in the handling process of execution the one API, and the session data of the session that buffer memory the one API is corresponding;
S2403:API agency receives the request of calling the 2nd API of sending from calling the API Calls equipment of the 2nd API;
S2404:API agency carries out the handling process of the 2nd API according to the request of calling the 2nd API, in the handling process of execution the 2nd API, according to the request of calling the 2nd API, comprise for identifying the external transactions ID of the session that an API is corresponding, obtain the session data of the session of buffer memory in the handling process of carrying out an API, according to the session data obtaining, session is processed.
Alternatively, the method also comprises:
API agency, carrying out in the handling process of an API, determines the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the API Calls equipment of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
API agency is in the handling process of execution the 2nd API, before obtaining the session data of the session of buffer memory in the handling process of carrying out an API, judge that the external transactions ID of the session that an API definite in the handling process of carrying out an API is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises.
Or alternatively, the method also comprises:
API agency, carrying out in the handling process of an API, determines the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the application of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
API agency is in the handling process of execution the one API, after determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the session of buffer memory;
API agency is in the handling process of execution the 2nd API, before obtaining the session data of the session of buffer memory in the handling process of carrying out an API, according to the sign of API supplier corresponding to the 2nd API sign, API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, judge carrying out the internal affairs ID that generates in the handling process of the 2nd API and to generate internal affairs ID in the handling process of execution the one API consistent.
Alternatively, the handling process of API agency execution the one API comprises: API agency carries out the handling process of an API based on the expandable mark language XML file for describing an API handling process;
Alternatively, the handling process of API agency execution the 2nd API comprises: API agency carries out the handling process of the 2nd API based on the XML file for describing the 2nd API handling process.
The procedure schematic diagram of the second Dialog processing that Figure 25 provides for the embodiment of the present invention.As shown in figure 25, the method comprises:
S2501: carry out in the handling process of an API API agency, obtain the external transactions ID of the session that an API is corresponding the response of the API that API Calls equipment returns from API Agency; Or API Calls equipment is to API agency transmission external transactions ID, so that API agency is defined as the external transactions ID receiving the external transactions ID of the session that the one API is corresponding;
S2502:API invocation facility sends the request of calling the 2nd API to API agency, request comprises the external transactions ID of the session that an API is corresponding, so that API acts on behalf of according to the external transactions ID of session, obtain API agency at the session data of carrying out the session of buffer memory in an API handling process, and according to the session data of the session of obtaining, session is processed.
The structural representation that the 4th kind of API that Figure 26 provides for the embodiment of the present invention acts on behalf of.As shown in figure 26, this API agency comprises:
The first processing module 2601, the request of calling an API of sending for the API Calls equipment receiving from calling the first API API; According to the request of calling an API, carry out the handling process of an API, in the handling process of execution the one API, the session data of the session that buffer memory the one API is corresponding;
The second processing module 2602, the request of calling the 2nd API of sending for the invocation facility receiving from calling the 2nd API; According to the request of calling the 2nd API, carry out the handling process of the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of the first processing module 2601 session of buffer memory in the handling process of carrying out an API, according to the session data obtaining, session is processed.
Alternatively, the first processing module 2601 also for: carrying out the handling process of an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the API Calls equipment of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
The second processing module 2602 also for: carrying out the handling process of the 2nd API, obtain before the first processing module 2601 carries out the session data of the session of buffer memory in the handling process of an API, judge that the external transactions ID of the session that the API that determines is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises in the handling process of carrying out an API.
Or, alternatively, the first processing module 2601 also for: carrying out the handling process of an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the invocation facility of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding; After determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the session of buffer memory;
The second processing module 2602 also for: carrying out the handling process of the 2nd API, obtain before the first processing module 2601 carries out the session data of the session of buffer memory in the handling process of an API, according to API supplier corresponding to the 2nd API sign, the sign of the API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, the internal affairs ID that judgement generates in the handling process of execution the 2nd API is consistent with the internal affairs ID that the first processing module 2601 generates in the handling process of execution the one API.
Alternatively, the first processing module 2601 is specifically for the handling process of carrying out an API based on expandable mark language XML file for describing an API handling process;
The second processing module 2602 is specifically for the handling process of carrying out the 2nd API based on XML file for describing the 2nd API handling process.
The structural representation of the API Calls equipment that Figure 27 provides for the embodiment of the present invention.As shown in figure 27, this API Calls equipment comprises:
The first processing module 2701, for the handling process of carrying out an API API agency, obtains the external transactions ID of the session that an API is corresponding from API Agency the response of an API who returns; Or send external transactions ID to API agency, so that API agency is defined as the external transactions ID receiving the external transactions ID of the session that the one API is corresponding;
The second processing module 2702, for sending the request of calling the 2nd API to API agency, request comprises the external transactions ID of the session that an API is corresponding, so that API acts on behalf of according to the external transactions ID of session, obtain API agency at the session data of carrying out the session of buffer memory in an API handling process, and according to the session data of the session of obtaining, session is processed.
The embodiment of the present invention also provides the method for API of generation a kind of and has carried out the method for API handling process, it is similar that the first API providing to the embodiment of the present invention due to these two kinds of methods acts on behalf of the principle of dealing with problems, its enforcement can, with reference to the first API agency's enforcement, therefore repeat part and repeat no more.
The procedure schematic diagram of a kind of API of generation that Figure 28 provides for the embodiment of the present invention.As shown in figure 28, the method comprises:
The API that API developers in S2801:API agency receives for generating API in graphical API development interface generates instruction;
S2802:API developers generates instruction according to this API receiving and generates the API proxy resources that is used for the handling process of describing this API;
S2803:API developers is issued the API agent engine in API agency by this API proxy resources generating, so that API agent engine receiving after the request of this API of API Calls equipment calls, according to the request of calling this API receiving, carry out the handling process of this API in this API proxy resources.
The procedure schematic diagram of a kind of API of execution handling process that Figure 29 provides for the embodiment of the present invention.As shown in figure 29, the method comprises:
API agent engine in S2901:API agency receives the request of calling API that API Calls equipment sends;
S2902:API agent engine is according to the request of calling API receiving, carry out the handling process of this API of API proxy resources for describing this API, to be wherein API developers in API agency generate instruction and generate and issue API agent engine for generating the API of this API according to what receive this API resource;
S2903:API agent engine judges to be had the operation of buffer memory session data or noly has an operation of obtaining session data in the handling process of this API, if there is the operation of buffer memory session data, perform step S2904, if having, obtain the operation of session data, perform step S2905;
S2904:API agent engine generates session data according to the request of calling this API, and the session data of generation is cached in the data buffer storage in API agency;
S2905:API agent engine reads session data according to the request of calling this API from data buffer storage.Those skilled in the art should understand, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt complete hardware implementation example, completely implement software example or the form in conjunction with the embodiment of software and hardware aspect.And the present invention can adopt the form at one or more upper computer programs of implementing of computer-usable storage medium (including but not limited to magnetic disc store, CD-ROM, optical memory etc.) that wherein include computer usable program code.
The present invention is with reference to describing according to flow chart and/or the block diagram of the method for the embodiment of the present invention, equipment (system) and computer program.Should understand can be by the flow process in each flow process in computer program instructions realization flow figure and/or block diagram and/or square frame and flow chart and/or block diagram and/or the combination of square frame.Can provide these computer program instructions to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, the instruction that makes to carry out by the processor of computer or other programmable data processing device produces the device for realizing the function of specifying at flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame.
These computer program instructions also can be stored in energy vectoring computer or the computer-readable memory of other programmable data processing device with ad hoc fashion work, the instruction that makes to be stored in this computer-readable memory produces the manufacture that comprises command device, and this command device is realized the function of specifying in flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame.
These computer program instructions also can be loaded in computer or other programmable data processing device, make to carry out sequence of operations step to produce computer implemented processing on computer or other programmable devices, thereby the instruction of carrying out is provided for realizing the step of the function of specifying in flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame on computer or other programmable devices.
Although described the preferred embodiments of the present invention, once those skilled in the art obtain the basic creative concept of cicada, can make other change and modification to these embodiment.So claims are intended to be interpreted as comprising preferred embodiment and fall into all changes and the modification of the scope of the invention.
Obviously, those skilled in the art can carry out various changes and modification and not depart from the spirit and scope of the present invention the present invention.Like this, if within of the present invention these are revised and modification belongs to the scope of the claims in the present invention and equivalent technologies thereof, the present invention is also intended to comprise these changes and modification interior.
Claims (17)
1. a method for Dialog processing, is characterized in that, described method comprises:
API agency receives the request of calling an API of sending from calling the API Calls equipment of the first API API;
Described API agency carries out the handling process of an API according to the request of calling an API, in the handling process of execution the one API, and the session data of the session that buffer memory the one API is corresponding;
Described API agency receives the request of calling the 2nd API of sending from calling the API Calls equipment of the 2nd API;
Described API agency carries out the handling process of the 2nd API according to the request of calling the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of the described session of buffer memory in the handling process of carrying out an API, according to the described session data obtaining, described session is processed.
2. the method for claim 1, is characterized in that, described method also comprises:
Described API agency, carrying out in the handling process of an API, determines the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the API Calls equipment of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
Described API agency is in the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, judge that the external transactions ID of the session that an API definite in the handling process of carrying out an API is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises.
3. the method for claim 1, is characterized in that, described method also comprises:
Described API agency, carrying out in the handling process of an API, determines the external transactions ID of the session that an API is corresponding, and definite external transactions ID is notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the application of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
Described API agency is in the handling process of execution the one API, after determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the described session of buffer memory;
Described API agency is in the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, according to the sign of API supplier corresponding to the 2nd API sign, API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, judge that the internal affairs ID generating is consistent with the internal affairs ID generating in the handling process of execution the 2nd API in the handling process of execution the one API.
4. the method as described in claim 1~3 any one, is characterized in that,
The handling process that described API agency carries out an API comprises: described API agency carries out the handling process of an API based on the expandable mark language XML file for describing an API handling process;
The handling process that described API agency carries out the 2nd API comprises: described API agency carries out the handling process of the 2nd API based on the XML file for describing the 2nd API handling process.
5. a method for Dialog processing, is characterized in that, described method comprises:
API API agency, carry out in the handling process of an API, the response of the API that API Calls equipment returns from described API Agency, obtain the external transactions ID of the session that an API is corresponding; Or API Calls equipment is to described API agency transmission external transactions ID, so that described API agency is defined as the described external transactions ID receiving the external transactions ID of the session that the one API is corresponding;
Described API Calls equipment sends the request of calling the 2nd API to described API agency, described request comprises the external transactions ID of the described session that a described API is corresponding, so that described API acts on behalf of according to the external transactions ID of described session, obtain described API agency at the session data of carrying out the described session of buffer memory in an API handling process, and according to the session data of the described session of obtaining, described session is processed.
6. an application programming interface API agency, is characterized in that, described API agency comprises:
The first processing module, the request of calling an API of sending for the API Calls equipment receiving from calling the first API API; According to the request of calling an API, carry out the handling process of an API, in the handling process of execution the one API, the session data of the session that buffer memory the one API is corresponding;
The second processing module, the request of calling the 2nd API of sending for the invocation facility receiving from calling the 2nd API; According to the request of calling the 2nd API, carry out the handling process of the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of described the first processing module described session of buffer memory in the handling process of carrying out an API, according to the described session data obtaining, described session is processed.
7. API agency as claimed in claim 6, is characterized in that,
Described the first processing module also for: carrying out the handling process of an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the API Calls equipment of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding;
Described the second processing module also for: carrying out the handling process of the 2nd API, obtain before described the first processing module carries out the session data of the described session of buffer memory in the handling process of an API, judge that the external transactions ID of the session that the API that determines is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises in the handling process of carrying out an API.
8. API agency as claimed in claim 6, is characterized in that,
Described the first processing module also for: carrying out the handling process of an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to the API Calls equipment that calls the 2nd API; Or receive the external transactions ID sending from calling the API Calls equipment of the 2nd API, and the external transactions ID of reception is defined as to the external transactions ID of the session that an API is corresponding; After determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the described session of buffer memory;
Described the second processing module also for: carrying out the handling process of the 2nd API, obtain before described the first processing module carries out the session data of the described session of buffer memory in the handling process of an API, according to API supplier corresponding to the 2nd API sign, the sign of the API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, the internal affairs ID that judgement generates in the handling process of execution the 2nd API is consistent with the internal affairs ID that described the first processing module generates in the handling process of execution the one API.
9. the agency of the API as described in claim 6~8 any one, is characterized in that,
Described the first processing module is specifically for the handling process of carrying out an API based on expandable mark language XML file for describing an API handling process;
Described the second processing module is specifically for the handling process of carrying out the 2nd API based on XML file for describing the 2nd API handling process.
10. an API Calls equipment, is characterized in that, described equipment comprises:
The first processing module, for the handling process of carrying out an API API API agency, obtains the external transactions ID of the session that an API is corresponding from described API Agency the response of an API who returns; Or send external transactions ID to described API agency, so that described API agency is defined as the described external transactions ID receiving the external transactions ID of the session that the one API is corresponding;
The second processing module, for sending the request of calling the 2nd API to described API agency, described request comprises the external transactions ID of the described session that a described API is corresponding, so that described API acts on behalf of according to the external transactions ID of described session, obtain described API agency at the session data of carrying out the described session of buffer memory in an API handling process, and according to the session data of the described session of obtaining, described session is processed.
The system of 11. 1 kinds of Dialog processings, comprises application programming interface API agency and API Calls equipment, it is characterized in that,
Described API agency is used for: according to the request of calling an API receiving, carry out the handling process of an API, and in the handling process of execution the one API, the session data of the session that buffer memory the one API is corresponding; According to the request of calling the 2nd API receiving from described API Calls equipment, carry out the handling process of the 2nd API, in the handling process of execution the 2nd API, the external transactions for identifying the session that an API is corresponding comprising according to the request of calling the 2nd API identifies ID, obtain the session data of the described session of buffer memory in the handling process of carrying out an API, according to the described session data obtaining, described session is processed;
Described API Calls equipment is used for: to described API agency, send the request of calling the 2nd API, described request comprises the external transactions ID of the described session that an API is corresponding.
12. systems as claimed in claim 11, is characterized in that,
Described API agency also for: in the handling process of carrying out an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to described API Calls equipment; Described API Calls equipment also for: described API agency, carry out the handling process of an API, receive the external transactions ID of the described session of described API agent advertisement; Or
Described API Calls equipment also for: described API agency, carry out the handling process of an API, external transactions ID issued to described API agency; Described API agency also for: receive the external transactions ID sending from described API Calls equipment, and the external transactions ID of reception be defined as to the external transactions ID of the session that an API is corresponding;
Described API agency also for: in the handling process of carrying out the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, judge that the external transactions ID of the session that an API definite in the handling process of carrying out an API is corresponding is consistent with the external transactions ID that the request of calling the 2nd API comprises.
13. systems as claimed in claim 11, is characterized in that,
Described API agency also for: in the handling process of carrying out an API, determine the external transactions ID of the session that an API is corresponding, and definite external transactions ID notified to described API Calls equipment; Described API Calls equipment also for: described API agency, carry out the handling process of an API, receive the external transactions ID of the described session of described API agent advertisement; Or
Described API Calls equipment also for: described API agency, carry out the handling process of an API, external transactions ID issued to described API agency; Described API agency also for: receive the external transactions ID sending from described API Calls equipment, and the external transactions ID of reception be defined as to the external transactions ID of the session that an API is corresponding;
Described API agency also for: in the handling process of carrying out an API, after determining the external transactions ID of the session that an API is corresponding, according to the sign of API supplier corresponding to an API sign, API rear end that an API is corresponding, and definite external transactions ID, generate corresponding internal affairs ID, and the corresponding relation of the session data of the internal affairs ID of record generation and the described session of buffer memory; In the handling process of execution the 2nd API, before obtaining the session data of the described session of buffer memory in the handling process of carrying out an API, according to the sign of API supplier corresponding to the 2nd API sign, API rear end that the 2nd API is corresponding and call the external transactions ID that the request of the 2nd API comprises, generate corresponding internal affairs ID, judge that the internal affairs ID generating is consistent with the internal affairs ID generating in the handling process of execution the 2nd API in the handling process of execution the one API.
14. systems as described in claim 11~13 any one, is characterized in that, described API agency specifically for:
Based on the expandable mark language XML file for describing an API handling process, carry out the handling process of an API;
Based on the XML file for describing the 2nd API handling process, carry out the handling process of the 2nd API.
15. 1 kinds of application programming interface API agencies, is characterized in that, described API agency comprises:
API developers, for graphical API development interface is provided, and the API receiving in the described development interface providing for generating API generates instruction; According to the described API receiving, generate instruction and generate the API proxy resources that is used for the handling process of describing described API; The described API proxy resources generating is issued to API agent engine;
API agent engine, the described API proxy resources sending for preserving the described API developers of reception, and receiving after the request of API described in API Calls equipment calls, according to the request of calling described API, carry out the handling process of API described in described API proxy resources; If there is the operation of buffer memory session data in the handling process of described API, according to the request of calling described API, generates session data, and the session data of generation is cached in data buffer storage; If there is the operation of obtaining session data in the handling process of described API, according to the request of calling described API, from data buffer storage, read session data;
Data buffer storage, the session data generating for buffer memory API agent engine, and the session data that API agent engine is read sends to API agent engine.
16. 1 kinds generate the method for application programming interface API, it is characterized in that, described method comprises:
The API that API developers in API agency receives for generating API in graphical API development interface generates instruction;
Described API developers generates instruction according to the described API receiving and generates the API proxy resources that is used for the handling process of describing described API;
Described API developers is issued the API agent engine in described API agency by the described API proxy resources generating, so that described API agent engine receiving after the request of API described in API Calls equipment calls, according to the request of calling described API receiving, carry out the handling process of API described in described API proxy resources.
The method of 17. 1 kinds of executive utility DLL (dynamic link library) API handling processes, is characterized in that, described method comprises:
API agent engine in API agency receives the request of calling API that API Calls equipment sends;
Described API agent engine is according to the request of calling described API receiving, carry out the handling process of API described in the API proxy resources for describing described API, wherein said API resource is that the API developers in described API agency generates and issue described API agent engine according to the API generation instruction for generating described API receiving;
If there is the operation of buffer memory session data in the handling process of described API, described API agent engine generates session data according to the request of calling described API, and the session data of generation is cached in the data buffer storage in described API agency; If there is the operation of obtaining session data in the handling process of described API, described API agent engine reads session data according to the request of calling described API from described data buffer storage.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310754454.3A CN103731427B (en) | 2013-12-31 | 2013-12-31 | Conversation processing method, device and system |
PCT/CN2014/093469 WO2015101151A1 (en) | 2013-12-31 | 2014-12-10 | Session processing method, device and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310754454.3A CN103731427B (en) | 2013-12-31 | 2013-12-31 | Conversation processing method, device and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN103731427A true CN103731427A (en) | 2014-04-16 |
CN103731427B CN103731427B (en) | 2017-04-12 |
Family
ID=50455354
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201310754454.3A Active CN103731427B (en) | 2013-12-31 | 2013-12-31 | Conversation processing method, device and system |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN103731427B (en) |
WO (1) | WO2015101151A1 (en) |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104144221A (en) * | 2014-08-19 | 2014-11-12 | 湖北盛天网络技术股份有限公司 | File access method and device |
WO2015101151A1 (en) * | 2013-12-31 | 2015-07-09 | 华为技术有限公司 | Session processing method, device and system |
WO2016188293A1 (en) * | 2015-05-28 | 2016-12-01 | 阿里巴巴集团控股有限公司 | Data acquisition method and device |
CN107231398A (en) * | 2016-03-25 | 2017-10-03 | 阿里巴巴集团控股有限公司 | Information interacting method and device |
CN107743616A (en) * | 2015-04-08 | 2018-02-27 | 亚马逊技术有限公司 | The end points management system of API agency service is provided |
CN109582655A (en) * | 2018-11-08 | 2019-04-05 | 深圳市云智融科技有限公司 | Localization method and device, the computer readable storage medium of system log |
CN110209505A (en) * | 2019-03-06 | 2019-09-06 | 腾讯科技(深圳)有限公司 | A kind of data request method and relevant device |
CN113064987A (en) * | 2021-04-30 | 2021-07-02 | 中国工商银行股份有限公司 | Data processing method, apparatus, electronic device, medium, and program product |
US11263034B2 (en) | 2014-09-30 | 2022-03-01 | Amazon Technologies, Inc. | Low latency computational capacity provisioning |
US11354169B2 (en) | 2016-06-29 | 2022-06-07 | Amazon Technologies, Inc. | Adjusting variable limit on concurrent code executions |
US11360793B2 (en) | 2015-02-04 | 2022-06-14 | Amazon Technologies, Inc. | Stateful virtual compute system |
US11388210B1 (en) | 2021-06-30 | 2022-07-12 | Amazon Technologies, Inc. | Streaming analytics using a serverless compute system |
US11461124B2 (en) | 2015-02-04 | 2022-10-04 | Amazon Technologies, Inc. | Security protocols for low latency execution of program code |
US11467890B2 (en) | 2014-09-30 | 2022-10-11 | Amazon Technologies, Inc. | Processing event messages for user requests to execute program code |
US11550713B1 (en) | 2020-11-25 | 2023-01-10 | Amazon Technologies, Inc. | Garbage collection in distributed systems using life cycled storage roots |
US11561811B2 (en) | 2014-09-30 | 2023-01-24 | Amazon Technologies, Inc. | Threading as a service |
US11593270B1 (en) | 2020-11-25 | 2023-02-28 | Amazon Technologies, Inc. | Fast distributed caching using erasure coded object parts |
US11714682B1 (en) | 2020-03-03 | 2023-08-01 | Amazon Technologies, Inc. | Reclaiming computing resources in an on-demand code execution system |
US11714675B2 (en) | 2019-06-20 | 2023-08-01 | Amazon Technologies, Inc. | Virtualization-based transaction handling in an on-demand network code execution system |
US11836516B2 (en) | 2018-07-25 | 2023-12-05 | Amazon Technologies, Inc. | Reducing execution times in an on-demand network code execution system using saved machine states |
US11861386B1 (en) | 2019-03-22 | 2024-01-02 | Amazon Technologies, Inc. | Application gateways in an on-demand network code execution system |
US11875173B2 (en) | 2018-06-25 | 2024-01-16 | Amazon Technologies, Inc. | Execution of auxiliary functions in an on-demand network code execution system |
US11943093B1 (en) | 2018-11-20 | 2024-03-26 | Amazon Technologies, Inc. | Network connection recovery after virtual machine transition in an on-demand network code execution system |
US11968280B1 (en) | 2021-11-24 | 2024-04-23 | Amazon Technologies, Inc. | Controlling ingestion of streaming data to serverless function executions |
US12015603B2 (en) | 2021-12-10 | 2024-06-18 | Amazon Technologies, Inc. | Multi-tenant mode for serverless code execution |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR102346620B1 (en) | 2017-07-11 | 2022-01-03 | 삼성전자 주식회사 | Method and apparatus or discoverying network exposure function and configuring chaining |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101690073A (en) * | 2007-07-04 | 2010-03-31 | 艾利森电话股份有限公司 | Cross over the IP link establishment of data network |
US20100302261A1 (en) * | 2009-05-29 | 2010-12-02 | Microsoft Corporation | Fixed Function Pipeline Application Remoting Through A Shader Pipeline Conversion Layer |
CN103475517A (en) * | 2013-09-04 | 2013-12-25 | 青岛海信宽带多媒体技术有限公司 | Optical network terminal equipment and hardware configuration parameter saving method thereof |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103731427B (en) * | 2013-12-31 | 2017-04-12 | 华为技术有限公司 | Conversation processing method, device and system |
-
2013
- 2013-12-31 CN CN201310754454.3A patent/CN103731427B/en active Active
-
2014
- 2014-12-10 WO PCT/CN2014/093469 patent/WO2015101151A1/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101690073A (en) * | 2007-07-04 | 2010-03-31 | 艾利森电话股份有限公司 | Cross over the IP link establishment of data network |
US20100302261A1 (en) * | 2009-05-29 | 2010-12-02 | Microsoft Corporation | Fixed Function Pipeline Application Remoting Through A Shader Pipeline Conversion Layer |
CN103475517A (en) * | 2013-09-04 | 2013-12-25 | 青岛海信宽带多媒体技术有限公司 | Optical network terminal equipment and hardware configuration parameter saving method thereof |
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015101151A1 (en) * | 2013-12-31 | 2015-07-09 | 华为技术有限公司 | Session processing method, device and system |
CN104144221B (en) * | 2014-08-19 | 2017-07-14 | 湖北盛天网络技术股份有限公司 | file access method and device |
CN104144221A (en) * | 2014-08-19 | 2014-11-12 | 湖北盛天网络技术股份有限公司 | File access method and device |
US11561811B2 (en) | 2014-09-30 | 2023-01-24 | Amazon Technologies, Inc. | Threading as a service |
US11467890B2 (en) | 2014-09-30 | 2022-10-11 | Amazon Technologies, Inc. | Processing event messages for user requests to execute program code |
US11263034B2 (en) | 2014-09-30 | 2022-03-01 | Amazon Technologies, Inc. | Low latency computational capacity provisioning |
US11461124B2 (en) | 2015-02-04 | 2022-10-04 | Amazon Technologies, Inc. | Security protocols for low latency execution of program code |
US11360793B2 (en) | 2015-02-04 | 2022-06-14 | Amazon Technologies, Inc. | Stateful virtual compute system |
CN107743616A (en) * | 2015-04-08 | 2018-02-27 | 亚马逊技术有限公司 | The end points management system of API agency service is provided |
WO2016188293A1 (en) * | 2015-05-28 | 2016-12-01 | 阿里巴巴集团控股有限公司 | Data acquisition method and device |
CN107231398A (en) * | 2016-03-25 | 2017-10-03 | 阿里巴巴集团控股有限公司 | Information interacting method and device |
US11354169B2 (en) | 2016-06-29 | 2022-06-07 | Amazon Technologies, Inc. | Adjusting variable limit on concurrent code executions |
US11875173B2 (en) | 2018-06-25 | 2024-01-16 | Amazon Technologies, Inc. | Execution of auxiliary functions in an on-demand network code execution system |
US11836516B2 (en) | 2018-07-25 | 2023-12-05 | Amazon Technologies, Inc. | Reducing execution times in an on-demand network code execution system using saved machine states |
CN109582655A (en) * | 2018-11-08 | 2019-04-05 | 深圳市云智融科技有限公司 | Localization method and device, the computer readable storage medium of system log |
US11943093B1 (en) | 2018-11-20 | 2024-03-26 | Amazon Technologies, Inc. | Network connection recovery after virtual machine transition in an on-demand network code execution system |
CN110209505A (en) * | 2019-03-06 | 2019-09-06 | 腾讯科技(深圳)有限公司 | A kind of data request method and relevant device |
US11861386B1 (en) | 2019-03-22 | 2024-01-02 | Amazon Technologies, Inc. | Application gateways in an on-demand network code execution system |
US11714675B2 (en) | 2019-06-20 | 2023-08-01 | Amazon Technologies, Inc. | Virtualization-based transaction handling in an on-demand network code execution system |
US11714682B1 (en) | 2020-03-03 | 2023-08-01 | Amazon Technologies, Inc. | Reclaiming computing resources in an on-demand code execution system |
US11593270B1 (en) | 2020-11-25 | 2023-02-28 | Amazon Technologies, Inc. | Fast distributed caching using erasure coded object parts |
US11550713B1 (en) | 2020-11-25 | 2023-01-10 | Amazon Technologies, Inc. | Garbage collection in distributed systems using life cycled storage roots |
CN113064987A (en) * | 2021-04-30 | 2021-07-02 | 中国工商银行股份有限公司 | Data processing method, apparatus, electronic device, medium, and program product |
US11388210B1 (en) | 2021-06-30 | 2022-07-12 | Amazon Technologies, Inc. | Streaming analytics using a serverless compute system |
US11968280B1 (en) | 2021-11-24 | 2024-04-23 | Amazon Technologies, Inc. | Controlling ingestion of streaming data to serverless function executions |
US12015603B2 (en) | 2021-12-10 | 2024-06-18 | Amazon Technologies, Inc. | Multi-tenant mode for serverless code execution |
Also Published As
Publication number | Publication date |
---|---|
CN103731427B (en) | 2017-04-12 |
WO2015101151A1 (en) | 2015-07-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN103731427A (en) | Conversation processing method, device and system | |
CN112000348B (en) | Control method, device and computer equipment for service gray level release | |
Dhillon et al. | The hyperledger project | |
US8856800B2 (en) | Service-level enterprise service bus load balancing | |
CN108287839A (en) | A kind of page loading method and equipment | |
US8145593B2 (en) | Framework for web services exposing line of business applications | |
CN108509523A (en) | Structuring processing method, equipment and the readable storage medium storing program for executing of block chain data | |
CN101819551B (en) | Method and system for recording service interaction data of enterprise message system | |
US20160294929A1 (en) | System and method for reusing javascript code available in a soa middleware environment from a process defined by a process execution language | |
CN114553960A (en) | Data caching method, device, equipment and storage medium | |
CN113010561A (en) | Data acquisition method and device based on super account book and computer system | |
US8224933B2 (en) | Method and apparatus for case-based service composition | |
CN115297008A (en) | Intelligent computing network-based collaborative training method and device, terminal and storage medium | |
US20100153565A1 (en) | Connection management in line-of-business | |
CN116204239A (en) | Service processing method, device and computer readable storage medium | |
Tankov et al. | Kotless: A serverless framework for kotlin | |
US7543300B2 (en) | Interface for application components | |
Moschoyiannis et al. | True concurrency in long-running transactions for digital ecosystems | |
US20160292003A1 (en) | System and method for supporting object notation variables in a process defined by a process execution language for execution in a soa middleware environment | |
Cibrán et al. | Aspect-oriented programming for dynamic web service selection, integration and management | |
Plebani et al. | MicroMAIS: executing and orchestrating Web services on constrained mobile devices | |
Yoo et al. | A web service composition framework using integer programming with non-functional objectives and constraints | |
Baraki et al. | Sam: A semantic-aware middleware for mobile cloud computing | |
US8180854B2 (en) | Aspect services | |
US20090199159A1 (en) | Declarative execution context splitting |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |