Business software calling method and device, storage medium and electronic equipment

Abstract

The invention discloses a business software calling method and device, a storage medium and electronic equipment. The method comprises the following steps: receiving a target service request initiated by a target user; in response to the target service request, sending a parameter acquisition request corresponding to the reference service software to a user verification server under the condition that the reference service software needs to provide service data when the target service is executed; receiving a reference login parameter returned by the user verification server, and obtaining reference service data required for executing the target service from the reference service software according to the reference login parameter; and executing the target service according to the reference service data. Through the method and the device, the problem of relatively low calling efficiency of the business software and the like in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and specifically, to a method and device for calling business software, a storage medium and an electronic device. Background Art

[0002] Existing SaaS cloud platform (also known as software platform) service providers mainly provide basic software and hardware infrastructure. Enterprises rent basic functions such as computing power, network, storage, and rely on the operation and maintenance capabilities of the service providers. However, these service providers usually do not provide further functions, resulting in the need for independent development of each SaaS product software (also known as business software) to implement all functions, including user authentication. Each SaaS product software has an independent user system and data, which are not interoperable with each other, resulting in data island problems. For example, when enterprise K uses financial management software A and invoice management software B at the same time, A cannot automatically obtain B's invoice data to generate financial records, unless B provides an API interface, A develops a user authorization function, and can access B's data only after obtaining K's authorization.

[0003] This solution has security risks, because A may call B's API interface without the customer's authorization, causing B's data to be leaked to A without the customer's knowledge. Data access between SaaS product software has security risks, and there is a lack of a convenient data sharing mechanism. Users need to authenticate multiple times in each business software, resulting in low efficiency in calling business software.

[0004] Currently, no effective solution has been proposed for problems such as low calling efficiency of business software in related technologies. Summary of the invention

[0005] The main purpose of this application is to provide a method and device for calling business software, a storage medium and an electronic device to solve the problem of low calling efficiency of business software in related technologies.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for calling business software is provided. A software platform is run on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide operation resources for each business software to run the corresponding business, each business software is allowed to access a user verification server, and the user verification server is configured to record the login parameters used by the user when logging into the business software. The method is applied to the target business software among the N business software, and the method includes:

[0007] Receiving a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service;

[0008] In response to the target service request, when the reference service software needs to provide service data when the target service is executed, a parameter acquisition request corresponding to the reference service software is sent to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, the login parameters used by the target user when logging into the reference service software are sent to the target service software;

[0009] Receiving the reference login parameters returned by the user verification server, and acquiring the reference business data required for executing the target business from the reference business software according to the reference login parameters;

[0010] The target service is executed according to the reference service data.

[0011] Optionally, the sending a parameter acquisition request corresponding to the reference business software to the user verification server includes:

[0012] generating the parameter acquisition request carrying the reference service identifier of the reference service software;

[0013] The parameter acquisition request is transmitted to the user verification server.

[0014] Optionally, a target communication interface is deployed on the reference business software, and the obtaining reference business data required for executing the target business from the reference business software according to the reference login parameter includes:

[0015] Generate a data acquisition request carrying the reference login parameter, wherein the data acquisition request is used to request to obtain the business data required to execute the target business from the reference business software;

[0016] Sending the data acquisition request to the target communication interface, wherein the reference business software is configured to extract the reference login parameter from the data acquisition request; verifying whether the reference login parameter is the login parameter used by the target user when logging into the reference business software; returning the reference business data to the target business software if it is verified that the reference login parameter is the login parameter used by the target user when logging into the reference business software; prohibiting returning the reference business data to the target business software if it is verified that the reference login parameter is not the login parameter used by the target user when logging into the reference business software;

[0017] The reference business data returned by the reference business software in response to the data acquisition request is received.

[0018] Optionally, the software platform is further allocated with a software verification server, and before receiving the target service request initiated by the target user, the method further includes:

[0019] Detecting a login request currently received by the software platform;

[0020] In the case of detecting a target login request initiated by the target user, calling the software verification server to perform an initial verification operation on the target user to obtain an initial verification result, wherein the target login request is used to request to log in to the target business software, and the initial verification operation is used to verify whether the target user has registered the target business software;

[0021] In the case where the initial verification result is used to indicate that the target user has registered the target business software, calling the user verification server to perform a target verification operation on the target user to obtain a target verification result, wherein the target verification operation is used to verify whether the target user has passed the software platform verification;

[0022] When the target verification result indicates that the target user has passed the software platform verification, the target user is controlled to log in to the target business software, wherein the target user is allowed to initiate the target business request to the target business software after logging in to the target business software.

[0023] Optionally, the calling the software verification server to perform an initial verification operation on the target user to obtain an initial verification result includes:

[0024] An initial verification request carrying a target user identifier of the target user is sent to the software verification server, wherein the software verification server is used to extract the target user identifier from the initial verification request; obtain a candidate user identifier set corresponding to the target business software, the candidate user identifier set including user identifiers of P candidate users who are currently registered with the target business software, where P is an integer greater than or equal to 1; search for the target user identifier from the candidate user identifier set; when the target user identifier is found from the candidate user identifier set, return a pre-authorization code to the target user, the pre-authorization code being used to indicate that the target user has registered the target business software, and the initial verification result including the pre-authorization code;

[0025] Receive a pre-authorization code returned by the software verification server in response to the initial verification request.

[0026] Optionally, a reference user identification set is stored on the user verification server, the reference user identification set includes user identifications of M reference users that have currently passed verification on the software platform, M is an integer greater than or equal to 1, and the calling of the user verification server to perform a target verification operation on the target user to obtain a target verification result includes:

[0027] Sending a target verification request carrying the pre-authorization code and the target user identifier to the user verification server, wherein the user verification server is used to search for the target user identifier from a reference user identifier set; in the case where the target user identifier is found from the reference user identifier set, displaying an authorization interface to the target user; and in the case where the target user is authorized in the authorization interface, returning a user authorization code to the target business software; the target business software obtains target login parameters for logging into the target business software from the software verification server through the user authorization code, and the target verification result includes the target login parameters;

[0028] Receive a target login parameter returned by the user verification server in response to the target verification request, wherein the target login parameter is used to indicate that the target user has passed the software platform verification.

[0029] Optionally, the software platform is further allocated with a software data server, the software data server records corresponding user identification, business software and business data, and the controlling the target user to log in to the target business software includes:

[0030] Sending the target user identifier and the target login parameters of the target business software to the software data server, wherein the software data server is configured to find the target business data corresponding to the target user identifier and the target business software from the corresponding user identifiers, business software and business data upon receiving the target login parameters;

[0031] Receiving the target business data returned by the software data server;

[0032] Control the target user to log in to the target business software according to the target business data.

[0033] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a device for calling business software is provided. A software platform is run on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide operation resources for each business software to run the corresponding business, each business software is allowed to access a user verification server, the user verification server is configured to record the login parameters used by the user when logging into the business software, the device is applied to the target business software among the N business software, and the device includes:

[0034] A receiving module, used to receive a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service;

[0035] a sending module, used to respond to the target service request, and in the case where the reference service software needs to provide service data when the target service is executed, send a parameter acquisition request corresponding to the reference service software to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, send the login parameters used by the target user when logging into the reference service software to the target service software;

[0036] An acquisition module, used for receiving the reference login parameters returned by the user verification server, and acquiring the reference business data required for executing the target business from the reference business software according to the reference login parameters;

[0037] An execution module is used to execute the target service according to the reference service data.

[0038] Through the present application, a method for calling business software is proposed, a software platform is run on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide running resources for each business software to run the corresponding business, each business software is allowed to access the user verification server, the user verification server is configured to record the login parameters used by the user when logging into the business software, and the target business software among the N business software adopts the following steps: receiving a target business request initiated by a target user, wherein the target business request is used to request the target business software to execute the target business; responding to the target business request, when the target business needs to refer to the business software to provide business data when executing the target business, sending a parameter acquisition request corresponding to the reference business software to the user verification server, wherein the parameter acquisition request is used to request to obtain the target user used when logging into the reference business software Login parameters, the user verification server is used to verify whether the target user has logged in to the reference business software, and when the target user has logged in to the reference business software, the login parameters used by the target user to log in to the reference business software are sent to the target business software; the reference login parameters returned by the user verification server are received, and the reference business data required for executing the target business is obtained from the reference business software according to the reference login parameters; the target business is executed according to the reference business data. Through the above method, when the reference business software needs to provide business data when executing the target business, the reference login parameters of the reference business software can be obtained through the user verification server, and then the reference business data required for executing the target business can be obtained from the reference business software according to the reference login parameters to execute the target business, which saves the time consumed by repeated authentication in the reference business software and solves the problem of low calling efficiency of business software in related technologies. Thus, the technical effect of improving the calling efficiency of business software is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0040] Figure 1 It is a flowchart of a method for calling business software provided in an embodiment of the present application;

[0041] Figure 2 It is a schematic diagram of executing a target business according to the target business software provided in the embodiment of the present application;

[0042] Figure 3 It is a schematic diagram of a target user logging into a target business software according to an embodiment of the present application;

[0043] Figure 4 This is a schematic diagram of the OAuth2.0 authentication process;

[0044] Figure 5 is a schematic diagram of a device for calling business software according to an embodiment of the present application;

[0045] Figure 6 is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0047] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0048] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0049] For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0050] OAuth: is an authorization and authentication service protocol that allows services to share user data or perform operations. This sharing usually requires the authorization of the user. Because of the user's authorization, the authorized system can obtain user data without infringing the user's privacy, thereby providing users with simple login access functions. The current mainstream protocol is OAuth2.

[0051] SaaS platform: (Software as a Service) The provider builds all the network infrastructure and software and hardware operating platforms required for the informatization of the enterprise, and is responsible for a series of services such as all pre-implementation and subsequent maintenance. The enterprise does not need to purchase software and hardware, build computer rooms, or recruit IT personnel, and can use the information system through the Internet. It is also referred to as the software platform below.

[0052] SaaS product: This application refers to the SaaS software deployed on the SaaS platform, hereinafter referred to as business software.

[0053] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0054] The collected information involved in this disclosure is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0055] The present invention is described below in conjunction with preferred implementation steps. Figure 1 is a flowchart of a method for calling business software according to an embodiment of the present application, such as Figure 1 As shown, a software platform is running on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide running resources for each business software to run the corresponding business, each business software is allowed to access the user verification server, the user verification server is configured to record the login parameters used by the user when logging in to the business software, the method is applied to the target business software among the N business software, and the method comprises the following steps:

[0056] Step S102, receiving a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service;

[0057] Step S104, in response to the target service request, in the case where the reference service software needs to provide service data when the target service is executed, a parameter acquisition request corresponding to the reference service software is sent to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, the login parameters used by the target user when logging into the reference service software are sent to the target service software;

[0058] Step S106, receiving the reference login parameters returned by the user verification server, and acquiring reference business data required for executing the target business from the reference business software according to the reference login parameters;

[0059] Step S108: executing the target service according to the reference service data.

[0060] Through the above steps, when the reference business software needs to provide business data when executing the target business, the reference login parameters of the reference business software can be obtained through the user verification server, and then the reference business data required for executing the target business can be obtained from the reference business software according to the reference login parameters to execute the target business, saving the time consumed by repeated authentication in the reference business software, and solving the problem of low calling efficiency of business software in related technologies. Thus, the technical effect of improving the calling efficiency of business software is achieved.

[0061] Optionally, in this embodiment, Figure 2 is a schematic diagram of the target business software executing the target business according to the embodiment of the present application, such as Figure 2 As shown, the target user may be, but is not limited to, a user who specifically uses SaaS software products (also known as business software) (for example, a financial staff of an enterprise) Zhang San, who accesses the financial institution SaaS service directory website (the login website of the software platform, through which the business software deployed on the software platform can be subscribed and logged in) through the browser of his computer. Because the financial institution provides a SaaS cloud platform (i.e., software platform) to the outside world, there are many SaaS products (i.e., business software) on the platform. Zhang San himself is a financial institution user and has been certified by the financial institution. After Zhang San logs in to the financial institution SaaS service directory website, he can click on a SaaS product that he needs to use to register or use it through the SaaS service directory page. The target business software may be, but is not limited to, A SaaS software. When the target business software executes the target business, it needs to refer to the business software (which can be B SaaS software) to provide business data (A needs B's data about Zhang San user).

[0062] Optionally, in this embodiment, each business software is allowed to access the user verification server, which is configured to record the login parameters used by the user when logging into the business software. It should be noted that the token_A generated by Zhang San's login to A and the token_B generated by Zhang San's login to B are fixed within a short period of time (such as 1 minute). Of course, the tokens generated by different users are different. At this time, if A obtains token_B, he can legally obtain Zhang San's data on B through the OAuth authentication service of financial institution Q.

[0063] Therefore, the process requires A to be authenticated by the user verification server of financial institution Q, and then financial institution Q recognizes the operation as the user's intention and returns token_B to A.

[0064] Zhang San logs into A SaaS software through the user authentication server of financial institution Q (the method of target user logging into target business software is described in detail below), but does not necessarily log into B SaaS software manually (may log in manually or not). At this time, A SaaS software needs the data of B SaaS software (for example, A SaaS software is financial software and needs the invoice information of user Zhang San that is already on B SaaS software). A SaaS software authenticates through the user authentication server of financial institution Q, and after passing the authentication, requests to obtain the data of user Zhang San from B SaaS software.

[0065] In an exemplary embodiment, sending the parameter acquisition request corresponding to the reference service software to the user verification server includes: generating the parameter acquisition request carrying the reference service identifier of the reference service software; and transmitting the parameter acquisition request to the user verification server.

[0066] Optionally, in this embodiment, if Figure 2 As shown, the Oauth request in step 2 can be, but is not limited to, the parameter acquisition request. A SaaS software sends an Oauth request to financial institution Q. The current Oauth request sent by A SaaS software needs to add an "ID information of the data provider SaaS (i.e., reference business software, such as B SaaS software)" (i.e., reference business identification). The ID is a parameter maintained by each SaaS software in financial institution Q. Each SaaS (business software) has a unique ID identification. By reading the parameter, financial institution Q knows that A SaaS software needs the data of B SaaS software.

[0067] In an exemplary embodiment, a target communication interface is deployed on the reference business software, and the reference business data required for executing the target business is obtained from the reference business software according to the reference login parameters, including: generating a data acquisition request carrying the reference login parameters, wherein the data acquisition request is used to request to obtain the business data required for executing the target business from the reference business software; sending the data acquisition request to the target communication interface, wherein the reference business software is configured to extract the reference login parameters from the data acquisition request; verifying whether the reference login parameters are the login parameters used by the target user when logging into the reference business software; returning the reference business data to the target business software if it is verified that the reference login parameters are the login parameters used by the target user when logging into the reference business software; prohibiting returning the reference business data to the target business software if it is verified that the reference login parameters are not the login parameters used by the target user when logging into the reference business software; and receiving the reference business data returned by the reference business software in response to the data acquisition request.

[0068] Optionally, in this embodiment, if Figure 2 As shown, after A SaaS software sends the Oauth request (i.e., parameter acquisition request) to the user verification server of financial institution Q through step 2, the user verification server authenticates the target user (Zhang San), during which Zhang San completes the authorization action on the authorization page of the user verification server (corresponding to Figure 2 Step 3 in the above example). After the user authentication server authenticates Zhang San, the data returned is token_B (i.e., reference login parameters) for Zhang San to log in to B SaaS software (corresponding to Figure 2 4 in the previous step).

[0069] B SaaS software provides an invoice data API interface. When A SaaS software calls the API interface of B SaaS software, it sends token_B generated by Zhang San logging into B SaaS software to B SaaS software (corresponding to Figure 2 Step 5 in the above example).

[0070] B SaaS software will verify that Token_B is legitimate (it has actually been certified by financial institution Q, otherwise ASaaS software would not know token_B), so B SaaS software returns the invoice data to A SaaS software normally (corresponding to Figure 2 6 in the previous step).

[0071] It is worth noting that in order to ensure the security of data requests, tokens usually have time limits, such as 1 minute, or call limits, such as only being able to be used once. These limits are pre-configured by the financial institution Q (OAuth service provider).

[0072] In an exemplary embodiment, the software platform is further allocated with a software verification server. Before receiving the target business request initiated by the target user, the method further includes: detecting the login request currently received by the software platform; in the case of detecting the target login request initiated by the target user, calling the software verification server to perform an initial verification operation on the target user to obtain an initial verification result, wherein the target login request is used to request to log in to the target business software, and the initial verification operation is used to verify whether the target user has registered the target business software; in the case where the initial verification result is used to indicate that the target user has registered the target business software, calling the user verification server to perform a target verification operation on the target user to obtain a target verification result, wherein the target verification operation is used to verify whether the target user has passed the software platform verification; in the case where the target verification result is used to indicate that the target user has passed the software platform verification, controlling the target user to log in to the target business software, wherein the target user is allowed to initiate the target business request to the target business software after logging in to the target business software.

[0073] Optionally, in this embodiment, the above steps S102-S108 record the process of the target user calling the user verification server of the financial institution to call the reference business data of the reference business software to the target business software, where the premise is that the target user has pre-logged in the target business software and the reference business software on the software platform, and the specific login method is not the traditional method in which the target user performs identity authentication in the target business software and the reference business software respectively, and this traditional method has the disadvantage of low efficiency due to repeated authentication. The solution proposed in this application calls the user verification server of the financial institution to participate in the login process of the user logging in to the corresponding business software. The following takes the target user (Zhang San) logging in to the target business software (ASaaS software) as an example to explain the login method of calling the user verification server of the financial institution to assist the user in logging in to the corresponding business software.

[0074] Figure 3 is a schematic diagram of a target user logging into a target business software according to an embodiment of the present application, such as Figure 3As shown, the target user logs in to the target business software based on the OAuthd authentication mechanism of the user verification server. Currently, financial institution Q provides a SaaS financial ecological cloud platform (i.e., software platform) to the internal development department or external corporate customers. In addition to providing basic hardware, computing power, and storage infrastructure, it can provide enterprises with a unified user authentication and login service based on the offline strong authentication user system of financial institution Q. Enterprises can fully trust the corporate qualifications that have been authenticated by financial institution Q and complete the business functions of SaaS software based on existing corporate data. The most common protocol for user authentication is the OAuth2 protocol. Figure 4 This is a schematic diagram of the OAuth2.0 authentication process, such as Figure 4 As shown, the authentication service developed based on OAuth has a unified authentication process. Since it is a standard process, it will not be repeated here.

[0075] Based on the OAuth2.0 authentication process, if the authentication service is provided by the SaaS cloud platform of financial institution Q, then financial institution Q is the authentication service provider, and the SaaS software deployed on the SaaS platform of financial institution Q is the caller of the authentication service. Figure 3 As shown, the following authentication process can be designed.

[0076] 1) A specific user who uses SaaS software products (for example, a company's financial personnel, the target user) Zhang San visits the SaaS service directory website of financial institution Q through his computer's browser. Because financial institution Q provides a SaaS cloud platform (software platform) to the outside world, there are many SaaS products (business software) on the platform. Zhang San himself is a user of financial institution Q and is certified by financial institution Q. After Zhang San logs in to the financial institution Q SaaS service directory website, he can click on a SaaS product he needs to use to register or use it through the SaaS service directory page.

[0077] 2) After clicking the SaaS software link, you will be redirected to the SaaS software (for example, the target business software). This jump link will automatically carry Zhang San's user ID. The user ID is an encrypted string generated by the internal user authentication server of financial institution Q when the user logs in to the website.

[0078] 3) The SaaS software server uses the user ID string to request a pre-authorization code from the OAuth authentication server (equivalent to the software verification server) of the financial institution Q. The pre-authorization code is a 64-bit random string that is used to represent the current SaaS and the OAuth access action identifier of the user Zhang San.

[0079] 4) The SaaS software carries the authorization code to access the user authentication server of financial institution Q (equivalent to the user verification server), and the authentication server of the user of financial institution Q provides subsequent user authorization functions.

[0080] 5) The user authentication server of financial institution Q needs to determine whether the user ID (i.e. Zhang San) has logged in to the SaaS service directory website of financial institution Q. If logged in, the server has authenticated the user before, and directly returns a user authorization page. If not logged in, or because Zhang San has logged in for too long and the user login information is invalid, then it needs to return to a login page this time, and user Zhang San needs to re-enter the username and password of financial institution Q to log in, and then display the authorization page after logging in. The authorization page prompts the user whether to agree to provide some user data of financial institution Q (such as company name, company unified social credit code, etc.) to the SaaS software.

[0081] 6) User Zhang San clicks to agree. If it is more strict, he needs to insert the financial institution's QU shield and press the U shield button to indicate his consent.

[0082] 7) After the user agrees to the authorization, the user authentication service of financial institution Q will return the actual user authorization code to SaaS.

[0083] 8) SaaS uses the authorization code to obtain a data access token from the OAuth authentication server of financial institution Q.

[0084] 9) After obtaining the token, send it to financial institution Q and obtain user data from the data provider server of financial institution Q.

[0085] 10) SaaS obtains the user's data and performs subsequent business logic processing.

[0086] In an exemplary embodiment, the calling of the software verification server to perform an initial verification operation on the target user to obtain an initial verification result includes: sending an initial verification request carrying a target user identifier of the target user to the software verification server, wherein the software verification server is used to extract the target user identifier from the initial verification request; obtaining a candidate user identifier set corresponding to the target business software, the candidate user identifier set including user identifiers of P candidate users who are currently registered with the target business software, where P is an integer greater than or equal to 1; searching for the target user identifier from the candidate user identifier set; when searching for the target user identifier from the candidate user identifier set, returning a pre-authorization code to the target user, the pre-authorization code being used to indicate that the target user has registered the target business software, and the initial verification result including the pre-authorization code; and receiving the pre-authorization code returned by the software verification server in response to the initial verification request.

[0087] Optionally, in this embodiment, the initial verification request carrying the target user identifier of the target user is sent to the software verification server, which may be, but is not limited to, Figure 3 In step 2) of the above, after clicking the SaaS software link, the user is redirected to the SaaS software (e.g., the target business software). This redirect link will automatically carry Zhang San's user ID, which is an encrypted string generated by the internal user authentication server of financial institution Q when the user logs into the website. The target user identifier can be, but is not limited to, a user ID.

[0088] In an exemplary embodiment, a reference user identification set is stored on the user verification server, and the reference user identification set includes user identifications of M reference users who have currently passed the verification of the software platform, where M is an integer greater than or equal to 1. The calling of the user verification server to perform a target verification operation on the target user to obtain a target verification result includes: sending a target verification request carrying the pre-authorization code and the target user identification to the user verification server, wherein the user verification server is used to search for the target user identification from the reference user identification set; when the target user identification is found from the reference user identification set, the user verification server displays an authorization interface to the target user; and when the target user is authorized in the authorization interface, the user authorization code is returned to the target business software; the target business software obtains a target login parameter for logging into the target business software from the software verification server through the user authorization code, and the target verification result includes the target login parameter; and receiving the target login parameter returned by the user verification server in response to the target verification request, wherein the target login parameter is used to indicate that the target user has passed the verification of the software platform.

[0089] Optionally, in this embodiment, a reference user identification set is stored on the user verification server, and the reference user identification set includes user identifications of M reference users that have currently passed the verification of the software platform, where M is an integer greater than or equal to 1, that is, the reference user may be, but is not limited to, similar to Zhang San, who is a user of financial institution Q and is authenticated by financial institution Q.

[0090] Optionally, in this embodiment, sending the target verification request carrying the pre-authorization code and the target user identifier to the user verification server may be, but is not limited to, Figure 3 In step 4) the SaaS software takes the authorization code to access the user authentication server of financial institution Q (equivalent to the user verification server), and the authentication server of the user of financial institution Q provides subsequent user authorization functions.

[0091] Optionally, in this embodiment, the authorization interface is used to prompt the user whether to agree to provide some user data of financial institutions (such as company name, company unified social credit code, etc.) to the SaaS software.

[0092] Optionally, in this embodiment, the target business software obtains the target login parameter for logging into the target business software from the software verification server through the user authorization code, which may be but is not limited to: Figure 3 In step 8) the SaaS software uses the authorization code (i.e., the user authorization code) to obtain a data access token (i.e., the target login parameter) from the OAuth authentication server (i.e., the software verification server) of the financial institution Q.

[0093] In an exemplary embodiment, the software platform is also allocated a software data server, which records the corresponding user identification, business software and business data. The control of the target user to log in to the target business software includes: sending the target user identification and the target login parameters of the target business software to the software data server, wherein the software data server is configured to, upon receiving the target login parameters, find out the target business data corresponding to the target user identification and the target business software from the corresponding user identification, business software and business data; receive the target business data returned by the software data server; and control the target user to log in to the target business software according to the target business data.

[0094] Optionally, in this embodiment, the software data server may be, but is not limited to, Figure 3The target user ID (e.g., Zhang San) and the target login parameter (e.g., tokenA) of the target business software (e.g., A SaaS software) are sent to the software data server, which may be, but is not limited to, Figure 3 After getting the token (target login parameter) in steps 9)-10), the token is sent to the data provider server of financial institution Q to obtain user data. The SaaS software (for example, the target business software) gets the user data and performs the next business logic processing.

[0095] It should be noted that the calling method of the business software proposed in this application is based on the OAuth authentication service provided by the SaaS platform service provider. First, it can simplify user login and simplify the user system development of each SaaS software. Second, it can open up the data path between SaaS software deployed on the same SaaS platform. For users, they can get cross-product linkage service functions through simple authorization, without repeated manual operations, which greatly improves work efficiency. Third, the SaaS platform provides unified user authentication, which improves security during data exchange between SaaS products and reduces the risk of SaaS software unauthorized access to user data.

[0096] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0097] The embodiment of the present application also provides a service software calling device. It should be noted that the service software calling device of the embodiment of the present application can be used to execute the service software calling method provided by the embodiment of the present application. The service software calling device provided by the embodiment of the present application is introduced below.

[0098] Figure 5 Schematic diagram of a calling device for business software according to an embodiment of the present application. A software platform is running on a software resource server, and N business software are deployed on the software platform, where N is an integer greater than 1. The software resource server is used to provide running resources for the business corresponding to each business software, and each business software is allowed to access a user verification server, which is configured to record the login parameters used by the user when logging into the business software. The device is applied to a target business software among the N business software, such as Figure 5 As shown, the device comprises:

[0099] The receiving module 502 is used to receive a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service;

[0100] The sending module 504 is used to respond to the target service request, and in the case where the reference service software needs to provide service data when the target service is executed, send a parameter acquisition request corresponding to the reference service software to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, send the login parameters used by the target user when logging into the reference service software to the target service software;

[0101] The acquisition module 506 is used to receive the reference login parameters returned by the user verification server, and acquire the reference business data required for executing the target business from the reference business software according to the reference login parameters;

[0102] The execution module 508 is used to execute the target service according to the reference service data.

[0103] Optionally, in the calling device for the business software provided in the embodiment of the present application, the sending module includes:

[0104] A first generating unit, configured to generate the parameter acquisition request carrying the reference service identifier of the reference service software;

[0105] A transmission unit is used to transmit the parameter acquisition request to the user verification server.

[0106] Optionally, in the calling device for the business software provided in the embodiment of the present application, the target communication interface is deployed on the reference business software, and the acquisition module includes:

[0107] A second generating unit is used to generate a data acquisition request carrying the reference login parameter, wherein the data acquisition request is used to request to obtain the business data required for executing the target business from the reference business software;

[0108] A first sending unit is used to send the data acquisition request to the target communication interface, wherein the reference business software is configured to extract the reference login parameter from the data acquisition request; verify whether the reference login parameter is the login parameter used by the target user when logging into the reference business software; if it is verified that the reference login parameter is the login parameter used by the target user when logging into the reference business software, return the reference business data to the target business software; if it is verified that the reference login parameter is not the login parameter used by the target user when logging into the reference business software, prohibit returning the reference business data to the target business software;

[0109] The first receiving unit is configured to receive the reference business data returned by the reference business software in response to the data acquisition request.

[0110] Optionally, in the service software calling device provided in the embodiment of the present application, the software platform is further allocated with a software verification server, and the device further includes:

[0111] A detection module, used for detecting a login request currently received by the software platform before receiving a target service request initiated by a target user;

[0112] A first calling module is used to call the software verification server to perform an initial verification operation on the target user to obtain an initial verification result when a target login request initiated by the target user is detected, wherein the target login request is used to request to log in to the target business software, and the initial verification operation is used to verify whether the target user has registered the target business software;

[0113] A second calling module is used to call the user verification server to perform a target verification operation on the target user to obtain a target verification result when the initial verification result indicates that the target user has registered the target business software, wherein the target verification operation is used to verify whether the target user has passed the software platform verification;

[0114] A control module is used to control the target user to log in to the target business software when the target verification result indicates that the target user has passed the software platform verification, wherein the target user is allowed to initiate the target business request to the target business software after logging in to the target business software.

[0115] Optionally, in the service software calling device provided in the embodiment of the present application, the first calling module includes:

[0116] A second sending unit is used to send an initial verification request carrying a target user identifier of the target user to the software verification server, wherein the software verification server is used to extract the target user identifier from the initial verification request; obtain a candidate user identifier set corresponding to the target business software, the candidate user identifier set including user identifiers of P candidate users who are currently registered with the target business software, where P is an integer greater than or equal to 1; search for the target user identifier from the candidate user identifier set; when the target user identifier is searched from the candidate user identifier set, return a pre-authorization code to the target user, the pre-authorization code being used to indicate that the target user has registered the target business software, and the initial verification result including the pre-authorization code;

[0117] The second receiving unit is used to receive the pre-authorization code returned by the software verification server in response to the initial verification request.

[0118] Optionally, in the calling device of the business software provided in the embodiment of the present application, the user verification server stores a reference user identification set, the reference user identification set includes user identifications of M reference users who have currently passed the verification of the software platform, M is an integer greater than or equal to 1, and the second calling module includes:

[0119] A third sending unit is used to send a target verification request carrying the pre-authorization code and the target user identifier to the user verification server, wherein the user verification server is used to search for the target user identifier from a reference user identifier set; when the target user identifier is found from the reference user identifier set, an authorization interface is displayed to the target user; and when the target user is authorized in the authorization interface, a user authorization code is returned to the target business software; the target business software obtains a target login parameter for logging into the target business software from the software verification server through the user authorization code, and the target verification result includes the target login parameter;

[0120] The third receiving unit is used to receive the target login parameter returned by the user verification server in response to the target verification request, wherein the target login parameter is used to indicate that the target user has passed the software platform verification.

[0121] Optionally, in the service software calling device provided in the embodiment of the present application, the software platform is further allocated with a software data server, the software data server records the corresponding user identification, service software and service data, and the control module includes:

[0122] a fourth sending unit, configured to send the target user identifier and the target login parameter of the target business software to the software data server, wherein the software data server is configured to find the target business data corresponding to the target user identifier and the target business software from the corresponding user identifiers, business software and business data upon receiving the target login parameter;

[0123] A fourth receiving unit, configured to receive the target service data returned by the software data server;

[0124] A control unit is used to control the target user to log in to the target business software according to the target business data.

[0125] The calling device of the business software provided in the embodiment of the present application can obtain the reference login parameters of the reference business software through the user verification server when the target business needs to provide business data by referring to the business software when executing the target business, and then obtain the reference business data required for executing the target business from the reference business software according to the reference login parameters to execute the target business, thereby saving the time consumed by repeated authentication in the reference business software and solving the problem of low calling efficiency of business software in the related art. Thus, the technical effect of improving the calling efficiency of business software is achieved.

[0126] The calling device of the business software includes a processor and a memory. The above units are stored in the memory as program units, and the processor executes the above program units stored in the memory to realize corresponding functions.

[0127] The processor includes a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and the technical effect of improving the calling efficiency of business software can be achieved by adjusting the kernel parameters.

[0128] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0129] An embodiment of the present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, the calling method of the business software is implemented.

[0130] An embodiment of the present invention provides a processor, which is used to run a program, wherein the calling method of the business software is executed when the program is running.

[0131] A software platform is run on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide operation resources for each business software to run the corresponding business, each business software is allowed to access a user verification server, the user verification server is configured to record the login parameters used by the user when logging into the business software, the method is applied to a target business software among the N business software, Figure 6 is a schematic diagram of an electronic device according to an embodiment of the present application, such as Figure 6 As shown, an embodiment of the present invention provides an electronic device, the electronic device includes a processor, a memory, and a program stored in the memory and executable on the processor, and the processor implements the following steps when executing the program:

[0132] Receiving a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service;

[0133] In response to the target service request, when the reference service software needs to provide service data when the target service is executed, a parameter acquisition request corresponding to the reference service software is sent to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, the login parameters used by the target user when logging into the reference service software are sent to the target service software;

[0134] Receiving the reference login parameters returned by the user verification server, and acquiring the reference business data required for executing the target business from the reference business software according to the reference login parameters;

[0135] The target service is executed according to the reference service data.

[0136] Optionally, the processor may further implement the following steps when executing the program:

[0137] generating the parameter acquisition request carrying the reference service identifier of the reference service software;

[0138] The parameter acquisition request is transmitted to the user verification server.

[0139] Optionally, the processor may further implement the following steps when executing the program:

[0140] Generate a data acquisition request carrying the reference login parameter, wherein the data acquisition request is used to request to obtain the business data required to execute the target business from the reference business software;

[0141] Sending the data acquisition request to the target communication interface, wherein the reference business software is configured to extract the reference login parameter from the data acquisition request; verifying whether the reference login parameter is the login parameter used by the target user when logging into the reference business software; returning the reference business data to the target business software if it is verified that the reference login parameter is the login parameter used by the target user when logging into the reference business software; prohibiting returning the reference business data to the target business software if it is verified that the reference login parameter is not the login parameter used by the target user when logging into the reference business software;

[0142] The reference business data returned by the reference business software in response to the data acquisition request is received.

[0143] The software platform is also allocated with a software verification server. Optionally, the processor may further implement the following steps when executing the program:

[0144] Detecting a login request currently received by the software platform;

[0145] In the case of detecting a target login request initiated by the target user, calling the software verification server to perform an initial verification operation on the target user to obtain an initial verification result, wherein the target login request is used to request to log in to the target business software, and the initial verification operation is used to verify whether the target user has registered the target business software;

[0146] In the case where the initial verification result is used to indicate that the target user has registered the target business software, calling the user verification server to perform a target verification operation on the target user to obtain a target verification result, wherein the target verification operation is used to verify whether the target user has passed the software platform verification;

[0147] When the target verification result indicates that the target user has passed the software platform verification, the target user is controlled to log in to the target business software, wherein the target user is allowed to initiate the target business request to the target business software after logging in to the target business software.

[0148] Optionally, the processor may further implement the following steps when executing the program:

[0149] An initial verification request carrying a target user identifier of the target user is sent to the software verification server, wherein the software verification server is used to extract the target user identifier from the initial verification request; obtain a candidate user identifier set corresponding to the target business software, the candidate user identifier set including user identifiers of P candidate users who are currently registered with the target business software, where P is an integer greater than or equal to 1; search for the target user identifier from the candidate user identifier set; when the target user identifier is found from the candidate user identifier set, return a pre-authorization code to the target user, the pre-authorization code being used to indicate that the target user has registered the target business software, and the initial verification result including the pre-authorization code;

[0150] Receive a pre-authorization code returned by the software verification server in response to the initial verification request.

[0151] The user verification server stores a reference user identification set, wherein the reference user identification set includes user identifications of M reference users that have been verified by the software platform, where M is an integer greater than or equal to 1. Optionally, the processor may further implement the following steps when executing the program:

[0152] Sending a target verification request carrying the pre-authorization code and the target user identifier to the user verification server, wherein the user verification server is used to search for the target user identifier from a reference user identifier set; in the case where the target user identifier is found from the reference user identifier set, displaying an authorization interface to the target user; and in the case where the target user is authorized in the authorization interface, returning a user authorization code to the target business software; the target business software obtains target login parameters for logging into the target business software from the software verification server through the user authorization code, and the target verification result includes the target login parameters;

[0153] Receive a target login parameter returned by the user verification server in response to the target verification request, wherein the target login parameter is used to indicate that the target user has passed the software platform verification.

[0154] The software platform is also allocated with a software data server, and the software data server records the corresponding user identification, business software and business data. Optionally, the processor may further implement the following steps when executing the program:

[0155] Sending the target user identifier and the target login parameters of the target business software to the software data server, wherein the software data server is configured to find the target business data corresponding to the target user identifier and the target business software from the corresponding user identifiers, business software and business data upon receiving the target login parameters;

[0156] Receiving the target business data returned by the software data server;

[0157] Control the target user to log in to the target business software according to the target business data.

[0158] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0159] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program for initializing the following method steps:

[0160] A software platform is run on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide running resources for each business software to run the corresponding business, each business software is allowed to access a user verification server, the user verification server is configured to record the login parameters used by the user when logging into the business software, the method is applied to the target business software among the N business software, and optionally, the above-mentioned computer program product, when executed on a data processing device, is suitable for executing a program having the following method steps for initialization:

[0161] Receiving a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service;

[0162] In response to the target service request, when the reference service software needs to provide service data when the target service is executed, a parameter acquisition request corresponding to the reference service software is sent to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, the login parameters used by the target user when logging into the reference service software are sent to the target service software;

[0163] Receiving the reference login parameters returned by the user verification server, and acquiring the reference business data required for executing the target business from the reference business software according to the reference login parameters;

[0164] The target service is executed according to the reference service data.

[0165] Optionally, the above computer program product, when executed on a data processing device, is suitable for executing a program for initializing the following method steps:

[0166] generating the parameter acquisition request carrying the reference service identifier of the reference service software;

[0167] The parameter acquisition request is transmitted to the user verification server.

[0168] The target communication interface is deployed on the reference business software. Optionally, the above computer program product, when executed on a data processing device, is suitable for executing a program that initializes the following method steps:

[0169] Generate a data acquisition request carrying the reference login parameter, wherein the data acquisition request is used to request to obtain the business data required to execute the target business from the reference business software;

[0170] Sending the data acquisition request to the target communication interface, wherein the reference business software is configured to extract the reference login parameter from the data acquisition request; verifying whether the reference login parameter is the login parameter used by the target user when logging into the reference business software; returning the reference business data to the target business software if it is verified that the reference login parameter is the login parameter used by the target user when logging into the reference business software; prohibiting returning the reference business data to the target business software if it is verified that the reference login parameter is not the login parameter used by the target user when logging into the reference business software;

[0171] The reference business data returned by the reference business software in response to the data acquisition request is received.

[0172] The software platform is also allocated a software verification server. Optionally, the above-mentioned computer program product, when executed on a data processing device, is suitable for executing a program for initializing the following method steps:

[0173] Before receiving the target service request initiated by the target user, detecting the login request currently received by the software platform;

[0174] In the case of detecting a target login request initiated by the target user, calling the software verification server to perform an initial verification operation on the target user to obtain an initial verification result, wherein the target login request is used to request to log in to the target business software, and the initial verification operation is used to verify whether the target user has registered the target business software;

[0175] In the case where the initial verification result is used to indicate that the target user has registered the target business software, calling the user verification server to perform a target verification operation on the target user to obtain a target verification result, wherein the target verification operation is used to verify whether the target user has passed the software platform verification;

[0176] When the target verification result indicates that the target user has passed the software platform verification, the target user is controlled to log in to the target business software, wherein the target user is allowed to initiate the target business request to the target business software after logging in to the target business software.

[0177] Optionally, the above computer program product, when executed on a data processing device, is suitable for executing a program for initializing the following method steps:

[0178] An initial verification request carrying a target user identifier of the target user is sent to the software verification server, wherein the software verification server is used to extract the target user identifier from the initial verification request; obtain a candidate user identifier set corresponding to the target business software, the candidate user identifier set including user identifiers of P candidate users who are currently registered with the target business software, where P is an integer greater than or equal to 1; search for the target user identifier from the candidate user identifier set; when the target user identifier is found from the candidate user identifier set, return a pre-authorization code to the target user, the pre-authorization code being used to indicate that the target user has registered the target business software, and the initial verification result including the pre-authorization code;

[0179] Receive a pre-authorization code returned by the software verification server in response to the initial verification request.

[0180] The user verification server stores a reference user identification set, the reference user identification set including user identifications of M reference users that have been verified by the software platform, where M is an integer greater than or equal to 1. Optionally, the above-mentioned computer program product, when executed on a data processing device, is suitable for executing a program having the following method steps for initialization:

[0181] Sending a target verification request carrying the pre-authorization code and the target user identifier to the user verification server, wherein the user verification server is used to search for the target user identifier from a reference user identifier set; in the case where the target user identifier is found from the reference user identifier set, displaying an authorization interface to the target user; and in the case where the target user is authorized in the authorization interface, returning a user authorization code to the target business software; the target business software obtains target login parameters for logging into the target business software from the software verification server through the user authorization code, and the target verification result includes the target login parameters;

[0182] Receive a target login parameter returned by the user verification server in response to the target verification request, wherein the target login parameter is used to indicate that the target user has passed the software platform verification.

[0183] The software platform is also allocated with a software data server, which records the corresponding user identification, business software and business data. Optionally, the above-mentioned computer program product, when executed on a data processing device, is suitable for executing a program initializing the following method steps:

[0184] Sending the target user identifier and the target login parameters of the target business software to the software data server, wherein the software data server is configured to find the target business data corresponding to the target user identifier and the target business software from the corresponding user identifiers, business software and business data upon receiving the target login parameters;

[0185] Receiving the target business data returned by the software data server;

[0186] Control the target user to log in to the target business software according to the target business data.

[0187] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0188] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0189] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0190] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0192] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0193] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0194] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0195] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0196] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for calling business software, characterized in that: A software platform is run on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide operation resources for each business software to run the corresponding business, each business software is allowed to access a user verification server, the user verification server is configured to record the login parameters used by the user when logging into the business software, and the method is applied to a target business software among the N business software, including: Receiving a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service; In response to the target service request, when the reference service software needs to provide service data when the target service is executed, a parameter acquisition request corresponding to the reference service software is sent to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, the login parameters used by the target user when logging into the reference service software are sent to the target service software; Receiving the reference login parameters returned by the user verification server, and acquiring the reference business data required for executing the target business from the reference business software according to the reference login parameters; The target service is executed according to the reference service data.

2. The method according to claim 1, characterized in that: The sending a parameter acquisition request corresponding to the reference business software to the user verification server includes: generating the parameter acquisition request carrying the reference service identifier of the reference service software; The parameter acquisition request is transmitted to the user verification server.

3. The method according to claim 1, characterized in that: The target communication interface is deployed on the reference business software, and the reference business data required for executing the target business is obtained from the reference business software according to the reference login parameter, including: Generate a data acquisition request carrying the reference login parameter, wherein the data acquisition request is used to request to obtain the business data required to execute the target business from the reference business software; Sending the data acquisition request to the target communication interface, wherein the reference business software is configured to extract the reference login parameter from the data acquisition request; verifying whether the reference login parameter is the login parameter used by the target user when logging into the reference business software; returning the reference business data to the target business software if it is verified that the reference login parameter is the login parameter used by the target user when logging into the reference business software; prohibiting returning the reference business data to the target business software if it is verified that the reference login parameter is not the login parameter used by the target user when logging into the reference business software; The reference business data returned by the reference business software in response to the data acquisition request is received.

4. The method according to claim 1, characterized in that: The software platform is also allocated with a software verification server. Before receiving the target service request initiated by the target user, the method further includes: Detecting a login request currently received by the software platform; In the case of detecting a target login request initiated by the target user, calling the software verification server to perform an initial verification operation on the target user to obtain an initial verification result, wherein the target login request is used to request to log in to the target business software, and the initial verification operation is used to verify whether the target user has registered the target business software; In the case where the initial verification result is used to indicate that the target user has registered the target business software, calling the user verification server to perform a target verification operation on the target user to obtain a target verification result, wherein the target verification operation is used to verify whether the target user has passed the software platform verification; When the target verification result indicates that the target user has passed the software platform verification, the target user is controlled to log in to the target business software, wherein the target user is allowed to initiate the target business request to the target business software after logging in to the target business software.

5. The method according to claim 4, characterized in that The calling of the software verification server to perform an initial verification operation on the target user to obtain an initial verification result includes: An initial verification request carrying a target user identifier of the target user is sent to the software verification server, wherein the software verification server is used to extract the target user identifier from the initial verification request; obtain a candidate user identifier set corresponding to the target business software, the candidate user identifier set including user identifiers of P candidate users who are currently registered with the target business software, where P is an integer greater than or equal to 1; search for the target user identifier from the candidate user identifier set; when the target user identifier is found from the candidate user identifier set, return a pre-authorization code to the target user, the pre-authorization code being used to indicate that the target user has registered the target business software, and the initial verification result including the pre-authorization code; Receive a pre-authorization code returned by the software verification server in response to the initial verification request.

6. The method according to claim 5, characterized in that The user verification server stores a reference user identification set, the reference user identification set includes user identifications of M reference users that have been verified by the software platform, where M is an integer greater than or equal to 1, and the calling of the user verification server to perform a target verification operation on the target user to obtain a target verification result includes: Sending a target verification request carrying the pre-authorization code and the target user identifier to the user verification server, wherein the user verification server is used to search for the target user identifier from a reference user identifier set; in the case where the target user identifier is found from the reference user identifier set, displaying an authorization interface to the target user; and in the case where the target user is authorized in the authorization interface, returning a user authorization code to the target business software; the target business software obtains target login parameters for logging into the target business software from the software verification server through the user authorization code, and the target verification result includes the target login parameters; Receive a target login parameter returned by the user verification server in response to the target verification request, wherein the target login parameter is used to indicate that the target user has passed the software platform verification.

7. The method according to claim 6, characterized in that The software platform is also allocated with a software data server, and the software data server records the corresponding user identification, business software and business data. The control of the target user to log in to the target business software includes: Sending the target user identifier and the target login parameters of the target business software to the software data server, wherein the software data server is configured to find the target business data corresponding to the target user identifier and the target business software from the corresponding user identifiers, business software and business data upon receiving the target login parameters; Receiving the target business data returned by the software data server; Control the target user to log in to the target business software according to the target business data.

8. A device for calling business software, characterized in that: A software platform is run on a software resource server, N business software are deployed on the software platform, N is an integer greater than 1, the software resource server is used to provide operation resources for each business software to run the corresponding business, each business software is allowed to access the user verification server, the user verification server is configured to record the login parameters used by the user when logging into the business software, the device is applied to the target business software among the N business software, and the device includes: A receiving module, used to receive a target service request initiated by a target user, wherein the target service request is used to request the target service software to execute a target service; a sending module, used to respond to the target service request, and in the case where the reference service software needs to provide service data when the target service is executed, send a parameter acquisition request corresponding to the reference service software to the user verification server, wherein the parameter acquisition request is used to request to obtain the login parameters used by the target user when logging into the reference service software, and the user verification server is used to verify whether the target user has logged into the reference service software, and when it is verified that the target user has logged into the reference service software, send the login parameters used by the target user when logging into the reference service software to the target service software; An acquisition module, used for receiving the reference login parameters returned by the user verification server, and acquiring the reference business data required for executing the target business from the reference business software according to the reference login parameters; An execution module is used to execute the target service according to the reference service data.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method according to any one of claims 1 to 7 when executed.

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.

Images