Business data acquisition method and business data display method

Abstract

The invention provides a business data acquisition method and a business data display method. The method comprises the steps that a data request sent by a first account is acquired through a service server in a service operation system, and the data request carries a request type identifier; under the condition that the request type identifier indicates that the data request is a data request initiated by a first account through a service auxiliary system, target authentication information is acquired according to the data request, and the first account is used for executing service auxiliary operation through the service auxiliary system; calling a service auxiliary authentication interface associated with the service auxiliary system, and sending an authentication request to an authentication server matched with the service auxiliary system based on the target authentication information; and under the condition that the authentication result received according to the service auxiliary authentication interface indicates that the data request is an approvable request, returning service data of the second account to the first account. According to the method and the device, the technical problem of relatively low business data acquisition efficiency in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of computers, and more particularly, to a method for obtaining service data and a method for displaying service data. Background Art

[0002] In various Internet applications, in order to provide Internet services to users more efficiently, some service-type accounts can be used to assist user accounts in performing related operations. For example, in an e-commerce application, a customer service account can be used to answer relevant questions of a user account and help the user account perform various information query and information synchronization operations.

[0003] To facilitate providing services to user accounts through customer service accounts, a corresponding client is usually developed for the customer service account and a corresponding server background is deployed. That is to say, in the existing method, a dedicated service page needs to be developed for the customer service account and a corresponding service background needs to be deployed, and relevant service data of the user account can be obtained through the newly developed service page and service background for customer service. It can be seen that the existing method for obtaining relevant service data has the technical problem of low efficiency.

[0004] In view of the above problems, no effective solution has been proposed yet. Summary of the Invention

[0005] Embodiments of the present invention provide a method for obtaining service data and a method for displaying service data, so as to at least solve the technical problem of low efficiency in the existing method for obtaining relevant service data.

[0006] According to one aspect of the embodiments of the present invention, a method for obtaining service data is provided, including: obtaining a data request sent by a first account through a service server in a service operating system, where the service operating system is used to provide service for an object account, the data request is used to obtain service data of a second account, and a request type identifier is carried in the data request; when the request type identifier indicates that the data request is a data request initiated by the first account through a service assistance system, obtaining target authentication information according to the data request, where the first account is used to perform service assistance operations through the service assistance system; calling a service assistance authentication interface associated with the service assistance system, and sending an authentication request to an authentication server matching the service assistance system based on the target authentication information; when the authentication result received according to the service assistance authentication interface indicates that the data request is an allowable request, returning the service data of the second account to the first account.

[0007] According to one aspect of an embodiment of the present invention, a method for displaying business data is provided, comprising: receiving a data request in a target client logged in with a first account, wherein the data request is used to obtain business data of a second account, the first account and the second account have a business auxiliary relationship, and the first account is used to perform business auxiliary operations through the target client matched with a business auxiliary system; in the case where target authentication information is obtained according to an account identifier of the first account, generating a target jump path according to the target authentication information and a request type identifier, wherein the request type identifier is used to indicate that the first account initiates the data request through the business auxiliary system; forwarding the data request to a business server in a business operating system according to the target jump path, wherein the business operating system is used to provide business services for the target account; in the case where the business server determines that the data request is an allowable request according to the target authentication information and the request type identifier, obtaining the business data returned by the business server, and displaying a business operation page matched with the business operating system according to the business data.

[0008] According to another aspect of an embodiment of the present invention, there is also provided a device for acquiring business data, comprising: a first acquisition unit, configured to acquire a data request sent by a first account through a business server in a business operating system, wherein the business operating system is used to provide business services for a target account, the data request is used to acquire business data of a second account, the data request is used to acquire business data of the second account, and the data request carries a request type identifier; a second acquisition unit, configured to acquire target authentication information according to the data request when the request type identifier indicates that the data request is a data request initiated by the first account through a business auxiliary system, wherein the first account is used to perform business auxiliary operations through the business auxiliary system; a calling unit, configured to call a business auxiliary authentication interface associated with the business auxiliary system, and to send an authentication request to an authentication server matched with the business auxiliary system based on the target authentication information; and a sending unit, configured to return the business data of the second account to the first account when the authentication result received through the business auxiliary authentication interface indicates that the data request is an approved request.

[0009] Optionally, the above-mentioned second acquisition unit includes: a first acquisition module, used to obtain the authentication credential from the above-mentioned data request, wherein the above-mentioned authentication credential is used to indicate a reference authentication result of a reference authentication operation performed based on the first account identifier of the above-mentioned first account; a second acquisition module, used to obtain the second account identifier from the above-mentioned data request, wherein the above-mentioned second account identifier is used to indicate the above-mentioned second account in the above-mentioned business auxiliary system; and a determination module, used to determine the above-mentioned authentication credential and the above-mentioned second account identifier as the above-mentioned target authentication information.

[0010] Optionally, the apparatus for obtaining the above service data further includes: a first authentication unit, configured to determine that the data request is not approvable when the authentication result indicates that the authentication credential is not pre-cached in the authentication server; determine that the data request is not approvable when the authentication result indicates that the caching duration of the authentication credential in the authentication server exceeds the effective duration; and determine that the data request is not approvable when the authentication result indicates that there is no service assistance relationship between the first account and the second account, where the service assistance relationship is used to indicate that the service assistance operation is an authorized operation.

[0011] Optionally, the apparatus for obtaining the above service data further includes: a second authentication unit, configured to obtain the account association relationship between the first account and the second account when the authentication result indicates that the authentication information cached in the authentication server matches the authentication credential, where the authentication information includes the pre-cached authentication credential and the effective duration of the authentication credential, and the authentication credential is ciphertext information generated by the authentication server according to the first account identifier and the operation timestamp of the reference authentication operation; and determine that the data request is approvable when the account association relationship between the first account and the second account is a service assistance relationship, where the service assistance relationship is used to indicate that the first account is authorized to perform the service assistance operation for the second account.

[0012] Optionally, the apparatus for obtaining the above service data further includes one of the following: a third obtaining unit, configured to obtain the service data of the second account requested by the service assistance system from the data storage server in the service operation system when the authentication result indicates that the data request is approvable, where the service assistance system is configured to replace the second account identifier in the data request with a third account identifier and send a reference data request to the data storage server according to the third account identifier, the second account identifier is the account identifier indicating the second account in the service assistance system, and the third account identifier is the account identifier indicating the second account in the service operation system; a fourth obtaining unit, configured to request the service data of the second account from the data storage server in the service operation system when the authentication result indicates that the data request is approvable.

[0013] Optionally, the second obtaining unit includes: a third obtaining module, configured to obtain the login indication information carried in the target authentication information; and update the login status of the second account in the service operation system according to the login indication information.

[0014] Optionally, the apparatus for obtaining the above-mentioned service data further includes: a third authentication unit, configured to, when the request type identifier indicates that the data request is a data request initiated by the first account through the service operating system, obtain the account identifier information of the first account according to the data request, where the account identifier information indicates that the first account and the second account are the same object account; obtain the authentication result according to the account identifier information; and when the authentication result indicates that the data request is an approvable request, return the service data of the second account to the first account.

[0015] According to another aspect of the embodiments of the present invention, there is also provided an apparatus for displaying service data, including: a receiving unit, configured to receive a data request in a target client logged in with a first account, where the data request is used to obtain service data of a second account, there is a service assistance relationship between the first account and the second account, and the first account is used to perform service assistance operations through the target client matching the service assistance system; a generating unit, configured to generate a target jump path according to the target authentication information and a request type identifier when the target authentication information is obtained according to the account identifier of the first account, where the request type identifier is used to indicate that the first account initiates the data request through the service assistance system; a forwarding unit, configured to forward the data request to a service server in the service operating system according to the target jump path, where the service operating system is used to provide service for an object account; and a display unit, configured to obtain the service data returned by the service server and display a service operation page matching the service operating system according to the service data when the service server determines that the data request is an approvable request according to the target authentication information and the request type identifier.

[0016] Optionally, the generating unit includes: a first obtaining module, configured to obtain an authentication credential, where the authentication credential is used to indicate a reference authentication result of a reference authentication operation performed according to the first account identifier of the first account; a second obtaining module, configured to obtain a second account identifier, where the second account identifier is used to indicate the second account in the service assistance system; a third obtaining module, configured to obtain a reference jump path for indicating the service server; and a generating module, configured to splice the authentication credential, the second account identifier, and the request type identifier with the reference jump path to obtain the target jump path, where the target authentication information includes the authentication credential and the second account identifier.

[0017] Optionally, the first obtaining module is configured to: send a reference authentication request to the authentication server matched by the service assistance system according to the first account identifier of the first account; when the authentication server performs a reference authentication operation on the first account according to the first account identifier and the authentication is passed, obtain ciphertext information generated by the authentication server according to the first account identifier and the operation timestamp of the reference authentication operation, and the ciphertext information is synchronously cached in the authentication server; determine the ciphertext information as the authentication credential.

[0018] Optionally, the display device of the service data further includes: a third obtaining unit, configured to obtain login indication information, where the target authentication information includes the login indication information, and the login indication information is used to indicate the login status of the second account in the service operating system; splice the target authentication information, the request type identifier and the reference jump path indicating the service server to obtain the target jump path.

[0019] According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, in which a computer program is stored, where the computer program is configured to execute the service data obtaining method or the service data display method when running.

[0020] According to another aspect of the embodiments of the present application, there is provided a computer program product or a computer program, the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the service data obtaining method or the service data display method as described above.

[0021] According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including a memory and a processor, a computer program is stored in the memory, and the processor is configured to execute the service data obtaining method or the service data display method through the computer program.

[0022] In an embodiment of the present invention, a data request sent by a first account is obtained through a business server in a business operation system, where the business operation system is used to provide business services for an object account, the data request is used to obtain business data of a second account, and a request type identifier is carried in the data request; in the case where the request type identifier indicates that the data request is a data request initiated by the first account through a business assistance system, target authentication information is obtained according to the data request, where the first account is used to perform business assistance operations through the business assistance system; a business assistance authentication interface associated with the business assistance system is called, and an authentication request is sent to an authentication server matching the business assistance system based on the target authentication information; in the case where the authentication result received according to the business assistance authentication interface indicates that the data request is an approvable request, the business data of the second account is returned to the first account, thereby realizing the improvement of the efficiency of the first account to obtain the account data of the second account by reusing the background server in the business operation system.

[0023] In the above embodiment, the data acquisition request for the first account to obtain the business data of the second account can be processed by reusing the business server in the business operation system, and the request channel can be identified by the business server in the business operation system, that is, in the case where it is determined that the data acquisition request sent by the first account is triggered by the business assistance system, the authentication of the data acquisition request is realized by calling relevant interfaces, and in the case where the authentication is passed, the business data of the second account is sent to the first account. Thereby, the development of corresponding background processing logic for the business assistance system is avoided, and at the same time, the business data with a unified format can be obtained by reusing the business server in the business operation system. Furthermore, in the case of transmitting relevant data to the first account, the data display method in the business operation system can be reused for page display, thereby avoiding the repeated development of the data display page of the business assistance system and improving the acquisition and display efficiency of business data, and solving the technical problem of low acquisition efficiency of existing business data. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings described herein are used to provide a further understanding of the present invention, and constitute a part of this application. The illustrative embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation to the present invention. In the drawings:

[0025] Figure 1 is a schematic diagram of a hardware environment of an optional method for obtaining business data according to an embodiment of the present invention;

[0026] Figure 2 is a flowchart of an optional method for obtaining business data according to an embodiment of the present invention;

[0027] Figure 3 is a schematic diagram of an optional method for obtaining business data according to an embodiment of the present invention;

[0028] Figure 4 It is a schematic diagram of another optional method for obtaining service data according to an embodiment of the present invention;

[0029] Figure 5 It is a flowchart of an optional method for displaying service data according to an embodiment of the present invention;

[0030] Figure 6 It is a schematic diagram of yet another optional method for obtaining service data according to an embodiment of the present invention;

[0031] Figure 7 It is a schematic diagram of yet another optional method for obtaining service data according to an embodiment of the present invention;

[0032] Figure 8 It is a timing diagram of an optional method for obtaining service data according to an embodiment of the present invention;

[0033] Figure 9 It is a schematic diagram of yet another optional method for obtaining service data according to an embodiment of the present invention;

[0034] Figure 10 It is a schematic diagram of yet another optional method for obtaining service data according to an embodiment of the present invention;

[0035] Figure 11 It is a timing diagram of another optional method for obtaining service data according to an embodiment of the present invention;

[0036] Figure 12 Schematic diagram of the structure of an optional service data acquisition device according to an embodiment of the present invention;

[0037] Figure 13 It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present invention;

[0038] Figure 14 Schematic diagram of the structure of an optional service data display device according to an embodiment of the present invention;

[0039] Figure 15 It is a schematic diagram of the structure of another optional electronic device according to an embodiment of the present invention. Detailed implementation manners

[0040] To enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0041] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present invention described here can be implemented in an order different from those illustrated or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0042] It should be noted that in the relevant embodiments of the present application, the methods for obtaining and displaying various data need to comply with the regulations of various normative documents; in addition, before obtaining and displaying the relevant data of an account, the authorization permission of the corresponding account owner needs to be obtained.

[0043] According to one aspect of the embodiments of the present application, a method for obtaining service data is provided. As an optional implementation manner, the above method for obtaining service data can be but is not limited to being applied to a service data acquisition hardware system such as Figure 1 shown by the terminal device 102, the network 104, the server 106, the database 108, and the server 110. As Figure 1 shown, the terminal device 102 can be connected to the server 106 and the server 110 through the network 104. The above network 104 can include but is not limited to: wired networks, wireless networks, where the wired network includes: local area networks, metropolitan area networks, and wide area networks, and the wireless network includes: Bluetooth, WIFI, and other networks that implement wireless communication.

[0044] The above terminal device 102 may include, but is not limited to, terminal devices such as mobile phones, computers, intelligent voice interaction devices, intelligent household appliances, and in-vehicle terminals. Specifically, the client running on the terminal device corresponding to the above terminal device 102 may be a client that provides auxiliary services for an object account. For example, it may be a customer service client for a target service, which is used to provide auxiliary services for user accounts using the above target service. It can be understood that in the process of providing services through the above customer service client, relevant service data of the corresponding user account needs to be obtained. For example, historical data such as commodity consumption records and application usage records authorized and permitted by the user account. This embodiment can be achieved through, for example, Figure 1 the system shown to obtain the relevant service data of the user account.

[0045] The above terminal device 102 is also provided with a display, a processor, and a memory. The display can be used to display the interaction interface of the above customer service client. The processor can be used to obtain and encode the collected service data; the memory is used to temporarily store the obtained service data.

[0046] It should be noted that the server 106 may be a background server corresponding to the business operating system, and the server 110 may be a background server corresponding to the business assistance system. It can be understood that the above business operating system may correspond to the client used by the user account, and the above business assistance system may correspond to the client used by the customer service account. Furthermore, the server 106 can be used to process relevant operation requests of the user account, and the server 110 can be used to process relevant requests of the customer service account. In this embodiment, the server 106 in the business operating system can be reused to process the data acquisition request of the customer service account for the user account.

[0047] In a specific embodiment, a first account is logged in to the client running on the above terminal device 102. As shown in step S102, a data acquisition request is sent to the server 106 through the network 104. The server 106 executes steps S104 to S110 to obtain the data request sent by the first account through the business server in the business operating system. Among them, the business operating system is used to provide business services for the object account, and the data request is used to obtain the service data of the second account. The data request carries a request type identifier; in the case where the request type identifier indicates that the data request is a data request initiated by the first account through the business assistance system, target authentication information is obtained according to the data request, where the first account is used to perform business assistance operations through the business assistance system; the business assistance authentication interface associated with the business assistance system is called; an authentication request is sent to the server 110 through the network 104, that is, an authentication request is sent to the authentication server matching the business assistance system based on the target authentication information;

[0048] Next, as in step S112, the server 110 returns the authentication result to the server 106 via the network 104;

[0049] As in step S114, when the authentication result indication data request received according to the service-assisted authentication interface indicates an allowable request, the server 106 sends service data to the first account via the network 104;

[0050] Finally, in the terminal device 102, since the service data it receives is directly returned by the service server in the service operating system, therefore, the display page in the service operating system can be reused in the client to display the service data of the second account, that is, step S116 is executed to display the service data of the second account based on the service operating system page.

[0051] The server 106 and the server 110 can be a single server, or a server cluster composed of multiple servers, or a cloud server.

[0052] In the embodiment of the present invention, the data request sent by the first account is obtained through the service server in the service operating system, where the service operating system is used to provide service for the object account, the data request is used to obtain the service data of the second account, and the data request carries a request type identifier; when the request type identifier indicates that the data request is a data request initiated by the first account through the service assistance system, the target authentication information is obtained according to the data request, where the first account is used to perform service assistance operations through the service assistance system; the service-assisted authentication interface associated with the service assistance system is called, and an authentication request is sent to the authentication server matching the service assistance system based on the target authentication information; when the authentication result received according to the service-assisted authentication interface indicates that the data request is an allowable request, the service data of the second account is returned to the first account, thereby improving the efficiency of the first account to obtain the account data of the second account by reusing the background server in the service operating system.

[0053] In the above - mentioned embodiments, the data acquisition request of the first account for obtaining the service data of the second account can be processed by re - using the service server in the service operation system, and the request channel can be identified by the service server in the above - mentioned service operation system. That is, when it is determined that the data acquisition request sent by the first account is triggered through the service assistance system, the authentication of the data acquisition request can be realized by calling relevant interfaces. And when the authentication is passed, the service data of the second account is sent to the first account. Thus, the development of corresponding background processing logic for the service assistance system is avoided. At the same time, by re - using the service server in the service operation system, service data with a unified format can be obtained. Furthermore, when transmitting relevant data to the first account, the data display method of the service operation system can be re - used for page display, thereby avoiding the repeated development of the data display page of the service assistance system, improving the efficiency of obtaining and displaying service data, and solving the technical problem of the low acquisition efficiency of existing service data.

[0054] As an alternative embodiment, as Figure 2 shown, the above - mentioned method for obtaining service data can be applied to a service server in a service operation system, and specifically may include the following steps:

[0055] S202, obtain the data request sent by the first account through the service server in the service operation system, where the service operation system is used to provide service for the object account, the data request is used to obtain the service data of the second account, and the data request carries a request type identifier;

[0056] S204, when the request type identifier indicates that the data request is a data request initiated by the first account through the service assistance system, obtain the target authentication information according to the data request, where the first account is used to perform service assistance operations through the service assistance system;

[0057] S206, call the service assistance authentication interface associated with the service assistance system, and send an authentication request to the authentication server matching the service assistance system based on the target authentication information;

[0058] S208, when the authentication result received according to the service assistance authentication interface indicates that the data request is an allowable request, return the service data of the second account to the first account.

[0059] First of all, it should be noted that in the relevant embodiments of this application, the methods for obtaining and displaying various data need to comply with the regulations of various normative documents; in addition, before obtaining and displaying the relevant data of the account, the authorization permission of the corresponding account entity needs to be obtained.

[0060] Understandably, the business operation system in step S202 and the business assistance system in step S204 above can be two different application systems corresponding to the same type of business service. The above business operation system can be mainly used to handle relevant requests and operations of user accounts, and the above business assistance system can be mainly used to handle relevant requests and operations of auxiliary accounts. It can be understood that the above auxiliary account can be an object account used to provide business assistance services for user accounts.

[0061] For example, when the above business service is an e-commerce service, the above business operation system can be the e-commerce platform system used by e-commerce users, and the above business assistance system can be the e-commerce customer service system used by the customer service objects in the above e-commerce platform. Correspondingly, the above auxiliary account can be the customer service account used by the above customer service objects; another example is that when the above business service is a media resource playback service, the above business operation system can be the media playback system used by media playback website users, and the above business assistance system can be the customer service system used by the customer service objects in the above media playback website. Correspondingly, the above auxiliary account can be the customer service account used by the above customer service objects. The above introduction of the business operation system and the business assistance system is only an example, and the possible combinations of the above business operation system and the business assistance system are not limited in this embodiment.

[0062] Furthermore, in step S202 above, the above first account can be an auxiliary account. In the process of providing services for the second account, it is necessary to obtain and display relevant business data of the second account. For example, when the above business service is an e-commerce service, the above business data can be the historical consumption records of the above second account; when the above business service is a media resource playback service, the above business data can be the historical playback records of the above second account. The specific data content of the above business data is not limited in this embodiment.

[0063] In the above step S204, the business server may determine the request channel of the data request according to the request type identifier carried in the data request. Specifically, it may include at least two request channels. The first channel is the data request initiated by the first account of the above auxiliary type through the above business assistance system, and the second channel may also be the data request initiated by the second account of the user type through the above business operation system. The above first channel may correspond to querying the relevant authorization data of the target user account when the customer service account provides relevant services to the target user account; the above second channel may correspond to querying the historical operation data or historical business data of the target user account itself in the logged-in client. That is to say, in this embodiment, the business server may reuse the processing of data requests related to business data and distinguish data requests sent from different channels according to the request type identifier carried in the data request.

[0064] In the case where it is determined through the above step S204 that the data request is a data request initiated by the first account through the business assistance system, the target authentication information may be further obtained according to the data request. Optionally, when the target authentication information is the relevant information carried in the data request, the method of obtaining the target authentication information may be to directly extract relevant parameters from the request message associated with the request; in another embodiment, it may also be to further request other servers to perform preliminary authentication on the data request and use the authentication result obtained from the preliminary authentication as the target authentication information.

[0065] In a preferred embodiment, when the request type identifier indicates that the data request is a data request initiated by the first account through the business assistance system, obtaining the target authentication information according to the data request includes:

[0066] S1. Obtain an authentication credential from the data request, where the authentication credential is used to indicate the reference authentication result for performing a reference authentication operation according to the first account identifier of the first account;

[0067] S2. Obtain a second account identifier from the data request, where the second account identifier is used to indicate the second account in the business assistance system;

[0068] S3. Determine the authentication credential and the second account identifier as the target authentication information.

[0069] It can be understood that the above target authentication information may specifically include the above authentication certificate and the above second account identifier. The above authentication certificate may be the result obtained by performing a reference authentication operation based on the first account identifier of the first account, and is used to indicate that the above first account is a legitimate account and the above request operation is a legitimate operation; the above second account identifier may be used to determine the matching relationship between the two in combination with the above first account identifier, and further determine whether the above first account has been authorized by the second account.

[0070] It can be understood that after obtaining the above target authentication information, the above authentication operation can be performed by calling the relevant interface through the above step S206. Specifically, the above relevant interface may be a business assistance authentication interface associated with the business assistance system, and an authentication request can be sent to an authentication server matching the business assistance system through the above business assistance authentication interface.

[0071] In this embodiment, since the first account (which may be a customer service account, for example) is an object account matching the business assistance system (which may be a customer service system, for example), the background server related to the business assistance system may store the legality verification information related to the above first account, and store the matching relationship between the above first account and the second account, and determine that the first account is an auxiliary account authorized by the second account. Through the above step S206, the relevant information originally stored in the business assistance system can be used for accurate authentication operations, avoiding the deployment or caching of relevant authentication information in the business operation system and improving the efficiency of the authentication operation.

[0072] Finally, through the above step S208, that is, when it is indicated according to the authentication result received by the business assistance authentication interface that the data request is a permissible request, the business data of the second account is returned to the first account. It should be noted that the above business data may be the relevant data pre-stored in the above business server, or may be the data further requested and obtained from other storage servers by the above business server when it is indicated according to the authentication result received by the business assistance authentication interface that the data request is a permissible request; optionally, the above business data may also be the business data requested and obtained through the relevant background server in the above business assistance system after passing the authentication by the authentication server in the business assistance system. In this embodiment, the acquisition channel of the above business data is not limited.

[0073] In an alternative embodiment, after obtaining the data request sent by the first account through the business server in the business operation system, it further includes:

[0074] S1. When the request type identifier indicates that the data request is a data request initiated by the first account through the business operation system, obtain the account identifier information of the first account according to the data request, where the account identifier information indicates that the first account and the second account are the same object account;

[0075] S2. Obtain the authentication result according to the account identifier information;

[0076] S3. When the authentication result indicates that the data request is an approvable request, return the business data of the second account to the first account.

[0077] It can be understood that in this embodiment, when it is determined according to the above request type identifier by the above business server that the data request is a data request initiated by the first account through the business operation system, it can be determined that the above first account is the object account used by the user object. Furthermore, it can be determined that the above first account and the second account are the same object account by comparing the account identifiers. In other words, in this embodiment, the application scenario corresponding to the above embodiment is that the user account queries the business data of the account itself. In the above embodiment, the business server can be directly used to perform the authentication operation and determine whether to return the business data to the first account according to the authentication result.

[0078] The following will be combined with Figure 3 to specifically describe the above embodiment of the present application.

[0079] As Figure 3 shown, when the first account is an auxiliary account (for example, specifically a service consultant account), the second account is a customer account, and the business data is specifically the account operation record of the second account, the first account can trigger the operation of viewing the operation record of the second account on the business assistance system page. In this embodiment, the display page of the above operation record can be reused, that is, the same data display page as that on the business operation system page is displayed for the first account, that is, step S302 is executed to jump to the business operation system page; for the background server, the data requests triggered through the above business operation system page are uniformly sent to the business operation system authentication gateway (in this embodiment, the above business server is specifically this business operation system authentication gateway).

[0080] The above business operation system authentication gateway executes the processing operation for data acquisition requests from two different channels. For the data acquisition request directly triggered by the second account through the business operation system page, direct authentication is performed, that is, step S304-2 is executed, and the authentication passes. For the data acquisition request triggered by the first account through the business assistance system page, it is sent to the above business operation system authentication gateway through the jump of the above business operation system page, and step S304-1 is executed without authentication. At the same time, an authentication request is sent to the business assistance system authentication gateway through interface call. Finally, after the business assistance system authentication server executes S306, the authentication passes, and the business assistance system data request server executes S308 to provide interface generalization call to request the business data (operation record data) of the second account from the business operation system data storage server.

[0081] As Figure 3 described above, in the way of channel differentiation, the target authentication verification information is jumped from the business assistance system to the business operation system, and the source is identified in the business server of the business operation system and then the authentication is requested from the business assistance system, and then the relevant business data in the background business operation system is requested.

[0082] In the above embodiment, the data acquisition request for the first account to obtain the business data of the second account can be processed by reusing the business server in the business operation system, and the request channel can be identified by the business server in the above business operation system. That is, when it is determined that the data acquisition request sent by the first account is triggered through the business assistance system, the authentication of the data acquisition request is realized by calling relevant interfaces. And when the authentication passes, the business data of the second account is sent to the first account. Thus, the development of corresponding background processing logic for the business assistance system is avoided. At the same time, by reusing the business server in the business operation system, business data with a unified format can be obtained. Furthermore, when the relevant data is transmitted to the first account, the data display method in the business operation system can be reused for page display, and thus the repeated development of the data display page of the business assistance system is avoided, improving the acquisition and display efficiency of business data and solving the technical problem of low acquisition efficiency of existing business data.

[0083] In an optional embodiment, after the above-mentioned call to the business assistance authentication interface associated with the business assistance system and sending an authentication request to the authentication server matching the business assistance system based on the target authentication information, it further includes:

[0084] Case 1: When the authentication result indicates that the authentication credential is not pre-cached in the authentication server, determine that the data request is an inaccurate request;

[0085] Case 2: When the authentication result indicates that the caching duration of the authentication credential in the authentication server exceeds the valid duration, determine that the data request is a non-approve request;

[0086] Case 3: When the authentication result indicates that there is no service assistance relationship between the first account and the second account, determine that the data request is a non-approve request, where the service assistance relationship is used to indicate that the service assistance operation is an authorized operation.

[0087] It should be understood that in the above embodiment, the authentication operation performed by the authentication server based on the target authentication information has at least two types of authentication operations. In the first authentication operation, it is possible to determine whether the data request is approvable based on the above authentication credential; in the second authentication operation, it is possible to determine whether the data request is approvable based on the account association relationship between the first account and the second account. It can be understood that in the above embodiment, when both of the above two authentication operations pass, it can be determined that the above data request is an approvable operation, and when any one of the above two authentication operations fails, it can be determined that the above data acquisition operation is a non-approve operation. In the above embodiment, when the authentication fails, the service server can obtain the above authentication result to determine whether to send service data to the first account.

[0088] More specifically, the above first authentication operation at least needs to determine whether the above authentication credential is cached in the authentication server, and determine whether the received above authentication credential is within the preset validity period.

[0089] The above authentication credential can be the authentication result determined by performing a reference authentication operation based on the first account identifier of the above first account to determine that the above first account is a legal auxiliary account; after performing the reference authentication operation on the above first account, the above authentication credential can be generated in the above authentication server according to relevant information such as the account identifier of the above first account. On the one hand, the above authentication server can return the above authentication credential to the first account, and on the other hand, it can also cache the above authentication credential in the authentication server. Then, in the case where the first account requests the service data of the second account, authentication verification is performed through the authentication credential pre-cached in the above authentication server.

[0090] In an alternative embodiment, the authentication credential may be generated in the authentication server according to the first account identifier of the first account in the service assistance system using a target encryption algorithm, which may include, but is not limited to, digital signature algorithms, symmetric encryption algorithms (one or more of AES, DES, 3DES), asymmetric encryption algorithms (one or more of RSA, DSA, ECC), and linear hashing algorithms (one or more of MD5, SHA1, HMA). The specific generation algorithm of the authentication credential is not limited in this embodiment.

[0091] Optionally, the authentication credential may also be generated according to the target encryption algorithm based on the first account identifier and one or more parameters such as the request timestamp and the valid duration of the reference authentication request.

[0092] In a specific manner, as Figure 4 shown, the authentication credential of the first account may specifically be an authentication ticket, the validity period of which is 1 minute and the length is 32 bits. In addition, the authentication ticket corresponds to the system identifier of the auxiliary account in the service assistance system.

[0093] In an alternative manner, the valid duration of each cached authentication credential may be set in the authentication server, and when the duration after the generation of the authentication credential reaches the corresponding valid duration, the corresponding duration may be deleted from the authentication server, thereby restricting the validity period of the authentication credential. In another alternative embodiment, the valid duration comparison calculation may be performed according to the valid duration information carried in the authentication credential and the request timestamp information corresponding to the reference authentication request, and the validity period of the authentication credential may be restricted by the duration comparison, so as to ensure the data security in the data acquisition process by means of the time-limited authentication verification information of the ticket.

[0094] In an alternative embodiment, before returning the service data of the second account to the first account when the authentication result indicating that the data request received according to the service assistance authentication interface is an allowable request, it further includes:

[0095] S1. When the authentication information cached in the authentication server matches the authentication credential, obtain the account association relationship between the first account and the second account, where the authentication information includes the pre-cached authentication credential and the valid duration of the authentication credential, and the authentication credential is the ciphertext information generated by the authentication server according to the first account identifier and the operation timestamp of the reference authentication operation;

[0096] S2. When the account association relationship between the first account and the second account is a business assistance relationship, determine that the data request is an approvable request, where the business assistance relationship is used to indicate that the first account has been authorized to perform business assistance operations for the second account.

[0097] It can be understood that in this embodiment, the authentication success can be fed back to the business service through the authentication result, thereby triggering subsequent data acquisition and sending operations.

[0098] In another alternative embodiment, when the authentication is passed in the authentication server, the subsequent data acquisition operation can be directly triggered through the authentication server, and the business data returned by the authentication server is used to synchronously indicate the authentication result and the acquired business data.

[0099] Through the above embodiments of the present application, the data security in the process of acquiring business data is improved by means of time-limited authentication verification information of the authentication credential ticket.

[0100] In an alternative embodiment, before returning the business data of the second account to the first account when the authentication result indicates that the data request is an approvable request according to the business assistance authentication interface, one of the following is also included:

[0101] Method 1. When the authentication result indicates that the data request is an approvable request, obtain the business data of the second account requested by the business assistance system from the data storage server in the business operation system, where the business assistance system is used to replace the second account identifier in the data request with a third account identifier and send a reference data request to the business operation system according to the third account identifier. The second account identifier is the account identifier indicating the second account in the data storage server, and the third account identifier is the account identifier indicating the second account in the business operation system.

[0102] Method 2. When the authentication result indicates that the data request is an approvable request, request the business data of the second account from the data storage server in the business operation system.

[0103] It can be understood that in the above embodiments, two methods for acquiring business data are provided. In the first method, when the authentication operation is completed through the above authentication server, the business data can be further requested from the data storage server in the business operation system through the above authentication server; in the second method, when the authentication operation is completed through the above authentication server, the above business data can be requested from the data storage server through the above business server.

[0104] It can be understood that in the above first method, since it is necessary to forward the data acquisition request, it is necessary to correspondingly convert the second account identifier in the business assistance system into a third account identifier, so as to request the account data of the second account from the data storage server in the business operation system according to the third account identifier.

[0105] In an alternative implementation manner, when the request type identifier indicates that the data request is a data request initiated by the first account through the business assistance system, obtaining target authentication information according to the data request includes:

[0106] S1, obtaining the login indication information carried in the target authentication information;

[0107] S2, updating the login status of the second account in the business operation system according to the login indication information.

[0108] It can be understood that in this implementation manner, a status parameter for indicating the login status of the second account can also be carried in the data request. It can be understood that in this implementation manner, since the business data of the second account is obtained through the first account, in order to unify the processing logic in the business operation system, it can be indicated through the above login indication information that there is no need to log in to the second account in the above business operation system; in another implementation manner, the login indication information noNeedLogin can be used to cancel the login of the second account in the business operation system.

[0109] As an alternative implementation manner, as Figure 5 shown, the above method for displaying business data can be applied to a business assistance client, and specifically may include the following steps:

[0110] S502, in a target client logged in with the first account, receiving a data request, where the data request is used to obtain the business data of the second account, there is a business assistance relationship between the first account and the second account, and the first account is used to perform business assistance operations through the target client matching the business assistance system;

[0111] S504, when the target authentication information is obtained according to the account identifier of the first account, generating a target jump path according to the target authentication information and the request type identifier, where the request type identifier is used to indicate that the first account initiates a data request through the business assistance system;

[0112] S506, forwarding the data request to the business server in the business operation system according to the target jump path, where the business operation system is used to provide business services for the object account;

[0113] S508. When the business server determines that the data request is an allowable request based on the target authentication information and the request type identifier, obtain the business data returned by the business server, and display a business operation page that matches the business operating system based on the business data.

[0114] The following further describes the above embodiments with the business assistance client as the execution subject. As shown in Figure 6 Figure (a) of [], a session window between the current first account and the second account is displayed in the business assistance client. It can be understood that the first account can perform instant messaging with the second account through the above session window to assist the second account in performing relevant business operations. A chat input box 601 and a user identification box 602 are displayed in the session window. Information such as the avatar identifier and account level identifier of the second account can be displayed in the user identification box 602. In addition, in response to a trigger operation on the operation record 603 control in the user identification box 602, it can be displayed as shown in Figure 6 Figure (b) of [], in response to Figure 6 a trigger operation on the "March" icon in Figure (b) of [], the above steps S502 to S508 can be triggered, that is, obtain the consumption log of the second account for March, and display the consumption log of the second account for March (as shown in Figure 6 Figure (c) of []). It can be understood that in this embodiment, since the relevant data of the second account can be directly obtained according to the processing operation of the business operating system through the above touch operation, and then the format of the end service consultant perspective data that is the same as the user business system (business operating system) can be output on the current page of the first account, so as to realize the business system page for viewing customer data in the form of the service consultant perspective (that is, the business assistance system).

[0115] In an optional embodiment, when the target authentication information is obtained according to the account identifier of the first account, generating the target jump path according to the target authentication information and the request type identifier includes:

[0116] S1. Obtain an authentication credential, where the authentication credential is used to indicate the reference authentication result of performing a reference authentication operation according to the first account identifier of the first account;

[0117] S2. Obtain a second account identifier, where the second account identifier is used to indicate the second account in the business assistance system;

[0118] S3. Obtain a reference jump path for indicating the authentication server;

[0119] S4. Concatenate the authentication credential, the second account identifier, and the request type identifier with the reference jump path to obtain the target jump path, where the target authentication information includes the authentication credential and the second account identifier.

[0120] Optionally, when obtaining the target authentication information based on the account identifier of the first account, when generating the target jump path according to the target authentication information and the request type identifier, it further includes:

[0121] S1. Obtain the login indication information. Among them, the target authentication information includes the login indication information, and the login indication information is used to indicate the login status of the second account in the business operation system;

[0122] S2. Concatenate the target authentication information, the request type identifier with the reference jump path indicating the authentication server to obtain the target jump path.

[0123] In this embodiment, the target jump path can be obtained by concatenating the reference jump path corresponding to the business operation system and the relevant operation parameters, and then the business operation page is displayed according to the target jump path. As Figure 7 shown, the above-mentioned relevant parameter information may include the authentication ticket parameter, the second account identifier parameter, the request channel identifier parameter, and the original link parameter. The above-mentioned target jump path (complete link) is obtained by concatenating the above four parameters. It should be noted that the above-mentioned jump path can specifically be a URL path.

[0124] For example, for a user, when the reference jump path for displaying the user's monthly operation record is link A, the above-mentioned target jump path can specifically be:

[0125] A / index? ticket=123123&externalUserId=123123&channel=scrm&_noNeedLogin=1, where A / is the original jump path, "ticket=123123" indicates that the authentication credential ticket is "123123", "externalUserId=123123" indicates that the second account identifier is "123123", "channel=scrm" is the request type identifier, indicating that the above data request is a data request initiated by the first account through the business assistance system, and "noNeedLogin" is used to cancel the login of the second account in the business operation system.

[0126] Through the above embodiment, the business operation system page accepts the authentication credential ticket information, the access source, and the account identifier of the user account in the business assistance system that could not be accepted originally in the way of URL parameter passing, and then it is convenient for the business server in the business operation system to obtain the authentication result by passing parameters through the business assistance authentication interface.

[0127] In an optional embodiment, the above-mentioned obtaining the authentication credential includes:

[0128] S1. Send a reference authentication request to the authentication server matched by the service assistance system according to the first account identifier of the first account.

[0129] S2. When the authentication server performs a reference authentication operation on the first account according to the first account identifier and the authentication is passed, obtain the ciphertext information generated by the authentication server according to the first account identifier and the operation timestamp of the reference authentication operation. The ciphertext information is synchronously cached in the authentication server.

[0130] S3. Determine the ciphertext information as the authentication credential.

[0131] It can be understood that in this embodiment, the above method for obtaining the authentication credential may be to send a reference authentication request to the authentication server matched by the service assistance system according to the target client, and obtain the corresponding authentication credential according to the reference authentication request.

[0132] The following is combined with Figure 8 to illustrate a complete embodiment of this application.

[0133] In this embodiment, the main bodies for interaction include: the front end (i.e., a specific target client), the service operation system gateway (i.e., a specific service server in the above service operation system), the service assistance system gateway, the service assistance system authentication server, and the service operation system storage server (i.e., a specific data storage server in the service operation system). It should be noted that in this embodiment, the above service assistance system at least includes the service assistance system gateway and the service assistance system authentication server.

[0134] First, in the target client logged in with the first account (auxiliary account), execute S802 to display the service assistance system page; then, in response to the trigger operation of the function control related to the service data of the second account, execute S804 to receive the user data display request.

[0135] Next, S806. The front end sends a reference authentication request to the service assistance system gateway.

[0136] The service assistance system gateway executes S808 to forward the reference authentication request.

[0137] After receiving the reference authentication request, the service assistance system authentication server, S810, returns the reference authentication result. It can be understood that in this embodiment, the above reference authentication request is used to perform account authentication according to the first account identifier of the first account.

[0138] Next, the service assistance system gateway executes S812 to request the target authentication information.

[0139] The authentication server of the service assistance system executes S814 and S816, generates target authentication information, caches it, sets the valid duration, and returns the target authentication information.

[0140] The gateway of the service assistance system executes S818 and returns the target authentication information to the front end.

[0141] The front end executes S820, splices the target jump link according to the target authentication information, and requests the target page and business data according to the target jump link.

[0142] Next, the front end executes S822 and requests the target page and business data from the business operation system gateway.

[0143] The gateway of the business operation system executes S824, does not perform authentication, and forwards the data acquisition request.

[0144] After receiving the data acquisition request, the gateway of the service assistance system executes S826 and requests to perform authentication according to the target authentication information. It can be understood that in this embodiment, the authentication operation includes the first authentication and the second authentication.

[0145] The authentication server of the service assistance system executes S828 to check whether the target authentication information is included in the server cache, and executes S830 to return the first authentication result.

[0146] The gateway of the service assistance system executes S832 and requests to perform authentication according to the account identifier.

[0147] The authentication server S834 of the service assistance system checks the account association relationship between the first account and the second account, and executes S836 to return the second authentication result.

[0148] Next, after the authentication is passed, the authentication server of the service assistance system executes S838 and requests business data from the business operation system storage server.

[0149] The operating system storage server executes S840 and returns the business data to the authentication server of the service assistance system and the gateway of the service assistance system.

[0150] The gateway of the service assistance system executes S842 and returns the business data to the gateway of the business operation system.

[0151] The gateway of the business operation system executes S844 and returns the business data to the front end.

[0152] Finally, the front end executes S846 and renders the business display page in the business operation system according to the business data.

[0153] The following is a further description in conjunction with Figure 9 For the above embodiments, as Figure 9As shown in the figure, in this embodiment, the request channel can be determined as the business assistance system or the business operation system based on the parameter information carried by the URL link. If the request channel of the data acquisition request is the business assistance system, then it is logged in without password in the business operation system; if the request channel of the data acquisition request is the business operation system, then the normal data acquisition logic (business logic) is executed in the business operation system.

[0154] During the background interface request process, the corresponding interface to be called is also determined according to the request channel of the data acquisition request. When the request channel is the business assistance system, the interface proxy center is called by passing parameters, that is, the relevant servers in the business assistance system perform complete verification operations. When the request channel is the business operation system, the verification operation is directly performed, and the background interface is requested to obtain relevant business data. It should be noted that the authentication operation and the data acquisition operation can be implemented through one address of the interface proxy center.

[0155] During the above process of calling the proxy center interface, as Figure 10 shown, the routing parameters carried are the request parameters of the original interface, rpc_service_name and rpc_method_name are the original URLs, and the URL is input as a parameter of the proxy center; in addition, the authentication ticket and the second account identifier also need to be used as the request header, thus constituting the call function of the interface proxy center.

[0156] The following will combine Figure 11 to describe another embodiment of the present application. In this embodiment, the business assistance system may further include a business assistance system gateway, an account authentication server, an operation authentication server, and an interface call server. The specific steps may be as follows:

[0157] On the first page of the target client, S1102 and S1104 are executed to display the business assistance system page; a request is made to display the user monthly report;

[0158] Through the first page, S1106 is executed to request the target authentication information from the business assistance system gateway; specifically including: S1108, the business assistance system gateway requests account authentication; the account authentication server executes S1110 and returns the account authentication result; S1112, the business assistance system gateway requests the target authentication information; S1114, the operation authentication server generates the target authentication information, writes it into the server cache, and sets the valid duration; and S1116 is executed to return the target authentication information; the business assistance system gateway executes S1118 to return the target authentication information;

[0159] Next, execute S1120 to generate a target jump link. For example, parameters can be passed through parameter splicing on the original url link, carrying authentication credential ticket information, channel information, and the second account identifier information of the second account in the business assistance system. In the first page, execute S1122 to request data and the target page from the business operation system gateway according to the target jump link.

[0160] In the second page, execute S1124 to send an authentication request carrying the target authentication information.

[0161] The business operation system gateway executes S1126 to directly forward the authentication request without authentication.

[0162] The business assistance system gateway executes S1128 to request authentication. The operation authentication server executes S1130 to check whether the target authentication information exists in the cache, and executes S1132 to return the authentication result. The business assistance system gateway continues to execute S1134 to request business data. The account authentication server executes S1136 to find the account association relationship, and executes S1138 to complete the request information. Then execute S1140 to forward the data acquisition request through the interface call server. The interface call server obtains business data from the business data storage server through generalization call and executes S1142 to return the business data. Then, as in S1144 to S1148, return the business data to the second page.

[0163] In the above embodiments, data calls can be made through interfaces such as rpc_service_name and rpc_method_name. The proxy center in the business assistance system in the background will request each interface to the data storage server in the business operation system. Since it is a request between the backgrounds, there is no need for the C-end user to re-authenticate during this operation process.

[0164] The interfaces of each business system of the business operation system can be directly accessed in the proxy center of the business assistance system, or manual registration and addition of access can be performed using a blacklist or whitelist.

[0165] During the authentication process, it is also necessary to determine whether the auxiliary account can view the relevant information of the current customer, that is, to determine whether they have an associated subordinate relationship. That is to say, during the authentication process, the proxy center of the business assistance system (i.e., the server related to authentication) with a fixed link can be accessed through the front end. The proxy center first checks whether the ticket has expired, whether the first account corresponding to the ticket is related to the second account identifier of the C-end customer. After passing the verification, the second account identifier is converted into the third account identifier in the C-end business system of the customer, and then the information of the customer is accessed.

[0166] Finally, execute S1150 for page rendering.

[0167] It can be understood that in the above embodiments, by generating time-limited ticket authentication verification information, the authentication verification information is redirected from the B-side service consultant system to the C-side customer business system. The C-side business system identifies the source and requests the B-side service consultant system for authentication and service relationship verification, and then requests the background core business system. The data in the format of the B-side service consultant's perspective that is identical to the C-side business system is output, so as to realize the C-side business system page for viewing C-side customer data from the perspective of the B-side service consultant.

[0168] In the above embodiments, the security of customer data is ensured by means of time-limited authentication verification information of tickets; the C-side business system page receives ticket information, access sources, and the IDs of customers in the B-side business system that could not be recognized originally through URL parameter passing; the C-side business system page requests the B-side authentication proxy forwarding center located in the C-side business system through channel differentiation; through the front-end interface proxy, the background interface differentiates requests according to channels and carries additional channel parameters, thereby improving the efficiency of business data acquisition and business data display.

[0169] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0170] According to another aspect of the embodiments of the present invention, there is also provided a business data acquisition device for implementing the above business data acquisition method. As Figure 12 shown, the device includes:

[0171] A first acquisition unit 1202, configured to acquire a data request sent by a first account through a business server in a business operation system, where the business operation system is used to provide business services for an object account, the data request is used to acquire business data of a second account, and a request type identifier is carried in the data request;

[0172] A second acquisition unit 1204, configured to acquire target authentication information according to the data request when the request type identifier indicates that the data request is a data request initiated by the first account through a business assistance system, where the first account is used to perform business assistance operations through the business assistance system;

[0173] A calling unit 1206, configured to call a service assistance authentication interface associated with the above service assistance system, and send an authentication request to an authentication server matching the above service assistance system based on the above target authentication information;

[0174] A sending unit 1208, configured to return the above service data of the second account to the above first account when the authentication result received according to the above service assistance authentication interface indicates that the above data request is an approvable request.

[0175] Optionally, the above second obtaining unit 1204 includes: a first obtaining module, configured to obtain an authentication credential from the above data request, where the authentication credential is used to indicate a reference authentication result for performing a reference authentication operation according to the first account identifier of the above first account; a second obtaining module, configured to obtain a second account identifier from the above data request, where the second account identifier is used to indicate the above second account in the above service assistance system; and a determining module, configured to determine the above authentication credential and the above second account identifier as the above target authentication information.

[0176] Optionally, the above service data obtaining device further includes: a first authentication unit, configured to determine that the above data request is a non - approvable request when the authentication result indicates that the authentication credential is not pre - cached in the above authentication server; determine that the above data request is a non - approvable request when the authentication result indicates that the caching duration of the authentication credential in the above authentication server exceeds the effective duration; and determine that the above data request is a non - approvable request when the authentication result indicates that there is no service assistance relationship between the above first account and the above second account, where the service assistance relationship is used to indicate that the above service assistance operation is an authorized operation.

[0177] Optionally, the above service data obtaining device further includes: a second authentication unit, configured to obtain an account association relationship between the above first account and the above second account when the authentication result indicates that the authentication information cached in the above authentication server matches the above authentication credential, where the authentication information includes the pre - cached above authentication credential and the effective duration of the authentication credential, and the authentication credential is a ciphertext information generated by the above authentication server according to the above first account identifier and the operation timestamp of the above reference authentication operation; and determine that the above data request is an approvable request when the account association relationship between the above first account and the above second account is a service assistance relationship, where the service assistance relationship is used to indicate that the above first account is authorized to perform the above service assistance operation for the above second account.

[0178] Optionally, the apparatus for obtaining the foregoing service data further includes one of the following: a third obtaining unit, configured to obtain the service data of the second account requested by the service assistance system from the service operating system when the authentication result indicates that the data request is an allowable request, where the service assistance system is configured to replace the second account identifier in the data request with a third account identifier and send a reference data request to the service operating system according to the third account identifier, the second account identifier is an account identifier indicating the second account in the service assistance system, and the third account identifier is an account identifier indicating the second account in the service operating system; a fourth obtaining unit, configured to request the service data of the second account from the service operating system when the authentication result indicates that the data request is an allowable request.

[0179] Optionally, the second obtaining unit 1204 includes: a third obtaining module, configured to obtain the login indication information carried in the target authentication information; and update the login status of the second account in the service operating system according to the login indication information.

[0180] Optionally, the apparatus for obtaining the service data further includes: a third authentication unit, configured to obtain the account identifier information of the first account according to the data request when the request type identifier indicates that the data request is a data request initiated by the first account through the service operating system, where the account identifier information indicates that the first account and the second account are the same object account; obtain the authentication result according to the account identifier information; and return the service data of the second account to the first account when the authentication result indicates that the data request is an allowable request.

[0181] Optionally, in this embodiment, for the embodiments to be implemented by the foregoing respective unit modules, reference may be made to the foregoing respective method embodiments, which will not be elaborated herein.

[0182] According to another aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the foregoing method for obtaining service data. The electronic device may be Figure 13 the terminal device or server shown in the figure. This embodiment takes the electronic device as the terminal device as an example for illustration. As Figure 13 shown in the figure, the electronic device includes a memory 1302 and a processor 1304. A computer program is stored in the memory 1302, and the processor 1304 is configured to execute the steps in any of the foregoing method embodiments through the computer program.

[0183] Optionally, in this embodiment, the foregoing electronic device may be at least one of multiple network devices in a computer network.

[0184] Optionally, in this embodiment, the above-mentioned processor may be set to execute the following steps through a computer program:

[0185] S1. Obtain a data request sent by a first account through a business server in a business operation system. Herein, the above-mentioned business operation system is used to provide business services for an object account, and the data request is used to obtain business data of a second account. The data request carries a request type identifier.

[0186] S2. When the request type identifier indicates that the data request is a data request initiated by the first account through a business assistance system, obtain target authentication information according to the data request. Herein, the first account is used to perform business assistance operations through the business assistance system.

[0187] S3. Invoke a business assistance authentication interface associated with the business assistance system, and send an authentication request to an authentication server matching the business assistance system based on the target authentication information.

[0188] S4. When the authentication result received according to the business assistance authentication interface indicates that the data request is an approvable request, return the business data of the second account to the first account.

[0189] Optionally, those of ordinary skill in the art can understand that Figure 13 The structure shown is only schematic. The electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a handheld computer, and terminal devices such as Mobile Internet Devices (MID) and PAD. Figure 13 It does not limit the structure of the above-mentioned electronic device. For example, the electronic device may further include more or fewer components (such as a network interface, etc.) than those shown Figure 13 in the figure, or have a different configuration from that shown Figure 13 in the figure.

[0190] Among them, the memory 1302 can be used to store software programs and modules, such as the program instructions / modules corresponding to the method and device for obtaining service data in the embodiments of the present invention. The processor 1304 executes various functional applications and the acquisition of service data by running the software programs and modules stored in the memory 1302, that is, implements the above-mentioned method for obtaining service data. The memory 1302 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 1302 may further include a memory remotely disposed relative to the processor 1304, and these remote memories can be connected to the terminal through a network. Examples of the above network include but are not limited to the Internet, enterprise intranet, local area network, mobile communication network, and combinations thereof. Among them, the memory 1302 can specifically but not limitedly be used to store various elements in the scene picture, data acquisition information, and other information. As an example, as Figure 13 shown, the above-mentioned memory 1302 may include, but not limited to, the first acquisition unit 1202, the second acquisition unit 1204, the invocation unit 1206, and the sending unit 1208 in the above-mentioned device for obtaining service data. In addition, it may also include, but not limited to, other module units in the above-mentioned device for obtaining service data, which will not be elaborated in this example.

[0191] Optionally, the above-mentioned transmission device 1306 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wired network and a wireless network. In one instance, the transmission device 1306 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers through a network cable, thereby enabling communication with the Internet or a local area network. In one instance, the transmission device 1306 is a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0192] In addition, the above-mentioned electronic device further includes: a display 1308, which is used to display the virtual scene in the interface; and a connection bus 1310, which is used to connect each module component in the above-mentioned electronic device.

[0193] In other embodiments, the above-mentioned terminal device or server may be a node in a distributed system. Among them, the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting multiple nodes through network communication. Among them, the nodes can form a peer-to-peer (Peer To Peer) network, and any form of computing device, such as a server, a terminal, and other electronic devices, can become a node in the blockchain system by joining the peer-to-peer network.

[0194] According to one aspect of the present application, a computer program product is provided. The computer program product includes a computer program / instructions, and the computer program / instructions contain program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication part, and / or installed from a removable medium. When the computer program is executed by a central processing unit, various functions provided by the embodiments of the present application are executed.

[0195] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0196] According to one aspect of the present application, a computer-readable storage medium is provided. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method for obtaining the above business data.

[0197] Optionally, in this embodiment, the above computer-readable storage medium may be set to store a computer program for executing the following steps:

[0198] S1. Obtain a data request sent by a first account through a business server in a business operation system, where the business operation system is used to provide business services for an object account, the data request is used to obtain business data of a second account, the data request is used to obtain business data of the second account, and a request type identifier is carried in the data request;

[0199] S2. When the request type identifier indicates that the data request is a data request initiated by the first account through a business assistance system, obtain target authentication information according to the data request, where the first account is used to perform business assistance operations through the business assistance system;

[0200] S3. Invoke a business assistance authentication interface associated with the business assistance system, and send an authentication request to an authentication server matching the business assistance system based on the target authentication information;

[0201] S4. When the authentication result received according to the business assistance authentication interface indicates that the data request is an approvable request, return the business data of the second account to the first account.

[0202] According to another aspect of the embodiments of the present invention, a display device for business data for implementing the above method for displaying business data is further provided. As Figure 14 shown, the device includes:

[0203] The receiving unit 1402 is configured to receive a data request in a target client logged in with a first account, wherein the data request is used to obtain business data of a second account, there is a business assistance relationship between the first account and the second account, and the first account is used to perform a business assistance operation through the target client matched with the business assistance system;

[0204] The generating unit 1404 is configured to generate a target jump path according to the target authentication information and a request type identifier when the target authentication information is obtained according to the account identifier of the first account, wherein the request type identifier is used to indicate that the first account initiates the data request through the business auxiliary system;

[0205] A forwarding unit 1406, configured to forward the data request to a service server in a service operating system according to the target jump path, wherein the service operating system is configured to obtain the service data of the second account;

[0206] Display unit 1408 is used to obtain the business data returned by the business operating system when the business operating system determines that the data request is an approved request based on the target authentication information and the request type identifier, and display a business operation page matching the business operating system based on the business data.

[0207] Optionally, the generation unit includes: a first acquisition module, used to acquire an authentication credential, wherein the authentication credential is used to indicate a reference authentication result of a reference authentication operation performed based on the first account identifier of the first account; a second acquisition module, used to acquire a second account identifier, wherein the second account identifier is used to indicate the second account in the business auxiliary system; a third acquisition module, used to acquire a reference jump path indicating the business server; and a generation module, used to concatenate the authentication credential, the second account identifier and the request type identifier with the reference jump path to obtain the target jump path, wherein the target authentication information includes the authentication credential and the second account identifier.

[0208] Optionally, the above-mentioned first acquisition module is used to: send a reference authentication request to the authentication server matched by the above-mentioned business auxiliary system according to the above-mentioned first account identifier of the above-mentioned first account; when the above-mentioned authentication server performs a reference authentication operation on the above-mentioned first account according to the above-mentioned first account identifier and the authentication is passed, obtain the ciphertext information generated by the above-mentioned authentication server according to the above-mentioned first account identifier and the operation timestamp of the above-mentioned reference authentication operation, and synchronously cache the above-mentioned ciphertext information in the above-mentioned authentication server; and determine the above-mentioned ciphertext information as the above-mentioned authentication credential.

[0209] Optionally, the display device of the above-mentioned business data also includes: a third acquisition unit, used to obtain login indication information, wherein the above-mentioned target authentication information includes the above-mentioned login indication information, and the above-mentioned login indication information is used to indicate the login status of the above-mentioned second account in the above-mentioned business operating system; the above-mentioned target authentication information, the above-mentioned request type identifier and the reference jump path indicating the above-mentioned business server are spliced ​​to obtain the above-mentioned target jump path.

[0210] According to another aspect of the embodiment of the present invention, an electronic device for implementing the above-mentioned method for displaying business data is also provided. The electronic device may be Figure 15 The terminal device or server shown in the figure. This embodiment is described by taking the electronic device as a terminal device as an example. Figure 15 As shown, the electronic device includes a memory 1502 and a processor 1504. The memory 1502 stores a computer program, and the processor 1504 is configured to execute the steps in any of the above method embodiments through the computer program.

[0211] Optionally, in this embodiment, the electronic device may be located in at least one network device among a plurality of network devices of a computer network.

[0212] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0213] S1, receiving a data request in a target client logged in with a first account, wherein the data request is used to obtain business data of a second account, there is a business assistance relationship between the first account and the second account, and the first account is used to perform a business assistance operation through the target client matched with a business assistance system;

[0214] S2, when the target authentication information is obtained according to the account identifier of the first account, generating a target jump path according to the target authentication information and the request type identifier, wherein the request type identifier is used to indicate that the first account initiates the data request through the business auxiliary system;

[0215] S3, forwarding the data request to a business server in a business operating system according to the target jump path, wherein the business operating system is used to obtain the business data of the second account;

[0216] S4, when the business operating system determines that the data request is an approved request based on the target authentication information and the request type identifier, obtains the business data returned by the business operating system, and displays a business operation page matching the business operating system based on the business data.

[0217] Optionally, those of ordinary skill in the art can understand that Figure 15 The structure shown is only illustrative, and the electronic device can also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a personal digital assistant, and terminal devices such as Mobile Internet Devices (MID), PAD, etc. Figure 15 It does not limit the structure of the above-mentioned electronic device. For example, the electronic device may further include more or fewer components (such as a network interface, etc.) than those shown Figure 15 in, or have a different configuration from that shown Figure 15 in.

[0218] Among them, the memory 1502 can be used to store software programs and modules, such as the program instructions / modules corresponding to the display method and device of service data in the embodiments of the present invention. The processor 1504 executes various functional applications and the display of service data by running the software programs and modules stored in the memory 1502, that is, implements the above-mentioned display method of service data. The memory 1502 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 1502 may further include a memory remotely provided with respect to the processor 1504, and these remote memories can be connected to the terminal through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof. Among them, the memory 1502 can specifically but not limitedly be used to store various elements in the scene picture, data acquisition information, etc. As an example, as Figure 15 shown, the above memory 1502 may but not limitedly include the receiving unit 1402, the generating unit 1404, the forwarding unit 1406, and the display unit 1408 in the above display device of service data. In addition, it may also include but not limited to other module units in the above display device of service data, which will not be elaborated in this example.

[0219] Optionally, the above transmission device 1506 is used to receive or send data via a network. Specific examples of the above network may include a wired network and a wireless network. In one instance, the transmission device 1506 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers through a network cable so as to communicate with the Internet or a local area network. In one instance, the transmission device 1506 is a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0220] In addition, the electronic device further includes: a display 1508 for displaying a virtual scene in an interface; and a connection bus 1510 for connecting various module components in the electronic device.

[0221] In other embodiments, the terminal device or server may be a node in a distributed system, wherein the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the multiple nodes in the form of network communication. Among them, a peer-to-peer network may be formed between the nodes, and any form of computing device, such as a server, a terminal or other electronic device, may become a node in the blockchain system by joining the peer-to-peer network.

[0222] According to one aspect of the present application, a computer program product is provided, the computer program product comprising a computer program / instruction, the computer program / instruction comprising a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication part, and / or installed from a removable medium. When the computer program is executed by a central processing unit, various functions provided by the embodiments of the present application are executed.

[0223] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0224] According to one aspect of the present application, a computer-readable storage medium is provided, and a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above-mentioned method for displaying business data.

[0225] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0226] S1, receiving a data request in a target client logged in with a first account, wherein the data request is used to obtain business data of a second account, there is a business assistance relationship between the first account and the second account, and the first account is used to perform a business assistance operation through the target client matched with a business assistance system;

[0227] S2, when the target authentication information is obtained according to the account identifier of the first account, generating a target jump path according to the target authentication information and the request type identifier, wherein the request type identifier is used to indicate that the first account initiates the data request through the business auxiliary system;

[0228] S3. Forward the above data request to the business server in the business operation system according to the above target jump path, where the business operation system is used to obtain the business data of the second account;

[0229] S4. When the business operation system determines that the data request is an approvable request according to the above target authentication information and the above request type identifier, obtain the above business data returned by the business operation system, and display a business operation page matching the business operation system according to the above business data.

[0230] Optionally, in this embodiment, those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the relevant hardware of the terminal device through a program, and the program can be stored in a computer-readable storage medium. The storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc, etc.

[0231] If the integrated unit in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in the above computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in the storage medium and includes several instructions for causing one or more computer devices (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the above methods in various embodiments of the present invention.

[0232] In the above embodiments of the present invention, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0233] In several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the above unit division is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces. The indirect coupling or communication connection of units or modules can be in an electrical or other form.

[0234] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or may be distributed over multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0235] In addition, each functional unit in various embodiments of the present invention may be integrated in a processing unit, may exist separately as individual physical units, or two or more units may be integrated in one unit. The above-mentioned integrated units may be implemented in the form of hardware or in the form of software functional units.

[0236] The above are only the preferred embodiments of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present invention.

Claims

1. A method for obtaining service data, characterized in that, Including: Obtaining a data request sent by a first account through a business server in a business operation system, where the business operation system is used to provide business services for an object account, the data request is used to obtain business data of a second account, and a request type identifier is carried in the data request; When the request type identifier indicates that the data request is a data request initiated by the first account through a business assistance system, obtaining target authentication information according to the data request, where the first account is used to perform business assistance operations through the business assistance system; Invoking a business assistance authentication interface associated with the business assistance system, and sending an authentication request to an authentication server matching the business assistance system based on the target authentication information; When the authentication result received according to the business assistance authentication interface indicates that the data request is an approvable request, returning the business data of the second account to the first account.

2. The method according to claim 1, characterized in that The step of, when the request type identifier indicates that the data request is a data request initiated by the first account through a business assistance system, obtaining target authentication information according to the data request includes: Obtaining an authentication credential from the data request, where the authentication credential is used to indicate a reference authentication result for performing a reference authentication operation according to a first account identifier of the first account; Obtaining a second account identifier from the data request, where the second account identifier is used to indicate the second account in the business assistance system; Determining the authentication credential and the second account identifier as the target authentication information.

3. The method according to claim 2, characterized in that After the step of invoking a business assistance authentication interface associated with the business assistance system and sending an authentication request to an authentication server matching the business assistance system based on the target authentication information, further including: When the authentication result indicates that the authentication credential is not pre-cached in the authentication server, determining that the data request is a non-approvable request; When the authentication result indicates that a caching duration of the authentication credential cached in the authentication server exceeds an effective duration, determining that the data request is a non-approvable request; When the authentication result indicates that there is no business assistance relationship between the first account and the second account, determining that the data request is a non-approvable request, where the business assistance relationship is used to indicate that the business assistance operation is an authorized operation.

4. The method according to claim 2, wherein Before the step of, when the authentication result received according to the business assistance authentication interface indicates that the data request is an approvable request, returning the business data of the second account to the first account, further including: When the authentication result indicates that authentication information cached in the authentication server matches the authentication credential, obtaining an account association relationship between the first account and the second account, where the authentication information includes the pre-cached authentication credential and an effective duration of the authentication credential, and the authentication credential is a ciphertext information generated by the authentication server according to the first account identifier and an operation timestamp of the reference authentication operation; When the account association relationship between the first account and the second account is a service assistance relationship, determine that the data request is an approvable request, where the service assistance relationship is used to indicate that the first account has been authorized to perform the service assistance operation for the second account.

5. The method according to claim 2, wherein Before returning the service data of the second account to the first account when the authentication result received according to the service assistance authentication interface indicates that the data request is an approvable request, it further includes one of the following: When the authentication result indicates that the data request is an approvable request, obtain the service data of the second account requested by the service assistance system from the data storage server in the service operation system, where the service assistance system is used to replace the second account identifier in the data request with a third account identifier and send a reference data request to the data storage server according to the third account identifier, the second account identifier is the account identifier indicating the second account in the service assistance system, and the third account identifier is the account identifier indicating the second account in the service operation system; When the authentication result indicates that the data request is an approvable request, request the service data of the second account from the data storage server in the service operation system.

6. The method according to claim 1, characterized in that, When the request type identifier indicates that the data request is a data request initiated by the first account through the service assistance system, obtaining target authentication information according to the data request includes: Obtain the login indication information carried in the target authentication information; Update the login status of the second account in the service operation system according to the login indication information.

7. The method according to claim 1, characterized in that, After obtaining the data request sent by the first account through the service server in the service operation system, it further includes: When the request type identifier indicates that the data request is a data request initiated by the first account through the service operation system, obtain the account identifier information of the first account according to the data request, where the account identifier information indicates that the first account and the second account are the same object account; Obtain the authentication result according to the account identifier information; When the authentication result indicates that the data request is an approvable request, return the service data of the second account to the first account.

8. A method for displaying service data, characterized in that, It includes: Receive a data request in the target client logged in with the first account, where the data request is used to obtain the service data of the second account, there is a service assistance relationship between the first account and the second account, and the first account is used to perform service assistance operations through the target client matching the service assistance system; When the target authentication information is obtained according to the account identifier of the first account, generate a target jump path according to the target authentication information and the request type identifier, where the request type identifier is used to indicate that the first account initiates the data request through the service assistance system. Forward the data request to the business server in the business operation system according to the target jump path, where the business operation system is used to provide business services for the object account; When the business server determines that the data request is an allowable request according to the target authentication information and the request type identifier, obtain the business data returned by the business server, and display a business operation page matching the business operation system according to the business data.

9. The method according to claim 8, wherein The generating the target jump path according to the target authentication information and the request type identifier when obtaining the target authentication information according to the account identifier of the first account includes: Obtain an authentication credential, where the authentication credential is used to indicate a reference authentication result of performing a reference authentication operation according to the first account identifier of the first account; Obtain a second account identifier, where the second account identifier is used to indicate the second account in the business assistance system; Obtain a reference jump path for indicating the business server; Concatenate the authentication credential, the second account identifier, and the request type identifier with the reference jump path to obtain the target jump path, where the target authentication information includes the authentication credential and the second account identifier.

10. The method according to claim 9, wherein The obtaining the authentication credential includes: Send a reference authentication request to the authentication server matching the business assistance system according to the first account identifier of the first account; When the authentication server performs a reference authentication operation on the first account according to the first account identifier and the authentication is passed, obtain the ciphertext information generated by the authentication server according to the first account identifier and the operation timestamp of the reference authentication operation, and the ciphertext information is synchronously cached in the authentication server; Determine the ciphertext information as the authentication credential.

11. The method according to claim 8, wherein When generating the target jump path according to the target authentication information and the request type identifier when obtaining the target authentication information according to the account identifier of the first account, it further includes: Obtain login indication information, where the target authentication information includes the login indication information, and the login indication information is used to indicate the login status of the second account in the business operation system; Concatenate the target authentication information, the request type identifier with the reference jump path indicating the business server to obtain the target jump path.

12. A method for obtaining service data, characterized in that, Includes: A first obtaining unit, configured to obtain a data request sent by a first account through a business server in a business operation system, where the business operation system is used to provide business services for an object account, the data request is used to obtain business data of a second account, the data request is used to obtain business data of the second account, and the data request carries a request type identifier; A second obtaining unit, configured to obtain target authentication information according to the data request when the request type identifier indicates that the data request is a data request initiated by the first account through a business assistance system, where the first account is used to perform business assistance operations through the business assistance system; A calling unit, configured to call a business assistance authentication interface associated with the business assistance system, and send an authentication request to an authentication server matching the business assistance system based on the target authentication information; A sending unit is used to return the service data of the second account to the first account when the authentication result received by the service auxiliary authentication interface indicates that the data request is an approved request.

13. A display device for service data, characterized in that, include: A receiving unit, configured to receive a data request in a target client logged in with a first account, wherein the data request is used to obtain business data of a second account, a business assistance relationship exists between the first account and the second account, and the first account is used to perform a business assistance operation through the target client matched with a business assistance system; a generating unit, configured to generate a target jump path according to the target authentication information and a request type identifier when the target authentication information is acquired according to the account identifier of the first account, wherein the request type identifier is used to indicate that the first account initiates the data request through the business auxiliary system; a forwarding unit, configured to forward the data request to a business server in a business operating system according to the target jump path, wherein the business operating system is configured to provide business services for the target account; A display unit is used to obtain the business data returned by the business server when the business server determines that the data request is an allowable request based on the target authentication information and the request type identifier, and to display a business operation page matching the business operating system based on the business data.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program executes the method described in any one of claims 1 to 7 or 8 to 11 when executed.

15. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, the steps of the method described in any one of claims 1 to 7 or 8 to 11 are implemented.

16. An electronic device, comprising a memory and a processor, characterized in that, A computer program is stored in the memory, and the processor is configured to execute the method described in any one of claims 1 to 7 or 8 to 11 through the computer program.

Images