Business software calling methods and devices, storage media and electronic devices

Abstract

This application discloses a method, apparatus, storage medium, and electronic device for invoking business software. Relating to the field of fintech, the method includes: receiving a target business request initiated by a target user; responding to the target business request, and if the execution of the target business requires business data provided by reference business software, sending a parameter retrieval request corresponding to the reference business software to a user verification server; receiving reference login parameters returned by the user verification server, and retrieving the reference business data required to execute the target business from the reference business software based on the reference login parameters; and executing the target business based on the reference business data. This application solves the problem of low invoking efficiency of business software in related technologies.

Description

Technical Field

[0001] This application relates to the field of financial technology, and more specifically, to a method and apparatus for invoking business software, a storage medium, and an electronic device. Background Art

[0002] Existing SaaS cloud platform (also known as software platform) service providers primarily offer basic hardware and software infrastructure. Enterprises rent basic functions such as computing power, network, and storage, and rely on the service provider's operational capabilities. However, these service providers typically do not provide more advanced functions, resulting in each SaaS product software (also known as business software) needing to independently develop and implement all functions, including user authentication. Each SaaS product software has an independent user system and data, which are not shared between them, creating data silos. For example, if enterprise K uses both financial management software A and invoice management software B, 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 only access B's data after obtaining authorization from K.

[0003] This approach poses security risks because A could unauthorizedly access B's API without the customer's consent, potentially leading to the leakage of B's ​​data to A without the customer's knowledge. Data access between SaaS product software also presents security risks and lacks convenient data sharing mechanisms. Users need to authenticate multiple times within each business application, resulting in low efficiency in data access between these applications.

[0004] There is currently no effective solution to the problem of low efficiency in calling business software in related technologies. Summary of the Invention

[0005] The main objective of this application is to provide a method and apparatus for invoking business software, a storage medium and an electronic device, in order to solve the problems of low invoking efficiency of business software in related technologies.

[0006] To achieve the above objectives, according to one aspect of this application, a method for invoking business software is provided. A software platform runs on a software resource server, on which N business software applications are deployed, where N is an integer greater than 1. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record login parameters used by a user when logging into the business software. The method is applied to a target business software among the N business software applications, and the method includes:

[0007] 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;

[0008] In response to the target service request, if the target service requires business data from the reference service software during execution, a parameter acquisition request corresponding to the reference service software is sent to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. The user verification server is used to verify whether the target user has logged into the reference service software, and when it verifies that the target user has logged into the reference service software, it sends the login parameters used by the target user when logging into the reference service software to the target service software.

[0009] Receive reference login parameters returned by the user verification server, and obtain reference service data required to execute the target service from the reference service software based on the reference login parameters;

[0010] The target service is executed based on the reference service data.

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

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

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

[0014] Optionally, a target communication interface is deployed on the reference service software, and the step of obtaining the reference service data required to execute the target service from the reference service software according to the reference login parameters includes:

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

[0016] The data acquisition request is sent to the target communication interface, wherein the reference service software is configured to extract the reference login parameters from the data acquisition request; verify whether the reference login parameters are the login parameters used by the target user when logging into the reference service software; if the reference login parameters are verified to be the login parameters used by the target user when logging into the reference service software, return the reference service data to the target service software; if the reference login parameters are verified to be different from the login parameters used by the target user when logging into the reference service software, prevent the return of the reference service data to the target service software.

[0017] Receive the reference service data returned by the reference service software in response to the data acquisition request.

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

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

[0020] Upon detecting a target login request initiated by the target user, the software verification server is invoked to perform an initial verification operation on the target user and obtain an initial verification result. The target login request is used to request login to the target business software, and the initial verification operation is used to verify whether the target user has already registered for the target business software.

[0021] When the initial verification result indicates that the target user has registered the target business software, the user verification server is invoked to perform a target verification operation on the target user to obtain a target verification result. The target verification operation is used to verify whether the target user has passed the verification of the software platform.

[0022] When the target verification result indicates that the target user has passed the verification of the software platform, 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.

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

[0024] An initial verification request carrying the 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 set of candidate user identifiers corresponding to the target business software, the set of candidate user identifiers including user identifiers of P candidate users 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 set of candidate user identifiers; if the target user identifier is found from the set of candidate user identifiers, return a pre-authorization code to the target user, the pre-authorization code indicating that the target user has registered with the target business software, and the initial verification result includes the pre-authorization code;

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

[0026] Optionally, the user verification server stores a set of reference user identifiers, which includes the user identifiers of M reference users who have already passed the verification by the software platform, where M is an integer greater than or equal to 1. The step of calling the user verification server to perform a target verification operation on the target user and obtaining the target verification result includes:

[0027] A target verification request carrying the pre-authorization code and the target user identifier is sent to the user verification server. The user verification server searches for the target user identifier from a set of reference user identifiers. If the target user identifier is found in the set of reference user identifiers, an authorization interface is displayed to the target user. If the target user grants authorization through the authorization interface, a user authorization code is returned 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 using the user authorization code. The target verification result includes the target login parameters.

[0028] The system receives target login parameters returned by the user verification server in response to the target verification request, wherein the target login parameters are used to indicate that the target user has passed the verification by the software platform.

[0029] Optionally, the software platform also allocates a software data server, which records user identifiers, business software, and business data. Controlling the target user to log in to the target business software includes:

[0030] The target user identifier and the target login parameters of the target business software are sent to the software data server, wherein the software data server is configured to, upon receiving the target login parameters, search for the target user identifier and the target business data corresponding to the target business software from the user identifier, business software and business data having the corresponding identifier;

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

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

[0033] To achieve the above objectives, according to another aspect of this application, a device for invoking business software is provided. A software platform runs on a software resource server, on which N business software applications are deployed, where N is an integer greater than 1. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record login parameters used by a user when logging into the business software. The device is applied to a target business software among the N business software applications, and the device includes:

[0034] A receiving module 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;

[0035] The sending module is used to respond to the target service request. When the target service requires business data from the reference service software during execution, the module sends a parameter acquisition request corresponding to the reference service software to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. The user verification server is used to verify whether the target user has logged into the reference service software. When it is verified that the target user has logged into the reference service software, the server sends the login parameters used by the target user when logging into the reference service software to the target service software.

[0036] The acquisition module is used to receive the reference login parameters returned by the user verification server, and to obtain the reference business data required to execute the target business from the reference business software according to the reference login parameters;

[0037] The execution module is used to execute the target service based on the reference service data.

[0038] This application proposes a method for invoking business software. A software platform runs on a software resource server, and N business software applications (N being an integer greater than 1) are deployed on the software platform. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record the login parameters used by users when logging into the business software. The target business software among the N business software applications performs the following steps: receiving a target business request initiated by the 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, and if the execution of the target business requires business data provided by the reference business software, 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 the parameters used by the target user when logging into the reference business software. The login parameters are used by the user verification server to verify whether a target user is logged into the reference business software. Upon verification, the server sends the login parameters used by the target user to the target business software. It also receives the reference login parameters returned by the user verification server and retrieves the necessary reference business data from the reference business software to execute the target business based on these parameters. Finally, it executes the target business based on this reference business data. This method allows the user verification server to obtain the reference login parameters of the reference business software when the target business requires data, thereby saving time spent on repeated authentication within the reference business software and resolving issues such as low efficiency in business software invocation in related technologies. This ultimately improves the technical efficiency of business software invocation. Attached Figure Description

[0039] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0040] Figure 1 This is a flowchart of a method for invoking business software according to an embodiment of this application;

[0041] Figure 2 This is a schematic diagram illustrating the execution of a target service by the target service software provided in the embodiments of this application;

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

[0043] Figure 4 This is a diagram illustrating the OAuth 2.0 authentication process;

[0044] Figure 5 This is a schematic diagram of a device for invoking business software according to an embodiment of this application;

[0045] Figure 6 This is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0046] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0047] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort 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, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0049] For ease of description, the following explains some of the nouns or terms used in the embodiments of this application:

[0050] OAuth is an authorization and authentication service protocol that allows services to share user data or perform operations, typically with the user's authorization. Because it is authorized by the user, the authorized system can obtain user data without infringing on user privacy, thus providing users with convenient login and access functionality. The current mainstream protocol is OAuth2.

[0051] SaaS platform: (Software as a Service) providers build all the network infrastructure and software and hardware operating platforms needed for enterprise informatization, and are responsible for all the services such as initial implementation and subsequent maintenance. Enterprises do not need to purchase software and hardware, build computer rooms, or hire IT personnel, and can use information systems through the Internet. Hereinafter referred to as software platform.

[0052] SaaS products: In this application, it refers to SaaS software deployed on a SaaS platform, hereinafter referred to as business software.

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

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

[0055] The present invention will now be described in conjunction with preferred implementation steps. Figure 1 This is a flowchart of a method for invoking business software according to an embodiment of this application, such as... Figure 1 As shown, a software platform runs on a software resource server, and N business software applications are deployed on the software platform, where N is an integer greater than 1. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record the login parameters used by users when logging into the business software. The method is applied to a target business software among the N business software applications, and the method includes the following steps:

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

[0057] Step S104: In response to the target service request, if the target service requires reference service software to provide service data during execution, a parameter acquisition request corresponding to the reference service software is sent to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. 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: Receive the reference login parameters returned by the user verification server, and obtain the reference service data required to execute the target service from the reference service software according to the reference login parameters;

[0059] Step S108: Execute the target service based on the reference service data.

[0060] Through the above steps, when the target service requires business data from the reference business software, the reference login parameters of the reference business software can be obtained through the user verification server. Then, based on these reference login parameters, the reference business data required to execute the target service can be retrieved from the reference business software. This saves the time consumed by repeated authentication within the reference business software and solves the problem of low call efficiency of business software in related technologies. Thus, the technical effect of improving the call efficiency of business software is achieved.

[0061] Optionally, in this embodiment, Figure 2 This is a schematic diagram illustrating the execution of target services by the target service software provided in the embodiments of this application, such as... Figure 2 As shown, the target user can be, but is not limited to, a user of a specific SaaS software product (also known as business software) (for example, a company's finance personnel, Zhang San). Zhang San accesses the financial institution's SaaS service directory website (the login website for the software platform, through which users can subscribe to and log in to the business software deployed on the platform) via his computer's browser. Because the financial institution provides a SaaS cloud platform (i.e., the software platform), there are many SaaS products (i.e., business software) on the platform. Zhang San is a user of the financial institution and has been certified by the institution. After logging into the financial institution's SaaS service directory website, Zhang San can register or use a desired SaaS product through the SaaS service directory page. The target business software can be, but is not limited to, SaaS software A. When performing target business operations, the target business software needs to refer to business software (which could be SaaS software B) to provide business data (A needs B's data about user Zhang San).

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

[0063] Therefore, in the process, A needs to be authenticated by the user verification server of financial institution Q, and then financial institution Q will recognize the operation as the user's intention and return token_B to A.

[0064] Zhang San logs into SaaS software A through the user authentication server of financial institution Q (the method of a target user logging into the target business software is described in detail below), but may not have manually logged into SaaS software B (manual login is possible, or not). At this time, SaaS software A needs data from SaaS software B (e.g., if SaaS software A is financial software, it needs the invoice information of user Zhang San that is already on SaaS software B). SaaS software A authenticates through the user authentication server of financial institution Q, and after successful authentication, requests to retrieve user Zhang San's data from SaaS software B.

[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, as Figure 2 As shown, the OAuth request in step 2 can be, but is not limited to, a request to retrieve the parameters. SaaS software A sends an OAuth request to financial institution Q. The OAuth request sent by SaaS software A needs to include the "ID information of the data provider SaaS (i.e., the reference business software, such as SaaS software B)" (i.e., the reference business identifier). This ID is a parameter maintained by each SaaS software on financial institution Q, and each SaaS (business software) has a unique ID. By reading this parameter, financial institution Q knows that SaaS software A needs data from SaaS software B.

[0067] In an exemplary embodiment, a target communication interface is deployed on the reference service software. The step of obtaining reference service data required for executing the target service from the reference service software based on the reference login parameters includes: generating a data acquisition request carrying the reference login parameters, wherein the data acquisition request is used to request the acquisition of service data required for executing the target service from the reference service software; sending the data acquisition request to the target communication interface, wherein the reference service software is configured to extract the reference login parameters from the data acquisition request; verifying whether the reference login parameters are login parameters used by the target user when logging into the reference service software; if the reference login parameters are verified to be login parameters used by the target user when logging into the reference service software, returning the reference service data to the target service software; if the reference login parameters are verified not to be login parameters used by the target user when logging into the reference service software, prohibiting the return of the reference service data to the target service software; and receiving the reference service data returned by the reference service software in response to the data acquisition request.

[0068] Optionally, in this embodiment, as Figure 2 As shown, after SaaS software A sends an OAuth request (i.e., a parameter retrieval request) to the user authentication server of financial institution Q in step 2, the user authentication server authenticates the target user (Zhang San). During this process, Zhang San completes the authorization action on the authorization page of the user authentication server (corresponding to...). Figure 2 Step 3). After the user verification server authenticates Zhang San, the returned data is Zhang San's token_B for logging into the B SaaS software (i.e., refer to the login parameters) (corresponding to Figure 2 Step 4 in the process.

[0069] SaaS software B provides an API interface for invoice data. When SaaS software A calls SaaS software B's API interface, it sends the token_B generated by Zhang San's login to SaaS software B (corresponding to...) Figure 2 Step 5 in the process.

[0070] Software B verifies that Token_B is valid (it has actually been certified by a financial institution, Q; otherwise, Software A wouldn't know about token_B). Therefore, Software B returns the invoice data to Software A normally (corresponding to...). Figure 2 Step 6 in the process.

[0071] It's worth noting that to ensure the security of data requests, tokens typically have time limits, such as one minute, or limits on the number of calls, such as only being usable once. These restrictions are pre-configured by the financial institution Q (the OAuth service provider).

[0072] In an exemplary embodiment, the software platform further allocates 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; if a target login request initiated by the target user is detected, invoking 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 login to the target service software, and the initial verification operation is used to verify whether the target user has already registered for the target service software; if the initial verification result indicates that the target user has already registered for the target service software, invoking 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 verification by the software platform; if the target verification result indicates that the target user has passed the verification by the software platform, controlling the target user to log in to the target service software, wherein after logging in to the target service software, the target user is allowed to initiate the target service request to the target service software.

[0073] Optionally, in this embodiment, steps S102-S108 describe the process of the target user calling the user authentication server of a financial institution to retrieve reference business data from the reference business software to the target business software. This is predicated on the target user having pre-logged into both the target business software and the reference business software on the software platform. The specific login method is not the traditional method of separate authentication in the target business software and the reference business software, as this traditional method suffers from low efficiency due to repeated authentication. The solution proposed in this application calls the user authentication server of a financial institution to participate in the user's login process for the corresponding business software. The following example, using the target user (Zhang San) logging into the target business software (ASaaS software), illustrates the method of calling the user authentication server of a financial institution to assist the user in logging into the corresponding business software.

[0074] Figure 3 This is a schematic diagram illustrating the login process of a target user to the target business software according to an embodiment of this application, such as... Figure 3As shown, target users log 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 ecosystem cloud platform (i.e., a software platform) to its internal development departments or external enterprise customers. Besides providing basic hardware, computing power, and storage infrastructure, it can provide enterprises with a unified user authentication and login service based on financial institution Q's offline strong authentication user system. Enterprises can fully trust the qualifications of enterprises already authenticated by financial institution Q and complete the business functions of the SaaS software based on existing enterprise data. The most common user authentication protocol is the OAuth2 protocol. Figure 4 This is a diagram illustrating the OAuth 2.0 authentication process, as shown below. Figure 4 As shown, authentication services developed based on OAuth have a unified authentication process, which will not be elaborated further as it is a standard process.

[0075] Based on the OAuth 2.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 financial institution Q SaaS platform is the caller of the authentication service. For example... Figure 3 As shown, the following authentication process can be designed.

[0076] 1) A specific user of a SaaS software product (for example, a company's finance personnel, the target user), Zhang San, accesses the SaaS service catalog website of financial institution Q through his computer's browser. Because financial institution Q provides a SaaS cloud platform (software platform), there are many SaaS products (business software) on the platform. Zhang San is a user of financial institution Q and has been certified by financial institution Q. After logging into the financial institution Q SaaS service catalog website, Zhang San can click on a SaaS product he needs to register or use through the SaaS service catalog page.

[0077] 2) After clicking the SaaS software link, you will be redirected to the SaaS software (e.g., the target business software). This redirection link will automatically include Zhang San's user ID. The user ID is an encrypted string generated by the financial institution's internal user authentication server when the user logs into the website.

[0078] 3) The SaaS software server requests a pre-authorization code from the financial institution Q's OAuth authentication server (equivalent to a software verification server) using the user ID string. The pre-authorization code is a 64-bit random string used to identify the current SaaS OAuth access action for user Zhang San.

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

[0080] 5) The financial institution Q user authentication server needs to determine whether the user ID (i.e., Zhang San) has already logged into the financial institution Q's SaaS service directory website. If logged in, the server has previously authenticated the user, and a user authorization page is directly returned. If not logged in, or if Zhang San's login information has expired due to prolonged use, a login page needs to be returned. User Zhang San needs to re-enter the financial institution Q username and password to log in, and then the authorization page is displayed. The authorization page prompts the user whether they agree to provide certain financial institution Q user data (such as company name, unified social credit code, etc.) to the SaaS software.

[0081] 6) User Zhang San clicks "agree". If it is more stringent, he / she needs to insert the financial institution's QU shield and press the button on the U shield to indicate agreement.

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

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

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

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

[0086] In an exemplary embodiment, the step of invoking the software verification server to perform an initial verification operation on the target user and 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 set of candidate user identifiers corresponding to the target business software, the set of candidate user identifiers including user identifiers of P candidate users 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 set of candidate user identifiers; if the target user identifier is found from the set of candidate user identifiers, returning a pre-authorization code to the target user, the pre-authorization code indicating that the target user has registered with the target business software, 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, sending an initial verification request carrying the target user's identifier to the software verification server can be, but is not limited to, […]. Figure 3 In step 2), after clicking the SaaS software link, you will be redirected to the SaaS software (e.g., the target business software). This redirection link will automatically include Zhang San's user ID. The user ID is an encrypted string generated by the financial institution's internal user authentication server when the user logs into the website. The target user identifier can be, but is not limited to, the user ID.

[0088] In an exemplary embodiment, the user verification server stores a reference user identifier set, which includes user identifiers of M reference users who have already passed the verification by the software platform, where M is an integer greater than or equal to 1. The step of calling the user verification server to perform a target verification operation on the target user and 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 the reference user identifier set; if the target user identifier is found in the reference user identifier set, displaying an authorization interface to the target user; and if the target user grants authorization through the authorization interface, returning a user authorization code to the target business software; the target business software obtaining target login parameters for logging into the target business software from the software verification server using the user authorization code, the target verification result including the target login parameters; and receiving the target login parameters returned by the user verification server in response to the target verification request, wherein the target login parameters indicate that the target user has passed the verification by the software platform.

[0089] Optionally, in this embodiment, the user verification server stores a set of reference user identifiers. The set of reference user identifiers includes the user identifiers of M reference users who have been verified by the software platform, where M is an integer greater than or equal to 1. That is, the reference users can be, but are not limited to, users of financial institution Q who are similar to Zhang San and have been certified by financial institution Q.

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

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

[0092] Optionally, in this embodiment, the target business software obtains the target login parameters for logging into the target business software from the software verification server using the user authorization code, which may include, but are not limited to, the following: 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 financial institution Q's OAuth authentication server (i.e., the software verification server).

[0093] In an exemplary embodiment, the software platform further allocates a software data server, which records user identifiers, business software, and business data. Controlling 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, upon receiving the target login parameters, to retrieve the target user identifier and the target business data corresponding to the target business software from the user identifier, business software, and business data; receiving the target business data returned by the software data server; and controlling the target user to log in to the target business software based on the target business data.

[0094] Optionally, in this embodiment, the software data server may, but is not limited to, providing... Figure 3The user data server of financial institution Q. Sending the target user identifier (e.g., Zhang San) and the target login parameters (e.g., token A) of the target business software (e.g., A SaaS software) to the software data server may, but is not limited to, for... Figure 3 After obtaining the token (target login parameter) in steps 9)-10), the token is sent to the data provider server of financial institution Q to retrieve user data. The SaaS software (e.g., the target business software) then obtains the user data and performs subsequent business logic processing.

[0095] It should be noted that the business software invocation method proposed in this application is based on the OAuth authentication service provided by the SaaS platform service provider. Firstly, this simplifies user login and the development of user systems for various SaaS software. Secondly, it establishes data pathways between SaaS software deployed on the same SaaS platform. For users, a simple authorization is all that's needed to access cross-product integrated services, eliminating the need for repetitive manual operations and significantly improving work efficiency. Thirdly, the unified user authentication provided by the SaaS platform enhances 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 flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0097] This application also provides a device for invoking business software. It should be noted that the device for invoking business software in this application can be used to execute the method for invoking business software provided in this application. The following describes the device for invoking business software provided in this application.

[0098] Figure 5 This is a schematic diagram of a business software invocation device according to an embodiment of this application. A software platform runs on a software resource server, and N business software programs are deployed on the software platform, where N is an integer greater than 1. The software resource server provides runtime resources for each business software program to run its corresponding business. Each business software program is allowed to access a user verification server, which is configured to record the login parameters used by a user when logging into the business software. The device is applied to a target business software program among the N business software programs, such as... Figure 5 As shown, the device includes:

[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. When the target service requires the reference service software to provide service data during execution, it sends a parameter acquisition request corresponding to the reference service software to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. The user verification server is used to verify whether the target user has logged into the reference service software. 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.

[0101] The acquisition module 506 is used to receive the reference login parameters returned by the user verification server, and to obtain the reference business data required to execute 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 based on the reference service data.

[0103] Optionally, in the business software invocation device provided in this application embodiment, the sending module includes:

[0104] The first generation unit is used 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 business software invocation device provided in this application embodiment, a target communication interface is deployed on the reference business software, and the acquisition module includes:

[0107] The second generation unit is used to generate a data acquisition request carrying the reference login parameters, wherein the data acquisition request is used to request the acquisition of business data required to execute the target business from the reference business software;

[0108] A first sending unit is configured to send the data acquisition request to the target communication interface, wherein the reference service software is configured to extract the reference login parameters from the data acquisition request; verify whether the reference login parameters are the login parameters used by the target user when logging into the reference service software; if the reference login parameters are verified to be the login parameters used by the target user when logging into the reference service software, return the reference service data to the target service software; if the reference login parameters are verified to be different from the login parameters used by the target user when logging into the reference service software, prohibit the return of the reference service data to the target service software.

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

[0110] Optionally, in the business software invocation device provided in this application embodiment, the software platform further allocates a software verification server, and the device further includes:

[0111] The detection module is used to detect the login request currently received by the software platform before receiving the target service request initiated by the target user;

[0112] The first calling module is used to call the software verification server to perform an initial verification operation on the target user and obtain an initial verification result when a target login request initiated by the target user is detected. 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 already registered for the target business software.

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

[0114] The control module is configured 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 verification of the software platform, wherein the target user is allowed to initiate the target business request to the target business software after logging in.

[0115] Optionally, in the business software invocation device provided in this application embodiment, the first invocation module includes:

[0116] The second sending unit is configured to send an initial verification request carrying the target user identifier of the target user to the software verification server, wherein the software verification server is configured to extract the target user identifier from the initial verification request; obtain a set of candidate user identifiers corresponding to the target business software, the set of candidate user identifiers including user identifiers of P candidate users 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 set of candidate user identifiers; and, if the target user identifier is found from the set of candidate user identifiers, return a pre-authorization code to the target user, the pre-authorization code indicating that the target user has registered with the target business software, and the initial verification result includes 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 business software invocation device provided in this application embodiment, the user verification server stores a reference user identifier set, the reference user identifier set including the user identifiers of M reference users who have been verified by the software platform, where M is an integer greater than or equal to 1, and the second invocation module includes:

[0119] The third sending unit is configured to send a target verification request carrying the pre-authorization code and the target user identifier to the user verification server. The user verification server is configured to search for the target user identifier from a set of reference user identifiers; if the target user identifier is found in the set of reference user identifiers, it displays an authorization interface to the target user; and if the target user authorizes the user through the authorization interface, it returns 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 using the user authorization code. The target verification result includes the target login parameters.

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

[0121] Optionally, in the business software invocation device provided in this application embodiment, the software platform further allocates a software data server, which records user identifiers, business software, and business data with corresponding identifiers. The control module includes:

[0122] The fourth sending unit is used to send 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, upon receiving the target login parameters, search for the target user identifier and the target business data corresponding to the target business software from the user identifier, business software and business data having the corresponding identifier;

[0123] The fourth receiving unit is used to receive the target service data returned by the software data server;

[0124] The control unit is used to control the target user to log in to the target business software based on the target business data.

[0125] The business software invocation device provided in this application embodiment, when requiring business data from reference business software during target business execution, can obtain reference login parameters of the reference business software through a user verification server. Then, based on the reference login parameters, it retrieves the reference business data required to execute the target business from the reference business software to execute the target business. This saves the time consumed by repeated authentication in the reference business software and solves the problem of low invocation efficiency of business software in related technologies. Thus, it achieves the technical effect of improving the invocation efficiency of business software.

[0126] The device for calling the business software includes a processor and a memory. The aforementioned units are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to achieve the corresponding functions.

[0127] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and adjusting kernel parameters can improve the efficiency of application software calls.

[0128] The memory may include non-permanent memory in computer-readable media, such as 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] This invention provides a computer-readable storage medium storing a program thereon, which, when executed by a processor, implements the calling method of the business software.

[0130] This invention provides a processor for running a program, wherein the program executes the calling method of the business software during runtime.

[0131] A software platform runs on a software resource server, on which N business software applications are deployed, where N is an integer greater than 1. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record the login parameters used by users when logging into the business software. The method is applied to a target business software application among the N business software applications. Figure 6 This is a schematic diagram of an electronic device according to an embodiment of this application, such as... Figure 6 As shown, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs the following steps:

[0132] 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;

[0133] In response to the target service request, if the target service requires business data from the reference service software during execution, a parameter acquisition request corresponding to the reference service software is sent to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. The user verification server is used to verify whether the target user has logged into the reference service software, and when it verifies that the target user has logged into the reference service software, it sends the login parameters used by the target user when logging into the reference service software to the target service software.

[0134] Receive reference login parameters returned by the user verification server, and obtain reference service data required to execute the target service from the reference service software based on the reference login parameters;

[0135] The target service is executed based on the reference service data.

[0136] Optionally, the processor described above may also perform the following steps when executing the program:

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

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

[0139] Optionally, the processor described above may also perform the following steps when executing the program:

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

[0141] The data acquisition request is sent to the target communication interface, wherein the reference service software is configured to extract the reference login parameters from the data acquisition request; verify whether the reference login parameters are the login parameters used by the target user when logging into the reference service software; if the reference login parameters are verified to be the login parameters used by the target user when logging into the reference service software, return the reference service data to the target service software; if the reference login parameters are verified to be different from the login parameters used by the target user when logging into the reference service software, prevent the return of the reference service data to the target service software.

[0142] Receive the reference service data returned by the reference service software in response to the data acquisition request.

[0143] The software platform also allocates a software verification server. Optionally, the processor may also perform the following steps when executing the program:

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

[0145] Upon detecting a target login request initiated by the target user, the software verification server is invoked to perform an initial verification operation on the target user and obtain an initial verification result. The target login request is used to request login to the target business software, and the initial verification operation is used to verify whether the target user has already registered for the target business software.

[0146] When the initial verification result indicates that the target user has registered the target business software, the user verification server is invoked to perform a target verification operation on the target user to obtain a target verification result. The target verification operation is used to verify whether the target user has passed the verification of the software platform.

[0147] When the target verification result indicates that the target user has passed the verification of the software platform, 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.

[0148] Optionally, the processor described above may also perform the following steps when executing the program:

[0149] An initial verification request carrying the 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 set of candidate user identifiers corresponding to the target business software, the set of candidate user identifiers including user identifiers of P candidate users 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 set of candidate user identifiers; if the target user identifier is found from the set of candidate user identifiers, return a pre-authorization code to the target user, the pre-authorization code indicating that the target user has registered with the target business software, and the initial verification result includes the pre-authorization code;

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

[0151] The user verification server stores a set of reference user identifiers, which includes the user identifiers of M reference users who have already passed the verification by the software platform, where M is an integer greater than or equal to 1. Optionally, the processor may also implement the following steps when executing the program:

[0152] A target verification request carrying the pre-authorization code and the target user identifier is sent to the user verification server. The user verification server searches for the target user identifier from a set of reference user identifiers. If the target user identifier is found in the set of reference user identifiers, an authorization interface is displayed to the target user. If the target user grants authorization through the authorization interface, a user authorization code is returned 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 using the user authorization code. The target verification result includes the target login parameters.

[0153] The system receives target login parameters returned by the user verification server in response to the target verification request, wherein the target login parameters are used to indicate that the target user has passed the verification by the software platform.

[0154] The software platform also allocates a software data server, which records user identifiers, business software, and business data. Optionally, the processor may also perform the following steps when executing the program:

[0155] The target user identifier and the target login parameters of the target business software are sent to the software data server, wherein the software data server is configured to, upon receiving the target login parameters, search for the target user identifier and the target business data corresponding to the target business software from the user identifier, business software and business data having the corresponding identifier;

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

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

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

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

[0160] A software platform runs on a software resource server, on which N business software applications are deployed, where N is an integer greater than 1. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record the login parameters used by users when logging into the business software. The method is applied to a target business software among the N business software applications. Optionally, when the above-mentioned computer program product is executed on a data processing device, it is suitable to execute a program with the following initialization steps:

[0161] 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;

[0162] In response to the target service request, if the target service requires business data from the reference service software during execution, a parameter acquisition request corresponding to the reference service software is sent to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. The user verification server is used to verify whether the target user has logged into the reference service software, and when it verifies that the target user has logged into the reference service software, it sends the login parameters used by the target user when logging into the reference service software to the target service software.

[0163] Receive reference login parameters returned by the user verification server, and obtain reference service data required to execute the target service from the reference service software based on the reference login parameters;

[0164] The target service is executed based on the reference service data.

[0165] Optionally, when the above-mentioned computer program product is executed on a data processing device, it is suitable to execute a program that initializes the following method steps:

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

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

[0168] The reference service software is deployed with a target communication interface. Optionally, when the aforementioned computer program product is executed on a data processing device, it is suitable to execute an initialization program with the following method steps:

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

[0170] The data acquisition request is sent to the target communication interface, wherein the reference service software is configured to extract the reference login parameters from the data acquisition request; verify whether the reference login parameters are the login parameters used by the target user when logging into the reference service software; if the reference login parameters are verified to be the login parameters used by the target user when logging into the reference service software, return the reference service data to the target service software; if the reference login parameters are verified to be different from the login parameters used by the target user when logging into the reference service software, prevent the return of the reference service data to the target service software.

[0171] Receive the reference service data returned by the reference service software in response to the data acquisition request.

[0172] The software platform also allocates a software verification server. Optionally, when the aforementioned computer program product is executed on a data processing device, it is suitable to execute an initialization program with the following method steps:

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

[0174] Upon detecting a target login request initiated by the target user, the software verification server is invoked to perform an initial verification operation on the target user and obtain an initial verification result. The target login request is used to request login to the target business software, and the initial verification operation is used to verify whether the target user has already registered for the target business software.

[0175] When the initial verification result indicates that the target user has registered the target business software, the user verification server is invoked to perform a target verification operation on the target user to obtain a target verification result. The target verification operation is used to verify whether the target user has passed the verification of the software platform.

[0176] When the target verification result indicates that the target user has passed the verification of the software platform, 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.

[0177] Optionally, when the above-mentioned computer program product is executed on a data processing device, it is suitable to execute a program that initializes the following method steps:

[0178] An initial verification request carrying the 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 set of candidate user identifiers corresponding to the target business software, the set of candidate user identifiers including user identifiers of P candidate users 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 set of candidate user identifiers; if the target user identifier is found from the set of candidate user identifiers, return a pre-authorization code to the target user, the pre-authorization code indicating that the target user has registered with the target business software, and the initial verification result includes the pre-authorization code;

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

[0180] The user verification server stores a set of reference user identifiers, which includes the user identifiers of M reference users who have already passed the verification by the software platform, where M is an integer greater than or equal to 1. Optionally, when the above-mentioned computer program product is executed on a data processing device, it is suitable to execute a program with the following initialization method steps:

[0181] A target verification request carrying the pre-authorization code and the target user identifier is sent to the user verification server. The user verification server searches for the target user identifier from a set of reference user identifiers. If the target user identifier is found in the set of reference user identifiers, an authorization interface is displayed to the target user. If the target user grants authorization through the authorization interface, a user authorization code is returned 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 using the user authorization code. The target verification result includes the target login parameters.

[0182] The system receives target login parameters returned by the user verification server in response to the target verification request, wherein the target login parameters are used to indicate that the target user has passed the verification by the software platform.

[0183] The software platform also allocates a software data server, which records user identifiers, business software, and business data. Optionally, when the aforementioned computer program product is executed on a data processing device, it is suitable to execute an initialization program with the following method steps:

[0184] The target user identifier and the target login parameters of the target business software are sent to the software data server, wherein the software data server is configured to, upon receiving the target login parameters, search for the target user identifier and the target business data corresponding to the target business software from the user identifier, business software and business data having the corresponding identifier;

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

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

[0187] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0188] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0189] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work 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 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0190] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function 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] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0193] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0194] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0195] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0196] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for invoking business software, characterized in that, A software platform runs on a software resource server, on which N business software applications are deployed, where N is an integer greater than 1. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record the login parameters used by users when logging into the business software. The method is applied to a target business software among the N business software applications, including: 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; In response to the target service request, if the target service requires business data from the reference service software during execution, a parameter acquisition request corresponding to the reference service software is sent to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. The user verification server is used to verify whether the target user has logged into the reference service software, and when it verifies that the target user has logged into the reference service software, it sends the login parameters used by the target user when logging into the reference service software to the target service software. Receive reference login parameters returned by the user verification server, and obtain reference service data required to execute the target service from the reference service software based on the reference login parameters; The target service is executed based on the reference service data.

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

3. The method according to claim 1, characterized in that, The reference service software is equipped with a target communication interface. The step of obtaining the reference service data required to execute the target service from the reference service software based on the reference login parameters includes: Generate a data acquisition request carrying the reference login parameters, wherein the data acquisition request is used to request the acquisition of business data required to execute the target business from the reference business software; The data acquisition request is sent to the target communication interface, wherein the reference service software is configured to extract the reference login parameters from the data acquisition request; verify whether the reference login parameters are the login parameters used by the target user when logging into the reference service software; if the reference login parameters are verified to be the login parameters used by the target user when logging into the reference service software, return the reference service data to the target service software; if the reference login parameters are verified to be different from the login parameters used by the target user when logging into the reference service software, prevent the return of the reference service data to the target service software. Receive the reference service data returned by the reference service software in response to the data acquisition request.

4. The method according to claim 1, characterized in that, The software platform also allocates a software verification server. Before receiving the target service request initiated by the target user, the method further includes: Detect the login request currently received by the software platform; Upon detecting a target login request initiated by the target user, the software verification server is invoked to perform an initial verification operation on the target user and obtain an initial verification result. The target login request is used to request login to the target business software, and the initial verification operation is used to verify whether the target user has already registered for the target business software. When the initial verification result indicates that the target user has registered the target business software, the user verification server is invoked to perform a target verification operation on the target user to obtain a target verification result. The target verification operation is used to verify whether the target user has passed the verification of the software platform. When the target verification result indicates that the target user has passed the verification of the software platform, 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.

5. The method according to claim 4, characterized in that, The step of calling the software verification server to perform an initial verification operation on the target user and obtaining an initial verification result includes: An initial verification request carrying the 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 set of candidate user identifiers corresponding to the target business software, the set of candidate user identifiers including user identifiers of P candidate users 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 set of candidate user identifiers; if the target user identifier is found from the set of candidate user identifiers, return a pre-authorization code to the target user, the pre-authorization code being used to indicate that the target user has registered with the target business software, and the initial verification result includes the pre-authorization code; Receive the 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 set of reference user identifiers, which includes the user identifiers of M reference users who have already passed the verification by the software platform, where M is an integer greater than or equal to 1. The step of calling the user verification server to perform a target verification operation on the target user and obtaining the target verification result includes: A target verification request carrying the pre-authorization code and the target user identifier is sent to the user verification server. The user verification server searches for the target user identifier from a set of reference user identifiers. If the target user identifier is found in the set of reference user identifiers, an authorization interface is displayed to the target user. If the target user grants authorization through the authorization interface, a user authorization code is returned 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 using the user authorization code. The target verification result includes the target login parameters. The system receives target login parameters returned by the user verification server in response to the target verification request, wherein the target login parameters are used to indicate that the target user has passed the verification by the software platform.

7. The method according to claim 6, characterized in that, The software platform also allocates a software data server, which records user identifiers, business software, and business data. Controlling the target user to log in to the target business software includes: The target user identifier and the target login parameters of the target business software are sent to the software data server, wherein the software data server is configured to, upon receiving the target login parameters, search for the target user identifier and the target business data corresponding to the target business software from the user identifier, business software and business data having the corresponding identifier; Receive the target business data returned by the software data server; Control the target user to log in to the target business software based on the target business data.

8. A device for invoking business software, characterized in that, A software platform runs on a software resource server, on which N business software applications are deployed, where N is an integer greater than 1. The software resource server provides runtime resources for each business software application to run its corresponding business. Each business software application is allowed to access a user verification server, which is configured to record the login parameters used by users when logging into the business software. The device is applied to a target business software among the N business software applications, and the device includes: A receiving module 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; The sending module is used to respond to the target service request. When the target service requires business data from the reference service software during execution, the module sends a parameter acquisition request corresponding to the reference service software to the user verification server. The parameter acquisition request is used to request the login parameters used by the target user when logging into the reference service software. The user verification server is used to verify whether the target user has logged into the reference service software. When it is verified that the target user has logged into the reference service software, the server sends the login parameters used by the target user when logging into the reference service software to the target service software. The acquisition module is used to receive the reference login parameters returned by the user verification server, and to obtain the reference business data required to execute the target business from the reference business software according to the reference login parameters; The execution module is used to execute the target service based on 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, when executed, performs the method of any one of claims 1 to 7.

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

Images