CN114546639A

CN114546639A - Service call processing method and device

Info

Publication number: CN114546639A
Application number: CN202210134051.8A
Authority: CN
Inventors: 齐普; 翟一帆; 程润峰; 刘鹏; 张宇; 郑江棱; 姚家艺; 马静
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2022-02-14
Filing date: 2022-02-14
Publication date: 2022-05-27
Anticipated expiration: 2042-02-14
Also published as: CN114546639B

Abstract

The embodiment of the specification provides a service call processing method and a service call processing device, wherein the service call processing method comprises the following steps: receiving a calling request which is sent by a source client and carries a subprogram identifier, and starting an agent subprogram corresponding to the subprogram identifier; the agent subprogram analyzes the calling request, carries out service interface calling based on the interface identification of the target service obtained by analysis, and obtains a service processing result returned by the service interface; the agent subprogram assembles a callback request containing the service processing result and a callback link based on a callback function carried by the call request; and executing a jump logic for jumping to the source client, and sending the callback request to the source client.

Description

Service call processing method and device

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing service invocation.

Background

With the development of internet technology and the popularization of mobile terminals, more and more services begin to extend to online scenes, application platform software capable of loading a plurality of application subprograms appears, the situation that users install different types of application programs on the mobile terminals is avoided, the service is handled by means of the subprograms loaded in the application platform software, and meanwhile, the subprograms can provide assistance for the service promotion of the subprograms by means of the capacity of the application platform.

Disclosure of Invention

One or more embodiments of the present specification provide a service call processing method, applied to a target client, where the method includes: receiving a calling request which is sent by a source client and carries a subprogram identifier, and starting an agent subprogram corresponding to the subprogram identifier. And the agent subprogram analyzes the calling request, calls a service interface based on the interface identifier of the target service obtained by analysis, and obtains a service processing result returned by the service interface. And the agent subprogram assembles the callback request comprising the service processing result and the callback link based on the callback function carried by the call request. And executing a jump logic for jumping to the source client, and sending the callback request to the source client.

One or more embodiments of the present specification provide another service call processing method, applied to a source client, where the method includes: and receiving the service request parameter submitted by the service interface call of the target service by the subprogram. And analyzing the service request parameters, and assembling the calling request based on the analysis result. And executing a jump logic for jumping to a target client, and sending the call request to the target client. And receiving a callback request which is sent by the target client and contains a service processing result and a jump back link, jumping to a service page of the subprogram corresponding to the jump back link, and returning the service processing result to the subprogram.

One or more embodiments of the present specification provide a service call processing apparatus, running on a target client, the apparatus including: and the agent subprogram starting module is configured to receive a calling request which is sent by the source client and carries the subprogram identifier, and start the agent subprogram corresponding to the subprogram identifier. And the service interface calling module is configured to analyze the calling request by the agent subprogram, call a service interface based on the interface identifier of the target service obtained by analysis, and acquire a service processing result returned by the service interface. And the callback request assembling module is configured to assemble the callback request containing the service processing result and the callback link by the agent subprogram based on the callback function carried by the call request. And the jump logic execution module is configured to execute jump logic for jumping to the source client and send the callback request to the source client.

One or more embodiments of the present specification provide another service call processing apparatus, running on a source client, the apparatus including: and the service request parameter receiving module is configured to receive the service request parameter submitted by the service interface call of the target service performed by the subprogram. And the service request parameter analysis module is configured to analyze the service request parameters and assemble the call request based on the analysis result. And the jump logic execution module is configured to execute jump logic for jumping to a target client and send the call request to the target client. And the service page jumping module is configured to receive a callback request which is sent by the target client and contains a service processing result and a jump back link, jump to a service page of the subprogram corresponding to the jump back link, and return the service processing result to the subprogram.

One or more embodiments of the present specification provide a service call processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: receiving a calling request which is sent by a source client and carries a subprogram identifier, and starting an agent subprogram corresponding to the subprogram identifier. And the agent subprogram analyzes the calling request, calls a service interface based on the interface identifier of the target service obtained by analysis, and obtains a service processing result returned by the service interface. And the agent subprogram assembles the callback request comprising the service processing result and the callback link based on the callback function carried by the call request. And executing a jump logic for jumping to the source client, and sending the callback request to the source client.

One or more embodiments of the present specification provide a service call processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and receiving the service request parameter submitted by the service interface call of the target service performed by the subprogram. And analyzing the service request parameters, and assembling the calling request based on the analysis result. And executing a jump logic for jumping to a target client, and sending the call request to the target client. And receiving a callback request which is sent by the target client and contains a service processing result and a jump back link, jumping to a service page of the subprogram corresponding to the jump back link, and returning the service processing result to the subprogram.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: receiving a calling request which is sent by a source client and carries a subprogram identifier, and starting an agent subprogram corresponding to the subprogram identifier. And the agent subprogram analyzes the calling request, calls a service interface based on the interface identifier of the target service obtained by analysis, and obtains a service processing result returned by the service interface. And the agent subprogram assembles the callback request comprising the service processing result and the callback link based on the callback function carried by the call request. And executing a jump logic for jumping to the source client, and sending the callback request to the source client.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: and receiving the service request parameter submitted by the service interface call of the target service by the subprogram. And analyzing the service request parameters, and assembling the calling request based on the analysis result. And executing a jump logic for jumping to a target client, and sending the call request to the target client. And receiving a callback request which is sent by the target client and contains a service processing result and a jump back link, jumping to a service page of the subprogram corresponding to the jump back link, and returning the service processing result to the subprogram.

Drawings

In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise;

FIG. 1 is a flow diagram of a service call processing method according to one or more embodiments of the present disclosure;

FIG. 2 is a schematic diagram of a cross-end service call provided in one or more embodiments of the present description;

fig. 3 is a timing diagram of a service invocation processing method applied to a user terminal scenario according to one or more embodiments of the present specification;

FIG. 4 is a flow diagram of another service call processing method provided by one or more embodiments of the present description;

fig. 5 is a schematic diagram of a service call processing apparatus according to one or more embodiments of the present disclosure;

FIG. 6 is a schematic diagram of another service call processing apparatus provided in one or more embodiments of the present disclosure;

fig. 7 is a schematic structural diagram of a service call processing device according to one or more embodiments of the present specification;

fig. 8 is a schematic structural diagram of a service call processing device according to one or more embodiments of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

An embodiment of a service invocation processing method provided in this specification:

referring to fig. 1, the service invocation processing method provided in this embodiment is applied to a target client, and specifically includes step S102 to step S108.

Step S102, receiving a calling request carrying a subprogram identifier sent by a source client, and starting an agent subprogram corresponding to the subprogram identifier.

In practical applications, different service boundaries often exist in different application programs installed on a user terminal in many scenarios, for example, a user is used to perform core processing and other service processing with high correlation with a user identity, such as core processing by using a payment application, and information search and browsing are performed by using a browser, while check processing is performed by using little or no browser.

In view of the above, the service call processing method provided by the present application, for a call request sent by a user in a process of accessing a subprogram and calling a target service at a source client, a target client starts a proxy subprogram and performs proxy of calling the target service by means of the proxy subprogram, specifically, the proxy subprogram analyzes the call request sent by the source client, performs service interface calling of the target service based on an analysis result, assembles a corresponding callback request based on a service processing result returned by the service interface calling, and finally sends the callback request to the source client in a process of executing a jump logic to the source client, thereby implementing cross-end service calling, so that a service call proxy implemented by means of the proxy subprogram at the source client enables a data security level in a process of performing service processing with the target client to be maintained with a data security level in a process of performing service processing at the source client And meanwhile, the service call agent realized by the agent subprogram of the target client side has more flexibility.

The source client is a client that initiates service invocation to another client, the invoked other client is called a target client, both the source client and the target client are application programs installed in the user terminal, optionally, the target client and the source client are installed in the same user terminal, that is: and realizing cross-terminal service call from the source client to the target client at the same user terminal.

In this embodiment, for a scenario in which a user accesses a subprogram in a source client access terminal, cross-terminal service invocation is performed on a target service that the user needs to use in the subprogram accessing process, specifically, the subprogram invokes the target service provided by the target client by means of the source client, and the target client performs corresponding service processing through the provided target service in response to the invocation of the source client, so that the cross-terminal invocation of the target service provided by the target client by the subprogram of the source client is achieved.

Specifically, a user performs corresponding service processing by using a target service if necessary in a process of accessing a subprogram of a source client, and the subprogram performs service interface calling of the target service, where the service interface calling specifically submits a corresponding service request parameter to the source client, and it should be noted that the service interface calling of the target service performed by the subprogram is only pre-calling of the target service, that is, the service interface pre-calling of the target service. After receiving the service request parameters submitted by the subprogram for calling the service interface, the source client analyzes the service request parameters, assembles a calling request based on the analysis result, then executes a jump logic for jumping to a target client, and sends the calling request to the target client so as to call the cross-terminal service to the target client according to the target service accessed by the subprogram.

The sub-program includes a program function module or an application component loaded on the host application (source client), or a program function module or an application component loaded and installed by the host application, such as an applet in the source client. From a service perspective, the sub-application has the capability of independently providing self-closed loop services, such as a small program running in the source client that performs device assurance service registration, application, and transaction self-closed loop capabilities. The agent subprogram refers to a subprogram which responds to the instruction of the target client and acts on the agent source client to carry out service call, and returns a call result to the source client in a callback mode.

In the service interface calling process of the target service, the service request parameter submitted to the source client by the subprogram is composed of a service parameter (such as service data of service access currently performed by the user in the subprogram) and/or an interface identifier of the service interface of the target service. Under the condition that the service request parameter consists of a service parameter and an interface identifier of a service interface of a target service, the service parameter and the interface identifier of the service interface of the target service can be obtained by analyzing the service request parameter, and calling request assembly is carried out on the basis, wherein in the assembly process, the target client is a proxy for service calling by means of a proxy subprogram, so that the subprogram identifier of the proxy subprogram can be assembled into the calling request; and by assembling a callback function in the call request, the jump to the target client side can smoothly jump back to the source client side after cross-terminal service call is carried out, and further, in order to ensure that the jump to the target client side can smoothly jump back to the service page of the current subprogram after cross-terminal service call is carried out, a jump link for identifying the service page of the current subprogram can be assembled in the call request.

In a specific execution process, in order to improve response efficiency of the subprogram in invoking a service interface of the target service, in this embodiment, an SDK (software Development kit) is integrated at a source client, and response timeliness of service invocation initiated by the subprogram is improved through a response of the SDK to the service interface invocation, and optionally, the service interface is a service interface in an interface library of the SDK integrated at the source client; the calling request comprises an interface identifier of the service interface.

And step S104, the agent subprogram analyzes the calling request, carries out service interface calling based on the interface identifier of the target service obtained by analysis, and obtains a service processing result returned by the service interface.

In specific implementation, the agent subprogram obtains the interface identifier of the target service included in the call request by analyzing the call request, and indicates that the call request sent by the source client is a call request for performing cross-terminal service call, then performs cross-terminal service call processing, specifically performs service interface call based on the interface identifier of the target service obtained by analyzing, and obtains a service processing result returned by the service interface.

Optionally, in the process of calling the service interface corresponding to the interface identifier, the agent subprogram transmits a service parameter submitted by a subprogram of the source client, which is included in the call request, to the service interface, and the service interface performs service processing based on the service parameter to obtain the service processing result.

In practical applications, the number of application programs installed on a user terminal is often large, and the application programs are not limited to a source client and a target client, in order to improve the applicability and the use flexibility of cross-terminal service calling, cross-terminal service calling between different application programs can be realized in a permission opening manner, taking the target client as an example, by setting a cross-terminal calling permission of the target client, as long as the cross-terminal calling permission of the target client is opened, the cross-terminal service calling of the target client can be realized, based on this, in an optional implementation manner provided in this embodiment, after the agent subprogram analyzes the calling request and before service interface calling is performed based on an interface identifier of the target service obtained by analysis, whether the source client opens the cross-terminal calling permission of the target client is verified, if so, the source client opens the cross-terminal calling permission of the target client is indicated, carrying out service interface calling based on the interface identifier of the target service obtained by analysis; if not, indicating that the source client does not open the cross-end calling authority of the target client, returning a calling failure prompt or an authority opening prompt for opening the cross-end calling authority of the target client to the source client, wherein the source client can open the cross-end calling authority of the target client by triggering the authority opening prompt; the source client can reinitiate cross-terminal service calling on the basis of opening the cross-terminal calling authority of the target client, or the agent subprogram calls a service interface based on the interface identifier of the target service obtained by analysis under the condition that the source client is detected to open the cross-terminal calling authority of the target client.

In an optional implementation manner provided by this embodiment, in a process in which a service interface of the target service performs service processing in response to a call of the agent subprogram, the service processing specifically includes: and calling a sensor configured by a user terminal provided with the target client to acquire user data, and performing service processing based on the acquired user data to obtain a service processing result. For example, in the process of performing the core processing in response to the invocation of the agent subprogram, a service interface of the core service invokes an image sensor configured in a user terminal of the installation target client to acquire a user image, and performs the core processing on the basis of the acquired user image to obtain a core processing result.

In specific implementation, in order to improve the security of service data in the cross-terminal service calling process, the service processing result can be returned to the source client through a callback request on the basis of encrypting the service processing result, and then returned to the subroutine by the source client, optionally, the service processing result is a ciphertext service processing result obtained by encrypting the plaintext service processing result by using the private key of the target service; after receiving the service processing result, the subprogram decrypts the ciphertext service processing result by adopting the public key of the target service to obtain the plaintext service processing result; by the implementation mode of encrypting and decrypting the service processing result, the service processing result can be sensed only by the service interface and the subprogram of the target service for performing corresponding service processing in the cross-terminal service calling process, and both the source client and the target client cannot acquire the service processing result, so that the service processing result is prevented from being leaked in the transmission processing process of the source client and the target client, and the service data safety in the cross-terminal service calling process is improved.

Similarly, the service parameters submitted by the subprogram in the service interface calling process of the target service can be encrypted and decrypted to improve the safety of the service parameter in the cross-terminal service calling process, specifically, the subprogram encrypts the service parameters by using a private key of the subprogram, ciphertext service parameters obtained after encryption are assembled to the calling request and are sent to the target client in the cross-terminal service calling process, after the agent subprogram transmits the ciphertext service parameters into the service interface, the service interface decrypts the plaintext service parameters by using the private key of the subprogram, and corresponding service processing is carried out on the basis of the plaintext service parameters.

And step S106, the agent subprogram assembles the callback request containing the service processing result and the callback link based on the callback function carried by the call request.

And after the service processing result returned by the service interface is obtained, assembling the callback request based on a callback function carried by the call request sent by the source client, specifically, in the assembling process, in order to enable the callback request to smoothly jump back to the service page called by the service interface of the target service initiated by the subprogram after returning to the source client, assembling a jump link of the service page called by the service interface for identifying the target service initiated by the subprogram into the callback request. And the jump back link is determined according to the jump link carried by the call request.

And step S108, executing a jump logic for jumping to the source client, and sending the callback request to the source client.

After the service interface of the target service is called by the agent subprogram to obtain the service processing result and the callback request containing the service processing result and the callback link is assembled, executing a jump logic for jumping to the source client, and sending the callback request to the source client; optionally, after receiving the callback request, the source client jumps to a service page of the subprogram corresponding to the callback link, and returns the service processing result to the subprogram.

In specific implementation, in order to ensure data consistency in a cross-terminal service calling process, token information is added to the calling request, the token information is used as a unique identifier for marking the cross-terminal service calling at this time, and it is ensured by means of the token information that a callback request returned by a target client corresponds to a calling request sent to the target client (the callback request and a calling request in the cross-terminal service calling process at one time); if yes, jumping to a service page of the subprogram corresponding to the jump-back link; if not, the prompt message with inconsistent request can be generated or not processed.

The following takes an application of the service processing method provided in this embodiment in a user terminal scenario as an example, and with reference to fig. 2 and fig. 3, further describes the service processing method provided in this embodiment, and with reference to fig. 3, the service processing method applied to a target client in the user terminal scenario specifically includes the following steps.

As shown in fig. 2, the target client and the source client are installed on the same user terminal, the source client provides a sub-program for the user to access the service, and the source client is integrated with an SDK; the target client provides a proxy subroutine for performing cross-terminal service call processing.

In step S310, the target client receives the invocation request sent by the SDK integrated by the source client.

Step S312, the target client starts the corresponding agent subprogram according to the subprogram identifier carried by the calling request.

And step S314, the agent subprogram analyzes the calling request, calls the service interface according to the interface identifier of the target service obtained by analysis, and obtains a service processing result returned by the service interface.

After the agent subprogram analyzes the call request, the service parameters, the callback function and the jump link are obtained besides the interface identifier of the target service; and the service parameters are transmitted to the service interface for service processing in the service interface calling process of the agent subprogram.

And step S316, the agent subprogram assembles the jump link into a rebound link through a callback function, and assembles a callback request according to the rebound link and a service processing result.

For example, the callback function may be a callback function, the jump Link may be a Scheme type Link, and the jump Link may be a Deep Link Scheme type Link.

Step S318, the agent subprogram executes the jump logic of the jump back to the source client, and sends a callback request to the SDK integrated with the source client.

For example, the agent subroutine may open the source client via the openother application interface and execute a jump logic to jump to the source client.

Another embodiment of a service call processing method provided in this specification:

the service call processing method applied to the source client provided in this embodiment is mutually matched with the service call processing method applied to the target client provided in the foregoing embodiment in the execution process, so please refer to the corresponding contents of the foregoing embodiment in this embodiment.

Referring to fig. 4, the service call processing method provided in this embodiment is applied to a source client, and the method specifically includes step S402 to step S408.

Step S402, receiving the service request parameter submitted by the service interface call of the target service by the subprogram.

In this embodiment, the source client is a client that initiates a service call to another client, the called another client is called a target client, both the source client and the target client are application programs installed in a user terminal, and optionally, the target client and the source client are installed in the same user terminal, that is: and realizing cross-terminal service call from the source client to the target client at the same user terminal.

The subprogram includes a program function module or an application component loaded on the host application (source client), or a program function module or an application component loaded and installed by the host application, such as an applet in the source client. From a service perspective, the sub-application has the capability of independently providing self-closed loop services, such as a small program running in the source client that performs device assurance service registration, application, and transaction self-closed loop capabilities.

In specific implementation, aiming at a scenario of a subprogram of a user in a source client access terminal, cross-terminal service calling is performed on a target service which is required to be used by the user in the subprogram accessing process, specifically, the subprogram calls the target service provided by the target client by means of the source client, and the target client responds to the calling of the source client and performs corresponding service processing through the provided target service, so that the cross-terminal calling of the subprogram of the source client to the target service provided by the target client is realized. Specifically, a user performs corresponding service processing by using a target service if necessary in a process of accessing a subprogram of a source client, and the subprogram performs service interface calling of the target service, where the service interface calling specifically submits a corresponding service request parameter to the source client, and it should be noted that the service interface calling of the target service performed by the subprogram is only pre-calling of the target service, that is, the service interface pre-calling of the target service.

In the process of calling the service interface of the target service, the subprogram submits the service request parameter to the source client, which is composed of the service parameter (such as the service data that the user currently accesses the service in the subprogram) and/or the interface identifier of the service interface of the target service.

In a specific execution process, in order to improve response efficiency of the subprogram in performing service interface calling of the target service, in this embodiment, the SDK is integrated at the source client, and the response timeliness of the service calling initiated by the subprogram is improved through a response of the SDK to the service interface calling, optionally, the service interface is a service interface in an interface library of the SDK integrated at the source client; the calling request comprises an interface identifier of the service interface.

Step S404, analyzing the service request parameters, and assembling the calling request based on the analysis result.

After receiving the service request parameters submitted by the subprogram in the process of calling the service interface of the target service, in the step, analyzing the service request parameters, and assembling a calling request for cross-terminal service calling to the target client according to an analysis result.

Under the condition that the service request parameter consists of a service parameter and an interface identifier of a service interface of a target service, the service parameter and the interface identifier of the service interface of the target service can be obtained by analyzing the service request parameter, and calling request assembly is carried out on the basis, wherein in the assembly process, the target client is a proxy for service calling by means of a proxy subprogram, so that the subprogram identifier of the proxy subprogram can be assembled into the calling request; and by assembling a callback function in the call request, the jump to the target client side can smoothly jump back to the source client side after cross-terminal service call is carried out, and further, in order to ensure that the jump to the target client side can smoothly jump back to the service page of the current subprogram after cross-terminal service call is carried out, a jump link for identifying the service page of the current subprogram can be assembled in the call request. The agent subprogram refers to a subprogram which responds to the instruction of the target client and acts on the agent source client to carry out service call, and returns a call result to the source client in a callback mode.

Step S406, executing a jump logic for jumping to a target client, and sending the call request to the target client.

In specific implementation, after the calling request is sent to the target client, the target client performs service calling proxy based on the calling request, that is: performing service calling by using an identity proxy source client of a target client, and optionally starting a proxy subprogram corresponding to a subprogram identifier by the target client based on the subprogram identifier carried by the calling request; and the agent subprogram calls a service interface based on the interface identifier of the target service obtained by analyzing the call request.

As described above, the service parameters submitted by the subprogram in the process of making the service interface call of the target service are assembled on the basis of the call request, that is: the calling request comprises service parameters submitted by a subprogram in the calling process of a service interface of the target service, optionally, the service parameters are transmitted into the service interface in the calling process of the interface, and the service interface performs service processing based on the service parameters to obtain the service processing result.

In practical application, the number of application programs installed on a user terminal is often large, the application programs are not limited to a source client and a target client, cross-terminal service calling between different application programs can be realized in a permission opening mode in order to improve applicability and use flexibility of the cross-terminal service calling, taking the target client as an example, the cross-terminal service calling of the target client can be realized by setting the cross-terminal calling permission of the target client as long as the cross-terminal calling permission of the target client is opened, optionally, the source client opens the cross-terminal calling permission of the target client, and correspondingly, an agent subprogram of the target client responds to a calling request sent by the source client based on the cross-terminal calling permission.

In addition, after the agent subprogram analyzes the calling request and before the service interface calling is carried out based on the interface identifier of the target service obtained by analysis, the target client can also check whether the source client opens the cross-terminal calling authority of the target client, if so, the source client indicates that the source client opens the cross-terminal calling authority of the target client, and the service interface calling is carried out based on the interface identifier of the target service obtained by analysis; if not, indicating that the source client does not open the cross-end calling authority of the target client, returning a calling failure prompt or an authority opening prompt for opening the cross-end calling authority of the target client to the source client, wherein the source client can open the cross-end calling authority of the target client by triggering the authority opening prompt; the source client can reinitiate cross-terminal service calling on the basis of opening the cross-terminal calling authority of the target client, or the agent subprogram calls a service interface based on the interface identifier of the target service obtained by analysis under the condition that the source client is detected to open the cross-terminal calling authority of the target client.

Step S408, receiving a callback request containing a service processing result and a rebound link sent by the target client, jumping to a service page of the subprogram corresponding to the rebound link, and returning the service processing result to the subprogram.

In addition, in specific implementation, in order to ensure data consistency in a cross-terminal service calling process, token information is added to the calling request, the token information is used as a unique identifier for marking the cross-terminal service calling of this time, and the token information is used to ensure that a callback request returned by a target client corresponds to a calling request sent to the target client (the calling request and the callback request in a cross-terminal service calling process of one time); if yes, jumping to a service page of the subprogram corresponding to the jump-back link; if not, the prompt message with inconsistent request can be generated or not processed.

In the case of the source client-integrated SDK, as described above, the SDK integrated by the client may further execute the above-described receiving subroutine to perform the service request parameter submitted by the service interface call of the target service, parse the service request parameter, and assembles a call request based on the analysis result, executes a jump logic for jumping to a target client, and sends the call request to the target client, and a service call processing procedure of receiving a callback request containing a service processing result and a callback link sent by the target client, jumping to a service page of the subprogram corresponding to the callback link, and returning the service processing result to the subprogram, the development difficulty of the source client and the operating pressure of the service call initiated by the subprogram on the source client can be effectively reduced by responding to the service interface call by the SDK integrated with the source client.

The following takes an application of the service processing method provided in this embodiment in a user terminal scenario as an example, and with reference to fig. 2 and fig. 3, further describes the service processing method provided in this embodiment, and with reference to fig. 3, the service processing method applied to a source client in the user terminal scenario specifically includes the following steps.

Step S302, the SDK receives the service request parameter submitted by the service interface call of the target service carried out by the subprogram.

Step S304, the SDK analyzes the service request parameter to obtain the service parameter and the interface identifier of the service interface of the target service.

And S306, the SDK assembles the call request according to the service parameter, the interface identifier, the callback function, the subprogram identifier of the agent subprogram and the jump link.

Step S308, the SDK executes the jump logic of the target client side jump and sends a call request to the target client side.

In step S320, the SDK receives the callback request sent by the agent subroutine of the target client.

In step S322, the SDK jumps to the service page of the subroutine corresponding to the jump-back link according to the jump-back link included in the call-back request, and returns the service processing result included in the call-back request to the subroutine.

An embodiment of a service call processing apparatus provided in this specification is as follows:

in the foregoing embodiment, a service call processing method applied to a target client is provided, and correspondingly, a service call processing apparatus running on the target client is also provided, which is described below with reference to the accompanying drawings.

Referring to fig. 5, a schematic diagram of a service call processing apparatus provided in this embodiment is shown.

Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.

The present embodiment provides a service call processing apparatus, operating on a target client, where the apparatus includes:

an agent subprogram starting module 502, configured to receive a call request carrying a subprogram identifier sent by a source client, and start an agent subprogram corresponding to the subprogram identifier;

a service interface calling module 504 configured to analyze the calling request by the agent subprogram, perform service interface calling based on the interface identifier of the target service obtained by analysis, and obtain a service processing result returned by the service interface;

a callback request assembling module 506 configured to assemble, by the agent subroutine, a callback request including the service processing result and a callback link based on a callback function carried by the call request;

a jump logic execution module 508 configured to execute jump logic that jumps to the source client and send the callback request to the source client.

in the foregoing embodiment, a service call processing method applied to a source client is provided, and correspondingly, a service call processing apparatus running on the source client is also provided, which is described below with reference to the accompanying drawings.

Referring to fig. 6, a schematic diagram of a service call processing apparatus provided in this embodiment is shown.

The present embodiment provides a service call processing apparatus, operating on a source client, where the apparatus includes:

a service request parameter receiving module 602 configured to receive a service request parameter submitted by a service interface call of a target service performed by a subroutine;

a service request parameter parsing module 604 configured to parse the service request parameters and assemble a call request based on a parsing result;

a skip logic execution module 606 configured to execute a skip logic that skips to a target client and send the call request to the target client;

a service page jump module 608 configured to receive a callback request including a service processing result and a jump back link sent by the target client, jump to a service page of the subroutine corresponding to the jump back link, and return the service processing result to the subroutine.

An embodiment of a service call processing device provided in this specification is as follows:

corresponding to the service call processing method applied to the target client described above, based on the same technical concept, one or more embodiments of the present specification further provide a service call processing device, where the service call processing device is configured to execute the service call processing method provided above, and fig. 7 is a schematic structural diagram of a service call processing device provided in one or more embodiments of the present specification.

The service call processing device provided by this embodiment includes:

as shown in fig. 7, the service call processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 701 and a memory 702, where one or more stored applications or data may be stored in the memory 702. Memory 702 may be, among other things, transient storage or persistent storage. The application program stored in memory 702 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a service call processing device. Still further, the processor 701 may be configured to communicate with the memory 702 to execute a series of computer-executable instructions in the memory 702 on a service call processing device. The service call processing apparatus may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input/output interfaces 705, one or more keyboards 706, and the like.

In a particular embodiment, the service call processing apparatus comprises a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may comprise one or more modules, and each module may comprise a series of computer-executable instructions for the service call processing apparatus, and execution of the one or more programs by the one or more processors comprises computer-executable instructions for:

receiving a calling request which is sent by a source client and carries a subprogram identifier, and starting an agent subprogram corresponding to the subprogram identifier;

the agent subprogram analyzes the calling request, carries out service interface calling based on the interface identification of the target service obtained by analysis, and obtains a service processing result returned by the service interface;

the agent subprogram assembles a callback request containing the service processing result and a callback link based on a callback function carried by the call request;

and executing a jump logic for jumping to the source client, and sending the callback request to the source client.

corresponding to the service call processing method applied to the source client described above, based on the same technical concept, one or more embodiments of the present specification further provide a service call processing device, where the service call processing device is configured to execute the service call processing method provided above, and fig. 8 is a schematic structural diagram of a service call processing device provided in one or more embodiments of the present specification.

The service call processing device provided by this embodiment includes:

as shown in fig. 8, the service call processing device may have a large difference due to different configurations or performances, and may include one or more processors 801 and a memory 802, and one or more stored applications or data may be stored in the memory 802. Wherein the memory 802 may be a transient storage or a persistent storage. The application program stored in memory 802 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a service call processing device. Still further, the processor 801 may be configured to communicate with the memory 802 to execute a series of computer-executable instructions in the memory 802 on the service call processing device. The service call processing apparatus may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input/output interfaces 805, one or more keyboards 806, and the like.

In one particular embodiment, the service call processing apparatus comprises a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may comprise one or more modules, and each module may comprise a series of computer-executable instructions for the service call processing apparatus, and the one or more programs configured to be executed by the one or more processors comprise computer-executable instructions for:

receiving a service request parameter submitted by a service interface call of a target service performed by a subprogram;

analyzing the service request parameters, and assembling a calling request based on an analysis result;

executing a jump logic for jumping to a target client, and sending the call request to the target client;

and receiving a callback request which is sent by the target client and contains a service processing result and a jump back link, jumping to a service page of the subprogram corresponding to the jump back link, and returning the service processing result to the subprogram.

An embodiment of a storage medium provided in this specification is as follows:

on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the service call processing method applied to the target client described above.

The storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed by the processor, the following processes are implemented:

It should be noted that the embodiment of the storage medium in this specification and the embodiment of the service invocation processing method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the foregoing corresponding method, and repeated details are not described again.

An embodiment of a storage medium provided in this specification is as follows:

on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the service call processing method applied to the source client described above.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry for implementing the logical method flows can be readily obtained by a mere need to program the method flows with some of the hardware description languages described above and into an integrated circuit.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

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

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

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

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

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. A service call processing method is applied to a target client, and comprises the following steps:

2. The service call processing method according to claim 1, wherein the call request includes a service parameter submitted by a subroutine of the source client, the service parameter is transmitted to the service interface in an interface call process, and the service interface performs service processing based on the service parameter to obtain the service processing result.

3. The service call processing method according to claim 2, wherein the source client jumps to a service page of the subroutine corresponding to the callback link after receiving the callback request, and returns the service processing result to the subroutine.

4. The service invocation processing method according to claim 3, wherein the service processing result is a ciphertext service processing result obtained by encrypting a plaintext service processing result by using a private key of the target service;

and after receiving the service processing result, the subprogram decrypts the ciphertext service processing result by adopting the public key of the target service to obtain the plaintext service processing result.

5. The service call processing method according to claim 3, wherein the call request carries token information, and the source client performs the following operations before jumping to the service page of the subroutine corresponding to the jump-back link:

verifying whether the token information carried in the callback request is the same as the token information carried in the call request;

and if so, executing the operation of jumping to the service page of the subprogram corresponding to the jump-back link.

6. The service call processing method according to claim 1, the service processing comprising:

and calling a sensor configured by a user terminal provided with the target client to acquire user data, and performing service processing based on the acquired user data to obtain a service processing result.

7. The service call processing method according to claim 1, wherein after the agent subprogram parses the call request operation and before the service interface call operation is executed based on the interface identifier of the target service obtained by parsing, the following operations are performed:

verifying whether the source client opens the cross-terminal calling authority of the target client;

and if so, executing the service interface calling operation based on the interface identifier of the target service obtained by analysis.

8. The service call processing method according to any one of claims 1 to 7, wherein the target client and the source client are installed in the same user terminal.

9. A service call processing method is applied to a source client, and comprises the following steps:

10. The service call processing method according to claim 9, wherein the service interface is a service interface in an interface library of the SDK integrated by the source client;

the calling request comprises an interface identifier of the service interface.

11. The service call processing method according to claim 9, wherein the target client starts an agent subprogram corresponding to the subprogram identifier based on the subprogram identifier carried in the call request;

and the agent subprogram calls a service interface based on the interface identifier of the target service obtained by analyzing the call request.

12. The service call processing method according to claim 9, wherein the source client opens a cross-end call authority of the target client, and the proxy subprogram of the target client responds to the call request sent by the source client based on the cross-end call authority.

13. The service invocation processing method according to claim 9, wherein the service processing result is a ciphertext service processing result obtained by encrypting a plaintext service processing result using a private key of the target service;

14. The service call processing method according to claims 9 to 13, wherein the target client and the source client are installed in the same user terminal.

15. A service call processing apparatus, operating at a target client, the apparatus comprising:

the agent subprogram starting module is configured to receive a calling request which is sent by a source client and carries a subprogram identifier, and start an agent subprogram corresponding to the subprogram identifier;

the service interface calling module is configured to analyze the calling request by the agent subprogram, call a service interface based on an interface identifier of the target service obtained by analysis, and obtain a service processing result returned by the service interface;

a callback request assembling module configured to assemble a callback request including the service processing result and a callback link by the agent subprogram based on a callback function carried by the call request;

and the jump logic execution module is configured to execute jump logic for jumping to the source client and send the callback request to the source client.

16. A service call processing apparatus, running on a source client, the apparatus comprising:

the service request parameter receiving module is configured to receive a service request parameter submitted by a service interface call of a target service performed by a subprogram;

the service request parameter analysis module is configured to analyze the service request parameters and assemble a calling request based on an analysis result;

a skip logic execution module configured to execute a skip logic that skips to a target client and send the call request to the target client;

and the service page jumping module is configured to receive a callback request which is sent by the target client and contains a service processing result and a jump back link, jump to a service page of the subprogram corresponding to the jump back link, and return the service processing result to the subprogram.

17. A service call processing device comprising:

a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:

18. A service call processing device comprising:

19. A storage medium storing computer-executable instructions that when executed by a processor implement the following:

20. A storage medium storing computer-executable instructions that when executed by a processor implement the following: